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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 5 Dec 2007 01:26:12 +0100
From:	"Rafael J. Wysocki" <>
To:	Kristoffer Ericson <>
Cc:	linux-main <>,
	Alan Stern <>
Subject: Re: Suspend order


On Tuesday, 4 of December 2007, Kristoffer Ericson wrote:
> Hey rafael,
> For obvious reasons it would be great to have serial output to be the last to enter suspend, thus giving every last drop of debugging
> before actually turning the machine "off".
> I'm not aware of any specific order currently, from what I've seen currently  every driver is asked to go into suspend at the same time. This of course providing driver x isn't dependant on driver y. You following?
> So, without digging to much into this, is there any specific order?

Yes, there is.

Devices are suspended in the order reverse with respect to the one in which
they have been registered (ie. the last registered device is suspended first).

Still, if you want the serial console to work over the suspend, try booting the
kernel with the no_console_suspend command line switch (that's applicable to
the current mainline, there was a configuration option for that previously).

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists