From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?Jan_Kundr=E1t?= <jan.kundrat@fzu.cz>
Subject: Re: Avoid crash dump
Date: Mon, 13 Dec 2004 19:04:03 +0100
Message-ID: <41BDD993.4020905@fzu.cz>
References: <87fz2ahygk.wl@badger.wordzoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-admin@lists.sourceforge.net>
In-Reply-To: <87fz2ahygk.wl@badger.wordzoo.com>
Sender: xen-devel-admin@lists.sourceforge.net
Errors-To: xen-devel-admin@lists.sourceforge.net
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.sourceforge.net>
List-Help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
To: Jared Rhine <jared@wordzoo.com>
Cc: xen-devel@lists.sourceforge.net
List-Id: xen-devel@lists.xenproject.org

> Is there a way to avoid the Xen on-screen crash dump/traceback?  I'm
> having a xen startup (before dom0) problem with a particular
> configuration where I don't have a serial port, so I can't see the
> last messages output before the crash.
> 
> I'll probably be able to find the code and comment it out, if nothing
> currently exists.  In which case, please consider this feature request.
> 

You could find the kmsgdump patch usefull, it saves such dumps to floppy.

jkt

-- 
cd /local/pub && more beer > /dev/mouth



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/