Date: Sun, 27 Nov 2005 20:48:24 -0800
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Alternatives to serial console for oops.
Message-Id: <20051127204824.2758c534.rdunlap@xenotime.net>
In-Reply-To: <4389D63B.4000702@superbug.demon.co.uk>
References: <4389D63B.4000702@superbug.demon.co.uk>
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: 945
Lines: 23

On Sun, 27 Nov 2005 15:52:27 +0000 James Courtier-Dutton wrote:

> Hi,
> 
> I wish to view the oops that are normally output on the serial port of 
> the PC. The problem I have, is that my PC does not have a serial port.
> Are there any alternatives for getting that vital oops from the kernel 
> just as it crashes apart from the serial console.
> Could I get it to use some other interface? e.g. Network interface.
> Parallel port is also not an option.

If the oops occurs after booting (e.g., it's in a module that you
can load after boot to cause the oops) and if you have USB ports
and a usb-serial converter device, you should be able to use
usb-console output to capture the oops.

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