Messages in this thread | | | Subject | Re: BSOD | From | Jim Gettys <> | Date | Tue, 20 Mar 2007 16:33:56 -0400 |
| |
On Tue, 2007-03-20 at 20:19 +1100, Paul Mackerras wrote:
> Anything is better than nothing. At the moment we get nothing if you > are in X when the panic occurs, even for the nicest, most well-behaved > panics. :) If we can change that to getting something sometimes, > that's a win.
Treating the display as a frame buffer if at all possible is more likely to work than anything else. All the kernel needs to know is beginning address, stride (# bytes/line; not necessarily the same as the number of pixels on a row), number of rows, and depth of the display. Thereafter, it's just a SMOP as they say (and the sometimes maligned fbdev driver of course already has all this code, and usually oops messages do ok on fbdev).
The other interesting headache that comes up sometimes is when the oops message is more than a screen-full long.
One may also need to reset lookup tables to some sane value, and halt the GPU, and maybe worry about video overlays. - Jim
-- Jim Gettys One Laptop Per Child
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |