Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#47890 - [linux] USB 3.0 port not working with Canon PIXMA MP250

Attached to Project: Arch Linux
Opened by Todo ays (entodoays) - Monday, 25 January 2016, 13:36 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 October 2017, 18:24 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The scanner feature of this Multi-function printer was working fine until recently.

Today, I tried to scan using Simple Scan and the scan hung up after a second or two with the moving light 10 cm from the edge. Simple scan keeps waiting and the printer display continued turning. Then I receive an "error communicating with device" error.

I checked the scanner on a windows machine and it works perfectly.

So I tried Xsane. Hitting "preview", the scanner seems to scan all the way but no info is received.

Then I tried disconnecting the scanner from the usb hub and connecting this directly to the laptop to the same USB 3.0 port. Same issue.

Finally, I tried connecting the scanner to another USB 2.0 port and it worked properly.

So it seems there's a bug in the USB 3.0 handling in the latest kernel.




Additional info:
Computer: Toshiba Satellite R830
kernel version: 4.3.3-3-ARCH
Hardware info: 05:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)

Steps to reproduce:
Scan using simple scan or xsane while the printer is connected to a USB 3.0 port.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 06 October 2017, 18:24 GMT
Reason for closing:  Fixed
Comment by Todo ays (entodoays) - Tuesday, 09 February 2016, 13:25 GMT
This problem is still present with kernel 4.4.1-2-ARCH.
Comment by mattia (nTia89) - Monday, 02 October 2017, 19:52 GMT
is this issue still valid?
Comment by Todo ays (entodoays) - Friday, 06 October 2017, 13:07 GMT
This issue was solved with one of the kernel updates.

Loading...