From owner-freebsd-current@FreeBSD.ORG Wed Apr 16 17:35:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6273837B401 for ; Wed, 16 Apr 2003 17:35:57 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12FEC43FBD for ; Wed, 16 Apr 2003 17:35:57 -0700 (PDT) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id F022D2ED40C; Wed, 16 Apr 2003 17:35:56 -0700 (PDT) Date: Thu, 17 Apr 2003 02:35:56 +0200 From: Maxime Henrion To: Lee Damon Message-ID: <20030417003556.GB21011@elvis.mu.org> References: <200304162227.h3GMRhWJ033255@castle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304162227.h3GMRhWJ033255@castle.org> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: fxp0 problems - 5.0-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2003 00:35:57 -0000 Lee Damon wrote: > Starting yesterday the kernel I built from latest CVSup started exhibiting > problems with fxp0, but not wi0 (the only NICs I have on my T30). > > The previous kernel, compiled on Monday the 7th (with sources SUPed > that morning) works fine. > > Under the new kernel fxp0 shows up with ifconfig and can be configured, > but it fails to pass packets. The packet count in netstat -in does > not climb, nor do any errors show up. Nothing is logged to indicate > error. It would be helpful if you could search what exact commit causes these problems. I'm particularly interested in knowing if your NIC is working OK with revision 1.168 of if_fxp.c. Also, it would be interesting to know what exact revision you have in the working kernel from the 7th. Assuming this kernel is /boot/kernel.old/kernel, this command should give you that information : ident /boot/kernel.old/kernel | grep fxp If for some reason you're using the fxp(4) driver as a module, run the above command on the if_fxp.ko file. Thanks, Maxime