From: Jens Axboe <axboe@suse.de>
To: "Nathaniel W. Filardo" <nwf@andrew.cmu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File system cache corruption in 2.6?
Date: Mon, 5 Jan 2004 13:19:05 +0100 [thread overview]
Message-ID: <20040105121905.GB3124@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58-035.0401050014450.5565@unix49.andrew.cmu.edu>
On Mon, Jan 05 2004, Nathaniel W. Filardo wrote:
> Hi all,
> I'm trying to work out the cause of a series of issues I've seen
> on my 2.6 machine. It appears as though files (specifically libraries) in
> memory can get corrupted, resulting in strangeness like segfaults and
> things like "relocation error: can't find symbol ...-VOMD-POINTER" instead
> of "...-VOID-POINTER".
That's a single bit error.
> I don't believe it's actual hardware failure for a few reasons: memtest86
> passes all tests, GCC doesn't crash (it's a Gentoo system, so gcc and I
> are well acquainted - and before I get jumped on, I've installed udev ;)
> ), and most importantly, sometimes thrashing the file system or engaging a
> kernel compile will rectify the situation, as just happened with emacs.
> It crashed, I killed it, it wouldn't load - I started a kernel compile,
> waited a bit, and lo', it works again. No messages of relevance appear in
> dmesg.
It looks _extremely_ much like bad memory, or bad hardware. Sometimes
memtest just doesn't catch all errors (how long did you run it? needs
several days often).
--
Jens Axboe
next prev parent reply other threads:[~2004-01-05 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 5:28 Nathaniel W. Filardo
2004-01-05 12:19 ` Jens Axboe [this message]
2004-01-05 21:29 ` Martin Schlemmer
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=20040105121905.GB3124@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nwf@andrew.cmu.edu \
/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®