From owner-freebsd-hackers Wed Nov 4 09:54:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02574 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 09:54:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from stone.locallink.net (Stone.LocalLink.Net [204.71.156.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02568 for ; Wed, 4 Nov 1998 09:54:15 -0800 (PST) (envelope-from kpitcher@locallink.net) Received: from Diamond (Diamond.LocalLink.Net [204.71.156.68]) by stone.locallink.net (8.8.8/8.8.7) with SMTP id NAA24300 for ; Wed, 4 Nov 1998 13:00:45 -0500 (EST) (envelope-from kpitcher@locallink.net) From: "Keith Pitcher" To: Subject: RE: SMC9432TX driver (tx) users Date: Wed, 4 Nov 1998 12:53:37 -0500 Message-ID: <000001be081c$0d0524e0$449c47cc@Diamond.LocalLink.Net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: <199811041414.GAA28825@hub.freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had similar timeout problems in the past. I had a box of 5 of these cards, put them in 3 different 2.2.6 systems all similarly configured. They were all running at 100Mbps. One of the machines - the most heavily used - would report a device timeout a few times a day. I put in another tx card and the problem stopped occuring. (I ended up putting the problematic card in a win box and it's worked fine for the past number of months.) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Keith Pitcher kpitcher@locallink.net LocalLink - Your Local Link to the World http://www.locallink.net 800 687-2202 616 424-4999 Fax : 616 424-4995 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message