From: Mike Bakhterev <mike.bakhterev@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: boot failure on i7-3317u in Samsung 900x3c
Date: Mon, 8 Oct 2012 00:43:16 +0600 [thread overview]
Message-ID: <CACx33gg6Hmh8E0Mv5TLdi5ufZcppHMws8XAdfaThF_Y2QBb5vA@mail.gmail.com> (raw)
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?
next reply other threads:[~2012-10-07 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 18:43 Mike Bakhterev [this message]
2012-10-08 10:09 ` Matt Fleming
2012-10-08 15:17 ` Mike Bakhterev
2012-10-08 16:45 ` Matt Fleming
2012-10-08 17:50 ` Mike Bakhterev
2012-10-08 18:05 ` Luck, Tony
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACx33gg6Hmh8E0Mv5TLdi5ufZcppHMws8XAdfaThF_Y2QBb5vA@mail.gmail.com \
--to=mike.bakhterev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®