From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Andres Salomon" <dilinger@debian.org>
Cc: "Andi Kleen" <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64 stack trace cleanup
Date: Fri, 24 Feb 2006 14:35:12 +0100 [thread overview]
Message-ID: <9a8748490602240535r5c956e76o6226e4bc8337f9dd@mail.gmail.com> (raw)
In-Reply-To: <1140780552.5073.26.camel@localhost.localdomain>
On 2/24/06, Andres Salomon <dilinger@debian.org> wrote:
> On Fri, 2006-02-24 at 11:47 +0100, Andi Kleen wrote:
[snip]
>
> > The problem is your new format uses more screen estate, which is precious
> > after an oops because the VGA scrollback is so small.
> > That is why i rejected the earlier attempts at changing this.
> >
>
> I don't see why this is a problem. Other architectures have done this
> for ages, without problems. I suspect most people get their backtraces
> from either serial console or logs, as copying them down from the screen
> or taking a picture of the panic is a rather large pain. It seems like
> you're penalizing everyone for a few select use cases.
>
Some of us don't have a digital camera for taking a picture (and
besides, being able to take a picture doesn't fix the problem of oops
output scrolling out of the visible screen area).
Some of us also don't have a second PC on which to capture logs via
netconsole or serial console.
Copying oopses down by hand from screen to paper sure is a pain (I
know, I've had to do it quite a few times), but for some it's the only
option and then we generally want as much info as possible on-screen
to copy down.
And btw, multi-column oops output has recently become an option for
i386 as well - in my oppinion a good thing.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-02-24 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 10:41 Andres Salomon
2006-02-24 10:47 ` Andi Kleen
2006-02-24 11:29 ` Andres Salomon
2006-02-24 12:22 ` Andi Kleen
2006-02-24 19:25 ` Alistair John Strachan
2006-02-24 19:40 ` Jesper Juhl
2006-02-24 13:35 ` Jesper Juhl [this message]
2006-02-24 12:50 ` Andrew Morton
2006-02-24 13:00 ` Andi Kleen
2006-02-24 13:13 ` Andrew Morton
2006-02-24 13:20 ` Andi Kleen
2006-02-24 15:53 ` Randy.Dunlap
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=9a8748490602240535r5c956e76o6226e4bc8337f9dd@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=ak@suse.de \
--cc=dilinger@debian.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®