On Tue, 2008-10-14 at 11:32 +0200, Geert Uytterhoeven wrote: > > which points again to smp_call_function_single...
Yup, it doesn't bring more information. At this stage, your 'other' CPU is stuck with interrupts disabled. Hard to tell what's happening without some HW assist. Do you have ways to trigger a non-maskable interrupt such as a 0x100 ? That would allow to catch the other guy in xmon and see what it was doing... It could be something in the ps3vram driver causing the kernel to lockup.... Now the question is whether the kernel is stuffed with something like a deadlock with interrupts off, or is it a HW problem causing a CPU to lockup on an access to the vram ? I'm afraid only you guys have tools that would allow to debug that sort of problem. Cheers, Ben. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
