From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: Next March 25: Boot failure on powerpc [recursive locking detected] Date: Thu, 26 Mar 2009 08:50:03 -0500 Message-ID: <1238075403.3342.1.camel@localhost.localdomain> References: <20090325191229.0e17eaf6.sfr@canb.auug.org.au> <49CA3BF4.3050801@in.ibm.com> <49CB2200.50703@in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49CB2200.50703@in.ibm.com> Sender: linux-scsi-owner@vger.kernel.org To: Sachin Sant Cc: linuxppc-dev@ozlabs.org, Stephen Rothwell , linux-next@vger.kernel.org, linux-scsi , Benjamin Herrenschmidt List-Id: linux-next.vger.kernel.org On Thu, 2009-03-26 at 12:04 +0530, Sachin Sant wrote: > Sachin Sant wrote: > > Today's next failed to boot on a powerpc box > > (Power6 blade IBM,7998-61X) with following recursive locking message. > > > > ============================================= > > [ INFO: possible recursive locking detected ] > > 2.6.29-next-20090325 #1 > After bisecting the failure seems to be because of the following > patch from James ( block: move SCSI timeout check into block ) > > http://patchwork.kernel.org/patch/8017/ > > If i back out the above mentioned patch, the machine boots fine > without any problems. Yes, that patch already got dropped for other reasons: http://marc.info/?t=123740773700002 I'm going to see if I can redo it in a better way, since moving this type of timeout checking from scsi to block is a useful generalisation. James