From owner-cvs-all@FreeBSD.ORG Sat Dec 16 01:28:01 2006 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B4BC16A47B; Sat, 16 Dec 2006 01:28:01 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5388E43CA0; Sat, 16 Dec 2006 01:26:16 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) by blake.polstra.com (8.13.8/8.13.8) with ESMTP id kBG1S0ci003069; Fri, 15 Dec 2006 17:28:00 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20061215203505.GA55141@dragon.NUXI.org> Date: Fri, 15 Dec 2006 17:28:00 -0800 (PST) From: John Polstra To: "David O'Brien" Cc: John Polstra , cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/bge if_bge.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Dec 2006 01:28:01 -0000 > I wonder if enabling MSI is what killed bge(4) for me. The booted kernel > would establish 1000Mbit link, but would see and wouldn't send any > packets. > > I have a Tyan K8W (s2885) which I experienced this on: > bge0: mem 0xfd7e0000-0xfd7effff irq 24 a > t device 9.0 on pci2 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > bge0: Ethernet address: 00:e0:81:27:a1:b8 I wouldn't be surprised if MSI was the culprit. I'm pretty sure the 5703 is one of the chips that has MSI-related bugs. You could try disabling MSI with the tunables mentioned in UPDATING, if you still have that short-lived version of the driver. John