On Mon, Oct 22, 2012 at 09:15:09PM +0200, Holger Hans Peter Freyther wrote: > On Mon, Oct 22, 2012 at 10:01:04AM -0700, Sarah Sharp wrote: > > Dear Sarah, > > > > Maybe Sarah can give you some pointers on where to look next. > > > > I've asked for a physical bus trace from one of our QA folks with the > > same scanner. I think that will shed some light on whether this is a > > host-side bug or a software bug. I do know that a certain set of > > scanners don't work under Ivy Bridge/Panther Point xHCI hosts, I just > > haven't had time to look at the bus trace to figure out why. > > is there anything I can help with at this point in time? How high/low > is this issue in your queue and do you know scanners that definately > work with xHCI hosts? I believe the scanners work under NEC/Rensas xHCI hosts, but not Intel hosts. So it is is an Intel specific issue. I'll let you know if there's anything you can do to help me. I currently have 19 bugs in our tracking system (2 priority 1, 2 P2, 4 P3, and 10 P4 bugs). Plus 4 todo items that may or may not be related to said bugs. The biggest challenge right now is the LPM code, which causes I/O errors on USB hard drives that don't support it, and some issues with suspend and hibernate. Those are priority 1 bugs. Your scanner issue is filed as a low priority (priority 4) bug because there is a work-around. For our scanner, if you unplug the device between scanning pages, it works. Does that work for you as well? Sarah Sharp -- 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