From: "Stephen C. Tweedie" <sct@redhat.com>
To: Gavin Baker <gavbaker@ntlworld.com>
Cc: linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: 2.4.13-ac7 ext3 OOPS
Date: Thu, 22 Nov 2001 20:24:32 +0000 [thread overview]
Message-ID: <20011122202432.A11821@redhat.com> (raw)
In-Reply-To: <20011118205039.A3208@box.penguin.power>
In-Reply-To: <20011118205039.A3208@box.penguin.power>; from gavbaker@ntlworld.com on Sun, Nov 18, 2001 at 08:50:39PM +0000
Hi,
On Sun, Nov 18, 2001 at 08:50:39PM +0000, Gavin Baker wrote:
> A seemingly random OOPS while using netscape. 2.4.13-ac7 with preempt patches on a RH7.2 laptop.
> Nov 18 13:12:45 n-files kernel: EIP: 0010:[get_hash_table+107/208] Not tainted
get_hash_table oopses are almost always caused by bad memory. For
some reason, the buffer cache hashes are peculiarly sensitive to
corruptions.
> Nov 18 13:12:45 n-files kernel: eax: c1430000 ebx: ffffffff ecx: 00000002 edx: 00003859
It's not enough to be conclusive, but the other common footprint of
random memory corruption is register dumps containing a value which is
all-zeroes except for one flipped bit, like your 0x00000002 value in
%ecx.
Let me know if you can reproduce this, but in the absense of any other
pattern, bad memory is the most likely cause for now.
--Stephen
next prev parent reply other threads:[~2001-11-22 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 20:50 2.4.13-ac7 ext3 OOPS Gavin Baker
2001-11-22 20:24 ` Stephen C. Tweedie [this message]
2001-11-24 15:55 ` Gavin Baker
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=20011122202432.A11821@redhat.com \
--to=sct@redhat.com \
--cc=gavbaker@ntlworld.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox