Subject: kern/10359: fxp driver gets "device timeout"
To: None <email@example.com>
From: None <firstname.lastname@example.org, email@example.com>
Date: 06/13/2000 20:21:10
>Synopsis: fxp driver gets "device timeout"
>Arrival-Date: Tue Jun 13 20:22:00 PDT 2000
>Originator: Hal Murray
Systems Research Center, Compaq Computer Corporation
System: NetBSD mckinley 1.4Z NetBSD 1.4Z (MIATA) #4: Fri Jun 9 04:01:32 PDT 2000
(from a driver that was modified to print more info)
Jun 13 20:15:14 foraker /netbsd: fxp2: device timeout: txdirty=3, txpending=128, snd.ifq_len=50
Jun 13 20:16:09 foraker /netbsd: fxp2: device timeout: txdirty=96, txpending=128, snd.ifq_len=50
Jun 13 20:16:14 foraker /netbsd: fxp2: device timeout: txdirty=96, txpending=128, snd.ifq_len=30
Jun 13 20:16:20 foraker /netbsd: fxp2: device timeout: txdirty=65, txpending=128, snd.ifq_len=50
Jun 13 20:16:25 foraker /netbsd: fxp2: device timeout: txdirty=51, txpending=128, snd.ifq_len=22
I have some tests that provoke this problem without dropping any
packets. I think that means the packets are getting sent correctly
but the cleanup routine isn't getting called.
I've never seen it happen when txpending wasn't 128.
I haven't noticed any troubles with similar gear and tests on i386.
I think any heavy network activity will do it if you wait
a while. I've seen it on moderate activity too. Most of
my tests will make it happen in under a minute.