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 06:21:39 +0200	[thread overview]
Message-ID: <20040614042139.GD29808@alpha.home.local> (raw)
In-Reply-To: <200406140223.i5E2N1k18221@mailout.despammed.com>

Hi,

On Sun, Jun 13, 2004 at 09:23:01PM -0500, ndiamond@despammed.com wrote:
> 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 :

   http://developer.odsl.org/rddunlap/kmsgdump/

Upon panic, it switches real mode, uses the bios to change display to text
mode (which does not work for every video card, but still most of them),
then put you in an interactive screen in which you can scroll the last
32 kB of kernel messages, then decide to dump them on a floppy disk or
print them on a parallel printer. This can also be configured to dump
automatically without user interaction and automatically reboot once
done.

Clearly what you need it seems,
Willy


  reply	other threads:[~2004-06-14  4:24 UTC|newest]

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

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=20040614042139.GD29808@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