From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Roger Heflin <rheflin@atipa.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange write errors on FAT32 partition (maybe an FAT32 bug?!)
Date: Thu, 09 Nov 2006 23:08:09 +0100 [thread overview]
Message-ID: <4553A6C9.4010906@scientia.net> (raw)
In-Reply-To: <4553A57C.5070503@atipa.com>
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
Roger Heflin wrote:
> The mc part does pci parity, it is separate from the
> chipset driver,
What? I thought the MC part does ECC and the pci part the parity stuff?
> I have even used the _mc part on a
> Itanium with no chipset driver at all and had it report
> parity errors properly, so I expect just the mc driver
> to work.
>
> You would need the k8 module for the cpu, but that is
> only if you want ECC checking also.
>
Where do I get this only when patching from CVS?
> If you got the _mc loaded do a "sysctl -a | grep mc" and
> see what things are set how, and reset if necessary
> check_pci_parity to 1.
Well ok,.. module is loaded now:
I've set check_pci_parity to 1 everything else is 0 in sysfs...
# sysctl -a | grep mc
error: "Operation not permitted" reading key "net.ipv6.route.flush"
net.ipv6.neigh.eth1.mcast_solicit = 3
net.ipv6.neigh.eth0.mcast_solicit = 3
net.ipv6.neigh.lo.mcast_solicit = 3
net.ipv6.neigh.default.mcast_solicit = 3
net.ipv4.conf.ppp0.mc_forwarding = 0
net.ipv4.conf.eth1.mc_forwarding = 0
net.ipv4.conf.eth0.mc_forwarding = 0
net.ipv4.conf.lo.mc_forwarding = 0
net.ipv4.conf.default.mc_forwarding = 0
net.ipv4.conf.all.mc_forwarding = 0
net.ipv4.neigh.ppp0.mcast_solicit = 3
net.ipv4.neigh.eth1.mcast_solicit = 3
net.ipv4.neigh.eth0.mcast_solicit = 3
net.ipv4.neigh.lo.mcast_solicit = 3
net.ipv4.neigh.default.mcast_solicit = 3
error: "Operation not permitted" reading key "net.ipv4.route.flush"
error: "Invalid argument" reading key "fs.binfmt_misc.register"
But this has nothing to do with edac, has it?
And I've already had diff errors again,..
so if there had been some parity issue it should have been logged, right?
[-- Attachment #2: calestyo.vcf --]
[-- Type: text/x-vcard, Size: 156 bytes --]
begin:vcard
fn:Mitterer, Christoph Anton
n:Mitterer;Christoph Anton
email;internet:calestyo@scientia.net
x-mozilla-html:TRUE
version:2.1
end:vcard
next prev parent reply other threads:[~2006-11-09 22:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 15:21 Strange write errors on FAT32 partition (maybe an FAT32 bug?!) 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 [this message]
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
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=4553A6C9.4010906@scientia.net \
--to=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