Reply to Message

Reply to Message

View discussion in a popup

Replying to:
1 Copper

DELL Inspiron 5567 MCE Errors On Boot (Linux Kernel)


This issue has been already escalated throughout the web in the past few months, but no solution is found, and there is no word from DELL on fixing or even trying to fix this.

The issue is (and judging by reports it affects mostly DELL laptops with Intel chipsets), that all of a sudden, few months back, my laptop (Inspiron 5567 with Linux Fedora 25) started reporting MCE hardware errors on boot. Everyone's first guess would be that maybe there are a hardware errors indeed, something wrong with some components, but this is not the case. These are fake MCE errors that started affecting a lot of people all of a sudden in the same timeframe. Laptop boots and works perfectly fine after that, but simply it makes your eyes bleed seeing these errors every day, turning your laptop on in front of your coleagues, friends, etc...

This is the report that pops up on boot:

[ 0.078741] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee20000000
[ 0.078745] mce: [Hardware Error]: TSC 0 ADDR fef1ce80 MISC 43880014086
[ 0.078749] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1492078107 SOCKET 0
APIC 0 microcode 4e
[ 0.078751] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee20000000
[ 0.078753] mce: [Hardware Error]: TSC 0 ADDR fef1ce40 MISC 7880014086
[ 0.078755] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1492078107 SOCKET 0
APIC 0 microcode 4e

Like I said there are reports all over the web about these MCE errors, and there was this discussion on Google+ where this guy from Dell, Mario Limonciello, said that this is neither hardware error, nor problem on Linux kernel side, but most likely a problem with device firmware, never coming to conclusion to when or will this ever be fixed.

Now my question is, is anybody at DELL even looking into this? People think of DELL as a very Linux-friendly oriented company, and a lot, like really a lot of people are using Linux on their DELL machines. It would be good then to act like that, not ignoring issues like this, and it's been months since this started happening.