Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751479AbXB0Svn (ORCPT ); Tue, 27 Feb 2007 13:51:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751294AbXB0Svn (ORCPT ); Tue, 27 Feb 2007 13:51:43 -0500 Received: from avexch1.qlogic.com ([198.70.193.115]:29304 "EHLO avexch1.qlogic.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751479AbXB0Svl (ORCPT ); Tue, 27 Feb 2007 13:51:41 -0500 Date: Tue, 27 Feb 2007 10:51:34 -0800 From: Andrew Vasquez To: Andre Noll Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, James Bottomley Subject: Re: qla2xxx BUG: workqueue leaked lock or atomic Message-ID: <20070227185134.GJ20397@andrew-vasquezs-computer.local> References: <20070226133153.GC4095@skl-net.de> <20070226182617.GC9968@andrew-vasquezs-computer.local> <20070227101100.GA22572@skl-net.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070227101100.GA22572@skl-net.de> Organization: QLogic Corporation User-Agent: Mutt/1.5.13 (2006-08-11) X-OriginalArrivalTime: 27 Feb 2007 18:51:41.0465 (UTC) FILETIME=[51A91090:01C75AA0] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2563 Lines: 58 On Tue, 27 Feb 2007, Andre Noll wrote: > On 10:26, Andrew Vasquez wrote: > > You are loading some stale firmware that's left over on the card -- > > I'm not even sure what 4.00.70 is, as the latest release firmware is > > 4.00.27. > > That's the firmware which came with the card. Anyway, I just upgraded > the firmware, but the bug remains. The backtrace differs a bit though > as now the tg3 network driver seems to be involved as well. > > Thanks for your help > Andre ... > [ 68.532665] BUG: at kernel/lockdep.c:1860 trace_hardirqs_on() > [ 68.532784] > [ 68.532785] Call Trace: > [ 68.532979] [] trace_hardirqs_on+0xd7/0x180 > [ 68.533168] [] _spin_unlock_irq+0x2b/0x40 > [ 68.533295] [] :qla2xxx:qla2x00_process_completed_request+0x137/0x1d0 > [ 68.533457] [] :qla2xxx:qla2x00_status_entry+0x82/0xa40 > [ 68.533577] [] __lock_acquire+0xcdf/0xd90 > [ 68.533693] [] _spin_unlock_irqrestore+0x42/0x60 > [ 68.533816] [] :qla2xxx:qla24xx_intr_handler+0x4e/0x2b0 > [ 68.533942] [] :qla2xxx:qla24xx_process_response_queue+0xc1/0x1c0 > [ 68.534102] [] :qla2xxx:qla24xx_intr_handler+0x1d4/0x2b0 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: commit befede3dabd204e9c546cbfbe391b29286c57da2 Author: Seokmann Ju Date: Tue Jan 9 11:37:52 2007 -0800 [SCSI] qla2xxx: correct locking while call starget_for_each_device() Removed spin_unlock_irq()/spin_lock_irq() pairs surrounding starget_for_each_device() calls. As Matthew W. pointed out, starget_for_each_device() can be called under a spinlock being held. The change has been tested and verified on qla2xxx.ko module. Thanks Matthew W. and Hisashi H. for help. Signed-off-by: Andrew Vasquez Signed-off-by: Seokmann Ju Signed-off-by: James Bottomley http://marc.theaimsgroup.com/?l=linux-scsi&m=116837234904583&w=2 Could you try the latest 2.6.21-rc which contains the correction? Regards, Andrew Vasquez - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/