February 8Feb 8 So I had a Fix Common Problems message today about an MCE Event being triggered. I dumped the logs to check those and saw these lines in there, but I'm unsure what issue these are possibly indicating. I did run memtest and that was fine and after reboot ran "mcelog --ascii" but it just sits there and does nothing (perhaps I should have run this before rebooting?)Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: Machine check events logged Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: CPU 17: Machine Check: 0 Bank 5: bea0000000000108 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff818cbbdc MISC d012000100000000 SYND 4d000000 IPID 500b000000000 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1770372115 SOCKET 0 APIC d microcode 8701034 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: Machine check events logged Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: CPU 21: Machine Check: 0 Bank 5: bea0000000000108 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff81b263f8 MISC d012000100000000 SYND 4d000000 IPID 500b000000000 Feb 6 04:02:17 ShadeNAS kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1770372115 SOCKET 0 APIC 19 microcode 8701034Any insight into what this might be? System is a B450 running a Ryzen 3900X in eco mode with a Perc H200 HBA.
February 9Feb 9 Community Expert Make sure this has been taken care of: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173
February 10Feb 10 Author 4 hours ago, JorgeB said:Make sure this has been taken care of: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173Thanks Jorge. I've seen that before and it hadn't come to mind looking at the issue. Are those sorts of problems likely to be recurring or could they happen out of nowhere and not happen again? I've been running this hardware configuration for a few years now without issue. It's also been running fine since.I am running memory at 3200 which appears to be fine in that thread. The deepest C state it seems to go into according to powertop is C2.
February 10Feb 10 Community Expert It could be related if the RAM is out of spec, if it's not, it could be a CPU issue. A little more voltage may help for the latter.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.