The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jan Evert van Grootheest <j.e.van.grootheest@caiway.nl>
To: R H <robheilman@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: March 2008: Current state of oops/crash dumps
Date: Tue, 04 Mar 2008 18:01:00 +0100	[thread overview]
Message-ID: <47CD804C.8010606@caiway.nl> (raw)
In-Reply-To: <a67db0c60803040835g78a5476dkdcefcd66fc696527@mail.gmail.com>

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


  parent reply	other threads:[~2008-03-04 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 16:35 March 2008: Current state of oops/crash dumps R H
2008-03-04 16:57 ` Jiri Kosina
2008-03-04 17:01 ` Jan Evert van Grootheest [this message]
2008-03-04 18:24   ` R H

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47CD804C.8010606@caiway.nl \
    --to=j.e.van.grootheest@caiway.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robheilman@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox