2.2.18 + Scheduling in interrupt

2.2.18 + Scheduling in interrupt

Post by Alan Co » Sun, 25 Feb 2001 10:20:03

Quote:> Aiee, killing interrupt handler
> alloc_skb called nonatomically from interrupt c016468f
> eth0: Tx request while isr active.
> Scheduling in interrupt

What ethernet card was this ?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

1. Suse personal 7.1 krnl 2.2.18, hda lost interrupt - no boot.


I'm new to Linux, and I hope this is the right group for my question.

I have a Compaq Evo D300 at work.
P4 1600/400, 128MB ram, 20GB hdd.

It came with windows XP installed.
I used partition magic 7.0 to 'split' the harddisk into two partitions.

I installed Suse linux personal 7.1 kernel 2.2.18 on the new partition,
letting yast create the swap partition and ext2, and format.
Swap partition 256 MB before the Ext2 partition.

After the install I booted into linux without any problems, I had to do the
dd if=/...... to setup XP boot.ini so that I would be able to boot Linux or
XP, without having to write lilo to the mbr.

After I got the boot setup working I havent been able to boot into linux.
It starts decompressing the kernel alright, but I get to:

hda: wdc wd200eb-11sfo ata disk drive
hdc: ltn 486s atapi cdrom drive
hda lost interrupt
hda lost interrupt
hda lost interrupt
hda: wdc wd200eb-11sfo ata disk drive
hdc lost interrupt
hdc lost interrupt
hdc lost interrupt

then it continues booting as normal until..

Partition check
hda:hda: lost interrupt
hda: lost interrupt
hda1 hda2hda: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
Ramdisk ....

then it continues again..

autorun done
hda lost interrupt
hda lost interrupt
hda lost interrupt
hda lost interrupt
hda lost interrupt

I've let for go for 20 minutes before I cut the power. It doesnt respond to

I searched the net, suse's support database, google groups, and I didnt
really find any answers. Only that it used to be an indication that the hdd
was going down. Its brandnew, so I dont think thats the case though.

Any help would be appreciated.
Thanks in advance.


2. kernel traces

3. Ooops on 2.2.18...

4. script for comparing two lists of usernames....???

5. 2.2.18-modules belonging?

6. bdflush not running???

7. Enabling Firewall on Redhat 9 (with 2.2.18) ?

8. Transmit timeout

9. Mixing UDMA33/66 drives, VIA IDE, Linux 2.2.18

10. PROBLEM: DHCP doesn't work in 2.2.18?

11. kernel 2.2.18 compile fails on slackware

12. KERNEL PANIC in 2.2.17 and 2.2.18

13. Big trouble trying to compile a 2.2.18 kernel