On 05/27/2010 04:30 PM, Alan Stern wrote: > On Thu, 27 May 2010, Andrew Morton wrote: > >> https://bugzilla.kernel.org/show_bug.cgi?id=16058 >> >> Summary: [BUG] Cannot boot any kernel from 2.6.27 on if a 256 >> byte sector SCSI disk is attached > >> As of 2.6.27 if any SCSI disk is attached that has been formatted with a 256 >> byte sector size, the boot process hangs. 512, 768, and 1024 byte sector disks >> do not seem to trigger this. The disks in use do NOT have a partition table. >> They are being used by out applications via the sg_io interface only. >> >> A 2.6.26.8 kernel works fine. >> >> I have bisected this problem to the following commit: >> >> # git bisect good >> 427e59f09fdba387547106de7bab980b7fff77be is first bad commit >> commit 427e59f09fdba387547106de7bab980b7fff77be >> Author: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> >> Date: Sat Mar 8 18:24:17 2008 -0600 >> >> [SCSI] make use of the residue value >> >> USB sometimes doesn't return an error but instead returns a residue >> value indicating part (or all) of the command wasn't completed. So if >> the driver _done() error processing indicates the command was fully >> processed, subtract off the residue so that this USB error gets >> propagated. >> >> Cc: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> >> Signed-off-by: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> >> >> :040000 040000 d3bad84ebe1bc231e8e7d6267907ca62fd4d0dcd >> c85f8cb8bd4910724f0101e41054555980727e16 M drivers >> >> Now, what USB has to do with my SCSI disks is beyond me. I have a >> feeling that this commit is just uncovering another problem. I've attached >> a bootlog from a serial console that ends where the boot hangs. >> >> The does the same thing on a 2.6.34 kernel. Anything I can do to help, I'm >> available. > > I'd guess that this has nothing to do with the sector size. Instead > the drive probably reports a non-zero residue when it shouldn't. Can > you add some debugging printk's to the patch to find out in more detail > what's going wrong? > > Alan Stern > > Yes, I can. But first let me ask, since reverting this patch on at least 2.6.32 - 2.6.34 does not help, would it possibly be better if I did a little more work to find out where it stops working with the above patch reverted or not? Mark -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
