From: Eric Sandeen <sandeen@sandeen.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-1.2689.fc6PAE: oops in ext3_clear_inode+0x52/0x8b
Date: Tue, 03 Oct 2006 00:32:14 -0500 [thread overview]
Message-ID: <4521F5DE.7070302@sandeen.net> (raw)
In-Reply-To: <20060928142313.8848cec9.akpm@osdl.org>
Andrew Morton wrote:
> On Thu, 28 Sep 2006 13:42:26 -0700
> Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>> I just filed this in the Redhat bugzilla, since its from the FC6 distro
>> kernel. But since its fairly close to current kernel.org kernels, I
>> thought it might be relevent.
>>
>> The bug is https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208488
>>
>> Unfortunately this isn't a very useful report since it was a once-off,
>> and there's a P-tainting module in there. But if anyone sees anything
>> else like this, it's interesting.
>>
>> The oops is:
>>
>> BUG: unable to handle kernel paging request at virtual address 756e6547
>
> 756e6547 -> uneG. Matches "GenuineIntel".
>
> That'll get written into a temporary page by the /proc/cpuinfo handler, so
> it might just be a use-uninitialised.
But strangely enough, it's the second report we've seen with this exact
backtrace, and the same "Genu" ascii string where the i_default_acl should be.
Both boxes had been through a suspend-to-ram recently, just in case that might
matter.
Seems like something more than random chance...
-Eric
next prev parent reply other threads:[~2006-10-03 5:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 20:42 2.6.18-1.2689.fc6PAE: oops in ext3_clear_inode+0x52/0x8b Jeremy Fitzhardinge
2006-09-28 20:48 ` James Morris
2006-09-28 21:00 ` Jeremy Fitzhardinge
2006-09-28 21:23 ` Andrew Morton
2006-09-28 21:26 ` Jeremy Fitzhardinge
2006-10-03 5:32 ` Eric Sandeen [this message]
2006-10-03 5:42 ` Adrian Bunk
2006-10-03 14:06 ` Eric Sandeen
2006-10-03 16:23 ` Adrian Bunk
2006-10-03 16:27 ` Eric Sandeen
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=4521F5DE.7070302@sandeen.net \
--to=sandeen@sandeen.net \
--cc=akpm@osdl.org \
--cc=jeremy@goop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.