Bug 15542

Summary: [de] de(4) suddenly stops working
Product: Base System Reporter: Achim Patzner <ap>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-CURRENT   
Hardware: Any   
OS: Any   

Description Achim Patzner 1999-12-17 22:00:02 UTC 
A short time after booting I'm getting something like
de1: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
Dec 17 22:27:21 duo /kernel: de1: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
Dec 17 22:27:21 duo /kernel: de1: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
Dec 17 22:29:50 duo /kernel: nfs server www:/httpd/htdocs: not responding

which is followed by one or both of the devices not generating interrupts
any more (at least systat tells me so). THis is even worse if both
interfaces got the same IRQ.

How-To-Repeat: 
Put two DEC based interfaces into one machine and wait a short time
Comment 1 Steve Price freebsd_committer freebsd_triage 1999-12-17 22:05:53 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-bugs

Misfiled PR.
Comment 2 Mike Barcroft freebsd_committer freebsd_triage 2001-07-21 19:23:25 UTC 
State Changed
From-To: open->feedback


Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE?
Comment 3 Mike Barcroft freebsd_committer freebsd_triage 2001-07-21 20:18:28 UTC 
State Changed
From-To: feedback->closed


E-mail sent to originator bounces.
Comment 4 Thomas Gellekum freebsd_committer freebsd_triage 2002-04-10 13:26:25 UTC 
State Changed
From-To: closed->open

Re-open, the problem still exists.
Comment 5 Ceri Davies freebsd_committer freebsd_triage 2004-11-03 21:55:33 UTC 
State Changed
From-To: open->feedback

de(4) has been through some changes since the PR was submitted; does 
this persist in 5.x or later 4.x releases?
Comment 6 glasgow 2005-06-20 19:33:27 UTC 
I'm seeing similar behavior on 5.1-RELEASE-p7, with a quad-port
(ZNYX ZX34X 21140A [10-100Mb/s] pass 2.2) using the de driver.

For me, it's not repeatable, but I'll see the occasional message
like this:

May  2 13:59:06 hostname kernel: de1: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
May  4 20:49:32 hostname kernel: de3: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
May  5 00:12:27 hostname kernel: de1: abnormal interrupt: transmit underflow (raising TX threshold to 128|512)
May  5 01:08:24 hostname kernel: de2: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)

And only occasionally (rarely) does the NIC lock up and stop sending
or receiving packets.  Often there is some time between the last of
these messages and when the NIC stops working, for example the last
lockup happened approx 17-Jun-05 22:00, but nothing was logged after
the message on May 5 above.
Comment 7 Mark Linimon freebsd_committer freebsd_triage 2008-01-27 08:45:06 UTC 
State Changed
From-To: feedback->closed

Feedback timeout. 

This PR has been sitting around for quite some time, and the driver has 
undergone a lot of changes since then.  If this is still an issue, let 
us know and we can reopen it.