From owner-freebsd-questions Fri May 14 12: 1:28 1999 Delivered-To: freebsd-questions@freebsd.org Received: from alyssa.ai.net (unknown [205.134.170.2]) by hub.freebsd.org (Postfix) with ESMTP id AC3BE14E18 for ; Fri, 14 May 1999 12:01:18 -0700 (PDT) (envelope-from nc@alyssa.ai.net) Received: (from nc@localhost) by alyssa.ai.net (8.8.5/8.8.6) id PAA01982; Fri, 14 May 1999 15:01:13 -0400 (EDT) Date: Fri, 14 May 1999 15:01:13 -0400 (EDT) From: Network Coordinator To: dg@root.com, questions@freebsd.org Subject: Re: tl0, fxp0 device timeout errors (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Swapped the cable and the switch port, and we are still getting the same problem. What does the error code mean? Thanks! ---------- Forwarded message ---------- Date: Wed, 12 May 1999 21:05:14 -0400 (EDT) From: Network Coordinator To: David Greenman Cc: questions@FreeBSD.ORG Subject: Re: tl0, fxp0 device timeout errors 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