The day-and-a-half mean between spin_lock lockups seems to be
eroding, 2nd lock-up today. Different numbers this time:
spin_lock_irqsave(f55cc66c) CPU #0 stuck at f00c3f10, owner PC(f694b694):CPU(0)
spin_lock(f014b9ac) CPU #1 stuck at f002e3d8, owner PC(f002e3d8):CPU(0)
spin_lock(f014b9ac) CPU #2 stuck at f002e3d8, owner PC(f002e3d8):CPU(0)
>>PC; f694b694 <END_OF_CODE+678e330/????> <=====
Trace; f55cc66c <END_OF_CODE+540f308/????>
>>PC; f002e3d8 <patchme_store_new_current+9c/338> <=====
Trace; f014b9ac <kernel_flag+0/8>
>>PC; f002e3d8 <patchme_store_new_current+9c/338> <=====
Trace; f014b9ac <kernel_flag+0/8>
Config is same as earlier post (same kernel/machine).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:13 EST