lkml.org 
[lkml]   [1999]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.2.10 SMP spin_lock bug....

> 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/

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:0.045 / U:0.228 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site