On Tue, 28 Nov 2000, Francois romieu wrote:
> > NETDEV WATCHDOG: eth0: transmit timed out
> > eth0: Transmit timeout using MII device, Tx status 0003.
> > eth0: Restarting the EPIC chip, Rx 4568454/4568454 Tx 6262613/6262623.
> > eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 2400
Hi,
The Tue, Nov 28, 2000 at 10:52:46AM +0100, Lukasz Trabinski wrote :
[...]
> I have the same problem with SMSC EPIC/100 83c170 Ethernet controller:
>
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timeout using MII device, Tx status 0003.
> eth0: Restarting the EPIC chip, Rx 456
In article <20001128042134.A1041@twoey> you wrote:
> Using 2.4-test10 I got a series of timeout errors on my tulip network
> card (Linksys LNE version 4, 00:0d.0 Ethernet controller: Bridgecom,
> Inc: Unknown device 0985 (rev 11)). Networking then completely stopped
> working. Restarting the inte
> > Linksys LNE version 4, 00:0d.0 Ethernet controller: Bridgecom, Inc:
> > Unknown device 0985 (rev 11)
[...]
> > Nov 28 04:04:52 twoey kernel: NETDEV WATCHDOG: eth0: transmit timed out
> > Nov 28 04:04:52 twoey kernel: eth0: Transmit timed out, status fc664010,
> > CSR12 , resetting...
Toby,
Nothing can be done without the full re-write of the driver.
The global request_io_lock is slammed into play way to early and release
way to late. You will have to suffer with this flaw until the spin of
2.5. We are talking about a rewrite that is still at least 60 days from
being ready
Using 2.4-test10 I got a series of timeout errors on my tulip network
card (Linksys LNE version 4, 00:0d.0 Ethernet controller: Bridgecom,
Inc: Unknown device 0985 (rev 11)). Networking then completely stopped
working. Restarting the interface with ifconfig fixed the problem.
I am using an SMP ke
6 matches
Mail list logo
