Messages in this thread | | | Date | Fri, 24 Feb 2006 14:35:12 +0100 | From | "Jesper Juhl" <> | Subject | Re: [PATCH] x86_64 stack trace cleanup |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |