All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 103351] Machine check exception on Broadwell quad-core with SpeedStep enabled
Date: Sat, 26 Sep 2015 03:03:32 +0000	[thread overview]
Message-ID: <bug-103351-137361-SlVQuSgyk6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-103351-137361@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=103351

Adrienne Cohea <adriennecohea@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adriennecohea@gmail.com

--- Comment #13 from Adrienne Cohea <adriennecohea@gmail.com> ---
This sounds a lot like what I am experiencing. I am on 4.1.6-1-ARCH #1 SMP
PREEMPT.

I have 100% ability to reproduce the lock up by trying to compile metasploit.
Everything I see in the systemd journal for the mcelog unit is of the form

Processor context corrupt
MCA: Internal Timer error
STATUS be00000000800400 MCGSTATUS 0

The CPU number on which the error occurs is generally 0 but not always.

I see a lot of MCGCAP lines that are the same across MCEs:

MCGCAP 1000c09 APICID 0 SOCKETID 0

APICID 0 (12 of 14 times)
APICID 2 (once)
APICID 4 (once)

Using "processor.max_cstate=0 intel_idle.max_cstate=0 idle=poll" worked for me
so far (but I only have a couple hours of up time; however, I'm now able to
compile stuff without the MCEs that have been happening with extreme regularity
during compiles).

