| 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, 19 Mar 2007 12:08:07 -0700 From: Pete Zaitcev <zaitcev@...hat.com> To: jg@...top.org Cc: zaitcev@...hat.com, linux-kernel@...r.kernel.org Subject: BSOD (was: [2/6] 2.6.21-rc2: known regressions) On Sun, 18 Mar 2007 12:40:45 -0400, Jim Gettys <jg@...top.org> wrote: > Also more seriously, a somewhat hybrid approach is in order for mode > setting: simple mode setting isn't much code and is required for sane > behavior on crash (it is nice to get oopses onto a screen); but the full > blown mode setting/configuration problem is so large that on some > hardware, it is likely left best left to a helper process (not the X > server). Jim, I doubt that a mode switch on oops is a good idea. Maybe I'm unlucky, but in my experience, it often is the case that systems fail to switch to text mode for shutdown. What is amazing, the very same systems switch to text mode on <Alt>F1 just fine, and then back to <Alt>F7! I would hazard a guess that this happens because nobody cares about shutdown modes to fix them. But then the same is true for crashes. I understand that you have your own experience, but thought to note this all the same. >From the constructive angle, I think that a crash should render into existing mode, into the currently mapped frame buffer. This is the only way how it can be made to work reliably. Yours, -- Pete - 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