[lkml]   [2007]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: BSOD
I agree with David and Jessie.

All the kernel needs to know for oopses is frame buffer depth, start,
stride, and how to get the GPU to "stop" (or it may very well overwrite
the screen). Trying to get back to a default mode setting first in the
middle of oopsing is very unlikely to succeed.

The time you want mode switching (or lack othereof) is at suspend/resume
time, not at oopses.

This presumes the frame buffer is accessible in the address space of the
kernel. There have been display devices where this is not true; but not
- Jim

On Mon, 2007-03-19 at 13:05 -0700, David Miller wrote:
> From: Jesse Barnes <>
> Date: Mon, 19 Mar 2007 12:54:36 -0700
> > Kernel based modesetting should get us a lot of things:
> But for panics you're ignoring what Peter and I are saying.
> Mode setting is complex and it is not going to work exactly when you
> need the kernel crash message the most.
> After debugging the kernel for 10+ years I can tell you one thing, for
> a bad crash what's going to happen is you'll get the printk but that's
> about all that will work at that point, and the kernel is going to
> hang next. Sometimes you won't get the whole panic message, just
> the beginning, even with the most simplistic printk implementation.
> You will not, I repeat, will not be able to mode switch or anything
> non-trivial like that when the kernel is in this state.
> Mode switching on panic, just say no. :-)
Jim Gettys
One Laptop Per Child

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-03-19 21:33    [W:0.203 / U:0.424 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site