| 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: <20130219125217.6b6f55ff@jbarnes-desktop> Date: Tue, 19 Feb 2013 12:52:17 -0800 From: Jesse Barnes <jbarnes@...tuousgeek.org> To: Chris Li <lkml@...isli.org> Cc: linux-kernel@...r.kernel.org, robert.moore@...el.com, feng.tang@...el.com, len.brown@...el.com, daniel.vetter@...ll.ch, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: i915 black screen introduced by ACPI changes On Tue, 19 Feb 2013 12:18:45 -0800 Chris Li <lkml@...isli.org> wrote: > Secondly, the one clue is that, setting "i915.modeset=0" alone will allow > the kernel to boot into X GUI login. It seems that the mode switch alone in > i915 can trigger the black screen. It is consistent with kernel lockup when I > logout of X desktop, where X want to reset the screen. > > Instead of guess which driver were at fault, can you suggest some experiment > to confirm or denial which driver is at fault? Well it definitely sounds i915 related. I was just thinking that if certain bits were routed to the nvidia chip instead of the i915 one, the i915 driver may get confused and panic. For debugging, you could modify the modeset_init function in i915_dma.c and make it return early with an error. You could use that to narrow down which part of init was failing. -- Jesse Barnes, Intel Open Source Technology Center -- 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