I guess it would be helpful to provide the kernel log for the phone where the reboots happen.
With USB debugging enabled, when the phone reboots, press Vol-up to immediately boot into recovery and execute
adb shell cat /proc/last_kmsg > last_kmsg-3.4.10-1.txt
I’d done that in a pm already.
It might already give a hint to boot the phone with the new module simply removed.
Yes, but as I’ve one phone which works with new kernel and one which doesn’t, and both have new camera module, I’m already sure the module is not too blame…
Very nice solution . I’m having such an all time good & handy mobile Linux on my ebooks SD card. That’s what I am missing when using Android, a FS capable of proper handling >4GB files.
Thanks to @Ingo we were able to bisect the kernel and find the offending commit.
New version to test: https://www.androidfilehost.com/?fid=4349826312261746343
Wow, that’s impressive work!
Now it runs fine:
May I ask what kind of rebase this is? Surely, Linux 3.4 ended with 3.4.113. This is the basis for the corresponding Android kernel (which is 3.4.113?) which is the basis for Qualcomm’s Android kernel with modifications found in CodeAurora? Or am I missing something?
And is it correct that on top of that come a ton of patches which are not regarded with a corresponding version number?
I think history is:
FP2 original code is based on Code Aurora code, with the manifest being LA.BF.1.1.1-03010-8x74.0. This incorporates Linux 3.4.0 
Code Aurora CAF was later updated by lineage kernel to LA.BF.1.1.3-01610-8x74.0 (LA.BF.1.1.3_rb1.13) and later to (LA.BF.1.1.3_rb1.15). Still based on 3.4.0
android-common (branch:deprecated/android-3.4) is updated by Google (without CAF) and incorporates linux-stable up to 3.4.67. This was the end of google maintenance for 3.4.
linux-stable is updated up to 3.4.113.
What we’re still missing in FP2 are the changes from 3) android-common on top of CAF. A subset of those changes had been integrated to “get it going” . Once this current kernel appears “stable”, I will have a look at this (again - yes, we also tried this once and it failed).
In theory, it would have been better to rebase the whole FP2 commits on top of CAF + android-common + linux-stable, but this is really too much work and maybe not worth the trouble. There have been a lot of security fixes on top of those, who would need to be replayed.
Hope this helps (hope also this is “correct”).
 TBH: I don’t know to what extend or tag or branch, the CAF sources have (some older version? of) android-common incorporated.
Thank you for clarifying!
Just a small question, can I backup my original version before flashing the new one :)? Can you give some insight, what the biggest or most evident changes the new kernel offers for FP2?
Just do a backup in twrp of the boot partition.
Now, that kernel seems to run fine, are you planning to add it to official LineageOS 17.1 for FP2, too? Just asking…
Would it make sense to test that kernel with 17.1 already now?
I will wait a bit to get 17.1 feedback and then make a version for 17.1 
 You cannot use this as such for 17.1
I got around 2-3 reboot a week with the new kernel, that was approximately the same frequency for the old one.
Two times an app freezed (whatsapp) then 2 second later the phone rebooted.
One time phone was idle then I heard the vibration and it did a random reboot.
I’ll try to catch the log next time
how flash img over adb (remote)?
adb flash boot *.img
There is now also version (with more android-common stuff) for 17.1. Please test. The 16.0 line is discontinued for obvious reasons now.