| 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
| ||
|
Message-Id: <20071204213132.d806a24f.Kristoffer.ericson@gmail.com> Date: Tue, 4 Dec 2007 21:31:32 +0100 From: Kristoffer Ericson <kristoffer.ericson@...il.com> To: rjw@...k.pl Cc: linux-main <linux-kernel@...r.kernel.org> Subject: Suspend order 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? Best wishes Kristoffer -- 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