Re: "xl*: transmission error" under -current

[Chris Cappuccio <chris@dqc.org>]

According to Jason's previous response on this issue, this error is actually
a diagnostic message and can be safely ignored.  Perhaps it should be removed 
from the driver...Jason ????

On Mon, 17 Jan 2000, root wrote:

 | I'm playing with ipf and bridging on a clone of my production firewall,
 | and I've just started seeing a few wierd things in the last week or so.
 | The machine in question, "topsecret" would just randomly reboot for no
 | good reason. no crashdump, and everything went away once I added ddb back
 | into my kernel. whatever...
 | 
 | The second one disturbs me a little more. For some strange reason, I'm
 | getting tx underruns on my 3com cards. yeah, I know 3com gear "needs
 | help." They're all I've got right now. I've got these 2 cards, an intel
 | 10/100Pro and an SMC 10/100 configured as a bridge, and currently there's
 | nothing plugged into the 3coms. 2.6release wasn't doing this, and I'm no
 | kernel hacker, so I can't point fingers at broken code, etc. Source is
 | current as of about 1045h MDT.
 | 
 | suggestions?
 | 
 | Error Text ======================================================
 | 
 | Jan 15 21:48:11 topsecret /bsd: xl1: transmission error: 90
 | Jan 15 21:48:11 topsecret /bsd: xl1: tx underrun, increasing tx start threshold to 120
 | Jan 15 21:48:12 topsecret /bsd: xl0: transmission error: 90
 | Jan 15 21:48:12 topsecret /bsd: xl0: tx underrun, increasing tx start threshold to 120
 | ...
 | Jan 17 10:32:03 topsecret /bsd: xl0: transmission error: 90
 | Jan 17 10:32:03 topsecret /bsd: xl0: tx underrun, increasing tx start threshold to 180
 | Jan 17 10:32:03 topsecret /bsd: xl1: transmission error: 90
 | Jan 17 10:32:03 topsecret /bsd: xl1: tx underrun, increasing tx start threshold to 180
 | 
 |