Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755859AbYHTV4O (ORCPT ); Wed, 20 Aug 2008 17:56:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751847AbYHTVz5 (ORCPT ); Wed, 20 Aug 2008 17:55:57 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:54086 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751371AbYHTVz4 (ORCPT ); Wed, 20 Aug 2008 17:55:56 -0400 Date: Wed, 20 Aug 2008 17:55:55 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Jeremy Fitzhardinge cc: Linux Kernel Mailing List , , "Rafael J. Wysocki" Subject: Re: 2.6.27-rc2 USB suspend regression In-Reply-To: <48AC8FB2.2040301@goop.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2454 Lines: 61 On Wed, 20 Aug 2008, Jeremy Fitzhardinge wrote: > Alan Stern wrote: > > On Wed, 20 Aug 2008, Jeremy Fitzhardinge wrote: > > > > > >> Using the Fedora Rawhide kernel RPM "2.6.27-0.238.rc2.fc10.i686" > >> (kernel-2.6.27-0.238.rc2.fc10.i686), I'm seeing suspend to ram > >> failures. The suspend seems to go OK, but then I just get endless: > >> > >> usb 5-1: uhci_result_common: failed with status 440000 > >> > >> messages, with occasional flickers of something else being printed > >> (perhaps). The machine is otherwise unresponsive. > >> > > > > You could comment out that error message in order to see what else is > > in the log. It is located in drivers/usb/host/uhci-q.c in the > > uhci_result_common() function. > > > > You could try running -rc3 instead of -rc2, although that probably > > won't make much difference. > > > > What USB devices do you have on the failing system? In particular, > > what is 5-1? If you unplug it before suspending, does the problem go > > away? (It certainly should!) > > > > > > No external usb devices. There are three internal USB devices: > Bluetooth, a Sierra CDMA modem thingy and a fingerprint reader. > > $ lsusb > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 005 Device 003: ID 0483:2016 SGS Thomson Microelectronics > Fingerprint Reader > Bus 005 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 003: ID 1199:0218 Sierra Wireless, Inc. MC5720 Wireless Modem > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > The rfkill switch "unplugs" the two wireless devices, so I'll try that > before suspending next time (if I remember). Obviously 5-1 is either the Bluetooth controller or the fingerprint reader. It's understandable that either one of them might have problems with a suspend/resume cycle, but the kernel ought to be able to recover by itself. It would help to see the USB debugging log (without all those useless uhci_result_common messages). Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/