* spinlock recursion bug
@ 2006-06-20 10:58 Oliver Spang
0 siblings, 0 replies; only message in thread
From: Oliver Spang @ 2006-06-20 10:58 UTC (permalink / raw)
To: linux-kernel
Arghhh, forgot the subject, so sorry for the repost:
I got the following bug from the kernel (2.6.16):
BUG: Spinlock recursion on CPU#0, swapped/0 (not tained)
lock d94566c4, .magic:dead4ead, .owner: swapper/0, .owner_cpu:0
BUG: Spinloc lockup on CPU#0, swapper/0, d94566c4 (not tained)
Unfortunately there is no dump or call trace afterwards, and the address of the lock isn't the same on each crash.
Could you give me a hint how to get a call trace after the crash, or can I somehow resolve the address of the lock to a symbol?
Can you please CC me, because I'm not subscribed to the list.
Regards,
Oliver
--
"Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-06-20 10:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-20 10:58 spinlock recursion bug Oliver Spang
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.