From: Pete Zaitcev <zaitcev@redhat.com>
To: Dominik Wezel <dio@qwasartech.com>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: USB EHCI Problem with Low Speed Devices on kernel 2.6.11+
Date: Sat, 27 Aug 2005 10:21:35 -0700 [thread overview]
Message-ID: <20050827102135.4e0b035d.zaitcev@redhat.com> (raw)
In-Reply-To: <mailman.1125150481.18996.linux-kernel2news@redhat.com>
On Sat, 27 Aug 2005 15:43:11 +0200, Dominik Wezel <dio@qwasartech.com> wrote:
Forwarding to linux-usb-devel with comments.
> Kernel
> ======
> - 2.6.8, 2.6.11.10 and 2.6.12.4, all show same problem
> Problem
> =======
> When turning on the laptop and during POST and GrUB loading, all ports
> on the hub are enabled. During the USB initialization phase, when the
> hub is detected, shortly all ports become disabled, then turn on again
> (uhci_hcd detects the lo-speed ports). Upon initialization of ehci_hcd
> however, the ports are disconnected again (for good):
>
> ---8<----
> Aug 27 14:29:50 solaris kernel: ehci_hcd 0000:00:1d.7: USB 2.0
> initialized, EHCI 1.00, driver 10 Dec 2004
> Aug 27 14:29:50 solaris kernel: hub 4-0:1.0: USB hub found
> Aug 27 14:29:50 solaris kernel: hub 4-0:1.0: 6 ports detected
> Aug 27 14:29:50 solaris kernel: usb 2-1: USB disconnect, address 2
> Aug 27 14:29:50 solaris kernel: usb 2-1.5: USB disconnect, address 3
> Aug 27 14:29:50 solaris kernel: usb 2-1.6: USB disconnect, address 4
> ---8<----
>
> Addresses 2, 3 and 4 are a keyboard, mouse and palm sync cable respectively.
>
> and afterwards the log becomes cluttered with:
>
> ---8<----
> Aug 27 14:30:31 solaris kernel: usb 4-3: new high speed USB device using
> ehci_hcd and address 79
> Aug 27 14:30:31 solaris kernel: usb 4-3: device not accepting address
> 79, error -71
> Aug 27 14:30:32 solaris kernel: usb 4-3: new high speed USB device using
> ehci_hcd and address 81
> Aug 27 14:30:32 solaris kernel: usb 4-3: device not accepting address
> 81, error -71
> Aug 27 14:30:33 solaris kernel: usb 4-3: new high speed USB device using
> ehci_hcd and address 86
> Aug 27 14:30:34 solaris kernel: usb 4-3: device not accepting address
> 86, error -71
> Aug 27 14:30:34 solaris kernel: usb 4-3: new high speed USB device using
> ehci_hcd and address 89
> Aug 27 14:30:35 solaris kernel: usb 4-3: device not accepting address
> 89, error -71
> Aug 27 14:30:35 solaris kernel: usb 4-3: new high speed USB device using
> ehci_hcd and address 90
> Aug 27 14:30:35 solaris kernel: usb 4-3: device not accepting address
> 90, error -71
> ---8<----
>
> first address to be assigned was 30 in all logs, but the number raises
> mostly in increments of 2 till about 120, then restarts with 12.
>
> Interestlingly, the keyboard and mouse have been detected immediately
> before the intialization of ehcihcd:
>
> ---8<---
> Aug 27 14:29:50 solaris kernel: uhci_hcd 0000:00:1d.2: Intel Corp.
> 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3
> Aug 27 14:29:50 solaris kernel: PCI: Setting latency timer of device
> 0000:00:1d.2 to 64
> Aug 27 14:29:50 solaris kernel: uhci_hcd 0000:00:1d.2: irq 11, io base
> 0x1840
> Aug 27 14:29:50 solaris kernel: uhci_hcd 0000:00:1d.2: new USB bus
> registered, assigned bus number 3
> Aug 27 14:29:50 solaris kernel: hub 3-0:1.0: USB hub found
> Aug 27 14:29:50 solaris kernel: hub 3-0:1.0: 2 ports detected
> /* These are the 2 ports on the laptop */
> Aug 27 14:29:50 solaris kernel: usb 2-1: new full speed USB device using
> uhci_hcd and address 2
> Aug 27 14:29:50 solaris kernel: hub 2-1:1.0: USB hub found
> Aug 27 14:29:50 solaris kernel: hub 2-1:1.0: 7 ports detected
> /* These are the 7 ports of the external hub */
> Aug 27 14:29:50 solaris kernel: usb 2-1.5: new low speed USB device
> using uhci_hcd and address 3
> Aug 27 14:29:50 solaris kernel: usb 2-1.6: new low speed USB device
> using uhci_hcd and address 4
> Aug 27 14:29:50 solaris kernel: usbcore: registered new driver hiddev
> Aug 27 14:29:50 solaris kernel: input: USB HID v1.10 Mouse [Logitech
> Trackball] on usb-0000:00:1d.1-1.5
> Aug 27 14:29:50 solaris kernel: input: USB HID v1.10 Keyboard [CHICONY
> USB Keyboard] on usb-0000:00:1d.1-1.6
> Aug 27 14:29:50 solaris kernel: input,hiddev96: USB HID v1.10 Device
> [CHICONY USB Keyboard] on usb-0000:00:1d.1-1.6
> Aug 27 14:29:50 solaris kernel: usbcore: registered new driver usbhid
> Aug 27 14:29:50 solaris kernel: drivers/usb/input/hid-core.c: v2.0:USB
> HID core driver
> ---8<---
>
> which means the ehci_hcd has afterwards superseded uhci_hcd.
>
> Even more interestingly: in about 5% of the boot cases, ehci_hcd manages
> to detect the ports correctly (or at least doesn't interfere with uhci).
Curious.
> Measures taken
> ==============
> I've found an article suggesting to
> echo Y > /sys/module/usbcore/parameters/old_scheme_first
Very funny.
> ---
> I've also found articles suggesting to throw away the hub and get
> another one, which of course I can't take plain seriously, because now I
> know the problem of this hub, and I'm not going to change it for a hub
> whose problem I even don't know yet... =;)
Borrow one for testing.
Also, plug Palm directly into computer. Surely it has more than one
USB connector.
> Measures not taken
> ==================
> I didn't test the hub on Microsoft Windows, because I assume that
> wouldn't add to the solution space, since the problem is clearly located
> in the uhci_hcd vs. ehci_hcd domain of the linux kernel, as the hub is
> fully functional (within the lo speed scope) when used with only uhci.
Actually, I suspected that this may be a poorly working Transaction
Tranlating (TT) hub. Which then may work on certain versions of
Windows.
-- Pete
next parent reply other threads:[~2005-08-27 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1125150481.18996.linux-kernel2news@redhat.com>
2005-08-27 17:21 ` Pete Zaitcev [this message]
2005-08-28 2:57 ` [linux-usb-devel] Re: USB EHCI Problem with Low Speed Devices on kernel 2.6.11+ Alan Stern
2005-08-28 4:45 ` Pete Zaitcev
2005-08-29 16:11 ` Dominik Wezel
2005-08-27 13:43 Dominik Wezel
2005-08-28 23:16 ` James Courtier-Dutton
2005-08-29 5:28 ` Jan De Luyck
2005-08-29 14:39 ` Randy.Dunlap
2005-08-29 7:53 ` Oliver Neukum
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=20050827102135.4e0b035d.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=dio@qwasartech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.