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: <Pine.LNX.4.44L0.1102221029100.1968-100000@iolanthe.rowland.org>
Date:	Tue, 22 Feb 2011 10:36:20 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Jiri Slaby <jirislaby@...il.com>
cc:	"Rafael J. Wysocki" <rjw@...e.com>, <akpm@...ux-foundation.org>,
	<linux-kernel@...r.kernel.org>,
	Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>
Subject: Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