From: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
To: "Darren Reed" <darrenr@reed.wattle.id.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.11: spinlock problem
Date: Fri, 23 Jun 2006 13:34:30 -0400 [thread overview]
Message-ID: <Pine.LNX.4.61.0606231331310.16810@chaos.analogic.com> (raw)
In-Reply-To: <200606231651.k5NGpbYr008153@firewall.reed.wattle.id.au>
On Fri, 23 Jun 2006, Darren Reed wrote:
> Hi,
>
> I'm seeing a spinlock held panic with a kernel stack like this:
>
> spinlock - panic, lock already held
> ..
> __do_softirq
> do_softirq
> =========
> do_IRQ
> common_interrupt
> spinlock/spinunlock
> ..
>
> when I load up the system in testing.
> The code protected by the spinlock is quite small - counter increment.
>
> I'm using 2.6.11-1.1369_FC4 #1, installed inside of vmware,
> running as a guest on a Windows XP box.
>
> Is this
> (a) linux allowing the IRQ too early
> (b) vmware not doing something right
> (c) enivitable
> (d) somehow my fault
> (e) something else?
>
> Thanks,
> Darren
Where's the code? Also, did you initialize the spin-lock variable
before use?
Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.4 on an i686 machine (5592.88 BogoMips).
New book: http://www.AbominableFirebug.com/
_
\x1a\x04
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
next prev parent reply other threads:[~2006-06-23 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 16:51 2.6.11: spinlock problem Darren Reed
2006-06-23 17:34 ` linux-os (Dick Johnson) [this message]
2006-06-24 2:47 ` Darren Reed
2006-06-25 9:38 ` Frederik Deweerdt
2006-06-23 19:19 ` Hareesh Nagarajan
2006-06-24 10:18 Chuck Ebbert
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=Pine.LNX.4.61.0606231331310.16810@chaos.analogic.com \
--to=linux-os@analogic.com \
--cc=darrenr@reed.wattle.id.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).