FS#58681 - [linux-firmware] Random crash/reboot on AMD Ryzen 5 1600

Attached to Project: Arch Linux
Opened by Peter (protake) - Monday, 21 May 2018, 12:00 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 27 May 2018, 06:03 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Laurent Carlier (lordheavy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

My PC just randomly crashed without any further notice. This is what dmesg says after the reboot:

[ 0.036666] smpboot: CPU0: AMD Ryzen 5 1600 Six-Core Processor (family: 0x17, model: 0x1, stepping: 0x1)
[ 0.046689] Performance Events: Fam17h core perfctr, AMD PMU driver.
[ 0.046695] ... version: 0
[ 0.046695] ... bit width: 48
[ 0.046696] ... generic registers: 6
[ 0.046697] ... value mask: 0000ffffffffffff
[ 0.046697] ... max period: 00007fffffffffff
[ 0.046698] ... fixed-purpose events: 0
[ 0.046698] ... event mask: 000000000000003f
[ 0.053346] Hierarchical SRCU implementation.
[ 0.073472] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[ 0.080012] smp: Bringing up secondary CPUs ...
[ 0.110030] x86: Booting SMP configuration:
[ 0.110032] .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11
[ 0.412290] mce: [Hardware Error]: Machine check events logged
[ 0.412290] mce: [Hardware Error]: CPU 11: Machine Check: 0 Bank 5: bea0000000000108
[ 0.412290] mce: [Hardware Error]: TSC 0 ADDR 1ffffa4800080 MISC d012000101000000 SYND 4d000000 IPID 500b000000000
[ 0.412290] mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1526903373 SOCKET 0 APIC d microcode 8001129
[ 0.412290] smp: Brought up 1 node, 12 CPUs

My guess is that this is related to the newest microcode update from AMD.
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Sunday, 27 May 2018, 06:03 GMT
Reason for closing:  None
Comment by Laurent Carlier (lordheavy) - Monday, 21 May 2018, 15:20 GMT Comment by Peter (protake) - Saturday, 26 May 2018, 22:29 GMT
Thanks for your suggestion. Maybe I was just jumping to conclusions here. It didn't happen again.

Loading...