From owner-freebsd-stable@FreeBSD.ORG Fri Mar 30 19:56:42 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A842816A400 for ; Fri, 30 Mar 2007 19:56:42 +0000 (UTC) (envelope-from besko@msu.edu) Received: from sys23.mail.msu.edu (sys23.mail.msu.edu [35.9.75.123]) by mx1.freebsd.org (Postfix) with ESMTP id 8AB6E13C4AE for ; Fri, 30 Mar 2007 19:56:42 +0000 (UTC) (envelope-from besko@msu.edu) Received: from sector14.cl.msu.edu ([35.8.1.195]) by sys23.mail.msu.edu with esmtpsa (Exim 4.52 #1) (TLSv1:AES256-SHA:256) id 1HXNDF-0003ll-Tg for freebsd-stable@freebsd.org; Fri, 30 Mar 2007 15:56:41 -0400 Message-ID: <460D6B7A.3000409@msu.edu> Date: Fri, 30 Mar 2007 15:56:42 -0400 From: Lisa Besko User-Agent: Thunderbird 1.5.0.7 (X11/20061101) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <460D3D09.1060101@msu.edu> In-Reply-To: <460D3D09.1060101@msu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus: None found by Clam AV Subject: Re: Sunfire X2200 ipfw and bge issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: besko@msu.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2007 19:56:42 -0000 Lisa Besko wrote: > Now any ideas on why they system reboots every time the ethernet cable > is plugged in to the bge0 port? or why the nve ethernet ports are not > recognized? > > I am getting an error the next time it reboots that says something like > "hyper transport sync flood" error and I have to press F1 to get it to > reboot. That error is from the BIOS I believe. I still have no idea why this was happening but I did disable the bge driver in the kernel and then patch the nve driver as stated in http://lists.freebsd.org/pipermail/freebsd-bugs/2006-November/020926.html and I was able to get the system up on the network. LB