Skip to contentSkip to conversation

spinlock recursion bug

DISCUSSION Oliver Spang 1 participant 1 message Jun 20, 2006

lore
Share & tools
lore
#0 lore raw

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

Signature · 2 lines
"Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail