| 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: <47A3856D.70906@redhat.com> Date: Fri, 01 Feb 2008 15:47:41 -0500 From: Chris Snook <csnook@...hat.com> To: Gene Heskett <gene.heskett@...il.com> CC: LKML <linux-kernel@...r.kernel.org> Subject: Re: log spamming Gene Heskett wrote: > Greetings; > > I just rebooted to a new config of 2.6.24, basically trying to strip out the > building of modules I don't use. And I enabled a couple of checks that > weren't checked in the kernel-hacking menu. .config posted on request. > > Now the messages log is being spammed at 2-5 second intervals by these: > Feb 1 10:41:08 coyote kernel: [ 3085.501037] MCE: The hardware reports a non > fatal, correctable incident occurred on CPU 0. > Feb 1 10:41:08 coyote kernel: [ 3085.501042] Bank 1: d400400000000152 > Feb 1 10:41:08 coyote kernel: [ 3085.501045] MCE: The hardware reports a non > fatal, correctable incident occurred on CPU 0. > Feb 1 10:41:08 coyote kernel: [ 3085.501048] Bank 2: d40040000000017a > > Always the same 2 addresses. Is this telling me I should be running memtest86 > for a couple of cycles? Those two addresses are in the same cache line, but they are *not* in the same 128-bit ECC block. This is probably a northbridge problem, not a RAM problem. It's not necessarily a hardware problem. I wouldn't be surprised if you swapped CPUs and still got the same result, due to BIOS misconfiguration. -- Chris -- 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