From owner-freebsd-current@FreeBSD.ORG Wed May 4 21:49:44 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 E64D8106564A for ; Wed, 4 May 2011 21:49:43 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9D7B08FC13 for ; Wed, 4 May 2011 21:49:43 +0000 (UTC) Received: by iyj12 with SMTP id 12so1869257iyj.13 for ; Wed, 04 May 2011 14:49:43 -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 :content-transfer-encoding; bh=LlAGSYQOuhMIDPr+LMbFjB96H8fdB+gGdCyCtnqS5LM=; b=m4N27eJfLYkfDEqfRkglRF3U07Q4gnpPQLW/h1DGiNqX86VsOU2TJ3YLEEGA/YxPry wYZ2Sltrdh4MZKyBQhfO5BxCnbnUMMOwRiYaajqVgZcjGdBLLFW1zB7axqSwee1/rhhZ jEE4rf9yn/feTJ4z1MDCcp3djsz/aReOG/sQU= 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:content-transfer-encoding; b=oDRNtk3G5ClHnDFhaHF3lJt5NR0KBgVVodtPFnMIoE9RJF+cK0xoAfg6R6cSLij0gp CAqmPjl1d6eHVtSe7k+uXzZ+qeOQk7fC0RT8sEIxqcaDvaJq0VposLDWQnWX1CQyGOus ZMnGqfJiWj/ygjj864wjv5v2jguUcoFnf2fg8= MIME-Version: 1.0 Received: by 10.42.246.133 with SMTP id ly5mr2159636icb.404.1304545783100; Wed, 04 May 2011 14:49:43 -0700 (PDT) Received: by 10.42.167.5 with HTTP; Wed, 4 May 2011 14:49:43 -0700 (PDT) In-Reply-To: References: <4D94A354.9080903@sentex.net> <4DC07013.9070707@gmx.net> <4DC078BD.9080908@gmx.net> Date: Wed, 4 May 2011 17:49:43 -0400 Message-ID: From: Arnaud Lacombe To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Wed, 04 May 2011 21:49:44 -0000 Hi, On Wed, May 4, 2011 at 5:38 PM, Jack Vogel wrote: > I have had my validation engineer busy all day, we have tried both > a 9 kernel as well as 8.2, =A0using 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?? > That would be consistent with what I reported back in February. I'll try to see if I can have a look at that on our platform tonight. - Arnaud > 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 b= een > 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 o= ur > 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 > _______________________________________________ > 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= " >