linux-kernel - Re: AMD A10: MCE Instruction Cache Error

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 4 Nov 2012 16:21:33 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Alexander Holler <holler@...oftware.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: AMD A10: MCE Instruction Cache Error

On Sat, Nov 03, 2012 at 11:45:25AM +0100, Alexander Holler wrote:
> Hmm, exactly that just happened twice in a row. Unfortunately the
> screen was already disabled (screen saving mode), so I couldn't see
> any message, if there was any. Just a dead box (not overclocked, I
> don't do such, I even had enabled the power saving mode in the BIOS,
> which seems to mean max. 3800 MHz). I think I should start getting
> nervous. :(

How do you know this happened twice if you couldn't see any message?

Also, can you enable netconsole or serial console, if possible, and try
to catch full dmesg from the boot and up until it happens.

Also, catch the dmesg of the box on the next time it reboots after the
freeze (btw, try doing a warm reboot because this is the only way we can
preserve valid error information) - if all works ok, it should decode
the MCE before the freeze (if the MCE caused it and it actually is the
reason for the freeze).

> What I meant with another priority is using something else than
> pr_emerg(), because pr_emerge() causes the message to become
> displayed on every console, at least on my F17 with default
> settings.

This is needed because we want those errors to actually be seen.

Thanks.

-- 
Regards/Gruss,
Boris.
--
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/