[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No, I did not take all goodies from 3.1.0 away. I kept all EAS changes, also from SD855. These should make the most noticeable difference anyways, both regarding battery and performance. F2FS is still updated to latest f2fs-stable git state.

RCU Boost may responsible for these reboots. I don´t think RCU Boost has that big of a noticeable impact on UI. I´m also suspecting another commit to be responsible, but we will see what happens now.

I may reintroduce the other commits from SD855 at some point.

I recommend 3.1.1 since it has 4.9.178 merged.

In no way do I pretend I can test for every possible use case, for every single user. I know I use my phone in a certain way and everyone does. My testers and me didn´t have any reboots for a few days with these patches. If some bug slipped through our fingers with our specific use case of the phone so be it. I know I don´t regularly use every single function the phone provides.

Especially with stuff which was included in 3.1.0 (sd 855 backports, RCU Boost (which is explicitly disabled in the Pixel 3 kernel)) such stuff can happen on certain use cases.

I mentioned to only report reboots and post logs if no mods, scripts, magic apps etc are used. If somebody uses mods, there is no absolute need to post a log since I cannot guarantee it will work with every single mod.

I mentioned that in the 2nd post.

Try to recreate the bug if possible on a fresh installation or at least with all mods removed. Without any mods, scripts, tweaks, strange apps that enhance your phone. Just latest magisk. If the mod modifies system and isn´t a magisk module you might need to dirty flash your rom. It would be also better to dirty flash the rom after you disabled magisk modules to rule out every possible interference.

If people still post logs and pretend to run no mods or simply don´t mention it, they hurt the whole community to put it simply.

For example the issue with the original 4.9.177 release was this commit:

https://github.com/aosp-mirror/kernel_common/commit/1fff19a925e524556e85efcd728efad5274ce5b6

it caused soft reboots (only to bootanimation). But only when mobile data and wifi were enabled simultaneously. Now many users disable one or the other manually when returning home/leaving the house. Some have even set up tasker profiles for this.

The problem was not at all identifiable in the dmesg (kernel log) but only visible in logcat, since it affected NETD. Plus it happened to me as soon as I flashed my kernel after merging original 4.9.177. So I knew something wasn´t right.

Just because most are unaffected by an issue doesn´t mean it´s non existent.

Ultimately I want to provide a stable kernel, because nobody likes their phone rebooting constantly. If one seemingly beneficial patch causes reboots for others I see no sense in keeping it.

Additionally this kernel is for 2 devices, of which I own only the Pixel 3 XL. There was more than one occasion where only the pixel 3 was affected by a kernel crash, but not the pixel 3 xl despite the kernel being unified. To give one more example.

Give it time and we will see, if I decide to bring back the missing SD855 backports. Just look at my git and you´ll notice the difference isn´t that huge :)

That are quite a few mods. :D

Even if you get reboots with this device configuration I won´t be able to help or debug this at all. You can report it and provide logs, but be sure to mention your device configuration.

xposed is a nightmare for debugging. If you decided to use it and it works fine it´s cool. If you get reboots on this kernel while using all these mods, because this kernel is update wise very far from stock you´re on your own.

The following is just aimed at the thread in general:

I really hope everybody understands this.

If you can´t recreate your reboots on a clean environment (your stock rom or a custom rom) without any mods installed it´s most likely not the kernel on it´s own causing troubles.

If I face bugs I do the same (if I can´t fix them otherwise myself)