From owner-freebsd-current@FreeBSD.ORG Thu Mar 31 15:53:08 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B026A106567D for ; Thu, 31 Mar 2011 15:53:08 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 6AD848FC1C for ; Thu, 31 Mar 2011 15:53:08 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id p2VFquqZ066022 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 31 Mar 2011 11:52:56 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <4D94A354.9080903@sentex.net> Date: Thu, 31 Mar 2011 11:52:52 -0400 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Olivier Smedts References: In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: FreeBSD current mailing list Subject: Re: problems with em(4) since update to driver 7.2.2 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: Thu, 31 Mar 2011 15:53:08 -0000 On 3/31/2011 11:20 AM, Olivier Smedts wrote: > Hello, > > I've got a problem under FreeBSD 9.0-CURRENT amd64 with the em driver. > It's loaded as a module. I was previously using r219710 (2011-03-17) > without any problem, but with latest HEAD I can't even send a ping. > Here's what appears in dmesg. I tried unloading / loading the module, > did not help. At the end I loaded my old if_em.ko and it worked : I ran into a similar problem with specific types of em NICs. For some reason, if it was compiled into the kernel it worked. As a module doing a netboot, it would fail. Does it work for you if the driver is statically compiled into the kernel by chance ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/