Message-ID: <4553A6C9.4010906@scientia.net>
Date: Thu, 09 Nov 2006 23:08:09 +0100
From: Christoph Anton Mitterer <calestyo@scientia.net>
User-Agent: Icedove 1.5.0.7 (X11/20061014)
MIME-Version: 1.0
To: Roger Heflin <rheflin@atipa.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: Strange write errors on FAT32 partition (maybe an FAT32 bug?!)
References: <4550A481.2010408@scientia.net> <87psbzrss2.fsf@duaron.myhome.or.jp> <4553744E.3050007@scientia.net> <45539188.5080607@atipa.com> <45539366.7070809@scientia.net> <45539588.7020504@atipa.com> <45539699.40105@scientia.net> <45539753.7060906@atipa.com> <4553A461.4080002@scientia.net> <4553A57C.5070503@atipa.com>
In-Reply-To: <4553A57C.5070503@atipa.com>
Content-Type: multipart/mixed;
 boundary="------------030003020208020204080606"
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2520
Lines: 69

This is a multi-part message in MIME format.
--------------030003020208020204080606
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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?

--------------030003020208020204080606
Content-Type: text/x-vcard; charset=utf-8;
 name="calestyo.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="calestyo.vcf"

YmVnaW46dmNhcmQNCmZuOk1pdHRlcmVyLCBDaHJpc3RvcGggQW50b24NCm46TWl0dGVyZXI7
Q2hyaXN0b3BoIEFudG9uDQplbWFpbDtpbnRlcm5ldDpjYWxlc3R5b0BzY2llbnRpYS5uZXQN
CngtbW96aWxsYS1odG1sOlRSVUUNCnZlcnNpb246Mi4xDQplbmQ6dmNhcmQNCg0K
--------------030003020208020204080606--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/