| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <p73d4xwg0il.fsf@bingen.suse.de> Date: 09 Aug 2007 18:01:38 +0200 From: Andi Kleen <andi@...stfloor.org> To: Phil Moors <pmoors@...akeasy.net> Cc: linux-kernel@...r.kernel.org Subject: Re: EDAC k8 MC1: unknown syndrome Phil Moors <pmoors@...akeasy.net> writes: > > But is the error really reporting a DIMM problem or a race condition in > the kernel code handling ECC? First if you don't use a mainline kernel you should at least mention it in the report. It could well be a race -- the k8 DAC code is always racing against the builtin machine check handler which reads the same registers. That is why it was never accepted for mainline and shouldn't be used. However these races should normally only cause lost events, not bogus data, so it's probably something the CPU really reported and EDAC doesn't understand. The builtin machine check code will report all the same information through mcelog (on x86-64) or syslog (on i386) -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists