Hello Eric, On 23/12/24(Mon) 17:05, Eric Grosse wrote: > On Thu, Dec 12, 2024 at 11:30 AM Martin Pieuchot <[email protected]> wrote: > ... > > That sounds like a memory corruption of some sort. It might be that > > recent changes hide it. I'd be glad if you could test George's change. > ... > > Thanks. If you run into such crash again, please try to get a trace > > from the cpu that panic'd. In this case cpu0. > > I'm finally back home and power cycled to get the machine back. After > compiling a new kernel with source from cvs (including George's change) > I pretty quickly got another crash:
Thanks for the report. Do I understand correctly that George's change is not the fix we're looking for your bug? > [...] > r1|Stopped at _rb_remove+0x36c: ld r4,8(r3) > TID PID UID PRFLAGS PFLAGS CPU COMMAND > *453813 7858 8889 0x2000002 0 3 compile > 36553 81731 8889 0x2000002 0 2 compile > 99640 86457 8889 0x2000002 0 7 compile > 242134 64462 8889 0x2000002 0 0 compile > 68242 72226 8889 0x2000002 0x4000000 4 go > 495275 4590 8889 0x2000002 0x4000000 1 compile > 250285 66963 0 0x14000 0x200 6 reaper > 241654 98481 0 0x14000 0x200 5 pagedaemon What is 'compile'? What are you compiling to trigger the bug?
