Date: Sun, 8 Jan 2006 17:45:05 -0800
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: gcoady@gmail.com
Cc: vherva@vianova.fi, linux-kernel@vger.kernel.org
Subject: Re: oops pauser.
Message-Id: <20060108174505.6c9b7566.rdunlap@xenotime.net>
In-Reply-To: <6cq2s1d3glnj56pcrqlj84s8ltilmo6jfp@4ax.com>
References: <20060105045212.GA15789@redhat.com>
	<Pine.LNX.4.61.0601050907510.10161@yvahk01.tjqt.qr>
	<20060105103339.GG20809@redhat.com>
	<20060108133822.GD31624@vianova.fi>
	<20060108055322.18d4236e.rdunlap@xenotime.net>
	<6cq2s1d3glnj56pcrqlj84s8ltilmo6jfp@4ax.com>
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: 1284
Lines: 33

On Mon, 09 Jan 2006 06:40:57 +1100 Grant Coady wrote:

> On Sun, 8 Jan 2006 05:53:22 -0800, "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> 
> >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.
> 
> So would it be viable to take over the screen in similar fashion?
> 
> Set it to 80x50 in BIOS and dump there --> call it the Penguin Oops 
> screen, or Poops for short :o)

It does take over the screen.  80x50 isn't needed since it knows how
to scroll the kernel log buffer on 80x25.

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