From: Andrew Morton <akpm@linux-foundation.org>
To: Andre Noll <maan@systemlinux.org>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>,
Jens Axboe <jens.axboe@oracle.com>,
Alasdair G Kergon <agk@redhat.com>, Adrian Bunk <bunk@stusta.de>
Subject: Re: qla2xxx BUG: workqueue leaked lock or atomic
Date: Tue, 6 Mar 2007 20:39:52 -0800 [thread overview]
Message-ID: <20070306203952.471218df.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070228153722.GJ22572@skl-net.de>
On Wed, 28 Feb 2007 16:37:22 +0100 Andre Noll <maan@systemlinux.org> wrote:
> On 16:18, Andre Noll wrote:
>
> > With 2.6.21-rc2 I am unable to reproduce this BUG message. However,
> > writing to both raid systems at the same time via lvm still locks up
> > the system within minutes.
>
> Screenshot of the resulting kernel panic:
>
> http://systemlinux.org/~maan/shots/kernel-panic-21-rc2-huangho2.png
>
It died in CFQ. Please try a different IO scheduler. Use something
like
echo deadline > /sys/block/sda/queue/scheduler
This could still be the old qla2xxx bug, or it could be a new qla2xxx bug,
or it could be a block bug, or it could be an LVM bug.
Adrian, can we please track this as a regression?
next prev parent reply other threads:[~2007-03-07 4:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 13:31 qla2xxx BUG: workqueue leaked lock or atomic Andre Noll
2007-02-26 18:26 ` Andrew Vasquez
2007-02-27 10:11 ` Andre Noll
2007-02-27 14:35 ` Andre Noll
2007-02-27 18:51 ` Andrew Vasquez
2007-02-28 15:18 ` Andre Noll
2007-02-28 15:37 ` Andre Noll
2007-03-07 4:39 ` Andrew Morton [this message]
2007-03-07 17:09 ` Andre Noll
2007-03-07 19:45 ` Andrew Morton
2007-03-07 20:05 ` Mingming Cao
2007-03-09 9:36 ` Andre Noll
2007-03-07 18:46 ` Jens Axboe
2007-03-08 8:52 ` Andre Noll
2007-03-08 9:02 ` Jens Axboe
2007-03-08 9:33 ` Andre Noll
2007-03-08 9:36 ` Jens Axboe
2007-03-08 10:29 ` Andre Noll
2007-03-08 10:35 ` Jens Axboe
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=20070306203952.471218df.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@SteelEye.com \
--cc=agk@redhat.com \
--cc=andrew.vasquez@qlogic.com \
--cc=bunk@stusta.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maan@systemlinux.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).