On Fri, 18 May 2018, Alexander Kappner wrote:
> Further debugging shows that the code that causes the device to hang is in
> drivers/scsi/sd.c:2698. So the reason why usb-storage works and UAS does
> not is because the device setting both skip_ms_page_3f=1 and
> skip_ms_page_8=1 is required.
> Was this tested with uas or usb-storage?
On both. dd works either way.
> Are you certain Oliver's new code was executed? If you put
> US_FL_NO_WP_DETECT only in unusual_devs.h and not in ususual_uas.h then
> it would not affect the uas driver.
Yes, the code ran.
Further debugging shows
On Thu, 17 May 2018, Alexander Kappner wrote:
> Oliver and Alan,
>
> thank for investigating.
>
> > this is suspicious. You do not actually whether US_FL_NO_WP_DETECT
> > by itself would make the device work. Can you please test that?
>
> US_FL_NO_WP_DETECT without US_FL_IGNORE_UAS does not
Oliver and Alan,
thank for investigating.
> this is suspicious. You do not actually whether US_FL_NO_WP_DETECT
> by itself would make the device work. Can you please test that?
US_FL_NO_WP_DETECT without US_FL_IGNORE_UAS does not make a difference,
even with the patch you included applied:
[
On Thu, 17 May 2018, Alexander Kappner wrote:
> Hi Alan,
>
> thanks for reviewing. (This is my first contribution that touches
> usb-storage, so please bear with me.)
>
> > That's kind of weird. Does the drive work under Windows in UAS mode?
>
> On the Windows 10 VM that I just spun up for
Am Donnerstag, den 17.05.2018, 01:15 -0700 schrieb Alexander Kappner:
> Yes. Without this flag, the device keeps throwing similar errors on
> usb-storage. That's the same result I get on a host that doesn't have UAS
> compiled in. Here's a dmesg:
Hi,
this is suspicious. You do not actually
Hi Alan,
thanks for reviewing. (This is my first contribution that touches
usb-storage, so please bear with me.)
> That's kind of weird. Does the drive work under Windows in UAS mode?
On the Windows 10 VM that I just spun up for testing this, access to the
drive uses "usbstor.inf" (rather
On Wed, 16 May 2018, Alexander Kappner wrote:
> The "G-Drive" (sold by G-Technology) external USB 3.0 drive
> hangs on write access under UAS:
>
> [ 136.079121] sd 15:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [ 136.079144] sd 15:0:0:0: [sdi] tag#0 Sense
