From: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
To: Ingo Molnar <mingo@elte.hu>, Linus Torvalds <torvalds@transmeta.com>
Cc: Kai Germaschewski <kai-germaschewski@uiowa.edu>,
<linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Arjan van de Ven <arjanv@redhat.com>
Subject: Re: [ANNOUNCE] [patch] kksymoops, in-kernel symbolic oopser, 2.5.38-B0
Date: Thu, 26 Sep 2002 18:16:27 +0100 [thread overview]
Message-ID: <200209261816.27194.ruthc@sharra.ivimey.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0209252155210.18747-100000@localhost.localdomain>
On Wednesday 25 September 2002 20:56, Ingo Molnar wrote:
> ------------[ cut here ]------------
> kernel BUG at time.c:99!
> invalid operand: 0000
> CPU: 1
> EIP: 0060:[<c011bd14>] Not tainted
> EFLAGS: 00010246
> EIP is at sys_gettimeofday+0x84/0x90
> eax: 0000004e ebx: cef9e000 ecx: 00000000 edx: 00000068
> esi: 00000000 edi: 00000000 ebp: bffffad8 esp: cef9ffa0
> ds: 0068 es: 0068 ss: 0068
> Process gettimeofday (pid: 549, threadinfo=cef9e000 task=cf84d860)
> Stack: 4001695c bffff414 40156154 00000004 c0112a40 cef9e000 400168e4
Something that's been bugging me of late: the Oops output is quite expensive
in lines on the terminal, which means if you get a couple of oops before the
kernel stops, you're unlikely to see the one that fired first.
To help with this, would it be good to use the following form for the initial
part:
kernel BUG at time.c:99, invalid operand: 0000
CPU 1: EIP: 0060:[<c011bd14>] Not tainted
EIP is at sys_gettimeofday+0x84/0x90
eax: 0000004e ebx: cef9e000 ecx: 00000000 edx: 00000068
esi: 00000000 edi: 00000000 ebp: bffffad8 esp: cef9ffa0
ds: 0068 es: 0068 ss: 0068 eflags: 00010246 [textflags]
Where [textflags] is some arch-specific representation of the flags word.
Also, in the same vein I would like to be able to say (as a kernel option):
if kernel-oops {
copy console output to [printer|serial] port
}
[printer output == ascii only, of course]
Regards,
Ruth
prev parent reply other threads:[~2002-09-26 17:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 9:02 [ANNOUNCE] [patch] kksymoops, in-kernel symbolic oopser, 2.5.38-B0 Ingo Molnar
2002-09-25 9:32 ` [re-ANNOUNCE] " Ingo Molnar
2002-09-25 9:51 ` Arnaldo Carvalho de Melo
2002-09-25 18:16 ` [ANNOUNCE] " Linus Torvalds
2002-09-25 19:23 ` Kai Germaschewski
2002-09-25 19:42 ` Ingo Molnar
2002-09-25 19:41 ` Kai Germaschewski
2002-09-25 19:46 ` Linus Torvalds
2002-09-25 19:54 ` Ingo Molnar
2002-09-25 19:52 ` Linus Torvalds
2002-09-25 20:04 ` Ingo Molnar
2002-09-25 20:31 ` Jeff Garzik
2002-09-25 19:55 ` Kai Germaschewski
2002-09-25 19:45 ` Linus Torvalds
2002-09-25 19:53 ` Ingo Molnar
2002-09-25 19:04 ` Cort Dougan
2002-09-25 20:14 ` Ingo Molnar
2002-09-25 19:56 ` Ingo Molnar
2002-09-25 22:04 ` J.A. Magallon
2002-09-27 20:48 ` Bill Davidsen
2002-09-27 21:13 ` Ingo Molnar
2002-09-27 23:58 ` J.A. Magallon
2002-09-26 17:16 ` Ruth Ivimey-Cook [this message]
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=200209261816.27194.ruthc@sharra.ivimey.org \
--to=ruth.ivimey-cook@ivimey.org \
--cc=arjanv@redhat.com \
--cc=kai-germaschewski@uiowa.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).