linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Reuben Farrelly <reuben-lkml@reub.net>,
	"Brown, Len" <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.13-mm1: hangs during boot ...
Date: Sat, 03 Sep 2005 12:14:16 -0400	[thread overview]
Message-ID: <1125764058.4615.4.camel@mulgrave> (raw)
In-Reply-To: <4319AA71.7090700@bigpond.net.au>

On Sat, 2005-09-03 at 23:51 +1000, Peter Williams wrote:
> > Are you seeing this "Device  not ready" message appear over and over, or 
> > just the once?
> 
> Just the once.

OK, I finally have a theory about this.  It's the everything goes via
bios code.  Previously there were several levels at which commands could
exit the SCSI stack; now we make everything go via bios, so they all
come out at the top.

get_capabilities() in sr.c is sending a TEST_UNIT_READY which will get
NOT_READY back.  Previously this was completing before it got to
scsi_io_completion(); now it doesn't.  There must be quite a few cases
like this.  The best fix is probably to use and respect REQ_QUIET for
internally generated commands.

James

  reply	other threads:[~2005-09-03 16:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.qs5cahs.i2khgm@ifi.uio.no>
     [not found] ` <fa.fm9i4v6.1ekchhm@ifi.uio.no>
2005-09-03 13:24   ` 2.6.13-mm1: hangs during boot Reuben Farrelly
2005-09-03 13:51     ` Peter Williams
2005-09-03 16:14       ` James Bottomley [this message]
2005-09-04 16:32     ` James Bottomley
2005-09-05  8:37       ` Reuben Farrelly
2005-09-03 15:57 Brown, Len
2005-09-03 22:48 ` Peter Williams
  -- strict thread matches above, loose matches on Subject: below --
2005-09-03  5:37 Brown, Len
2005-09-03  6:18 ` Peter Williams
2005-09-03  7:18   ` Peter Williams
2005-09-03  8:19     ` Len Brown
2005-09-03  9:28       ` Peter Williams
2005-09-03  9:48         ` Andrew Morton
2005-09-03  4:22 Brown, Len
2005-09-03  4:58 ` Peter Williams
2005-09-03  5:25   ` Andrew Morton
     [not found] <43184B8A.4040801@bigpond.net.au>
     [not found] ` <20050902131122.4c634211.akpm@osdl.org>
     [not found]   ` <43191DBF.10407@bigpond.net.au>
2005-09-03  4:16     ` Andrew Morton

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=1125764058.4615.4.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pwil3058@bigpond.net.au \
    --cc=reuben-lkml@reub.net \
    /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).