| 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: <200803301657.53232.gene.heskett@gmail.com> Date: Sun, 30 Mar 2008 16:57:53 -0400 From: Gene Heskett <gene.heskett@...il.com> To: linux-kernel@...r.kernel.org Subject: MCE going wild, 14 megs of this in the logs Greetings; Mar 30 16:46:42 coyote kernel: [469249.031832] MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0. Mar 30 16:46:42 coyote kernel: [469249.031838] Bank 1: d400400000000152 Mar 30 16:46:42 coyote kernel: [469249.031841] MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0. Mar 30 16:46:42 coyote kernel: [469249.031844] Bank 2: d40040000000017a Its always the same 2 addresses reported, and every 15 seconds. So I have the non-fatal part of MCE now turned off, & 2.6.24.4 rebuilding. I saw this once before, and a nearly round the clock run of memtest86 gave my memory a clean bill. Processor is an XP-2800, biostar mainboard with NForce2 chipset. Is this possibly a known artifact of this hardware? -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If I am elected, the concrete barriers around the WHITE HOUSE will be replaced by tasteful foam replicas of ANN MARGARET! -- 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