From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: Roger Heflin <rheflin@atipa.com>, linux-kernel@vger.kernel.org
Subject: Re: Strange write errors on FAT32 partition (maybe an FAT32 bug?!)
Date: Fri, 10 Nov 2006 10:28:55 +0000 [thread overview]
Message-ID: <1163154536.7900.23.camel@localhost.localdomain> (raw)
In-Reply-To: <4553A6C9.4010906@scientia.net>
Ar Iau, 2006-11-09 am 23:08 +0100, ysgrifennodd Christoph Anton
Mitterer:
> And I've already had diff errors again,..
> so if there had been some parity issue it should have been logged, right?
If it was a PCI side parity error yes. If you have dodgy memory then the
K8 will MCE and report that if the MCE code is loaded. If the memory is
non ECC or the CPU doesn't support ECC memory you'll get silent strange
behaviour, but a long run of memtest86 can usually find any main memory
problems.
Alan
next prev parent reply other threads:[~2006-11-10 10:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 15:21 Christoph Anton Mitterer
2006-11-07 18:55 ` OGAWA Hirofumi
2006-11-07 21:32 ` Christoph Anton Mitterer
2006-11-09 18:32 ` Christoph Anton Mitterer
[not found] ` <45539188.5080607@atipa.com>
2006-11-09 20:45 ` Christoph Anton Mitterer
2006-11-09 20:54 ` Roger Heflin
2006-11-09 20:59 ` Christoph Anton Mitterer
2006-11-09 21:02 ` Roger Heflin
2006-11-09 21:57 ` Christoph Anton Mitterer
2006-11-09 22:02 ` Roger Heflin
2006-11-09 22:08 ` Christoph Anton Mitterer
2006-11-09 22:14 ` Roger Heflin
2006-11-09 22:24 ` Christoph Anton Mitterer
2006-11-09 22:35 ` Roger Heflin
2006-11-09 22:38 ` Christoph Anton Mitterer
2006-11-09 22:42 ` Roger Heflin
2006-11-10 0:45 ` Christoph Anton Mitterer
2006-11-10 10:28 ` Alan Cox [this message]
2006-11-11 16:01 ` Christoph Anton Mitterer
2006-11-09 21:03 ` Roger Heflin
2006-11-09 21:11 ` Christoph Anton Mitterer
2006-11-09 22:23 ` Christoph Anton Mitterer
2006-11-10 1:49 ` OGAWA Hirofumi
2006-11-10 2:55 ` Christoph Anton Mitterer
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=1163154536.7900.23.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=calestyo@scientia.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rheflin@atipa.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
Powered by JetHome