public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-arch@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	devel@openvz.org
Subject: Re: [PATCH] Add ability to print calltraces tighter on i386
Date: 08 Aug 2007 17:26:13 +0200	[thread overview]
Message-ID: <p73zm12qc8a.fsf@bingen.suse.de> (raw)
In-Reply-To: <46B9D08F.8080402@openvz.org>

Pavel Emelyanov <xemul@openvz.org> writes:

> When printing a BUG or OOPS report the longest part of it is
> the calltrace, which sometimes (quite often) doesn't fit the
> standard 25-lines display. This may become a bad news when the
> system doesn't have a serial/net console and is completely frozen so
> that the terminal scrolling doesn't work.
> 
> The information that hides from the developer is registers, the
> top of the calltrace and information about the kernel and the
> crashed process (uname). As our experience shows, seeing this info is
> sometimes critical and having a short calltrace would help a lot.
> 
> The proposal is to make a boot-option called "tight_trace", that
> makes the calltrace show only the addresses in one line instead
> of the symbol names one per line.
> 
> E.g. OOPSes of 50 lines occupy ~20 with this patch.
> 
> This is an example of how it will look for i386, but if this
> will be found useful, I will make the patch for other arched
> I can test it on (at least x86_64, ia64).

Just use a higher resolution with vga=... 
I have yet to see an oops that doesn't fit on 80x50

-Andi

  reply	other threads:[~2007-08-08 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 14:17 [PATCH] Add ability to print calltraces tighter on i386 Pavel Emelyanov
2007-08-08 15:26 ` Andi Kleen [this message]
2007-08-08 15:09   ` Pavel Emelyanov
2007-08-08 15:20     ` Andi Kleen
2007-08-09  6:04       ` Ph. Marek
2007-08-09  8:10       ` [Devel] " Kirill Korotaev
2007-08-14  7:11   ` Pavel Machek

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=p73zm12qc8a.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=akpm@osdl.org \
    --cc=devel@openvz.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xemul@openvz.org \
    /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