From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: Top 9 kernel oopses/warnings for the week of December 29th, 2007
Date: Sat, 29 Dec 2007 14:17:12 +0100 [thread overview]
Message-ID: <20071229131712.GB21805@elte.hu> (raw)
In-Reply-To: <477630CF.5070609@linux.intel.com>
* Arjan van de Ven <arjan@linux.intel.com> wrote:
> kerneloops.org news:
>
> * As of 2.6.24-rc6, oopses have a unique identifier which makes it
> possible to filter out duplicate reports of (and replies to) the
> same oops. Unfortunately some reporters remove this line from their
> reports to lkml.
i'd not mind printing out the bootup-ID as a regular part of the oops,
as long as it's put into an unintrusive place, preferably without adding
a new line. (just use an empty spot somewhere)
for example:
Call Trace: (ID afbf0104e2079481)
[<ffffffff805079f6>] sysdev_driver_unregister+0x5b/0x91
[<ffffffff806f2ef4>] cpufreq_register_driver+0x15a/0x19b
[<ffffffff80cb0586>] powernowk8_init+0x86/0x94
Ingo
next prev parent reply other threads:[~2007-12-29 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 11:34 Top 9 kernel oopses/warnings for the week of December 29th, 2007 Arjan van de Ven
2007-12-29 13:17 ` Ingo Molnar [this message]
2007-12-29 19:18 ` Linus Torvalds
2007-12-29 19:31 ` Arjan van de Ven
2007-12-29 19:34 ` Arjan van de Ven
2007-12-29 19:52 ` Linus Torvalds
2007-12-29 21:53 ` Martin Josefsson
2007-12-29 22:21 ` Geert Uytterhoeven
2007-12-29 19:36 ` Björn Steinbrink
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=20071229131712.GB21805@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).