From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756591AbZBKJy1 (ORCPT ); Wed, 11 Feb 2009 04:54:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753341AbZBKJyR (ORCPT ); Wed, 11 Feb 2009 04:54:17 -0500 Received: from fg-out-1718.google.com ([72.14.220.153]:33716 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752341AbZBKJyP (ORCPT ); Wed, 11 Feb 2009 04:54:15 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=tx+tCXId7yFtX0TdxnLch+bwKPXS564oloKvZ+50NkCdIPSAy+CZ/azqj3gopiuUlt YwdmZr5+5NoU/uyHLlzlzeAa+t7rF+2c8CsGKLzlNX5lq4/Zm95nRJN3uQ6Hpd/YxS8N F5ZJfLhCwT69DlHkJPhJgDnMbFdcyOEDs62s8= Message-ID: <4992A040.6080302@gmail.com> Date: Wed, 11 Feb 2009 10:54:08 +0100 From: Jiri Slaby User-Agent: Thunderbird 2.0.0.19 (X11/20081227) MIME-Version: 1.0 To: "Rafael J. Wysocki" CC: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org, Greg KH , USB list , Alan Stern , linux-input@vger.kernel.org Subject: Re: dead USB devices after resume [mmotm 2009-02-10-16-35] References: <200902110036.n1B0aBZs013975@imap1.linux-foundation.org> <49928FDB.5020007@gmail.com> <200902111044.57869.rjw@sisk.pl> In-Reply-To: <200902111044.57869.rjw@sisk.pl> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Slaby Subject: Re: dead USB devices after resume [mmotm 2009-02-10-16-35] Date: Wed, 11 Feb 2009 10:54:08 +0100 Message-ID: <4992A040.6080302@gmail.com> References: <200902110036.n1B0aBZs013975@imap1.linux-foundation.org> <49928FDB.5020007@gmail.com> <200902111044.57869.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200902111044.57869.rjw-KKrjLPT3xs0@public.gmane.org> Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Rafael J. Wysocki" Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, mm-commits-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Greg KH , USB list , Alan Stern , linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-input@vger.kernel.org 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. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html