You are not logged in.
Pages: 1
My machine shuts down for no apparent reason...usually when running apt-get update or when trying to load a webpage (running crunchbang at the moment).
The same happens with other distros and with windows (BSOD/shutdown).
I've already ruled out memory module problems (ran memtest86 and also tried new DIMMs) and PSU problems - tested with 2 other PSUs.
The motherboard seems fine too, there are no swollen capacitors.
I'm thinking the CPU might be failing. It's an AMD Athlon64 X2 5600+. I disabled the second core, but that didn't help and sadly I can't disable cpu0 to see what happens then.
Also got a kernel panic at one point:
http://i.imgur.com/uoNYTfK.jpg
After running mcelog, I got the following:
Hardware event. This is not a software error.
CPU 1 1 instruction cache TSC 2a49a304b0
ADDR 122b400
TIME 1413710309 Sun Oct 19 12:18:29 2014
bit57 = processor context corrupt
bit61 = error uncorrected
bit62 = error overflow (multiple errors)
memory/cache error 'snoop mem transaction, instruction transaction, level 1'
STATUS f600000000000181 MCGSTATUS 4
CPUID Vendor AMD Family 15 Model 107
SOCKET 0 APIC 1 microcode 0
Does anyone know how to interpret this?
Last edited by svxiii (2014-10-20 19:48:36)
Offline
That screenshot indicates you are running 32-bit kernels with PAE enabled ?
Are you also running 32-bit / pae on windows and those other distros you tried ?
Either way, try running a 64-bit kernel .
NOTE : if it's really a hardware problem, running 64-bit won't help.
However, PAE often has problems and 32-bit linux tends to get less attention then 64-bit nowadays.
Last edited by Lone_Wolf (2014-10-21 10:26:33)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I tried with all the LiveCDs that I have. Both 32 and 64 bits. It didn't help.
Now I'm just trying to figure out which part is failing. CPU or mobo...
I've ruled out everything else.
Now despite the fact that the error was about cpu1, disabling it didn't help and unfortunately I can't disable cpu0.
Last edited by svxiii (2014-10-21 11:11:21)
Offline
Pages: 1