From: Russell King <rmk@arm.linux.org.uk>
To: Cort Dougan <cort@fsmlabs.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cheap lookup of symbol names on oops()
Date: Thu, 25 Jul 2002 23:18:22 +0100 [thread overview]
Message-ID: <20020725231822.H9800@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020725154425.T2276@host110.fsmlabs.com>; from cort@fsmlabs.com on Thu, Jul 25, 2002 at 03:44:25PM -0600
On Thu, Jul 25, 2002 at 03:44:25PM -0600, Cort Dougan wrote:
> You don't lose the hex data. The patch just prints data that the kernel
> already has. For some situations this patch does match the needs of
> developers better.
I recently had an oops on my laptop with a rh kernel with I think this
stuff in (it decoded the trace to symbols, etc).
The only problem was that the machine paniced at the end, with the
register dump off the top of the screen. The only thing visible was
the trace.
As useful as it was to have the trace, the oops was useless because
the rest of the information was missing.
So why didn't I scroll up? Because shift-pgup needs a task queue to
run, which doesn't happen after a panic, just like you can't ctrl-alt-del
to reboot (but you can alt-sysrq-b)...
Personally, I'd much rather have the standard oops output and be able
to scribble down the numbers, and then look them up than to have some
snazzy bit of code in the kernel do it for me and scroll the useful
information off the screen.
(And thanks for reminding me about the oops...)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-07-25 22:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 17:00 [PATCH] cheap lookup of symbol names on oops() Cort Dougan
2002-07-25 17:11 ` Christoph Hellwig
2002-07-25 17:21 ` Cort Dougan
2002-07-25 18:49 ` Benjamin LaHaise
2002-07-25 20:16 ` Cort Dougan
2002-07-25 19:04 ` Andrea Arcangeli
2002-07-25 20:27 ` Cort Dougan
2002-07-25 20:59 ` Andrea Arcangeli
2002-07-25 21:05 ` Cort Dougan
2002-07-25 22:06 ` Andrea Arcangeli
2002-07-25 22:05 ` Cort Dougan
2002-07-25 22:56 ` Andrea Arcangeli
2002-07-25 23:01 ` Cort Dougan
2002-07-26 22:37 ` module oops tracking [Re: [PATCH] cheap lookup of symbol names on oops()] Andrea Arcangeli
2002-07-26 22:55 ` Cort Dougan
2002-07-26 23:28 ` Andrea Arcangeli
2002-07-26 23:31 ` Cort Dougan
2002-07-27 0:10 ` Andrea Arcangeli
2002-07-27 2:15 ` cort
2002-07-27 0:19 ` Keith Owens
2002-07-27 0:31 ` Andrea Arcangeli
2002-07-27 1:19 ` Andrea Arcangeli
2002-07-27 1:33 ` Keith Owens
2002-07-27 1:47 ` Andrea Arcangeli
2002-07-25 21:12 ` [PATCH] cheap lookup of symbol names on oops() Lars Marowsky-Bree
2002-07-25 22:13 ` Andrea Arcangeli
2002-07-25 22:41 ` Rik van Riel
2002-07-25 23:01 ` Andrea Arcangeli
2002-07-26 7:57 ` Lars Marowsky-Bree
[not found] ` <Pine.LNX.4.44L.0207251941120.3086-100000@imladris.surriel. com>
2002-07-27 2:34 ` Stevie O
2002-07-25 22:39 ` Rik van Riel
2002-07-26 1:01 ` Marcin Dalecki
2002-07-25 22:46 ` Alan Cox
2002-07-25 21:44 ` Cort Dougan
2002-07-25 22:18 ` Russell King [this message]
2002-07-25 22:23 ` Cort Dougan
2002-07-25 22:44 ` Rik van Riel
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=20020725231822.H9800@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cort@fsmlabs.com \
--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