| 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
| ||
|
Date: Mon, 18 Aug 2008 22:37:11 -0500 From: David Fries <david@...es.net> To: Ingo Molnar <mingo@...e.hu> Cc: linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>, Pavel Machek <pavel@....cz>, "H. Peter Anvin" <hpa@...or.com>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH] i486 CR4 oops, no_console_suspend On Mon, Aug 18, 2008 at 08:41:20AM +0200, Ingo Molnar wrote: > > applied to tip/x86/urgent, thanks David. I've changed the conditions to > read_cr4_safe() instead - that's cleaner. Could you please check whether > the patch below works fine too on your box? Yes the 486 suspends and resumes with this patch. Is there any known problem with no_console_suspend and serial consoles? It worked to print the oops for me to track this down, and Documentation/kernel-parameters.txt says it is known to work with serial consoles, but on resume only kernel messages can output to the serial console. The getty on the serial port can't raed or write and processes trying to write to the port just hang without getting any data across. The serial port works fine across suspends without the no_console_suspend argument. Does anyone else see this? -- David Fries <david@...es.net> http://fries.net/~david/ (PGP encryption key available) -- 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