From owner-freebsd-questions@FreeBSD.ORG Mon Mar 12 09:23:34 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5040D16A401 for ; Mon, 12 Mar 2007 09:23:34 +0000 (UTC) (envelope-from wojtek@tensor.gdynia.pl) Received: from chylonia.3miasto.net (chylonia.3miasto.net [83.12.228.78]) by mx1.freebsd.org (Postfix) with ESMTP id C322513C43E for ; Mon, 12 Mar 2007 09:23:33 +0000 (UTC) (envelope-from wojtek@tensor.gdynia.pl) Received: from chylonia.3miasto.net (localhost [127.0.0.1]) by chylonia.3miasto.net (8.13.8/8.13.4) with ESMTP id l2C9NOdn038888; Mon, 12 Mar 2007 10:23:24 +0100 (CET) (envelope-from wojtek@tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by chylonia.3miasto.net (8.13.8/8.13.4/Submit) with ESMTP id l2C9NNMF038885; Mon, 12 Mar 2007 10:23:24 +0100 (CET) (envelope-from wojtek@tensor.gdynia.pl) X-Authentication-Warning: chylonia.3miasto.net: wojtek owned process doing -bs Date: Mon, 12 Mar 2007 10:23:23 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@chylonia.3miasto.net To: "Brian J. Conway" In-Reply-To: <20070312012217.0c325b4b.bconway@clue4all.net> Message-ID: <20070312102259.K38557@chylonia.3miasto.net> References: <20070310105759.6980f90e.bconway@clue4all.net> <20070311221556.2d41802a.bconway@clue4all.net> <20070312012217.0c325b4b.bconway@clue4all.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "illoai@gmail.com" , freebsd-questions@freebsd.org Subject: Re: Periodic xl watchdog timeouts on 6.2-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2007 09:23:34 -0000 >> reboots from kernel panics. Replacing the NIC >> solved it. > > It's possible, but I've tried 3 different 3c905C's between the two > (top-most) slots I'm using for them, and they all have the same symptom, set up speed and half/full duplex manually and it should fix a problem. at least did for me