From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Next March 25: Boot failure on powerpc [recursive locking detected]
Date: Thu, 26 Mar 2009 08:50:03 -0500 [thread overview]
Message-ID: <1238075403.3342.1.camel@localhost.localdomain> (raw)
In-Reply-To: <49CB2200.50703@in.ibm.com>
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
next prev parent reply other threads:[~2009-03-26 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090325191229.0e17eaf6.sfr@canb.auug.org.au>
2009-03-25 14:13 ` Next March 25: Boot failure on powerpc [recursive locking detected] Sachin Sant
2009-03-26 6:34 ` Sachin Sant
2009-03-26 13:50 ` James Bottomley [this message]
2009-03-27 5:56 ` Stephen Rothwell
2009-03-27 6:42 ` Jens Axboe
2009-03-27 6:53 ` Stephen Rothwell
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=1238075403.3342.1.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sachinp@in.ibm.com \
--cc=sfr@canb.auug.org.au \
/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).