From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@osdl.org>
Cc: David Brownell <david-b@pacbell.net>,
LKML <linux-kernel@vger.kernel.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Greg KH <greg@kroah.com>
Subject: 2.6.18-rc6-mm2 (-mm1): ohci_hcd does not recognize new devices
Date: Sat, 16 Sep 2006 10:13:45 +0200 [thread overview]
Message-ID: <200609161013.45800.rjw@sisk.pl> (raw)
In-Reply-To: <200609160013.16014.rjw@sisk.pl>
Hi,
On Saturday, 16 September 2006 00:13, Rafael J. Wysocki wrote:
> It looks like the ohci_hcd driver sometimes has problems with the
> initialization (eg. USB mouse doesn't work after a fresh boot and reloading
> of the driver helps).
>
> I have observed this on two different x86_64 boxes (HPC 6325, Asus L5D),
> but it is not readily reproducible. Anyway I've got a dmesg output from a
> failing case which is attached.
Actually, the problem is ohci_hcd doesn't seem to recognize devices plugged
into the USB ports.
For example, if I unplug and replug a mouse (that worked before unplugging),
it doesn't work any more. I have to reload ohci_hcd to make it work again.
This is 100% reproducible and occurs on the two boxes above.
Appended in a snippet from a dmesg output that I think is relevant to this
issue. It covers the unplugging and replugging of a USB mouse (there are no
more USB-related messages in the dmesg).
Greetings,
Rafael
hub 3-0:1.0: state 7 ports 4 chg 0000 evt 0010
ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [3] = 0x00030100 PESC CSC PPS
hub 3-0:1.0: port 4, status 0100, change 0003, 12 Mb/s
usb 3-4: USB disconnect, address 2
usb 3-4: unregistering device
usb 3-4: usb_disable_device nuking all URBs
ohci_hcd 0000:00:13.1: shutdown urb ffff81002f77d4b8 pipe 40408280 ep1in-intr
usb 3-4: unregistering interface 3-4:1.0
PM: Removing info for No Bus:usbdev3.2_ep81
usbdev3.2_ep81: ep_device_release called for usbdev3.2_ep81
PM: Removing info for usb:3-4:1.0
usb 3-4:1.0: uevent
PM: Removing info for No Bus:usbdev3.2
PM: Removing info for No Bus:usbdev3.2_ep00
usbdev3.2_ep00: ep_device_release called for usbdev3.2_ep00
PM: Removing info for usb:3-4
usb 3-4: uevent
hub 3-0:1.0: debounce: port 4: total 100ms stable 100ms status 0x100
hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0100
ehci_hcd 0000:00:13.2: GetStatus port 8 status 001403 POWER sig=k CSC CONNECT
hub 1-0:1.0: port 8, status 0501, change 0001, 480 Mb/s
hub 1-0:1.0: debounce: port 8: total 100ms stable 100ms status 0x501
ehci_hcd 0000:00:13.2: port 8 low speed --> companion
ehci_hcd 0000:00:13.2: GetStatus port 8 status 003002 POWER OWNER sig=se0 CSC
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
next prev parent reply other threads:[~2006-09-16 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 22:13 2.6.18-rc6-mm2 (-mm1): ohci_hcd sometimes does not initialize properly on x86_64 Rafael J. Wysocki
2006-09-16 8:13 ` Rafael J. Wysocki [this message]
2006-09-18 6:27 ` 2.6.18-rc6-mm2 (-mm1): ohci_hcd does not recognize new devices Rafael J. Wysocki
2006-09-18 6:50 ` Jan De Luyck
2006-09-18 11:20 ` Rafael J. Wysocki
2006-09-18 15:07 ` Alan Stern
2006-09-18 20:51 ` Rafael J. Wysocki
2006-09-18 21:16 ` Alan Stern
2006-09-19 0:04 ` 2.6.18-rc6-mm2 (-mm1): ohci_hcd sometimes does not initialize properly on x86_64 David Brownell
2006-09-19 20:53 ` Rafael J. Wysocki
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=200609161013.45800.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox