On 2014-11-15 15:21, LoneVVolf wrote:
On 15-11-14 06:57, Rasmus Liland wrote:
On 11/14/2014 10:29 PM, Rasmus Liland wrote:
On 2014-11-15 04:01, Mark Lee wrote:
Are you booting with the new intel u-code? Are you fairly sure this is a Intel microcode issue? I'm not completely certain; but it would make sense. I'd test it out. Thank you for your help thus far. I'll examine this further tomorrow, g'night. From rasmus first post: I'm experiencing machine check exceptions since every kernel after package
On 2014-11-15 06:10, Mark Lee wrote: linux-3.11.5-1 (Oct 14 2013) New intel microcode was only introduced with kernel 3.17 ... It's unlikely to have to do with this issue.
install mcelog, run it as the log tells you and post the result. Thank you for your new, important thoughts. I put the lines in a file called mce.log.
rasmus@angrist ~ % cat mce.log [19367.116196] mce: [Hardware Error]: CPU 1: Machine Check Exception: 5 Bank 4: b200000000100402 [19367.116202] mce: [Hardware Error]: RIP !INEXACT! 33:<00007f8b4934c8b7> [19367.116205] mce: [Hardware Error]: TSC 2824672b8e7 [19367.116211] mce: [Hardware Error]: PROCESSOR 0:306a9 TIME 14010118857 SOCKET 0 APIC 1 microcode 12 rasmus@angrist ~ % sudo mcelog --ascii < mce.log mce: [Hardware Error]: CPU 1: Machine Check Exception: 5 Bank 4: b200000000100402 mce: [Hardware Error]: RIP !INEXACT! 33:<00007f8b4934c8b7> mce: [Hardware Error]: TSC 2824672b8e7 mce: [Hardware Error]: PROCESSOR 0:306a9 TIME 14010118857 SOCKET 0 APIC 1 microcode 12 I never did use the mcelog tool before, but to me it looks like not much of an analysis, perhaps I'm doing it wrong. -- Rasmus Liland, jrl@jrl.dyndns.dk