Motherboard woes

Baloo · 06-06-2002, 06:09 AM

I recently purchased a Gigabyte GA-7VKML (http://www.buyabs.com/specs/gigabyte-7vkml.htm) in the hope that I could build a cheap linux development box as my other machine is a dual boot affair.

Now when booting I get the following messages (hdd is my cdrom drive)

hdd lost interrupt
hdd lost interrupt
hdd lost interrupt
hdd lost interrupt

Then it hangs.

I'm thinking that I will need to pass some parameters at the boot prompt but I have no idea what they may be.

I know that this motherboard works under Linux as this (http://www.racksaver.com/products/RS1212.asp) company sell a rackmounted server with Linux and the motherboard.

Any help would be great especially as my Linux development projects are being effected by this

trickykid · 06-06-2002, 09:22 AM

If your getting a hdd lost interupt, what makes you think its the motherboard.. sounds more like a kernel error.

This page might point you in the right direction. http://www.greenend.org.uk/rjk/2002/...interrupt.html

Baloo · 06-06-2002, 09:27 AM

I only thought it was the motherboard as thats the only component that has changed in the system I am checking and it worked before but not now.

The website you supplied looks very promising

When I get home from work I'll give it a go.

Thanks

Baloo · 07-22-2002, 11:33 AM

Still have the problem. I've tracked it down to linux/drivers/ide.c in

Code:

void ide_timer_expiry (unsigned long data)

It seems that the cdrom drive is timing out for some reason. After a few attempts it sometimes works but accessing the cd through 'ls' or trying to 'cp' anything gives me the

Code:

hdd: lost interrupt

again. Ejecting the cd drive on boot-up also seems to allow the system to boot but the cd drive is still off limits.

Any ideas?

finegan · 07-22-2002, 05:46 PM

Sometimes the kernel, 2.4.18 right? doesn't deal with quirky interrupt handling so well. Offhand, do you have the cdrom hooked up to an ATA100/133 extension slot, or a normal IDE slot, and how is this thing jumpered? Simply setting it for /dev/hdc and exchanging it for a drive may solve the problem.

I've had this same thing happen before, but spuriously, never on every boot-up, and getting an IDE irq happy has always been for me the simple voodoo of drive juggling.

Luck,

Finegan

mikek147 · 07-22-2002, 06:30 PM

Just a thought, if you can get the system up, look at /proc/interrupts to see if the ide controller is sharing interrupts with any other device. -mk