I have not changed any settings in the BIOS, so SpeedStep is still on.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2015-09-26  3:03 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23 13:45 [Bug 103351] New: Machine check exception on Broadwell quad-core with SpeedStep enabled bugzilla-daemon
2015-08-24 12:22 ` [Bug 103351] " bugzilla-daemon
2015-08-30 18:28 ` bugzilla-daemon
2015-08-31  5:55 ` bugzilla-daemon
2015-08-31  8:15 ` bugzilla-daemon
2015-09-01  2:08 ` bugzilla-daemon
2015-09-01  2:38 ` bugzilla-daemon
2015-09-03 22:22 ` bugzilla-daemon
2015-09-04 13:51 ` bugzilla-daemon
2015-09-04 16:06 ` bugzilla-daemon
2015-09-11 10:09 ` bugzilla-daemon
2015-09-14  0:32 ` bugzilla-daemon
2015-09-22 10:48 ` bugzilla-daemon
2015-09-26  3:03 ` bugzilla-daemon [this message]
2015-09-28 14:23 ` bugzilla-daemon
2015-09-28 14:58 ` bugzilla-daemon
2015-09-29  0:47 ` bugzilla-daemon
2015-09-29 16:49 ` bugzilla-daemon
2015-09-29 18:21 ` bugzilla-daemon
2015-09-29 18:26 ` bugzilla-daemon
2015-09-29 18:27 ` bugzilla-daemon
2015-09-29 18:43 ` bugzilla-daemon
2015-09-30  4:13 ` bugzilla-daemon
2015-09-30  4:49 ` bugzilla-daemon
2015-09-30  5:28 ` bugzilla-daemon
2015-09-30  5:43 ` bugzilla-daemon
2015-09-30 13:20 ` bugzilla-daemon
2015-09-30 16:52 ` bugzilla-daemon
2015-10-01  2:17 ` bugzilla-daemon
2015-10-01 11:51 ` bugzilla-daemon
2015-10-01 17:04 ` bugzilla-daemon
2015-10-01 18:58 ` bugzilla-daemon
2015-10-01 18:59 ` bugzilla-daemon
2015-10-01 19:01 ` bugzilla-daemon
2015-10-01 20:09 ` bugzilla-daemon
2015-10-01 21:44 ` bugzilla-daemon
2015-10-01 23:36 ` bugzilla-daemon
2015-10-07 10:42 ` bugzilla-daemon
2015-10-07 11:40 ` bugzilla-daemon
2015-10-07 12:57 ` bugzilla-daemon
2015-10-07 16:36 ` bugzilla-daemon
2015-10-07 16:37 ` bugzilla-daemon
2015-10-07 16:54 ` bugzilla-daemon
2015-10-07 20:21 ` bugzilla-daemon
2015-10-07 21:51 ` bugzilla-daemon
2015-10-08 10:09 ` bugzilla-daemon
2015-10-08 11:47 ` bugzilla-daemon
2015-10-08 11:53 ` bugzilla-daemon
2015-10-08 16:36 ` bugzilla-daemon
2015-10-08 17:22 ` bugzilla-daemon
2015-10-08 17:48 ` bugzilla-daemon
2015-10-08 18:02 ` bugzilla-daemon
2015-10-08 23:21 ` bugzilla-daemon
2015-10-09  1:18 ` bugzilla-daemon
2015-10-09  8:48 ` bugzilla-daemon
2015-10-09 13:20 ` bugzilla-daemon
2015-10-13 20:06 ` bugzilla-daemon
2015-10-14 15:23 ` bugzilla-daemon
2015-10-14 18:21 ` bugzilla-daemon
2015-10-14 20:50 ` bugzilla-daemon
2015-10-14 20:55 ` bugzilla-daemon
2015-10-14 21:14 ` bugzilla-daemon
2015-10-14 21:16 ` bugzilla-daemon
2015-10-14 21:31 ` bugzilla-daemon
2015-10-14 21:43 ` bugzilla-daemon
2015-10-15  1:05 ` bugzilla-daemon
2015-10-15 13:18 ` bugzilla-daemon
2015-10-15 13:19 ` bugzilla-daemon
2015-10-15 13:29 ` bugzilla-daemon
2015-10-15 14:07 ` bugzilla-daemon
2015-10-15 17:04 ` bugzilla-daemon
2015-10-15 18:06 ` bugzilla-daemon
2015-10-16 10:19 ` bugzilla-daemon
2015-10-16 10:24 ` bugzilla-daemon
2015-10-16 11:51 ` bugzilla-daemon
2015-10-16 13:19 ` bugzilla-daemon
2015-10-16 15:43 ` bugzilla-daemon
2015-10-16 15:57 ` bugzilla-daemon
2015-10-16 16:03 ` bugzilla-daemon
2015-10-16 17:17 ` bugzilla-daemon
2015-10-16 17:29 ` bugzilla-daemon
2015-10-16 17:43 ` bugzilla-daemon
2015-10-16 21:09 ` bugzilla-daemon
2015-10-17  5:03 ` bugzilla-daemon
2015-10-18 18:23 ` bugzilla-daemon
2015-10-19 10:16 ` bugzilla-daemon
2015-10-20 12:11 ` bugzilla-daemon
2015-10-21 20:49 ` bugzilla-daemon
2015-10-21 20:56 ` bugzilla-daemon
2015-10-21 20:58 ` bugzilla-daemon
2015-10-21 23:00 ` bugzilla-daemon
2015-10-22 11:32 ` bugzilla-daemon
2015-10-22 20:02 ` bugzilla-daemon
2015-10-23 12:31 ` bugzilla-daemon
2015-10-23 12:35 ` bugzilla-daemon
2015-11-03 12:51 ` bugzilla-daemon
2015-11-03 13:46 ` bugzilla-daemon
2015-11-09 12:10 ` bugzilla-daemon
2015-11-09 12:39 ` bugzilla-daemon
2015-11-09 19:05 ` bugzilla-daemon
2015-11-14 13:43 ` bugzilla-daemon
2015-11-15 15:35 ` bugzilla-daemon
2015-11-15 15:52 ` bugzilla-daemon
2015-11-22 21:43 ` bugzilla-daemon
2015-11-22 23:34 ` bugzilla-daemon
2015-11-25 18:49 ` bugzilla-daemon
2015-12-14 23:07 ` bugzilla-daemon
2016-01-09 23:40 ` bugzilla-daemon
2016-05-09  5:57 ` bugzilla-daemon
2016-05-10  4:26 ` bugzilla-daemon
2016-05-10  5:38 ` bugzilla-daemon

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=bug-103351-137361-SlVQuSgyk6@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-pm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.