To: James Colannino <lkml@colannino.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to capture kernel panics
References: <52765.69.93.110.242.1109288148.squirrel@69.93.110.242>
	<421E96AF.1070908@colannino.org>
From: Trond Hasle Amundsen <t.h.amundsen@usit.uio.no>
Organization: Universitas Osloensis
Date: Fri, 25 Feb 2005 14:26:57 +0100
In-Reply-To: <421E96AF.1070908@colannino.org> (James Colannino's message of
 "Thu, 24 Feb 2005 19:08:31 -0800")
Message-ID: <15toee8lqhq.fsf@klodrik.uio.no>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1031
Lines: 27

James Colannino <lkml@colannino.org> writes:

> shabanip wrote:
>
>>is there any way to capture and log kernel panics on disk or ...?
>
> My guess would be, at the very least, it depends on what part of the
> kernel is causing the panic.

A kernel panic means that the kernel no longer knows what it's doing,
and therefore stops doing anything immediately. Hence it won't use the
filesystems and cannot log the panic to anything but the console. I
would think the best solution to your problem is to set up a serial
console to another machine, and log everything to disk on that
machine. See Documentation/serial-console.txt for how to set up a
serial console.

Regards,

-- 
Trond Hasle Amundsen <t.h.amundsen@usit.uio.no>
Center for Information Technology Services, University of Oslo
-
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/