On 1/23/22 14:51, John David Anglin wrote: > On 2022-01-23 6:53 a.m., Rolf Eike Beer wrote: >> Am Sonntag, 26. Dezember 2021, 18:22:12 CET schrieb John David Anglin: >>> On 2021-12-26 11:21 a.m., Rolf Eike Beer wrote: >>>> [139181.966881] WARNING: CPU: 1 PID: 0 at kernel/rcu/tree.c:613 >>>> rcu_eqs_enter.constprop.0+0x8c/0x98 >>> This is probably not reproducible. You might try this change from Sven >>> I haven't found 5.15.11 to be stable. >> When I was running 5.15.0 I had uptimes of 21 and 29 days before crashes, and >> then 5 days before I rebooted into 5.15.11 to test that. >> >> With 5.15.11 my longest uptime was 5 days. >> >> I have switched to 5.15.4 afterwards, which is now already up for 2 weeks. I >> see regular userspace crashes with that, usually gcc or ld as the machine is >> mainly building things, which seems to happen way more often than it has >> happened with 5.15.0 for me. > The problem is how to find the changes responsible for this instability? I'm sure they aren't > caused by parisc specific changes. It would take a very long time to bisect and test, and it would > be very easy to make a mistake bisecting because the issues are close to random. > > So the best we can do is to analyze specific problems and try to fix them. I also faced problems with 5.15. So I switched all hppa debian buildd servers to 5.10.90 and they are running stable since 14 days now. I think 5.15 isn't used widely yet, so there are probably still many non-parisc related issues in it. Helge
