FATAL: kernel too old

[MarkWang0304]

KERNEL=/home/mark/Git/yocto-y2038/poky/build/tmp/deploy/images/y2038arm/zImage--4.19.bin runqemu -d y2038arm nographic

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.19.34-n2038-4d552acf337038028f7e2f63a927afb7adf65fc1 (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Fri Oct 30 03:23:30 UTC 2020
[ 0.000000] CPU: ARMv7 Processor [410fc090] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

root@y2038arm:# test_y2038
FATAL: kernel too old
root@y2038arm:# test_n2038
FATAL: kernel too old

[lmajewski]

I do create the Y2038 test image with:
bitbake y2038-image-devel -c cleansstate && bitbake y2038-tests -c cleansstate && bitbake y2038-image-devel

Then run it with
runqemu -d y2038arm nographic

Please check following things in meta-y2038/conf/distro/y2038.conf

1. Y2038_GLIBC_MIN_KERNEL_VERSION="5.1.0" - this is the minimal supported kernel to work with glibc. When it is set one shall also have set:
   PREFERRED_PROVIDER_virtual/kernel = "linux-y2038"
PREFERRED_VERSION_linux-y2038 = "5.1%"

2. To test with kernel not supporting syscalls properly handling 64 bit time:
   #Y2038_GLIBC_MIN_KERNEL_VERSION="5.1.0" -> then the minimal supported kernel by glibc version is v3.2
   PREFERRED_PROVIDER_virtual/kernel = "linux-lts"
PREFERRED_VERSION_linux-lts = "4.19%"
   (And comment out above two defines for 5.1 and linux-y2038)

Then you shall see 5.1 Linux running under QEMU:
root@y2038arm:~# uname -a Linux y2038arm 5.1.21-y2038-4a9b1eb8bc3ba4ad8b3b1aa3317cf8d4a3aaad83 #1

Note regarding test_n2038:
Some of those tests will fail as it is expected that some syscalls will fail as they cannot handle correctly
time with value larger than time_t type can handle on ARM (i.e. after Y2038 bug).