From owner-freebsd-current@FreeBSD.ORG Wed Dec 5 01:27:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84E4116A419 for ; Wed, 5 Dec 2007 01:27:23 +0000 (UTC) (envelope-from support@monkeybrains.net) Received: from ape.monkeybrains.net (ape.monkeybrains.net [208.69.40.11]) by mx1.freebsd.org (Postfix) with ESMTP id 593A213C474 for ; Wed, 5 Dec 2007 01:27:23 +0000 (UTC) (envelope-from support@monkeybrains.net) Received: from [192.168.0.100] (busymonkey.monkeybrains.net [66.92.187.117]) (authenticated bits=0) by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id lB50mc5i004224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Dec 2007 16:48:38 -0800 (PST) (envelope-from support@monkeybrains.net) Message-ID: <4755F566.4090207@monkeybrains.net> Date: Tue, 04 Dec 2007 16:48:38 -0800 From: "Support (Rudy)" User-Agent: Thunderbird 1.5.0.10 (X11/20070221) MIME-Version: 1.0 To: pyunyh@gmail.com References: <4754BF03.5090407@monkeybrains.net> <20071204051957.GC35245@cdnetworks.co.kr> <4754EA3D.1020902@monkeybrains.net> <20071204063238.GD35245@cdnetworks.co.kr> In-Reply-To: <20071204063238.GD35245@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on pita.monkeybrains.net X-Virus-Status: Clean X-Mailman-Approved-At: Wed, 05 Dec 2007 03:09:57 +0000 Cc: freebsd-current@freebsd.org, Rudy Subject: Re: nfe busted on 7.0-BETA4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 05 Dec 2007 01:27:23 -0000 Pyun YongHyeon wrote: > > I compiled the nfe as a MODULE so I could kldunload it and load up the nve > > -- if the patch didn't work. So, I added if_nfe_load to my > > /boot/loader.conf. Following my plan, I ran kldunload if_nfe... BUT! the > > module was automatically reloaded AND started to work properly. Hmmm.... > > It's confusing. Does it mean the patch fixed the issue? > Are you sure the nfe(4) kernel module used at boot is patched nfe(4)? Yes. Patched, rebuilt everything (so as to take nfe out of the kernel). I turned on the computer this morning (having changed nothing since yesterday when I made nfe a MODULE and added if_nfe_load=YES to my loader.conf) and the errors were not there. unreproducible bugs are a drag... will see if it crops up again. Rudy