[lkml]   [2011]   [Jan]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/2][concept RFC] x86: BIOS-save kernel log to disk upon panic
    On Tue, Jan 25, 2011 at 11:47 PM, Ahmed S. Darwish <> wrote:
    > I've faced some very early panics in latest kernel. Being a run of the mill
    > x86 laptop, the machine is void of debugging aids like serial ports or
    > network boot.
    > As a possible solution, below patches prototypes the idea of persistently
    > storing the kernel log ring to a hard disk partition using the enhanced BIOS
    > 0x13 services.

    Quite frankly, I'm not likely to _ever_ merge anything like this.

    Over the years, many people have tried to write things to disk on
    oops. I refuse to take it. No way in hell do I want the situation of
    "the system is screwed, so let's overwrite the disk" to be something
    the kernel I release might do. It's crazy. That disk is a lot more
    important than the kernel, and overwriting it when we might have
    serious memory corruption issues or something is not a thing I feel is

    I also don't think that it's safe to use the BIOS routines. That's not
    the environment they have been tested in - the boot environment is
    very different from the "running kernel" setup. Devices will have been
    possibly remapped, virtual mappings are different, things are just
    very random.

    Some vendors have taken things like this in the past, but I just
    wanted to say that I think it's too damn scary. I _really_ don't see
    the point.

    If you want to do the BIOS services thing, do it for video: copy the
    oops to low RAM, return to real mode, re-run the graphics card POST
    routines to initialize text-mode, and use the BIOS to print out the
    oops. That is WAY less scary than writing to disk.


     \ /
      Last update: 2011-01-25 21:37    [W:0.048 / U:13.572 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site