From owner-freebsd-questions@FreeBSD.ORG Tue Jun 24 22:46:48 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 942B11065671 for ; Tue, 24 Jun 2008 22:46:48 +0000 (UTC) (envelope-from david.gurvich@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.freebsd.org (Postfix) with ESMTP id 5EAE58FC1A for ; Tue, 24 Jun 2008 22:46:48 +0000 (UTC) (envelope-from david.gurvich@verizon.net) Received: from Lucifer ([71.249.92.114]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K2Z0034HOLNOHH6@vms046.mailsrvcs.net> for freebsd-questions@freebsd.org; Tue, 24 Jun 2008 17:46:36 -0500 (CDT) Date: Tue, 24 Jun 2008 18:46:29 -0400 From: David Gurvich To: freebsd-questions@freebsd.org Message-id: <20080624184629.22e2b026@Lucifer> MIME-version: 1.0 X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Subject: xl driver in FreeBSD6.3 fails to maintain connections 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: Tue, 24 Jun 2008 22:46:48 -0000 Hello, I have an x86 box with a 3com 905b ethernet card installed. I had frequent problems in connecting to it and in fact the card was not up when I checked. A reboot or 2 would bring the card up, but it would not stay up, ie ssh from another computer would disconnect. There did not appear to be any error messages and no configurations were changed for reboot. I suspect the card was being powered off. I have since given up on using FreeBSD on this box and installed Solaris10. As there do not appear to be any hardware issues with Solaris, I was curious if there is a known issue with either the xl driver or the network stack in 6.3 that may have been fixed in 7.0 .