Comment 2 for bug 446480

X86_MCE (Machine Check Exception) use cases/justification:

- David's laptop is running slowly with no indication why
 -> before moving his workflow over to Microsoft Windows, he (spending considerable time) rebuilds the kernel with CONFIG_X86_MCE after finding a tip on a forum
 -> after booting into his built kernel, he sees MCE reports in 'dmesg' saying that the processor is raising thermal trip (PROC_HOT#) events and is being throttled
 -> he cleans out a load of fluff from the heatsink air-flow path and performance is restored

- Jane is frustrated that occasionally on her desktop, processes get hit by SIGSEGV, SIGILL and SIGBUS, so she raises a launchpad report, but nothing looks suspicious and engineers at Canonical cannot reproduce the problem
 -> she switches to Windows and experiences the same issues
 -> after checking the Windows Event Log, she learns Machine Check Exceptions are being raised from the processor with timed-out memory reads. She replaces the memory in her desktop, resolving the problem and stays using Windows