[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070306203952.471218df.akpm@linux-foundation.org>
Date: Tue, 6 Mar 2007 20:39:52 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andre Noll <maan@...temlinux.org>
Cc: Andrew Vasquez <andrew.vasquez@...gic.com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
James Bottomley <James.Bottomley@...elEye.com>,
Jens Axboe <jens.axboe@...cle.com>,
Alasdair G Kergon <agk@...hat.com>,
Adrian Bunk <bunk@...sta.de>
Subject: Re: qla2xxx BUG: workqueue leaked lock or atomic
On Wed, 28 Feb 2007 16:37:22 +0100 Andre Noll <maan@...temlinux.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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists