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, 17 Oct 2015 05:03:04 +0000 [thread overview]
Message-ID: <bug-103351-137361-BtIqtrCvLw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-103351-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=103351
--- Comment #83 from Adrienne Cohea <adriennecohea@gmail.com> ---
(In reply to Henrique de Moraes Holschuh from comment #80)
> Adrienne, it could be really helpful if you could tell us more about your
> system, since it has always had RTM disabled, even with microcode 0xd...
> could you tell us what system is it (make, model), and the output of "dmesg
> | grep microcode" and /proc/cpuinfo, please?
Hey, everyone, I'm sorry it took me so long! This issue is important to
everyone. So what follows will be kind of a big dump of information, but I
don't know what all will be meaningful to everyone. So I've got 1) General
information, 2) BIOS-reported information, and 3) dmesg | grep microcode 4) cat
/proc/cpuinfo.
1) General Information
OEM: CyberPowerPC
Model Marketing Name: Fangbook III BX6
2) BIOS-Reported Information
BIOS Version: E16J2ICP.10E
EC Version 16J2ECP1 Ver5.06
CPU: Intel Core i7-5700HQ
Stepping: 40671
Microcode patch: d (Note, before boot...)
3) dmesg | grep microcode
-- on microcode 0xd --
[ 0.432493] microcode: CPU0 sig=0x40671, pf=0x20, revision=0xd
[ 0.432498] microcode: CPU1 sig=0x40671, pf=0x20, revision=0xd
[ 0.432503] microcode: CPU2 sig=0x40671, pf=0x20, revision=0xd
[ 0.432508] microcode: CPU3 sig=0x40671, pf=0x20, revision=0xd
[ 0.432513] microcode: CPU4 sig=0x40671, pf=0x20, revision=0xd
[ 0.432518] microcode: CPU5 sig=0x40671, pf=0x20, revision=0xd
[ 0.432522] microcode: CPU6 sig=0x40671, pf=0x20, revision=0xd
[ 0.432528] microcode: CPU7 sig=0x40671, pf=0x20, revision=0xd
[ 0.432559] microcode: Microcode Update Driver: v2.00
<tigran@aivazian.fsnet.co.uk>, Peter Oruba
-- on microcode 0x12 --
[ 0.000000] microcode: CPU0 microcode updated early to revision 0x12, date =
2015-06-19
[ 0.076100] microcode: CPU1 microcode updated early to revision 0x12, date =
2015-06-19
[ 0.083977] microcode: CPU2 microcode updated early to revision 0x12, date =
2015-06-19
[ 0.091894] microcode: CPU3 microcode updated early to revision 0x12, date =
2015-06-19
[ 0.434008] microcode: CPU0 sig=0x40671, pf=0x20, revision=0x12
[ 0.434014] microcode: CPU1 sig=0x40671, pf=0x20, revision=0x12
[ 0.434019] microcode: CPU2 sig=0x40671, pf=0x20, revision=0x12
[ 0.434023] microcode: CPU3 sig=0x40671, pf=0x20, revision=0x12
[ 0.434028] microcode: CPU4 sig=0x40671, pf=0x20, revision=0x12
[ 0.434033] microcode: CPU5 sig=0x40671, pf=0x20, revision=0x12
[ 0.434037] microcode: CPU6 sig=0x40671, pf=0x20, revision=0x12
[ 0.434043] microcode: CPU7 sig=0x40671, pf=0x20, revision=0x12
[ 0.434075] microcode: Microcode Update Driver: v2.00
<tigran@aivazian.fsnet.co.uk>, Peter Oruba
4) cat /proc/cpuinfo (showing CPU 0 only)
-- on microcode 0xd --
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 71
model name : Intel(R) Core(TM) i7-5700HQ CPU @ 2.70GHz
stepping : 1
microcode : 0xd
cpu MHz : 2113.171
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc a
perfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma
cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes
xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm
intel_pt
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2
erms invpcid rdseed adx smap xsaveopt
bugs :
bogomips : 5389.86
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
-- on microcode 0x12 --
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 71
model name : Intel(R) Core(TM) i7-5700HQ CPU @ 2.70GHz
stepping : 1
microcode : 0x12
cpu MHz : 2701.054
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc a
perfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma
cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes
xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm
intel_pt
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2
erms invpcid rdseed adx smap xsaveopt
bugs :
bogomips : 5390.35
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
When I "diffed" the /proc/cpuinfo outputs I saved off, only differences were in
microcode of course, bogomips, and cpu MHz. The following commands have always
returned no hits for me, even on the 0xd microcode that came stock:
grep flags /proc/cpuinfo | grep tsx
grep flags /proc/cpuinfo | grep rtm
grep flags /proc/cpuinfo | grep hle
If you need other information like the bridge, let me know. Thanks everyone so
much for explaining the problem and providing a workaround. 0x12 works
brilliantly for me.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-10-17 5: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
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 [this message]
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-BtIqtrCvLw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox