The USB controller present here does not interact well with uscanner. The problem manifests itself in an inability to instruct the scanner to conduct a scan more than once, reliably. The device will succeed, silently return to idle, and will never be heard from again. All SANE frontends fail to communicate with the scanner after this point. If another USB device such as a mouse is plugged in at the same time, this does not occur. This may provide a clue as to where the failure is hopefully. The scanner used to demonstrate this is an Agfa Snapscan e20. Whether this is specific to the type of scanner is unknown. The snapscan works flawlessly with other USB controllers using FreeBSD, including that included in the intel i810e chipset and the VIA KT133. This pinpoints an interaction with the SiS controller specifically. Fix: Workaround: Use a USB mouse or plug another USB device into the other port. This is a workaround to the issue, and the scanner(s) will proceed to work well. How-To-Repeat: Use snapscan e20 with SANE frontend such as xscanimage GIMP plugin. - Scan using different modes and resolutions, multiple times each. - Observe that when the scanner is the only device plugged into a USB port, this recurs. - Others who see this PR, please test this condition with other USB scanners (non-snapscan)
Responsible Changed From-To: freebsd-bugs->joe Assign to USB maintainer
Responsible Changed From-To: joe->freebsd-usb Hand this over to the usb mailling list.
can you still test this? I believe it to be fixed..
can you still test this? I believe it to be fixed.. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/48359
State Changed From-To: open->feedback Does this problem still occur with more recent releases?
State Changed From-To: feedback->closed Feedback timeout (> 3 months).