Repeated System Failure with "Lost Interrupt" error.

codedv · 07-19-2006, 06:59 AM

I have a server with Fedora Core 3 installed. It has been running fine for over a year but started having problems after changing the motherboard. Detailed here.

All other hardware including hard disks worked fine up until this point. The server now crashes periodicallly, aboout 3 times a day; it loses the console, network connectivity and just displays "hda lost interrupt" on the screen.

I am at the end of my tether with this problem. What was origianally a simple memory upgrade has turned into a fight to keep a server (which includes a website) up.

This is what I have tried so far:

Recompiling the kernel.
Disabling DMA from the BIOS.
Flashing the BIOS with the latest BIOS version.
Check the memory using Microsoft's memory test utility.
Try older kernels such as 2.2 and 2.4 which used to work on my system.

I am not sure what else to try. I get a few errors at bootup before init is executed but the fly past way to fast to see and do not appear to be logged anywhere and it usually crashes while Samaba is writing a roaming profile via windows.

My last option would be toreinstall the system completely. I don't want to have to do this unless absolutly necessary however.

Does anyone have any ideas of suggestions?

codedv · 07-19-2006, 01:46 PM

Attached is copy of the dmesg file written at startup and some interrup information:

Code:

-bash-3.00$ cat /proc/interrupts
           CPU0
  1:         20        Phys-irq  i8042
  5:          0        Phys-irq  ohci_hcd:usb1
 10:      78536        Phys-irq  eth0
 14:     224156        Phys-irq  ide0
 15:     371579        Phys-irq  ide1
256:     213776     Dynamic-irq  timer0
257:          0     Dynamic-irq  xenbus
258:          0     Dynamic-irq  console
259:          0     Dynamic-irq  net-be-dbg
NMI:          0
LOC:          0
ERR:          0
MIS:          0

http://adam.codedv.com/dmesg

t0nymac · 07-23-2006, 09:27 AM

A hardware fault is my guess, with the Network Interface Controller (NIC) as most likely component. If the NIC is a card then try another PCI slot as the slot might be faulty, then another NIC as the NIC might be faulty. If it's an onboard NIC then disable it in the BIOS and use a PCI card.

codedv · 07-24-2006, 03:54 AM

I shall try another PCI slot and also have another NIC I can try. It may be week before I get back due the sparadic nature of the error.

Thanks.