Re: writing OOPS/panic info to nvram?

[Rusty Russell <rusty@rustcorp.com.au>]

On 05 Sep 2002 01:07:01 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Thu, 2002-09-05 at 00:34, Paul Mackerras wrote:
> > IDE was relatively straightforward since you can do basic block I/O
> > with just the ATA-1 or ATA-2 registers and command set and PIO.  In
> > contrast, I believe SCSI defeated him. :)
> 
> You have to reset and retune the interface/controller registers as well,
> otherwise bad things can happen.

No, at this stage the code reboots the machine (well, I could call the ide
reset code at this point I guess).

Note that my mini oops dumper object file is a leafnode which doesn't use any
external code in the dump path (checked at build time).  It is armed with the
symbols and device & block offsets by userspace.  I plan to update it in the
next month, but it's trivial enough (a new driver with one hook in the oops
code) to be done after the freeze if reqd.

The interesting bit becomes harvesting those reports: this is a higher level
problem (userspace and privacy being the higher levels, respectively).

Rusty.
-- 
   there are those who do and those who hang on and you don't see too
   many doers quoting their contemporaries.  -- Larry McVoy