From: Mikael Pettersson <mikpe@user.it.uu.se>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: tulip (pnic) errors in 2.6.5-rc1
Date: Thu, 18 Mar 2004 10:44:02 +0100 [thread overview]
Message-ID: <16473.28514.341276.209224@alkaid.it.uu.se> (raw)
2.6.5-rc1 causes my Netgear FA310TX to
fill the kernel log with messages like:
eth1: In tulip_rx(), entry 57 004c0728.
eth1: interrupt csr5=0x02670050 new csr5=0x02660010.
eth1: exiting interrupt, csr5=0x2660010.
In tulip_rx(), entry 58 004c0728.
eth1: In tulip_rx(), entry 58 004c0728.
eth1: interrupt csr5=0x02670050 new csr5=0x02660010.
eth1: exiting interrupt, csr5=0x2660010.
In tulip_rx(), entry 59 006a0300.
eth1: In tulip_rx(), entry 59 006a0300.
eth1: interrupt csr5=0x02670050 new csr5=0x02660010.
eth1: exiting interrupt, csr5=0x2660010.
eth1: interrupt csr5=0x02670014 new csr5=0x02660010.
eth1: exiting interrupt, csr5=0x2660010.
and on and on and on ...
No previous kernel had this problem.
2.6.4 identifies the nic as:
PCI: Found IRQ 10 for device 0000:00:0b.0
tulip1: MII transceiver #1 config 3000 status 7829 advertising 01e1.
eth1: Lite-On 82c168 PNIC rev 32 at 0xa000, XX:XX:XX:XX:XX:XX, IRQ 10.
eth1: Setting full-duplex based on MII#1 link partner capability of 41e1.
/Mikael
next reply other threads:[~2004-03-18 9:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 9:44 Mikael Pettersson [this message]
2004-03-18 9:51 ` Jeff Garzik
2004-03-18 9:53 ` Jeff Garzik
2004-03-18 10:42 ` Mikael Pettersson
2004-03-18 10:48 ` Jeff Garzik
2004-03-18 12:45 ` Mikael Pettersson
2004-03-18 16:29 ` Mikael Pettersson
2004-03-18 16:39 ` Randy.Dunlap
2004-03-18 17:09 ` Randy.Dunlap
2004-03-18 17:39 ` Mikael Pettersson
2004-03-18 17:41 ` Randy.Dunlap
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=16473.28514.341276.209224@alkaid.it.uu.se \
--to=mikpe@user.it.uu.se \
--cc=jgarzik@pobox.com \
--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®