2.4.1: Abnormal interrupt from RTL8139

2.4.1: Abnormal interrupt from RTL8139

[Christian Ullrich]

I'm getting some of these messages in syslog:

Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000020.
Feb  7 17:32:53 christian kernel: eth0: Abnormal interrupt, status 00000041.
Feb  7 17:55:22 christian kernel: eth0: Abnormal interrupt, status 00000041.
Feb  7 17:59:04 christian kernel: eth0: Abnormal interrupt, status 00000040.
Feb  7 19:39:47 christian kernel: eth0: Abnormal interrupt, status 00000010.
Feb  7 19:39:47 christian kernel: eth0: Abnormal interrupt, status 00000010.

Kernel is 2.4.1, eth0 is an rtl8139. 
MB is an ABIT KT7, with VIA chipset.

I have not observed any effects related to these messages.

I'm including the output of Linus's dump_pirq script, if it is of any use:

Interrupt routing table found at address 0xfddd0:
  Version 1.0, size 0x00b0
  Interrupt router is device 00:07.0
  PCI exclusive interrupt mask: 0x8e00 [9,10,11,15]
  Compatible router: vendor 0x1106 device 0x0596

Device 00:11.0 (slot 1): 
  INTA: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTB: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTC: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTD: link 0x05, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]

Device 00:0f.0 (slot 2): 
  INTA: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTB: link 0x05, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTC: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTD: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]

Device 00:0d.0 (slot 3): SCSI storage controller
  INTA: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTB: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTC: link 0x05, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTD: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]

Device 00:0b.0 (slot 4): Multimedia audio controller
  INTA: link 0x05, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTB: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTC: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTD: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]

Device 00:09.0 (slot 5): Ethernet controller
  INTA: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTB: link 0x05, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTC: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTD: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]

Device 00:08.0 (slot 6): 
  INTA: link 0x05, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTB: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTC: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTD: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]

Device 00:13.0 (slot 7): 
  INTA: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTB: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTC: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTD: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]

Device 00:01.0 (slot 0): PCI bridge
  INTA: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTB: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTC: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTD: link 0x05, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]

Device 00:07.0 (slot 0): ISA bridge
  INTC: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
  INTD: link 0x05, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]

Interrupt router at 00:07.0: VIA 82C686 PCI-to-ISA bridge
  PIRQA (link 0x01): irq 10
  PIRQB (link 0x02): irq 15
  PIRQC (link 0x03): irq 11
  PIRQD (link 0x05): irq 9

-- 
Christian Ullrich		     Registrierter Linux-User #125183

"Sie können nach R'ed'mond fliegen -- aber Sie werden sterben"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.1: Abnormal interrupt from RTL8139

[Jeff Garzik]

Christian Ullrich wrote:
> I'm getting some of these messages in syslog:
> Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
> Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
> Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000020.
> Feb  7 17:32:53 christian kernel: eth0: Abnormal interrupt, status 00000041.
[...]
> I have not observed any effects related to these messages.

Those messages are logged at the debugging level... if they bother you,
don't log kern.debug...

	Jeff



-- 
Jeff Garzik       | "You see, in this world there's two kinds of
Building 1024     |  people, my friend: Those with loaded guns
MandrakeSoft      |  and those who dig. You dig."  --Blondie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: 2.4.1: Abnormal interrupt from RTL8139

[Christian Ullrich]

* Jeff Garzik wrote on Sunday, 2001-02-11:

> Christian Ullrich wrote:

> > I'm getting some of these messages in syslog:
> > Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
> > Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
> > Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000020.
> > Feb  7 17:32:53 christian kernel: eth0: Abnormal interrupt, status 00000041.
> [...]
> > I have not observed any effects related to these messages.
> 
> Those messages are logged at the debugging level... if they bother you,
> don't log kern.debug...

Well, doing something related to debugging implies that there _is_
something to debug. But since I don't have any problems and not
more than a few messages like these, thanks for your help.

-- 
Christian Ullrich		     Registrierter Linux-User #125183

"Sie können nach R'ed'mond fliegen -- aber Sie werden sterben"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://vger.kernel.org/lkml/

Re: 2.4.1: Abnormal interrupt from RTL8139

[Fernando Fuganti]

I've had some problems with this card, as Aristeu Rozanski have asked you
(Jeff) for some news about driver development...

we have some machines that did some random reboot or card lockups:
- rtl8139.c, card lockup
- (2.2.17) 8139too.c, machine reboot
- (2.2.18) 8139too.c (0.9.12-2.2 - PIO mode), machine reboot

we are testing new version with MMIO mode to find out what is wrong
(until now, it seems to be stable)

If you want, I could get more info or testing something else, ok ?


Fernando Fuganti


On Sun, 11 Feb 2001, Jeff Garzik wrote:

> Christian Ullrich wrote:
> > I'm getting some of these messages in syslog:
> > Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
> > Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000010.
> > Feb  6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 00000020.
> > Feb  7 17:32:53 christian kernel: eth0: Abnormal interrupt, status 00000041.
> [...]
> > I have not observed any effects related to these messages.
> 
> Those messages are logged at the debugging level... if they bother you,
> don't log kern.debug...
> 
> 	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://vger.kernel.org/lkml/