From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: Donald Becker <becker@scyld.com>
Cc: Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org, jgarzik@mandrakesoft.com
Subject: Re: RTL8139 difficulties in 2.2, not in 2.4
Date: Sun, 20 May 2001 12:27:59 +0200 [thread overview]
Message-ID: <20010520122759.B2910@emma1.emma.line.org> (raw)
In-Reply-To: <20010519140413.B1795@emma1.emma.line.org> <Pine.LNX.4.10.10105191107450.956-100000@vaio.greennet>
In-Reply-To: <Pine.LNX.4.10.10105191107450.956-100000@vaio.greennet>; from becker@scyld.com on Sat, May 19, 2001 at 11:15:38 -0400
On Sat, 19 May 2001, Donald Becker wrote:
> > eth1: Transmit timeout, status 0c 0005 media 18.
> > eth1: Tx queue start entry 4 dirty entry 0.
> > eth1: RTL8139 Interrupt line blocked, status 5.
> > eth1: RTL8139 Interrupt line blocked, status 5.
> > eth1: RTL8139 Interrupt line blocked, status 4.
> > eth1: RTL8139 Interrupt line blocked, status 4.
> > (continues every minute with status 4 if no traffic on interface)
>
> The card is reporting that the interrupt line has been asserted (Tx
> done), but the interrupt handler hasn't been called.
>
> You can verify this by watching the interrupt count in /proc/interrupts.
>
> Try booting the kernel with "noapic", which we recommend as the safe
> default setting.
Sorry, this didn't work out. I still get Tx descriptor dumps, and these:
eth1: RTL8139 Interrupt line blocked, status 5.
eth1: Transmit timeout, status 0c 0005 media 18.
eth1: Tx queue start entry 8 dirty entry 4, full.
eth1: Tx descriptor 0 is 9008a03c. (queue head)
eth1: Tx descriptor 1 is 9008a03c.
eth1: Tx descriptor 2 is 9008a03c.
eth1: Tx descriptor 3 is 9008a03c.
eth1: MII #32 registers are: 1000 782d 0000 0000 01e1 0000 0000 0000.
eth1: RTL8139 Interrupt line blocked, status 5.
/proc/interrupt looks like this:
CPU0
0: 37029 XT-PIC timer
1: 1049 XT-PIC keyboard
2: 0 XT-PIC cascade
4: 1955 XT-PIC serial
5: 173 XT-PIC ide2, eth0
8: 1 XT-PIC rtc
9: 0 XT-PIC eth1
10: 1323 XT-PIC serial
11: 41 XT-PIC sym53c8xx, es1371
13: 1 XT-PIC fpu
14: 14947 XT-PIC ide0
NMI: 0
So, yes, it looks as if there had not been a single eth1 IRQ. But why
does 2.4 get it right, then, even without special boot options?
--
Matthias Andree
next prev parent reply other threads:[~2001-05-20 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 12:04 Matthias Andree
2001-05-19 15:15 ` Donald Becker
2001-05-20 10:27 ` Matthias Andree [this message]
2001-05-20 14:47 ` Matthias Andree
2001-05-21 9:20 ` also in 2.4: " Matthias Andree
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=20010520122759.B2910@emma1.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.de \
--cc=becker@scyld.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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®