Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754525Ab1BVPgX (ORCPT ); Tue, 22 Feb 2011 10:36:23 -0500 Received: from iolanthe.rowland.org ([192.131.102.54]:59076 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753919Ab1BVPgW (ORCPT ); Tue, 22 Feb 2011 10:36:22 -0500 Date: Tue, 22 Feb 2011 10:36:20 -0500 (EST) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Jiri Slaby cc: "Rafael J. Wysocki" , , , Linux-pm mailing list Subject: Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded] In-Reply-To: <4D6377B8.7080805@gmail.com> 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: 2183 Lines: 70 On Tue, 22 Feb 2011, Jiri Slaby wrote: > On 02/04/2011 08:33 PM, Alan Stern wrote: > > On Fri, 4 Feb 2011, Jiri Slaby wrote: > > > >>>> It seems to suffice... No hangs still. Should I enable pm_async back > >>>> again to confirm the issue is still present? > >>> > >>> Yes, please, it would be good to know for sure. > >> > >> Ok, confirmed right now :). > >> > >> I disabled pm_async for USB again. What do you suggest next? > > > > What happens if you leave pm_async enabled but unplug all the USB > > devices before suspending? If there are any USB devices you can't > > unplug, you can get an equivalent result by unconfiguring the root > > hubs: > > > > for a in /sys/bus/usb/devices/usb* ; do > > echo 0 >$a/bConfigurationValue > > done > > This doesn't seem to help. The hang happened 3 times during the 2 weeks. > > I have /etc/pm/sleep.d/99usb-debug with: > #!/bin/bash > > send() { > for a in /sys/bus/usb/devices/usb* ; do > echo $1 >$a/bConfigurationValue > done > } > > case "$1" in > hibernate|suspend) > send 0 > ;; > thaw|resume) > send 1 > ;; > *) > ;; > esac > > exit 0 > > And it indeed properly enable/disable usb before/after suspend. Strange indeed. It's worth noting that the async stuff affects only the normal suspend and resume operations, not the late-suspend and early-resume operations. This means that it all likelihood, the system crashes either before finishing the suspend or after doing a fair amount of the resume. And yet that's not consistent with what you see on the screen. By the way, are you booting with no_console_suspend? And do you do "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before suspending? What about if you leave async enabled for all the USB devices _except_ usb[1-N]? 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/