1 |
Am 28.03.2015 um 23:00 schrieb Sebas Pedersen: |
2 |
> On 28-03-2015 06:45 PM, Volker Armin Hemmann wrote: |
3 |
>> Am 28.03.2015 um 14:58 schrieb Sebas Pedersen: |
4 |
>>> Hi guys, |
5 |
>>> |
6 |
>>> From a few days ago I am experimenting an MCE error. |
7 |
>>> Sometimes I turn on the computer and at some point while booting the |
8 |
>>> kernel (after the grub menu) just freezes and puts this: |
9 |
>>> |
10 |
>>> CPU 0: Machine Check Exception: 4 Bank 4: b200000000070f0f |
11 |
>>> TSC f5acc9180 |
12 |
>>> PROCESSOR 2:20fc2 TIME 1427486735 SOCKET 0 APIC 0 microcode 0 |
13 |
>>> |
14 |
>>> the number for TSC may vary, but the b200000000070f0f it's always the |
15 |
>>> same (at least for now). The error message suggest to parse the above |
16 |
>>> error with mcelog. I did that and the result was: |
17 |
>>> |
18 |
>>> Hardware event. This is not a software error. |
19 |
>>> CPU 0 4 northbridge TSC f5acc9180 |
20 |
>>> TIME 1427486735 Fri Mar 27 17:05:35 2015 |
21 |
>>> Northbridge Watchdog error |
22 |
>>> bit57 = processor context corrupt |
23 |
>>> bit61 = error uncorrected |
24 |
>>> bus error 'generic participation, request timed out |
25 |
>>> generic error mem transaction |
26 |
>>> generic access, level generic' |
27 |
>>> STATUS b200000000070f0f MCGSTATUS 4 |
28 |
>>> CPUID Vendor AMD Family 15 Model 44 |
29 |
>>> SOCKET 0 APIC 0 microcode 0 |
30 |
>>> |
31 |
>>> The error suggest it's a hardware problem. I replace de RAM with no |
32 |
>>> luck. Same error keeps happening. |
33 |
>>> |
34 |
>>> Any suggestion for identifying the problem or how to procede? |
35 |
>>> |
36 |
>>> Many thanks in advance! |
37 |
>>> |
38 |
>>> Sebas |
39 |
>>> |
40 |
>>> |
41 |
>> |
42 |
>> bios update/microcode update. A google search suggests that you have run |
43 |
>> into an errata. |
44 |
> |
45 |
> Oh OK, thank you. Must have miss that in the search. So you are saying |
46 |
> that the error comes from a bios errata (and don't know what microdode |
47 |
> is), and the fix is to update bios? |
48 |
|
49 |
no, possibly from a CPU errata and a bios update might bring in the |
50 |
microcode update that works around that. |