disabled CONFIG_FORCE_NR_CPUS option for 6.9.5 but the trace + panic still exists. So that one didn't help. I've also been bisecting the trace but have not finished it yet as the last half dozen builds produced non-bootable kernels. Anyway, I will continue it soon(ish) when I have a bit more free time.
--Ilkka
On Tue, Jun 18, 2024 at 5:52 PM Steven Rostedt rostedt@goodmis.org wrote:
On Thu, 13 Jun 2024 10:32:24 +0300 Ilkka Naulapää digirigawa@gmail.com wrote:
ok, so if you don't have any idea where this bug is after those debug patches, I'll try to find some time to bisect it as a last resort. Stay tuned.
FYI,
I just debugged a strange crash that was caused by my config having something leftover from your config. Specifically, that was:
CONFIG_FORCE_NR_CPUS
Do you get any warning about nr cpus not matching at boot up?
Regardless, can you disable that and see if you still get the same crash.
Thanks,
-- Steve