lkml.org 
[lkml]   [1998]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject2.0.34 bug -- eth0: Interrupt posted but not handled -- IRQ blocked by another device?
Date
Hello...

I got this message on a SMP machine (P II x 2 x 233Mhz) with dual 3com
905 ether cards. I also got this under kernels ~2.1.9x to 2.1.102, but
it went away in 2.1.103. If I can help with anything ( besides
programing, this is way above my head) I will...

-------------------from dmesg----------
12: @c0006ad0 length 80000048 status 80000048
13: @c0006ae0 length 80000048 status 80000048
14: @c0006af0 length 80000048 status 00000048
15: @c0006b00 length 80000048 status 00000048
eth0: Freeing Tx ring entries:<7>Socket destroy delayed (r=0 w=5024)
Socket destroy delayed (r=0 w=240)
Socket destroy delayed (r=0 w=240)
Socket destroy delayed (r=0 w=240)
eth0: transmit timed out, tx_status 00 status e601.
eth0: Interrupt posted but not handled -- IRQ blocked by another device?
Flags; bus-master 1, full 0; dirty 432878 current 432878.
Transmit list 00000000 vs. c0006af0.
0: @c0006a10 length 80000048 status 00000048
1: @c0006a20 length 80000048 status 00000048
2: @c0006a30 length 80000048 status 00000048
3: @c0006a40 length 80000048 status 00000048
4: @c0006a50 length 80000048 status 00000048
5: @c0006a60 length 80000048 status 00000048
6: @c0006a70 length 80000048 status 00000048
7: @c0006a80 length 80000048 status 00000048
8: @c0006a90 length 80000048 status 00000048
9: @c0006aa0 length 80000048 status 00000048
10: @c0006ab0 length 80000048 status 00000048
11: @c0006ac0 length 80000048 status 00000048
12: @c0006ad0 length 80000048 status 80000048
13: @c0006ae0 length 80000048 status 80000048
14: @c0006af0 length 80000048 status 00000048
15: @c0006b00 length 80000048 status 00000048
eth0: Freeing Tx ring entries:<7>Socket destroy delayed (r=0 w=3488)
Socket destroy delayed (r=0 w=240)
Socket destroy delayed (r=0 w=240)
Socket destroy delayed (r=0 w=240)
eth0: transmit timed out, tx_status 00 status e601.
eth0: Interrupt posted but not handled -- IRQ blocked by another device?
Flags; bus-master 1, full 0; dirty 432894 current 432894.
Transmit list 00000000 vs. c0006af0.
0: @c0006a10 length 80000048 status 00000048
1: @c0006a20 length 80000048 status 00000048
2: @c0006a30 length 80000048 status 00000048
3: @c0006a40 length 80000064 status 00000064
4: @c0006a50 length 80000048 status 00000048
5: @c0006a60 length 80000048 status 00000048
6: @c0006a70 length 80000048 status 00000048
7: @c0006a80 length 80000048 status 00000048
8: @c0006a90 length 80000048 status 00000048
9: @c0006aa0 length 80000048 status 00000048
10: @c0006ab0 length 80000048 status 00000048
-------------end from dmesg



This might be revelent....
--- message from my archive.

From: torvalds@transmeta.com (Linus Torvalds)
Subject: Re: NE2000 PCI problems FIXED!
Date: 20 May 1998 19:35:18 -0700

On Thu, 21 May 1998, Richard Gooch wrote:
>
> Hi, all. I've been pounding on 2.1.103 and I'm happy to say that the
> lost interrupt problems with my PCI NE2000 card seem to have gone
> away (Tyan Titan Pro, dual PPro 180). Lovely!

Good. We still have a case of level interrupts sometimes duplicating,
but
it's harmless. And we know why it happens and how to avoid it. So
there's
going to be some very slight work on the irq code still, but I'm
beginning
to consider it pretty much done other than that.

Anybody that still sees interrupt-related problems, speak now or forever
hold your peace..

Linus
--------------end message from archive
--

Christopher McCrory
Lead Bithead, Netus Inc.
chrismcc@netus.com
admin@netus.com

"Linux: Because rebooting is for adding new hardware"

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:2.540 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site