From: Neil Romig <neil@romig.demon.co.uk>
To: Dave Jones <davej@redhat.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: File corruption in 2.6.18 thru 2.6.22
Date: Thu, 23 Aug 2007 20:12:31 +0000 [thread overview]
Message-ID: <46CDEA2F.6040508@romig.demon.co.uk> (raw)
In-Reply-To: <20070823001634.GC18739@redhat.com>
Dave Jones wrote:
> On Sat, Aug 18, 2007 at 02:42:45PM +0000, Neil Romig wrote:
>
> > Everything is O.K using kernel 2.6.17.14, but 2.6.18 and beyond all have
> > this problem. It may take me months to sort this out on my own - any
> > suggestions?
>
> In most (though not all), a single bit was flipped.
> This is usually a sign of bad memory.
> Give it a going over with memtest86+ ?
>
> Dave
>
I have run memtest86+ twice without error, so I remain stumped. I can set up a loop to copy
a file and do a diff which runs OK, but when I boot 2.6.18 it drops out within a second or two.
Neil.
prev parent reply other threads:[~2007-08-23 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 14:42 File corruption in 2.6.18 thru 2.6.22 Neil Romig
2007-08-23 0:16 ` Dave Jones
2007-08-23 20:12 ` Neil Romig [this message]
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=46CDEA2F.6040508@romig.demon.co.uk \
--to=neil@romig.demon.co.uk \
--cc=davej@redhat.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).