linux-kernel - boot failure on i7-3317u in Samsung 900x3c

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-next>] [day] [month] [year] [list]

Date:	Mon, 8 Oct 2012 00:43:16 +0600
From:	Mike Bakhterev <mike.bakhterev@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: boot failure on i7-3317u in Samsung 900x3c

Greetings.

When i'm trying to boot the subject maching in UEFI mode i get
sometimes machine check exception 0xbe2000000003110a (i was not able
to decode this, as some bits are not covered in Intel's Manuals). It
emerges when i am booting 3.4.x, 3.5.4 and 3.5.5 kernels from
ArchLinux. When i am booting from SSD i get this error all the time,
when i'm booting from USB stick i get this sometimes (quite frequently
and the probability to boot succesfully is increased when i specify
"verbose" kernel option). I'm booting with systemd. The sytems boots
always successfully, when i use the installation ArchLinux image,
which is shipped with 3.5 kernel and boots in BIOS mode with
traditional initscripts.

It looks like race condition when configuring memory or something like this.

It is not hardware error, because Windows 7 and 8 boot and run fine.
And this is my second unit, because the first one was broken
(something with motherboard) when running Windows 8, and Linux on that
broken machine reported the same MCE. Now Windows works OK (if you
could say, it works), and Linux reports the same MCEs.

Here is some guy playing with caching of PCI memory region and getting
the same MCE on the Sandy Bridge:
http://stackoverflow.com/questions/11254023/how-to-do-mmap-for-cacheable-pcie-bar

Sorry, but i have no time to bisect this :(

P.S. Excuse me my English.

P.P.S. Can this be fixed with kernel command line options?
--
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/