From: Andre Noll <maan@systemlinux.org>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: qla2xxx BUG: workqueue leaked lock or atomic
Date: Wed, 28 Feb 2007 16:18:29 +0100 [thread overview]
Message-ID: <20070228151829.GI22572@skl-net.de> (raw)
In-Reply-To: <20070227185134.GJ20397@andrew-vasquezs-computer.local>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
On 10:51, Andrew Vasquez wrote:
> On Tue, 27 Feb 2007, Andre Noll wrote:
> > [ 68.532665] BUG: at kernel/lockdep.c:1860 trace_hardirqs_on()
>
> Ok, since 2.6.20, there been a patch added to qla2xxx which drops the
> spin_unlock_irq() call while attempting to ramp-up the queue-depth:
>
> Could you try the latest 2.6.21-rc which contains the correction?
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.
As lockdep revealed another dm-related lock problem on this kernel,
I guess I'll have to bother the lvm people on this.
Thanks
Andre
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-28 15:18 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 [this message]
2007-02-28 15:37 ` Andre Noll
2007-03-07 4:39 ` Andrew Morton
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=20070228151829.GI22572@skl-net.de \
--to=maan@systemlinux.org \
--cc=James.Bottomley@SteelEye.com \
--cc=andrew.vasquez@qlogic.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