From: James Bottomley <James.Bottomley@suse.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Boot failure with block/for-next
Date: Thu, 23 Dec 2010 10:10:14 -0600 [thread overview]
Message-ID: <1293120614.7776.0.camel@mulgrave.site> (raw)
In-Reply-To: <20101223155239.GB18482@htj.dyndns.org>
On Thu, 2010-12-23 at 16:52 +0100, Tejun Heo wrote:
> Hey,
>
> On Thu, Dec 23, 2010 at 09:27:21AM -0600, James Bottomley wrote:
> > > Subject: sd: don't clear media presence unless it's removable
> >
> > No, still the same failure. Here's an excised log of an unsuccessful
> > and successful disk probe:
>
> Hmmm... That's unfortunate.
>
> > /bin/sh: can't access tty; job control turned off
> > (initramfs) dmesg|grep sda
> > sd 2:0:1:0: [sda] 71132960 512-byte logical blocks: (36.4 GB/33.9 GiB)
> > sd 2:0:1:0: [sda] Write Protect is off
> > sd 2:0:1:0: [sda] Mode Sense: d3 00 10 08
> > sd 2:0:1:0: [sda] Write cache: disabled, read cache: enabled, supports DPO and FUA
> > device: 'sda': device_add
> > PM: Adding info for No Bus:sda
> > sda: unable to read partition table
> > sd 2:0:1:0: [sda] Attached SCSI disk
> > (initramfs) dmesg|grep sdb
> > sd 2:0:2:0: [sdb] 17942584 512-byte logical blocks: (9.18 GB/8.55 GiB)
> > sd 2:0:2:0: [sdb] Write Protect is off
> > sd 2:0:2:0: [sdb] Mode Sense: e3 00 10 08
> > sd 2:0:2:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
> > device: 'sdb': device_add
> > PM: Adding info for No Bus:sdb
> > sdb: sdb1 sdb2
> > device: 'sdb1': device_add
> > PM: Adding info for No Bus:sdb1
> > device: 'sdb2': device_add
> > PM: Adding info for No Bus:sdb2
> > sd 2:0:2:0: [sdb] Attached SCSI disk
>
> Can you please apply the debug patch I posted in the other message and
> post the boot log? Let's see how the partition read is failing.
That's actually a red herring ... the disk isn't spinning up, so the
partition read is getting a not ready.
James
next prev parent reply other threads:[~2010-12-23 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 17:27 James Bottomley
2010-12-22 17:53 ` Tejun Heo
2010-12-23 4:31 ` James Bottomley
2010-12-23 10:09 ` Tejun Heo
2010-12-23 15:27 ` James Bottomley
2010-12-23 15:52 ` Tejun Heo
2010-12-23 16:10 ` James Bottomley [this message]
2010-12-23 16:13 ` Tejun Heo
2010-12-23 18:25 ` James Bottomley
2010-12-24 11:03 ` Tejun Heo
2010-12-24 15:47 ` James Bottomley
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=1293120614.7776.0.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=axboe@kernel.dk \
--cc=htejun@gmail.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
Powered by JetHome