From: Jens Axboe <axboe@suse.de>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: more cfq spinlock badness
Date: Tue, 31 Jan 2006 10:09:45 +0100 [thread overview]
Message-ID: <20060131090944.GU4215@suse.de> (raw)
In-Reply-To: <20060131063938.GA1876@redhat.com>
On Tue, Jan 31 2006, Dave Jones wrote:
> Not seen this break for a while, but I just hit it again in 2.6.16rc1-git4.
>
> Dave
>
> BUG: spinlock bad magic on CPU#0, pdflush/1128
> lock: ffff81003a219000, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
>
> Call Trace: <ffffffff80206edc>{spin_bug+177} <ffffffff80207045>{_raw_spin_lock+25}
> <ffffffff801fea4a>{cfq_exit_single_io_context+85} <ffffffff801ff9a6>{cfq_exit_io_context+24}
> <ffffffff801f79b0>{exit_io_context+137} <ffffffff80135fbc>{do_exit+182}
> <ffffffff8010ba49>{child_rip+15} <ffffffff80146087>{keventd_create_kthread+0}
> <ffffffff8014629c>{kthread+0} <ffffffff8010ba3a>{child_rip+0}
> Kernel panic - not syncing: bad locking
Again, which devices have you used? Did it happen at shutdown, or? Did
the ub bug get fixed, if you are using that? The bug above has in the
past always been able to be explained by a driver destroying a structure
embedding the queue lock before the queue is dead.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-31 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 6:39 more cfq spinlock badness Dave Jones
2006-01-31 9:09 ` Jens Axboe [this message]
2006-01-31 17:36 ` Dave Jones
2006-02-01 11:02 ` Jens Axboe
2006-02-01 16:15 ` Dave Jones
[not found] ` <mailman.1138828082.21892.linux-kernel2news@redhat.com>
2006-02-03 18:44 ` Pete Zaitcev
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=20060131090944.GU4215@suse.de \
--to=axboe@suse.de \
--cc=davej@redhat.com \
--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