From: Jiri Slaby <jirislaby@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
Greg KH <gregkh@suse.de>, USB list <linux-usb@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-input@vger.kernel.org
Subject: Re: dead USB devices after resume [mmotm 2009-02-10-16-35]
Date: Wed, 11 Feb 2009 10:54:08 +0100 [thread overview]
Message-ID: <4992A040.6080302@gmail.com> (raw)
In-Reply-To: <200902111044.57869.rjw@sisk.pl>
On 02/11/2009 10:44 AM, Rafael J. Wysocki wrote:
> Please test current mainline, it may be a regression in there.
OK, will do.
> How exactly are the failing devices connected to the box?
There is a hub in the kbd. The mouse and kbd is behind it, I suppose:
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 12M
|__ Port 1: Dev 3, If 0, Class=HID, Driver=usbhid, 12M
|__ Port 1: Dev 3, If 1, Class=HID, Driver=usbhid, 12M
|__ Port 2: Dev 4, If 0, Class=HID, Driver=usbhid, 1.5M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
There is also a wheel at 6.3 if 1...
Bus 006 Device 004: ID 045e:00f0 Microsoft Corp.
Bus 006 Device 003: ID 0458:004c KYE Systems Corp. (Mouse Systems) Slimstar Pro
Keyboard
Bus 006 Device 002: ID 04b4:2050 Cypress Semiconductor Corp.
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I may try to plug the mouse directly to the root hub if it might help anyhow.
next prev parent reply other threads:[~2009-02-11 9:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200902110036.n1B0aBZs013975@imap1.linux-foundation.org>
2009-02-11 8:44 ` dead USB devices after resume [mmotm 2009-02-10-16-35] Jiri Slaby
2009-02-11 9:44 ` Rafael J. Wysocki
2009-02-11 9:54 ` Jiri Slaby [this message]
2009-02-11 13:38 ` Jiri Slaby
2009-02-11 21:49 ` Rafael J. Wysocki
2009-02-11 15:53 ` Alan Stern
2009-02-13 10:40 ` Jiri Slaby
2009-02-13 15:26 ` Alan Stern
2009-02-16 13:50 ` Jiri Slaby
2009-02-16 19:58 ` Alan Stern
2009-02-13 18:19 ` Jiri Kosina
2009-02-11 8:51 ` ACPI: S4 disappeared " Jiri Slaby
2009-02-11 10:17 ` Jiri Slaby
2009-02-11 15:43 ` Rafael J. Wysocki
2009-02-11 16:22 ` Ingo Molnar
2009-02-11 21:22 ` Rafael J. Wysocki
2009-02-13 9:37 ` Pavel Machek
2009-02-11 16:48 ` mmotm 2009-02-10-16-35 uploaded Randy Dunlap
2009-02-11 16:58 ` mmotm 2009-02-10-16-35 uploaded (s1d13xfb) Randy Dunlap
2009-02-11 22:01 ` Kristoffer Ericson
2009-02-11 17:06 ` mmotm 2009-02-10-16-35 uploaded (reiser4-quota) Randy Dunlap
2009-02-11 17:13 ` Jan Kara
2009-02-11 17:23 ` Edward Shishkin
2009-02-12 2:49 ` KOSAKI Motohiro
2009-02-12 2:53 ` Andrew Morton
2009-02-20 18:12 ` Zan Lynx
2009-02-20 18:30 ` Andrew Morton
2009-02-12 4:13 ` Volker Armin Hemmann
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=4992A040.6080302@gmail.com \
--to=jirislaby@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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