Bug 677049 - USB register timeout
Summary: USB register timeout
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-12 23:04 UTC by GeoffLeach
Modified: 2011-08-29 18:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-29 18:46:30 UTC
Type: ---


Attachments (Terms of Use)

Description GeoffLeach 2011-02-12 23:04:16 UTC
Description of problem:
Plugin of USB cable connecting to a parallel-to-USB connector fails

Version-Release number of selected component (if applicable):
2.6.35.11-83.fc14.i686 #1 SMP

How reproducible:
always

Steps to Reproduce:
1.plug in usb connector
2.fails
3.
  
Actual results:
fails

Expected results:
connects

Additional info: dmesg
 8046.227051] usb 2-1: new full speed USB device using uhci_hcd and address 6
[ 8046.408083] usb 2-1: New USB device found, idVendor=050d, idProduct=0002
[ 8046.408088] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8046.408092] usb 2-1: Product: IEEE-1284 Controller
[ 8046.408094] usb 2-1: Manufacturer: Belk USB Printing Support
[ 8047.552140] get_1284_register timeout
[ 8047.554102] uss720: async_complete: urb error -104
[repeats]
 8047.556111] uss720: async_complete: urb error -32
[sequence repeats]
[unplug connector]
[ 8485.688067] parport0: fix this legacy no-device port driver!
[ 8485.688427] uss720: async_complete: urb error -32

Works fine with 2.6.35.10-74.fc14.i686. Well, not quite. The reason for the plugging in is that if the connector is attached at boot, the device is not recognized. I imagine that it has to do with the Belkin converter being somewhat strange. At the other end, its an HP LaserJet 1300.

Comment 1 GeoffLeach 2011-02-12 23:15:04 UTC
FWIW, here's dmesg output after booting 2.6.35.10-74.fc14.i686

[  122.146074] usb 2-1: new full speed USB device using uhci_hcd and address 2
[  122.325102] usb 2-1: New USB device found, idVendor=050d, idProduct=0002
[  122.325110] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  122.325117] usb 2-1: Product: IEEE-1284 Controller
[  122.325121] usb 2-1: Manufacturer: Belk USB Printing Support
[  123.531167] usblp0: USB Bidirectional printer dev 2 if 0 alt 1 proto 2 vid 0x050D pid 0x0002
[  123.531208] usbcore: registered new interface driver usblp

Comment 2 Chuck Ebbert 2011-02-15 17:39:25 UTC
Huh, that's apparently caused by commit ecc1624a2fff45780959efbcb73ace18fdb3c58d in 2.6.35.11, which makes the uss720 driver control that device. You should be able to blacklist uss720 and have the generic usblp driver control the device like before.

Comment 3 GeoffLeach 2011-02-17 21:28:31 UTC
Blacklisting uss720 resolved the problem. Thanks.


Note You need to log in before you can comment on or make changes to this bug.