linux-kernel - Re: dead USB devices after resume [mmotm 2009-02-10-16-35]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4992D4C3.3050108@gmail.com>
Date:	Wed, 11 Feb 2009 14:38:11 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	linux-kernel@...r.kernel.org, mm-commits@...r.kernel.org,
	Greg KH <gregkh@...e.de>, USB list <linux-usb@...r.kernel.org>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-input@...r.kernel.org
Subject: Re: dead USB devices after resume [mmotm 2009-02-10-16-35]

On 02/11/2009 10:54 AM, Jiri Slaby wrote:
> 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.

I was not able to reproduce it with 1db8508. So it highly likely hasn't leaked
to the mainline.

>> 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.

No change. Wherever it is connected it fails to emit anything.

BTW It is sufficient to unplug the mouse from the kbd (i.e. the hub) and replug
it back.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/