From owner-freebsd-current@FreeBSD.ORG Thu Mar 31 17:14:43 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 886541065742 for ; Thu, 31 Mar 2011 17:14:43 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3FF0E8FC13 for ; Thu, 31 Mar 2011 17:14:42 +0000 (UTC) Received: by vws18 with SMTP id 18so2505335vws.13 for ; Thu, 31 Mar 2011 10:14:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=dCAcUh8oQtYc8TX2bTz0HvBKGtC9I8XVti0HpOSPUk4=; b=PEHcMQMcF8yDyctU/ADY2CwXfy7g35Da8roH8MRmH4LXvBz3MLvaGFl0OJLPt/FYOe vgbJEKON6thVxai1nm/UrZb+ToBVGq7fLSadCEiaMhqfJhv7f9TV2eSrqoZ2HpPgaUDS 6rqh5PWhiTeqcNrMVNgC3zuN4mfJa+rCaMDfw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=W6cWnfsn3W2ja9fmb/hzQxdbngG0eJpCoaMNd5uIVR5mnhmmeUM6qNVaia+lnVvGuJ omz2iyT4YEjkGtvTlP1qpif2LiNkRAAo07Gg5hgAdc4wCD2oyVRRdBRf15Blri9hkbh1 0f5VaS2hoAznRKygLR6Fxq8CEXBz8JU8Oep9k= MIME-Version: 1.0 Received: by 10.52.94.108 with SMTP id db12mr3805168vdb.293.1301590091256; Thu, 31 Mar 2011 09:48:11 -0700 (PDT) Received: by 10.52.167.6 with HTTP; Thu, 31 Mar 2011 09:48:11 -0700 (PDT) In-Reply-To: <4D94A354.9080903@sentex.net> References: <4D94A354.9080903@sentex.net> Date: Thu, 31 Mar 2011 09:48:11 -0700 Message-ID: From: Jack Vogel To: Mike Tancsa Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Olivier Smedts , 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 17:14:43 -0000 This problem happens for only one reason, you have insufficient mbufs to fill your rx ring. Its odd that it would differ when its static versus a loadable module though! With the 7.2.2 driver you also will use different mbuf pools depending on the MTU you are using. If you use jumbo frames it will use 4K clusters, if you go to 9K jumbos it will use 9K mbuf clusters. The number of these allocated by default is small (like 6400 small :). I would use 'netstat -m' to see what the pools look like. Now that I think about it, the reason it might fail as loaded while not as built in is you get allocation of the mbufs first when static, and something else is taking them before you can load when loadable?? I suspect all will be fine if you increase the pool size that you are using. Jack On Thu, Mar 31, 2011 at 8:52 AM, Mike Tancsa wrote: > 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/ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >