From: Christian Ullrich <chris@chrullrich.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.1: Abnormal interrupt from RTL8139
Date: Thu, 8 Feb 2001 09:38:54 +0100 [thread overview]
Message-ID: <20010208093854.A1122@christian.chrullrich.de> (raw)
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/
next reply other threads:[~2001-02-12 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 8:38 Christian Ullrich [this message]
2001-02-12 2:38 ` Jeff Garzik
2001-02-12 5:57 ` Christian Ullrich
2001-02-12 17:51 ` Fernando Fuganti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010208093854.A1122@christian.chrullrich.de \
--to=chris@chrullrich.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®