| 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: <87r66598eq.fsf@basil.nowhere.org> Date: Fri, 24 Oct 2008 20:04:29 +0200 From: Andi Kleen <andi@...stfloor.org> To: Felix von Leitner <felix-linuxkernel@...e.de> Cc: Linux Kernel Mailing list <linux-kernel@...r.kernel.org> Subject: Re: MCEs Felix von Leitner <felix-linuxkernel@...e.de> writes: > This is the kind of MCE that freezes the box and causes a panic. The > trace does not end up in syslog. I found a program called mcelog which > I am supposed to call regularly from cron, but how can that help me when > the first MCE I get insta-panics the box? When you do a warm boot (not power cycle, but reset button or panic=30) then the panic mce will be logged after reboot. > Now the most common causes for MCEs are apparently heat issues and bad > memory. I can rule out both. Could this be an artifact of some bad > ACPI tables? > > How do you debug this kind of problem? It's some sort of hardware problem, debugging it typically either involves fixing the cooling or exchanging components. -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