Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

During past month one of my Debian Squeeze (Linux 2.6.32-bpo.5-amd64) machines did lock up twice, hard. No response to ARP, dark console, Caps Lock, Num Lock not working, Magic SysRq ineffective. Changing the kernel to 3.2.0-0.bpo.2-amd64 from backports didn't help either.

Temperature and load monitoring doesn't show any spikes before crash.

How should I diagnose and debug such problem?

Is netconsole my only bet?

EDIT: I've already disabled screen blanking:



setterm -blank 0

on physical console.


This time it locked, the screen was still showing login prompt. Since last problems I've run a 6h load test with BOINC (Prime 95) test without any problem.

share|improve this question
ECC uncorrectable errors in the system logs, by any chance? – womble Jul 25 '12 at 9:41
Yes, either netconsole or a serial console could help. Testing of physical memory with memtest86 could also be helpful. Lastly, if the server is connected to a managed switch, could you find out if there are errors on the ethernet interface where the server is connected? I had these kind of crashes recently too, and I suspect it to be a bug in a network driver. – AndreasM Jul 25 '12 at 9:44
Memory is rather unlikely, the hardware was re-purposed (simple disk swap, case wasn't even opened) and was rock stable as a XenServer machine. It looks like ECC is disabled (?!), at least that's what EDAC module says, I'll look up to it. – Hubert Kario Jul 25 '12 at 10:29
Do you have a Broadcom ethernet NIC in the server? If so, what was your MTU set to? – Mike Pennington Jul 25 '12 at 11:14
@MikePennington: No, no Broadcom, I know about them... – Hubert Kario Jul 25 '12 at 11:50

I've found two possible solutions, I'll report if they worked. EDIT: They didn't

First is nmi_watchdog enabled by adding nmi_watchdog=1 to kernel boot parameters.

The second one (thanks @womble for the suggestion) was forcing ECC on by

modprobe amd64_edac_mod ecc_enable_override=1 edac_op_state=1

Unfortunately, support for ECC DDR3 memory in 2.6.32-bpo.5-amd64 (Debian squeeze) kernel is absent, I had to use 3.2 from backports.

I also added those options to general kernel parameters:

echo options amd64_edac_mod ecc_enable_override=1 edac_op_state=1 > /etc/modprobe.d/amd64_edac_mod.conf
share|improve this answer
up vote 0 down vote accepted

As the hangs were happening more and more often, the problem was probably caused by faulty mainboard or less likely, the CPU. After replacing those components the problems went away.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.