Hi The fix went upstream, but caused regression for other users, and had to be reverted. The cause of the regression was found but the new version was never properly tested and got left behind as more urgent issues arrived. I still need to attend a few other issues before taking up this again -Mathias On 21.05.2015 13:38, Hans-Peter Jansen wrote: > Dear Mathias, > > just a heads up: retesting with 4.0.4 revealed, that this issue isn't fixed > for my scanner still. To recap: driving the scanner through a ehci port is > fine, and fails miserably with xhci. > > OK: > > T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 4 > D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=1d6b ProdID=0002 Rev=04.00 > S: Manufacturer=Linux 4.0.4-2.g4f5e0d5-desktop ehci_hcd > S: Product=EHCI Host Controller > S: SerialNumber=0000:06:04.2 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 > P: Vendor=04b8 ProdID=0119 Rev=01.00 > S: Manufacturer=EPSON > S: Product=EPSON Scanner > C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=2mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > > NOT OK: > > T: Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=14 > D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 > P: Vendor=1d6b ProdID=0002 Rev=04.00 > S: Manufacturer=Linux 4.0.4-2.g4f5e0d5-desktop xhci-hcd > S: Product=xHCI Host Controller > S: SerialNumber=0000:00:14.0 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > T: Bus=06 Lev=01 Prnt=01 Port=10 Cnt=02 Dev#= 10 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 > P: Vendor=04b8 ProdID=0119 Rev=01.00 > S: Manufacturer=EPSON > S: Product=EPSON Scanner > C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=2mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbfs > > Additional notes: > > xsane scanner discovery takes ages (20-30 secs) to find the scanner in the > failing case. After selecting the correct device, it takes another delay of > 20-30 secs. for presenting the error dialog: error during device I/O. The same > procedure with ehci takes about a second until the device selection is shown, > and another 0.5 secs later it presents the fully functional scanning UI. > > This behavior persists since Linux 3.16.x (where I setup this box). > > Please let me know, if I can be of any help for you for resolving this issue. > I find it a little sad, that at the dawn of USB 3.1, we still fight with such > issues on the linux USB 3.0 front. Don't forget the many frustrated users > observing this, that will not speak up. > > Cheers, > Pete > > On Donnerstag, 29. Januar 2015 18:42:05 Mathias Nyman wrote: >> On 27.01.2015 14:12, Gunter Königsmann wrote: >>> That's very good news indeed. >>> >>> Will re-run the tests on my scanner and looking forward to the fix >>> entering mainline. In the meantime I can acknowledge that with the fix my >>> computer accepts USB memory sticks that normally didn't work. >>> >>> Kind regards, >>> >>> Gunter. >> >> Did some cleaning of the patch, and noticed it still had a few bits wrong, >> but apparently it worked anyway. >> >> I added the fixes on top of the ep_reset_halt_test branch. >> >> Can any of you with a failing scanner test that it still works? >> >> git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git >> and the ep_reset_halt_test branch, >> >> Thanks >> >> -Mathias > > -- > 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 > -- 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
