From owner-freebsd-net@FreeBSD.ORG Tue Jun 21 14:00:03 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AE0516A41C for ; Tue, 21 Jun 2005 14:00:03 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8ECC43D58 for ; Tue, 21 Jun 2005 14:00:02 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id CC7D846B8E; Tue, 21 Jun 2005 10:00:01 -0400 (EDT) Date: Tue, 21 Jun 2005 15:02:57 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Patrick Domack In-Reply-To: Message-ID: <20050621145127.L26664@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: EM Driver problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2005 14:00:03 -0000 On Mon, 20 Jun 2005, Patrick Domack wrote: > I have been using fxp network based cards, without issues. I have > recently changed over to em cards, and get kernel panics about once > every few days with them (mainly sbdrop panics). I already have > nsfclusters set to 32k, and freebsd vm memory set to 850megs, with 4g > memory installed. > > After playing adjusting things and not making any noticable > improvements, I upgraded the default freebsd em driver from 1.7 to the > 2.0 version on intels website. This seemed to fix things for awhile, > lastest two weeks before any problems happened, at witch time the > card/driver stopped recieving/sending packets. I am still looking into > exactly what happened here. I looked in some of the mailing list archives, but didn't see specific reports from you on the panics you are seeing. sbdrop() panics are almost always a sign of a device driver or network stack bug. In as much as possible, a detailed bug report with source code version, stack trace, etc, would be very helpful. Also, could you tell us a little more about the workload? If you've already submitted a PR or posted in detail somewhere, I pointer would be helpful, thanks! I'm not familiar with the if_em driver source from Intel, but one of the sets of changes that has been made to our driver that might not have been propagated into their driver is support for fine-grained locking, which is required if you're running on FreeBSD 5.3 or higher. Hangs are not unusual failure modes if locking is omitted. As such, I'd suggest we try to move debugging forward on vanilla FreeBSD source rather than the vendor's version of the driver. Thanks, Robert N M Watson