From: Wolfgang Schnitker <wolfgang.schnitker@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: solution to "usb disconnect problems regarding usb 1.1 and 2.0"
Date: Sun, 17 Jun 2007 13:14:11 +0200 [thread overview]
Message-ID: <200706171314.12254.wolfgang.schnitker@gmx.de> (raw)
Dear Kernel Developers,
I had some trouble with my usb devices, often showing a disconnect problem. I
did some googleing and saw, that it is a less or more common problem.
This problem is discussed in various internet sites.
log from my machine:
#############################
usb 4-6: new high speed USB device using ehci_hcd and address 7
usb 4-6: configuration #1 chosen from 1 choice
hub 4-6:1.0: USB hub found
hub 4-6:1.0: 4 ports detected
usb 4-6.1: new full speed USB device using ehci_hcd and address 8
usb 4-6.1: device descriptor read/64, error -32
usb 4-6.1: device descriptor read/64, error -32
usb 4-6.1: new full speed USB device using ehci_hcd and address 9
usb 4-6.1: device descriptor read/64, error -110
usb 4-6.1: device descriptor read/64, error -110
usb 4-6.1: new full speed USB device using ehci_hcd and address 10
usb 4-6.1: device not accepting address 10, error -32
usb 4-6.1: new full speed USB device using ehci_hcd and address 11
usb 4-6.1: device not accepting address 11, error -71
usb 4-6: USB disconnect, address 7
usb 4-6: new high speed USB device using ehci_hcd and address 12
usb 4-6: configuration #1 chosen from 1 choice
hub 4-6:1.0: USB hub found
hub 4-6:1.0: 4 ports detected
usb 4-6.1: new full speed USB device using ehci_hcd and address 13
usb 4-6.1: device descriptor read/64, error -32
usb 4-6.1: device descriptor read/64, error -32
usb 4-6.1: new full speed USB device using ehci_hcd and address 14
usb 4-6.1: device descriptor read/64, error -110
usb 4-6.1: device descriptor read/64, error -71
usb 4-6.1: new full speed USB device using ehci_hcd and address 15
usb 4-6.1: device not accepting address 15, error -71
usb 4-6.1: new full speed USB device using ehci_hcd and address 16
usb 4-6.1: device not accepting address 16, error -71
usb 4-6.1: new full speed USB device using ehci_hcd and address 17
usb 4-6.1: configuration #1 chosen from 1 choice
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
usb-storage: device found at 17
usb-storage: waiting for device to settle before scanning
USB Mass Storage support registered.
Vendor: Model: USB Card Reader Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 00
Vendor: Model: USB Card Reader Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 00
Vendor: Model: USB Card Reader Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 00
Vendor: Model: USB Card Reader Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 00
usb-storage: device scan complete
sd 0:0:0:0: Attached scsi removable disk sda
sd 0:0:0:1: Attached scsi removable disk sdb
sd 0:0:0:2: Attached scsi removable disk sdc
sd 0:0:0:3: Attached scsi removable disk sdd
usb 4-6.1: reset full speed USB device using ehci_hcd and address 17
usb 4-6.1: reset full speed USB device using ehci_hcd and address 17
usb 4-6.1: reset full speed USB device using ehci_hcd and address 17
usb 4-6.1: reset full speed USB device using ehci_hcd and address 17
usb 4-6.1: reset full speed USB device using ehci_hcd and address 17
usb 4-6.1: reset full speed USB device using ehci_hcd and address 17
usb 4-6.1: reset full speed USB device using ehci_hcd and address 17
usb 4-6.1: reset full speed USB device using ehci_hcd and address 17
usb 4-6.1: USB disconnect, address 17
#########################
I have a solution/hint to solve this problem.
In my case I had following NOT WORKING config:
internal USB-Card PCI --> USB Hub --> Card Reader
( ali usb card, i-rocks hub, Phision cardreader)
00:08.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:08.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:08.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:08.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01)
linux sets it up using:
ehci --> ehci --> ehci (total usb 2.0 support)
Bus 004 Device 028: ID 0d7d:0240 Phison Electronics Corp. I/O-Magic/Transcend
6-in-1 Card Reader
Bus 004 Device 027: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub [ednet]
but only the hub is a usb 2.0 compliant product. the card-reader is usb 1.1!!
So i changed physically the hub back to a 1.1 device.
and now linux sets this to
ohci --> ohci --> ohci
Bus 003 Device 011: ID 0d7d:0240 Phison Electronics Corp. I/O-Magic/Transcend
6-in-1 Card Reader
Bus 003 Device 010: ID 03eb:3301 Atmel Corp. at43301 4-port Hub
And this configuration works perfect, without any trouble any more.
So in my opinion the problem is comming from ehci, which tries to set up a usb
1.1 device in a 2.0 mode. this results in severe timing problems, because the
1.1 device is too slow to handle this protocol, this results in a "dead"
device from the point of view of the driver (no reaction). It disconnects the
device and reconnects it again. It is only a problem, if you use a HUB
between the USB Controller and the end device. I think we have to take care
about the last device in the chain to set it up in the correct way.
now log looks like this (and I am happy):
########################
usb 3-1: USB disconnect, address 8
ohci_hcd 0000:00:08.2: wakeup
usb 3-2: new full speed USB device using ohci_hcd and address 9
usb 3-2: configuration #1 chosen from 1 choice
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 9 if 1 alt 0
proto 2 vid 0x03F0 pid 0x2D11
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usb 3-1: new full speed USB device using ohci_hcd and address 10
usb 3-1: configuration #1 chosen from 1 choice
hub 3-1:1.0: USB hub found
hub 3-1:1.0: 4 ports detected
usb 3-1.2: new full speed USB device using ohci_hcd and address 11
usb 3-1.2: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 11
usb-storage: waiting for device to settle before scanning
Vendor: Model: USB Card Reader Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 00
sd 2:0:0:0: Attached scsi removable disk sda
Vendor: Model: USB Card Reader Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 00
sd 2:0:0:1: Attached scsi removable disk sdb
Vendor: Model: USB Card Reader Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 00
sd 2:0:0:2: Attached scsi removable disk sdc
Vendor: Model: USB Card Reader Rev: 1.05
Type: Direct-Access ANSI SCSI revision: 00
sd 2:0:0:3: Attached scsi removable disk sdd
usb-storage: device scan complete
SCSI device sda: 510976 512-byte hdwr sectors (262 MB)
sda: Write Protect is off
sda: Mode Sense: 43 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 510976 512-byte hdwr sectors (262 MB)
sda: Write Protect is off
sda: Mode Sense: 43 00 00 00
sda: assuming drive cache: write through
sda: sda1
##############################
I hope, that this will help you to work on this point.
Chears & have a nice day.
--
Wolfgang Schnitker
next reply other threads:[~2007-06-17 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 11:14 Wolfgang Schnitker [this message]
[not found] <fa.sk01i7wDPt73ssXVqjiuwKLchDE@ifi.uio.no>
2007-06-17 17:33 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200706171314.12254.wolfgang.schnitker@gmx.de \
--to=wolfgang.schnitker@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®