Date: Wed, 12 May 1999 21:05:14 -0400 (EDT) From: Network Coordinator <nc@ai.net> To: David Greenman <dg@root.com> Cc: questions@FreeBSD.ORG Subject: Re: tl0, fxp0 device timeout errors Message-ID: <Pine.BSF.3.91.990512210442.16410A-100000@alyssa.ai.net> In-Reply-To: <199905081733.KAA22276@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 8 May 1999, David Greenman wrote: > > > >On a few machines we see routine fxp0 and tl0 device timeout errors. The > >newest (the tl0's) are on Compaq 10/100 interfaces built onto the > >motherboards of Prosignia servers. > > > >WRT the tl0: > >The problem seems to be related to network traffic, not uptime. If we > >move 1-2Mbit/s for about 1 hr the boards lock up. A simple ifconfig tl0 > >down, ifconfig tl0 up clears the problem. When locked: ping, and other > >utils report no buffer space available. There _are_ plenty of MBUF clusters > >available. > > > >The console gets errors like: > > > >tl0: device timeout > >tl0: adapter check: 100007 > >tl0: device timeout > >tl0: adapter check: 100007 > >tl0: device timeout > >tl0: adapter check: 100007 > >tl0: device timeout > >tl0: adapter check: 100007 > >tl0: device timeout > >tl0: adapter check: 100007 > > > >The problems with the fxp0 are clearable just as easily, but the more > >traffic the system moves, the more often it needs to be done. Any way of > >knowing what the device is complaining about/concerned about? > > Could be caused by a cable problem. > We'll try changing the cable, but why would the problem be effected by an ifconfig tl0 up? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.990512210442.16410A-100000>