From: Chuck Ebbert <76306.1226@compuserve.com>
To: Konstantin Antselovich <konstantin@antselovich.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: BUG: spinlock recursion on CPU, kernel 2.6.16.20 & 2.6.16-1.2122_FC5[smp]
Date: Mon, 19 Jun 2006 05:57:39 -0400 [thread overview]
Message-ID: <200606190600_MC3-1-C2D8-23E5@compuserve.com> (raw)
In-Reply-To: <4491933C.7060100@antselovich.com>
On Thu, 15 Jun 2006 10:05:00 -0700, Konstantin Antselovich wrote:
> Jun 10 00:57:35 192.168.0.201 BUG: spinlock recursion on CPU#2, swapper/0
> Jun 10 00:57:35 192.168.0.201 lock: c266f600, .magic: dead4ead, .owner:
> swapper/0, .owner_cpu: 2
> Jun 10 00:57:35 192.168.0.201 [<c01cc02d>]
> Jun 10 00:57:35 192.168.0.201 _raw_spin_lock+0x33/0xd2
> Jun 10 00:57:35 192.168.0.201
> Jun 10 00:57:35 192.168.0.201 [<c02e5bf7>]
> Jun 10 00:57:35 192.168.0.201 _spin_lock_irqsave+0x9/0xd
> Jun 10 00:57:35 192.168.0.201
> Jun 10 00:57:35 192.168.0.201 [<f88b7768>]
> Jun 10 00:57:35 192.168.0.201 ahd_freeze_simq+0x12/0x43 [aic79xx]
Please try 2.6.17. The spinlock was removed.
--
Chuck
"You can't read a newspaper if you can't read." --George W. Bush
next reply other threads:[~2006-06-19 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 9:57 Chuck Ebbert [this message]
2006-06-19 21:46 ` Infinite interrupt loop, INTSTAT = 8 ( WAS: BUG: spinlock recursion on CPU, kernel 2.6.16.20 & 2.6.16-1.2122_FC5[smp]) Konstantin Antselovich
-- strict thread matches above, loose matches on Subject: below --
2006-06-15 17:05 BUG: spinlock recursion on CPU, kernel 2.6.16.20 & 2.6.16-1.2122_FC5[smp] Konstantin Antselovich
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=200606190600_MC3-1-C2D8-23E5@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=konstantin@antselovich.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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
all inboxes | Powered by JetHome®