From: Adrian Bunk <bunk@fs.tum.de>
To: Donald Becker <becker@scyld.com>,
linux-net@vger.kernel.org, jgarzik@pobox.com
Cc: linux-kernel@vger.kernel.org
Subject: Problem with 2.4.22 and SMC EtherPower II 9432
Date: Mon, 20 Oct 2003 22:59:33 +0200 [thread overview]
Message-ID: <20031020205933.GS23191@fs.tum.de> (raw)
Hi,
on two different machines the ethernet card works with kernel 2.2.20 but
not with kernel 2.4.22 (both contain machines contain the same card).
Card:
lspci:
00:0b.0 Ethernet controller: Standard Microsystems Corp [SMC] 83C170QF (rev 08)
cat /proc/pci:
Bus 0, device 11, function 0:
Ethernet controller: SMC 9432 TX (rev 8).
Fast devsel. Fast back-to-back capable. IRQ 10. Master Capable.
Latency=32. Min Gnt=8.Max Lat=28.
I/O at 0xb000 [0xb001].
Non-prefetchable 32 bit memory at 0xde800000 [0xde800000].
Kernel 2.2.20 (working):
kernel: eth0: SMSC EPIC/100 83c170 at 0xb000, IRQ 10, 00:e0:29:3d:e4:6f.
kernel: eth0: MII transceiver #3 control 3000 status 7809.
kernel: eth0: Autonegotiation advertising 01e1 link partner 0001.
...
kernel: eth0: Setting full-duplex based on MII #3 link partner capability of 45e1.
kernel 2.4.22 (not working):
kernel: epic100.c:v1.11 1/7/2001 Written by Donald Becker
<becker@scyld.com>
kernel: http://www.scyld.com/network/epic100.html
kernel: (unofficial 2.4.x kernel port, version 1.11+LK1.1.14, Aug 4,
2002)
kernel: epic100(00:0b.0): MII transceiver #3 control 3000 status 7809.
kernel: epic100(00:0b.0): Autonegotiation advertising 01e1 link partner
0001.
kernel: eth0: SMSC EPIC/100 83c170 at 0xb000, IRQ 10, 00:e0:29:3d:e4:6f.
...
kernel: eth0: Setting full-duplex based on MII #3 link partner capability of 45e1.
kernel: NETDEV WATCHDOG: eth0: transmit timed out
kernel: eth0: Transmit timeout using MII device, Tx status 4003.
kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 2/12.
kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
kernel: eth0: Setting half-duplex based on MII #3 link partner
capability of 0001.
kernel: NETDEV WATCHDOG: eth0: transmit timed out
kernel: eth0: Transmit timeout using MII device, Tx status 0003.
kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 3/12.
kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
kernel: NETDEV WATCHDOG: eth0: transmit timed out
kernel: eth0: Transmit timeout using MII device, Tx status 000b.
kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 4/12.
kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
kernel: NETDEV WATCHDOG: eth0: transmit timed out
kernel: eth0: Transmit timeout using MII device, Tx status 000b.
kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 5/12.
kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
kernel: NETDEV WATCHDOG: eth0: transmit timed out
kernel: eth0: Transmit timeout using MII device, Tx status 000b.
kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 6/12.
kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
kernel: eth0: Too much work at interrupt, IntrStatus=0x008d0004.
kernel: NETDEV WATCHDOG: eth0: transmit timed out
kernel: eth0: Transmit timeout using MII device, Tx status 000b.
kernel: eth0: Restarting the EPIC chip, Rx 1/1 Tx 7/17.
kernel: eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
Does anyone have an idea what's going wrong in 2.4.22?
TIA
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2003-10-20 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 20:59 Adrian Bunk [this message]
2003-10-20 21:30 ` Problem with 2.4.22 and SMC EtherPower II 9432 Francois Romieu
2003-10-20 21:49 ` Adrian Bunk
2003-10-20 22:14 ` Andreas Steinmetz
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=20031020205933.GS23191@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=becker@scyld.com \
--cc=jgarzik@pobox.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