public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: ndiamond@despammed.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Panics need better handling
Date: Mon, 14 Jun 2004 09:28:04 +0200	[thread overview]
Message-ID: <40CD5384.1050809@aitel.hist.no> (raw)
In-Reply-To: <200406140223.i5E2N1k18221@mailout.despammed.com>

ndiamond@despammed.com wrote:

> I am not asking for
>help in solving this particular panic,
>I am asking for help in general, in
>getting information displayed when it
>needs to be displayed.
>  
>
I have struggled with this from time to time.  Wanting to
report a trace, but it is too long for the screen. 

Using a framebuffer console helps a lot.  I use 1280x1024 resolution,
and 8x8 characters.  The resulting 160x128 console isn't
that fun to _work_ with, but most panics/oopses fit.  I rarely
work at the console anyway.  If you do, consider making two almost
identical kernels where console font size is the only difference.  (The
extra compile takes very little time.)  Then use the small-font kernel
when debugging.

Helge Hafting


  parent reply	other threads:[~2004-06-14  7:25 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
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 ` Helge Hafting [this message]
2004-06-14  7:44   ` Panics need better handling 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=40CD5384.1050809@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --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