On Mon, 15 Oct 2012, Holger Freyther wrote:
> Holger Freyther <holger@...> writes:
>
>
> >
> > Debian unstable switched to libusbx but kept the package name at
> > libusb. I have tested this with version 1.0.12.Okay, I see that there
> > has been some usb 3.0 changes in 1.0.13 and 1.0.14 and I am going to
> > test again.
>
> I have tested with 38e6eb86b2 (two commits after v1.0.14), verified
> that my version of libusb is picked (cat /proc/PID/maps | grep usb)
> and the symptoms are the same (first scan works, second one doesn't).
>
> I re-tested the scanner and it does not appear to be defective (I
> can scan several pages using a different computer/os).
>
> any ideas?
Actually, it would help to compare two usbmon traces taken on the same
computer, one using xhci-hcd and the other using {eou}hci-hcd. If
that's not possible then two such traces from different computers would
be almost as good.
I generally find usbmon output a lot easier to work with than wireshark
capture files. It's much more condensed and doesn't require any
mousing around. See Documentation/usb/usbmon.txt.
Did you actually scan a page while collecting the wireshark capture?
There's no indication of it in the data.
> it works perfectly with my old notebook and in OSX. The most notable
> change is that I now have USB 3.0 and that xhci_hcd doesn't appear to
> be too stable and is easy to blame. Unplug/Wait/Plug allows me to scan
> another page. Sometimes this leads to an oops in xhcd-hci (but the oops
> scrolls out of the console too fast and the system hardlocks and I don't
> have netconsole running).
It would be very helpful to get a copy of that oops message as well, if
you can get netconsole to work.
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
