| 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: <b6a2187b0708041929x6afd8787t368d3f9f27b709c1@mail.gmail.com> Date: Sun, 5 Aug 2007 10:29:14 +0800 From: "Jeff Chua" <jeff.chua.linux@...il.com> To: "Linus Torvalds" <torvalds@...ux-foundation.org> Cc: lkml <linux-kernel@...r.kernel.org>, "H. Peter Anvin" <hpa@...or.com> Subject: Re: Linux 2.6.23-rc2 On 8/5/07, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > Jeff - do I understand correctly that the "or" means that even *without* a > suspend-to-ram sequence, and just by going into X and then going back to > text-mode, the screen is corrupt? I've done more tests. It seems that "suspend-to-ram" sequence is the culprit. After resume, the text console is messed up. Not switching X/console. Boot up. Console -> X ok -> Console ok -> s2ram -> console bad -> X ok -> console bad -> X ok. > I just want to make sure that there is no suspend-related activity > required for this at all, and the only common issue is probably just that > suspend ends up *also* triggering the X mode-setting at resume.. It's suspend as indicated above. > (Side note: if you have a modern distro, you might try to change the line > that says > Driver "i810" > in the /etc/X11/xorg.conf to say > Driver "intel" I'll test this and get back. Thanks, Jeff. - 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