From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "David Newall" <david@davidnewall.com>
Cc: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>,
Scott <linux-kernel@bluecamel.eml.cc>,
linux-kernel@vger.kernel.org, mingo@elte.hu, hugh@veritas.com,
stefanr@s5r6.in-berlin.de
Subject: Re: almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as well
Date: Thu, 20 Dec 2007 23:48:29 +0200 [thread overview]
Message-ID: <84144f020712201348k117b7db5x6ab71de796bdee5b@mail.gmail.com> (raw)
In-Reply-To: <476A7E7E.7030704@davidnewall.com>
Hi,
On Dec 20, 2007 4:38 PM, David Newall <david@davidnewall.com> wrote:
> >>> and another one, this time tainted with the nvidia module:
> >>> 5194.130985] Unable to handle kernel paging request at 0000030000000000
> >>> RIP:
>
> Numbers like that don't suggest hardware faults. All those zeros: It's
> far too round. Sounds very like software. In fact, it sounds like the
> start of significant hardware region.
Nah, it's just that vma->anon_vma is probably supposed to be NULL here. And if
you look at all the oopses, they do suggest one particular byte lane
is dodgy (the
corruption is in bits 41-43 and 45).
The whole thing reminds me of another bug where memtest86 didn't find anything
because it's doing cached memory accesses: http://lkml.org/lkml/2007/10/3/259
Pekka
next prev parent reply other threads:[~2007-12-20 21:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 0:06 almost daily Kernel oops with 2.6.23.9 Hemmann, Volker Armin
2007-12-17 14:59 ` almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as well Hemmann, Volker Armin
2007-12-17 15:47 ` Hugh Dickins
2007-12-17 19:44 ` Hemmann, Volker Armin
2007-12-20 2:13 ` Hemmann, Volker Armin
2007-12-20 3:50 ` Scott
2007-12-20 5:53 ` Hemmann, Volker Armin
2007-12-20 14:38 ` David Newall
2007-12-20 18:37 ` Hemmann, Volker Armin
2007-12-20 21:48 ` Pekka Enberg [this message]
2007-12-20 22:13 ` Ingo Molnar
[not found] ` <1198134579.4429.10.camel@homer.simson.net>
2007-12-20 18:14 ` Hemmann, Volker Armin
2007-12-21 7:47 ` Mike Galbraith
2007-12-21 12:54 ` Hemmann, Volker Armin
2007-12-20 15:25 ` Stefan Richter
2007-12-20 18:12 ` Hemmann, Volker Armin
2007-12-20 19:04 ` Ingo Molnar
2007-12-20 20:29 ` Hemmann, Volker Armin
2007-12-21 2:09 ` Hemmann, Volker Armin
2007-12-21 11:19 ` Ingo Molnar
2007-12-29 23:03 ` Hemmann, Volker Armin
2007-12-20 19:06 ` Stefan Richter
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=84144f020712201348k117b7db5x6ab71de796bdee5b@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=david@davidnewall.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@bluecamel.eml.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stefanr@s5r6.in-berlin.de \
--cc=volker.armin.hemmann@tu-clausthal.de \
/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
all inboxes | Powered by JetHome®