From: Arjan van de Ven <arjan@linux.intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, netdev@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: Top 10 kernel oopses/warnings for the week of December 21st 2007
Date: Fri, 21 Dec 2007 15:30:45 +0100 [thread overview]
Message-ID: <476BCE15.6090902@linux.intel.com> (raw)
In-Reply-To: <p73ejdgf8vj.fsf@bingen.suse.de>
Andi Kleen wrote:
> Arjan van de Ven <arjan@linux.intel.com> writes:
>
>>
>> Rank 8: __change_page_attr
>> BUG at arch/x86/mm/pageattr_64.c:176
>> Reported 2 times
>> Reported this week for 2.6.24-rc5; history goes back to 2.6.15
>
> There is no BUG on this line on 2.6.24-rc5. Since there are many
> BUG_ONs in this file it is unclear which you mean.
>
> Could you always include the version of the kernel where the actual
> oops in the line came from?
in this case this is really all the version information available ;(
it seems to be a patched kernel without patched EXTRAVERSION.
But in the future if I have more specific information (eg it's only 1 kernel version) I'll mention it in more detail.
It gets unwieldy if there's 500 reports for an oops of course ;)
>
> Anyways there are a lot of third party modules who do strange
> things with c_p_a(), not always legal, so you might look up out for that
> pattern too. Perhaps report the out of tree modules loaded in the
> summary too?
I already always will mention if the oops is tainted or not (that I track specifically);
I'll keep an eye out for other non-tainting out of tree modules as well.
Thanks for the suggestions.
next prev parent reply other threads:[~2007-12-21 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 11:51 Top 10 kernel oopses/warnings for the week of December 21st 2007 Arjan van de Ven
2007-12-21 13:57 ` Andi Kleen
2007-12-21 14:30 ` Arjan van de Ven [this message]
2007-12-21 16:22 ` Andi Kleen
2007-12-21 14:09 ` Alan Cox
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=476BCE15.6090902@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=venkatesh.pallipadi@intel.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).