Message-ID: <47CD804C.8010606@caiway.nl>
Date: Tue, 04 Mar 2008 18:01:00 +0100
From: Jan Evert van Grootheest <j.e.van.grootheest@caiway.nl>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: R H <robheilman@gmail.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: March 2008: Current state of oops/crash dumps
References: <a67db0c60803040835g78a5476dkdcefcd66fc696527@mail.gmail.com>
In-Reply-To: <a67db0c60803040835g78a5476dkdcefcd66fc696527@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1109
Lines: 26

R H wrote:
> There is a lot of information on the web about Linux and oops/crash
> dumps.  Some positive, some quite negative.  There are lots of pages
> about tools, patches, best practices, etc.  The problem is that they
> all seem to be out of date.  I think the latest patch I have seen
> available was for 2.6.10.  All this data begs the question:
>
> What is the current state and roadmap for Linux kernel oops/crash dump
> capabilities?
>   
I'm sure that you've been looking at the Documentation/ tree
in the kernel sources? You should've come across netconsole
then. It will do just about the same as a serial console except
that it uses the network.
With newer kernels I don't think there's much need for
patches or tools. Although there are some things that you can
do to improve the stack traces (configure frame pointers, for
example).

-- Jan Evert

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