From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Brett Charbeneau <brett@wrl.org>,
Stephen Tweedie <sct@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [brett@wrl.org: Stumped about where to post an Oops!]
Date: 02 Aug 2004 11:21:31 +0100 [thread overview]
Message-ID: <1091442091.2125.11.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <20040726133422.66c42143.akpm@osdl.org>
Hi,
On Mon, 2004-07-26 at 21:34, Andrew Morton wrote:
> The 0x00040004 access address almost looks like some pointer-poisoning
> thing.
It's the result of doing
> 0: 39 72 04 cmp %esi,0x4(%edx) <=====
when %edx is 0x00040000.
That looks to me like a single bit-flip in memory, and get_hash_table is
one of those functions that shows up in traces all the time when you've
got bad memory (it's one of the kernel's hottest functions for doing
list-walks over dynamically-allocated data structures.)
This footprint would definitely have me reaching for memtest86 as the
next step. It certainly has all the hallmarks of a classic bit-flip bad
memory trace.
--Stephen
parent reply other threads:[~2004-08-02 10:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20040726133422.66c42143.akpm@osdl.org>]
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=1091442091.2125.11.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=akpm@osdl.org \
--cc=brett@wrl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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
all inboxes | Powered by JetHome®