Re: 2.2.10 SMP spin_lock bug....
Anton Blanchard (anton@progsoc.uts.edu.au)
Thu, 5 Aug 1999 21:20:44 +1000
> spin_lock (f0165514) CPU#1 stuck at f00554d8, owner PC(f0043cac):CPU3
> spin_lock (f0165514) CPU#2 stuck at f00554d8, owner PC(f0043cac):CPU3
> write_lock_irq (f0165514) CPU3 stuck at f0035470, owner PC(00000000):CPU(0)
> reader [i] = 00000000 reader [i] = 00000000 reader [i] = 00000000 reader [i]
> = 00000000 reader [i] = 00000000 reader [i] = 00000000 reader [i] = 00000000
> reader [i] = 00000000 reader [i] = 00000000 reader [i] = 00000000 reader [i]
> = 00000000 reader [i] = 00000000 reader [i] = 00000000 reader [i] = 00000000
> reader [i] = 00000000 reader [i] = 00000000 reader [i] = 00000000 reader [i]
> = 00000000 reader [i] = 00000000 reader [i] = 00000000 reader [i] = 00000000
> reader [i] = 00000000 reader [i] = 00000000 reader [i] = 00000000 reader [i]
> = 00000000 reader [i] = 00000000 reader [i] = 00000000 reader [i] = 00000000
Bad karma here. Can you lookup the hex numbers in your System.map? We can't
use a spinlock as a rwlock, but perhaps it is one of the srmmu races.
Anton
-
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/