Re: Regression - Linux 4.9: ums_eneub6250 broken: transfer buffer not dma capable - Trace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 6 May 2017, Andreas Hartmann wrote:

> Am 06.05.2017 um 19:27 schrieb Andreas Hartmann:
> > On 05/06/2017 at 06:43 PM Alan Stern wrote:
> >> For future tests, usbmon traces won't be useful.  The patches don't
> >> make any difference to the USB traffic (other than fixing that original
> >> issue involving non-DMA-able memory).  Instead they change the
> >> communication between the driver and the SCSI core.  USB_STORAGE_DEBUG
> >> will be most useful for tracking this.
> >
> > Tested now w/ patched 4.7.x and 4.8.x - they behave exactly the same as
> > 4.9.x. I don't think other versions will behave differently.
> > Tried to patch 4.4.x - but the patch doesn't apply.
> >
> > Most probably you need a USB_STORAGE_DEBUG with the unpatched driver -
> > true? 4.8.x would be ok?
> 
> I attached an original 4.8.x DEBUG output. Hope this helps!

Good.  And just for a clean comparison, DEBUG output for 4.8.x with the
patched driver would be very helpful.

I suspect the change in behavior is related to the fix I made for the
INQUIRY command.  The original version of the driver returned invalid
information, so the kernel did not realize the media was removable.  
My guess is that your GUI automatically rescans when you click on
Remove for a device on removable media.

If that's the cause, we can fix it by changing the INQUIRY data to 
indicate the media is non-removable.  We'll see...

Alan Stern

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



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux