| 1 |
On Tue, 4 Sep 2007 06:51:38 +1000 |
| 2 |
"Alan E. Davis" <lngndvs@×××××.com> wrote: |
| 3 |
|
| 4 |
> I think your solution is the better one, though. |
| 5 |
> |
| 6 |
> I did follow the instructions of the boot messages and installed an |
| 7 |
> mce log translation utility, but I didn't make sense of what to do |
| 8 |
> with it. |
| 9 |
|
| 10 |
The thing is, you are only masking symptoms. There may be something |
| 11 |
wrong, and perhaps you could save a lot of work later by fixing a |
| 12 |
problem before it turns catastrophic. |
| 13 |
|
| 14 |
from http://en.wikipedia.org/wiki/Machine_Check_Exception |
| 15 |
|
| 16 |
A Machine Check Exception, also called MCE, is a computer hardware |
| 17 |
error which occurs when a computer's central processing unit detects an |
| 18 |
unrecoverable hardware problem. |
| 19 |
|
| 20 |
Normal causes for MCE errors are overheating and/or incorrect hardware |
| 21 |
installation. Overheating can cause electrons to become more animated |
| 22 |
and thus escape from the silicon tracks, resulting in corrupted data. |
| 23 |
Some specific manually induced causes could be: |
| 24 |
|
| 25 |
Overclocking (naturally increases heat output) |
| 26 |
|
| 27 |
Poorly fitted heatsink/computer fans (the same problem can happen with |
| 28 |
excessive dust in the CPU fan) |
| 29 |
|
| 30 |
Computer software can also cause errors in this way (normally by |
| 31 |
corrupting data they are reading or writing). For example: |
| 32 |
|
| 33 |
-Software performing read or write operations to non-existent memory |
| 34 |
regions which leads to confusion for the processor and/or the system |
| 35 |
bus. |
| 36 |
|
| 37 |
3rd party programs |
| 38 |
|
| 39 |
mcelog |
| 40 |
mcelog is a Linux program to decode MCE's on x86-64 processors |
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-user@g.o mailing list |
Archives