From: "Oliver Spang" <Oliver.Spang@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: spinlock recursion bug
Date: Tue, 20 Jun 2006 12:58:15 +0200 [thread overview]
Message-ID: <20060620105815.72010@gmx.net> (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
--
"Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
reply other threads:[~2006-06-20 10:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060620105815.72010@gmx.net \
--to=oliver.spang@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.