public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: ndiamond@despammed.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Panics need better handling
Date: Mon, 14 Jun 2004 07:45:26 +0200	[thread overview]
Message-ID: <20040614054525.GE29808@alpha.home.local> (raw)
In-Reply-To: <200406140519.i5E5JEk23773@mailout.despammed.com>

On Mon, Jun 14, 2004 at 12:19:15AM -0500, ndiamond@despammed.com wrote:
> Willy Tarreau replied to me:
> 
> >> Is there
> >> any chance in getting the 24 most
> >> important lines of panic information
> >> displayed last, and putting the cursor
> >> at the end of the 24th line thereof, so
> >> that 24 valuable lines of panic
> >> information can be visible?
> >
> > You could try kmsgdump, which Randy Dunlap ported to 2.6
> [...]
> > Clearly what you need it seems,
> 
> Partly, yes it looks clearly what I
> need (though I need it for 2.4).

OK, so download the original 2.4 version here : 

  http://w.ods.org/linux/kernel/kmsgdump/0.4.4/

It still applies to 2.4.27-pre5.

> But surely every developer or maintainer
> of every driver or other part of the
> kernel also has a clear need for every
> Linux user to install this.  I am not
> the only one who needs to get these
> reports, right?  Shouldn't this be in
> the main kernel tree by now, and enabled
> by default?

Well, yes and no. Yes because it's useful, no because there are so many
other useful tools which would largely replace it and be more complete
(kdb, lkcd, ...) that one could wonder why it's in the kernel at all.
Since it's mainly useful to developers, and not too much intrusive, people
who need it can easily apply it to their tree.

Cheers,
Willy


  reply	other threads:[~2004-06-14  5:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14  5:19 Panics need better handling ndiamond
2004-06-14  5:45 ` Willy Tarreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-14 14:20 Cress, Andrew R
2004-06-14  5:52 ndiamond
2004-06-14  2:23 ndiamond
2004-06-14  4:21 ` Willy Tarreau
2004-06-14  4:34   ` Norberto Bensa
2004-06-14  7:28 ` Helge Hafting
2004-06-14  7:44   ` John Bradford

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=20040614054525.GE29808@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndiamond@despammed.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