[lkml]   [2001]   [Jul]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Problem with SMC Etherpower II + kernel newer 2.4.2
John Jasen wrote:
> a) bad cable?
> b) not negotiating speed and duplex with the switch correctly?
> c) bad card?


The same errors show up with the network cable plugged or unplugged on
all computers with the SMC card around here. But all these computers are
equipped with nearly the same hardware (see my first posting of the
/proc/pci file). Also the 2.4.6 kernel does not solve the problem.

> d) IRQ sharing causing a conflict?

I dont think so, at least I dont get a IRQ conflict message and there
is no other device shown as using the same interrupt. If I use the 2.4.2
kernel or a version below everything works fine on the same host.

Another strange effect is, that if I wait for quite some time (5-10
Minutes) while trying to start up the eth0 device with "ifconfig eth0
up" I see messages like

Jul 4 09:38:58 localhost kernel: eth0: Setting full-duplex based on MII
#3 link partner capability of 41e1.
Jul 4 09:39:00 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed
Jul 4 09:39:00 localhost kernel: eth0: Transmit timeout using MII
device, Tx status 000b.
Jul 4 09:39:02 localhost kernel: eth0: Too much work at interrupt,
Jul 4 09:40:55 localhost kernel: eth0: Setting half-duplex based on MII
#3 link partner capability of 0001.

in between hundreds of "too much work at interrupt" messages. This error
also occures regardles of the network cable is plugged or unplugged.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:56    [W:0.091 / U:1.532 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site