Re: Boot failure with block/for-next

[James Bottomley]

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/