Date: Sun, 8 Jan 2006 05:53:22 -0800
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: vherva@vianova.fi
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops pauser.
Message-Id: <20060108055322.18d4236e.rdunlap@xenotime.net>
In-Reply-To: <20060108133822.GD31624@vianova.fi>
References: <20060105045212.GA15789@redhat.com>
	<Pine.LNX.4.61.0601050907510.10161@yvahk01.tjqt.qr>
	<20060105103339.GG20809@redhat.com>
	<20060108133822.GD31624@vianova.fi>
Organization: YPO4
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 950
Lines: 25

On Sun, 8 Jan 2006 15:38:22 +0200 Ville Herva wrote:

> On Thu, Jan 05, 2006 at 05:33:39AM -0500, you [Dave Jones] wrote:
> > 
> > If I had any faith in the sturdyness of the floppy driver, I'd
> > recommend someone looked into a 'dump oops to floppy' patch, but
> > it too relies on a large part of the system being in a sane
> > enough state to write blocks out to disk.
> 
> I believe kmsgdump (http://www.xenotime.net/linux/kmsgdump/) uses its own
> minimal 16-bit floppy driver to save the oops dump. 

It just switches to real mode and uses BIOS calls.

> Kmsgdump has been around for ages and still works with 2.6.x. I almost
> always use it (all of my boxes still have floppy drives.)


---
~Randy
-
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/