| 1 |
On Sunday 29 Mar 2015 16:42:10 Sebas Pedersen wrote: |
| 2 |
> On 28-03-2015 08:50 PM, Mick wrote: |
| 3 |
> > On Saturday 28 Mar 2015 22:48:48 Sebas Pedersen wrote: |
| 4 |
> >> On 28-03-2015 07:37 PM, Volker Armin Hemmann wrote: |
| 5 |
> >> > Am 28.03.2015 um 23:00 schrieb Sebas Pedersen: |
| 6 |
> >> >> On 28-03-2015 06:45 PM, Volker Armin Hemmann wrote: |
| 7 |
> >> >>> Am 28.03.2015 um 14:58 schrieb Sebas Pedersen: |
| 8 |
> >> >>>> Hi guys, |
| 9 |
> >> >>>> |
| 10 |
> >> >>>> From a few days ago I am experimenting an MCE error. |
| 11 |
> >> >>>> Sometimes I turn on the computer and at some point while booting |
| 12 |
> >> >>>> the kernel (after the grub menu) just freezes and puts this: |
| 13 |
> >> >>>> |
| 14 |
> >> >>>> CPU 0: Machine Check Exception: 4 Bank 4: b200000000070f0f |
| 15 |
> >> >>>> TSC f5acc9180 |
| 16 |
> >> >>>> PROCESSOR 2:20fc2 TIME 1427486735 SOCKET 0 APIC 0 microcode 0 |
| 17 |
> >> >>>> |
| 18 |
> >> >>>> the number for TSC may vary, but the b200000000070f0f it's always |
| 19 |
> >> >>>> the |
| 20 |
> >> >>>> same (at least for now). The error message suggest to parse the |
| 21 |
> >> >>>> above |
| 22 |
> >> >>>> error with mcelog. I did that and the result was: |
| 23 |
> >> >>>> |
| 24 |
> >> >>>> Hardware event. This is not a software error. |
| 25 |
> >> >>>> CPU 0 4 northbridge TSC f5acc9180 |
| 26 |
> >> >>>> TIME 1427486735 Fri Mar 27 17:05:35 2015 |
| 27 |
> >> >>>> |
| 28 |
> >> >>>> Northbridge Watchdog error |
| 29 |
> >> >>>> |
| 30 |
> >> >>>> bit57 = processor context corrupt |
| 31 |
> >> >>>> bit61 = error uncorrected |
| 32 |
> >> >>>> |
| 33 |
> >> >>>> bus error 'generic participation, request timed out |
| 34 |
> >> >>>> |
| 35 |
> >> >>>> generic error mem transaction |
| 36 |
> >> >>>> generic access, level generic' |
| 37 |
> >> >>>> |
| 38 |
> >> >>>> STATUS b200000000070f0f MCGSTATUS 4 |
| 39 |
> >> >>>> CPUID Vendor AMD Family 15 Model 44 |
| 40 |
> >> >>>> SOCKET 0 APIC 0 microcode 0 |
| 41 |
> >> >>>> |
| 42 |
> >> >>>> The error suggest it's a hardware problem. I replace de RAM with no |
| 43 |
> >> >>>> luck. Same error keeps happening. |
| 44 |
> >> >>>> |
| 45 |
> >> >>>> Any suggestion for identifying the problem or how to procede? |
| 46 |
> >> >>>> |
| 47 |
> >> >>>> Many thanks in advance! |
| 48 |
> >> >>>> |
| 49 |
> >> >>>> Sebas |
| 50 |
> >> >>> |
| 51 |
> >> >>> bios update/microcode update. A google search suggests that you have |
| 52 |
> >> >>> run |
| 53 |
> >> >>> into an errata. |
| 54 |
> >> >> |
| 55 |
> >> >> Oh OK, thank you. Must have miss that in the search. So you are |
| 56 |
> >> >> saying that the error comes from a bios errata (and don't know what |
| 57 |
> >> >> microdode is), and the fix is to update bios? |
| 58 |
> >> > |
| 59 |
> >> > no, possibly from a CPU errata and a bios update might bring in the |
| 60 |
> >> > microcode update that works around that. |
| 61 |
> >> |
| 62 |
> >> I see, thanks for clarifying that. So looks like not too many options, |
| 63 |
> >> either try to update the bios and/or replace the CPU. |
| 64 |
> >> |
| 65 |
> >> I really appreciated you replys and time. |
| 66 |
> >> |
| 67 |
> >> Thanks!, |
| 68 |
> >> Sebas |
| 69 |
> > |
| 70 |
> > There's 'CONFIG_MICROCODE=y' and friends in the kernel which along with |
| 71 |
> > sys- |
| 72 |
> > apps/microcode-ctl will load what ever is the latest Intel/AMD CPU code |
| 73 |
> > (firmware) to patch any bugs with instructions that the CPU |
| 74 |
> > manufacturers have |
| 75 |
> > discovered. |
| 76 |
> |
| 77 |
> That's nice. I'm gonna compile the kernel and see what happends. |
| 78 |
> |
| 79 |
> Many thanks! |
| 80 |
|
| 81 |
Don't forget to enable the relevant module for your type of CPU. |
| 82 |
-- |
| 83 |
Regards, |
| 84 |
Mick |
Archives