On Tue, 2013-01-22 at 11:05 -0600, H. Peter Anvin wrote: > On 01/22/2013 09:43 AM, Alan Stern wrote: > > On Tue, 22 Jan 2013, Oliver Neukum wrote: > > > >> On Tuesday 22 January 2013 11:05:35 James Bottomley wrote: > >>>> May 3 18:19:06 relampago3 kernel: [ 3948.472796] sd 7:0:0:0: [sdf] > >>>> 1565565872 512-byte logical blocks: (801 GB/746 GiB) > >>> > >>> This looks like a wrap around of your actual size. This appears to > >>> indicate the device isn't replying correctly to READ CAPACITY. The > >>> conventional return from READ CAPACITY should be -1 which would trigger > >>> us to retry with READ CAPACITY(16). > >> > >> What can we do? The answer the device is giving is quite ordinary. > >> Do we need another quirk and an associated flag? > > > > The JMicron bridges are well known to be fairly buggy. Another quirk > > may indeed be the only solution. Oliver, would you like to write a > > patch for it? > > > > Would it make more sense to try READ CAPACITY(16) first? Or does that > have other bad effects? That has other effect: Many USB devices crash the firmware on 16 byte commands (sigh, welcome to our world ...) James -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
