From owner-freebsd-current@FreeBSD.ORG Wed May 4 21:38:26 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 9BE25106564A for ; Wed, 4 May 2011 21:38:26 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4723D8FC0C for ; Wed, 4 May 2011 21:38:25 +0000 (UTC) Received: by vxc34 with SMTP id 34so2163946vxc.13 for ; Wed, 04 May 2011 14:38:25 -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=kEsQMSNgYT9hOjfmH7GVyuD9+ss/fLV7/1hA8bBZh0A=; b=uykDipF/nd1XJPa4DJh01zvLPw856rKft4OD+JijJNhl7NsM+QQF0nUz7BYhU2C+p6 cuJGmxdsTfr0TAXkDZ8aqoHhmXboUlHaovWuOXQxBtxI1d0kEd7GvrnNiwjUZS8Jvsfg qOO0Mm1ByUREXwUfc60n6QwOWlFueup9wiwaI= 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=QCtLiEXMdHHCjtjCXnp0dL0y+cd85w4QD/WTn1MYNB//A4BL4kg6MqACBjk3CVUD8e QiQwRVEmjfgC8H2QgIRdJ+2tqSTJr6zTtk9IGFDFFQf6mHajOxpafL7urVzmaAsxPokA //DgCteNHnitRUEG4C3AxxsMe64/98XJG2Vn0= MIME-Version: 1.0 Received: by 10.52.18.14 with SMTP id s14mr2068229vdd.164.1304545105417; Wed, 04 May 2011 14:38:25 -0700 (PDT) Received: by 10.52.184.169 with HTTP; Wed, 4 May 2011 14:38:25 -0700 (PDT) In-Reply-To: References: <4D94A354.9080903@sentex.net> <4DC07013.9070707@gmx.net> <4DC078BD.9080908@gmx.net> Date: Wed, 4 May 2011 14:38:25 -0700 Message-ID: From: Jack Vogel To: Olivier Smedts Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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: Wed, 04 May 2011 21:38:26 -0000 I have had my validation engineer busy all day, we have tried both a 9 kernel as well as 8.2, using the code from HEAD, and we cannot reproduce this problem. The data your netstat -m shows suggests to me that what's happening is somehow setup of the receive ring is running more than once maybe?? You asked at one point how this could go into STABLE, well, because not only here at Intel, but at lots of external customers this code has been used and tested thoroughly. I am not calling into question your problem, but until I understand what it is I cannot "fix" it :) The thing I am guessing right now is the culprit is the setup code, the reason is that when I ported to the igb driver I found that it did not work on our newer hardware, and so I went back to the older version of setup for igb. Now, even though I have not seen hardware fail with em, maybe there is some. To help me give me a complete pciconf -lv, and if its a namebrand system tell me that, including all hardware in it. If you like Olivier I can make a version of em for you that also reverts the setup code the way I did for igb, see if that fixes it for you? Thanks for your patience, Jack