From owner-freebsd-stable@FreeBSD.ORG Sun Sep 14 20:08:54 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 357DED21; Sun, 14 Sep 2014 20:08:54 +0000 (UTC) Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 050CAA8; Sun, 14 Sep 2014 20:08:53 +0000 (UTC) Received: by mail-pd0-f177.google.com with SMTP id y10so4830894pdj.22 for ; Sun, 14 Sep 2014 13:08:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=V2H6OhVJ3+Oavj3nNA4G1co/mauzAVayq3fQkpTewXc=; b=RYBMI3C2bLEIzkPzElIXftq7ktOMDupzY4CnSJK+muqSWKfqk5v43rVgG3ZgeU8DDH mhPxYA6XdX7B3GrC1yBPBs6JT48L9i7bXCP8TkAVmgVrMO2tncdjBa842X37c7Vt/A32 viGBtjUgwapo1jSWHPKmniM10mNKCnDhFXx16vtLXeLdpIWzwDqjxoe+EQYcFGdVG3og qt0AVnAVmU+ed3PmLubwYQkAxgYFeCVtfVHogyRC0ljoRNFWHBfnLeg41GduJDY7EBK6 Fm5v+SdxqNIKr5V33b1XNKEa72l9a6zhmnYQgHgNOe2t0+gzwjV8c1z/U4V+vv7fjjSl AKVA== X-Received: by 10.70.119.97 with SMTP id kt1mr38148004pdb.54.1410725333355; Sun, 14 Sep 2014 13:08:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.55.162 with HTTP; Sun, 14 Sep 2014 13:08:13 -0700 (PDT) In-Reply-To: <5414DEAA.1060009@sentex.net> References: <1737288805.35881978.1410642408202.JavaMail.root@uoguelph.ca> <5414DEAA.1060009@sentex.net> From: Eric Joyner Date: Sun, 14 Sep 2014 13:08:13 -0700 Message-ID: Subject: Re: svn commit: r267935 - head/sys/dev/e1000 (with work around?) To: Mike Tancsa Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Glen Barber , Rick Macklem , freebsd-stable , Jack Vogel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2014 20:08:54 -0000 I'll try to, but I can't promise anything soon -- there's a lot of 10gig/40gig stuff to do. --- - Eric Joyner On Sat, Sep 13, 2014 at 5:17 PM, Mike Tancsa wrote: > > > Hi Eric, > Any chance you can look at this em driver bug in Jack's absence ? > > ---Mike > > > On 9/13/2014 5:06 PM, Rick Macklem wrote: > >> Mike Tansca wrote: >> >>> On 9/12/2014 7:33 PM, Rick Macklem wrote: >>> >>>> I wrote: >>>> >>>>> The patches are in 10.1. I thought his report said 10.0 in the message. >>>>> >>>>> If Mike is running a recent stable/10 or releng/10.1, then it has been >>>>> patched for this and NFS should work with TSO enabled. If it doesn't, >>>>> then something else is broken. >>>>> >>>> Oops, I looked and I see Mike was testing r270560 (which would have both >>>> the patches). I don't have an explanation why TSO and 64K rsize, wsize >>>> would cause a hang, but does appear it will exist in 10.1 unless it >>>> gets resolved. >>>> >>>> Mike, one difference is that, even with the patches the driver will be >>>> copying the transmit mbuf list via m_defrag() to 32 MCLBYTE clusters >>>> when using 64K rsize, wsize. >>>> If you can reproduce the hang, you might want to look at how many mbuf >>>> clusters are allocated. If you've hit the limit, then I think that >>>> would explain it. >>>> >>> >>> I have been running the test for a few hrs now and no lockups of the >>> nic, so doing the nfs mount with -orsize=32768,wsize=32768 certainly >>> >> ? seems to work around the lockup. How do I check the mbuf clusters ? >> >> Btw, in the past when reducing the rsize,wsize has fixed a problem that >> isn't fixed by disabling TSO, it has been a problem w.r.t. receiving a >> burst of ethernet packets. >> I believe this may be a problem with either the receive ring size or >> interrupt latency (testers have reported cases where changing the way >> the device driver uses interrupts have fixed the problem so that it >> worked with 64K rsize, wsize). >> >> I have no familiarity with this hardware/driver so I can't suggest >> anything specific to try except maybe how interrupts are handled, >> if the driver has a sysctl for that. >> >> rick >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> >> >> > > -- > ------------------- > 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/ >