GalaticStryder
commented
7 years ago Machine probing:
Arch Linux compiled BETA 3 today (morning) for D800 and in the afternoon for D802, on D802 touch panel firmware doesn't match and compilation date shows as in the morning. The utsrelease header is alright, though. Fedora 24 compiled an EXPERIMENTAL version 09/15 with Faux sound control and today an EXPERIMENTAL with the current state of lambda branch. The utsrelease header matches but the kernel version does not, shows up as version 09/15 and doesn't have the userspace code introduced recently.
Looks like the host is storing a wrong zImage somewhere and bringing it up in the flashable zip and this is not the script behavior.
Panorama: Well, looks like I need to fire this issue to keep track on this annoying error that doesn't seem arise from the kernel source code but some library update in host systems. As ARM debugging is limited, I'm not sure if that can be possible to arise from the devices' system or from the host system itself due to bad caching of DT nodes, generating the primary DT nodes without purging in the next compilation target.
Reproducing: Build the kernel using the script (or manually) for a given variant, flash it. Build it again, different name, new features and debugging will behave just like the previous one. If the variant has changed it will not boot or boot with major issues.
Example: After you flash B kernel version for Y target, the image won't change at all, it will remain A kernel version for an X target. Let's say you compile BETA 3 for D800 target, then compile BETA 4 for D802. The flashed BETA 4 will show up in dmesg/behavior as BETA 3 and screen will be unresponsive due to mismatching touch FW revision for the previous target (D800).
Debugging If you are building Lambda kernel, make a couple serialized builds with different names, let's say a BETA and an EXPERIMENTAL. Flash and run:
adb shell dmesg | grep LambdaWill print the version, BETA afaik.
Flash the other one with different tag. Let's say STABLE, run:
adb shell dmesg | grep LambdaThe Linux version must change as per tag being exported as LOCALVERSION.
There's also the possibility of compiling a given variant that's not yours and then compiling the right one for your variant. Flash that right one, fire another dmesg as I mentioned earlier.
Sometimes it can also rollback to an ancient version of kernel even though you've flashed the latest one.
The utsrelease header should also match the running/flashed kernel.
cat include/generated/utsrelease.hShare your results.