From owner-freebsd-stable@freebsd.org Thu Sep 7 03:42:07 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFB02E02BF8 for ; Thu, 7 Sep 2017 03:42:07 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E94D9746FF; Thu, 7 Sep 2017 03:42:06 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-qk0-x22f.google.com with SMTP id r141so24225780qke.2; Wed, 06 Sep 2017 20:42:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=oNc/TQqXi1PlNWhyijC/a26y4GNo6+VEoaVKgXaZhgQ=; b=m+Mf/utu7ngSeMaSXxPkPmwI6WJW3GtIjsqlENOcS5jhlqq4vueVsODO8AfAFteNBs 5lytA/kl/M4rjbQrKtBH8wpAYK/P7PQ7vDIQqfqLSGSNZXjd7woKPHXpPDy6o61oya/z ffzF2Wety5SwoNVWOfx7smiwkDaCdJNPpSLe3NfLDEqyQWeIxacJjGAgiQJP6Wi0uxwN /i9JYM2Y57LFXxY+8Q8mwmsinLZM87t9KZ1TFolsG/xyN39Yvlte13s4y+YHuNjdShY/ Y7wyy1OcrRHaosnRpCT6TqD4fhmC88xnFLuucbKaXs/LAyPam1Msj09gJUOw1gzHpIoC s09g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=oNc/TQqXi1PlNWhyijC/a26y4GNo6+VEoaVKgXaZhgQ=; b=jOQ9eHgP8ZCw2VVmoDoAZVY1/wUFKhNPtrN1DhVkOBEN/l5eG7W8WGeGekNg4xIYoh b40avPOoJ0XU8XCbatFGfQJB7VpvoBj4fd8pc4csxNsUEv8hU4fG10lvfj7Bl1yQsBmZ dp0+nirIdUEF1LUpqTjgj4nT0Xxgp0HxvrpASDnzzveitZhvAp41X3ixhGApB5+fjncx kOvereaCEz1YEPn8o8ZtPZhjJZWRz9+iCw0D61AvSmZaYEbFXmkkbUQ3QDiE+OSaShhs 99vYxLCEFK36htr7AYnHowM3uZhARDpgl3ltLlAhp/C8aDGVikIlk9GLxN2ktz70mcWp BumQ== X-Gm-Message-State: AHPjjUhwxVmmrAUx+f31R2nPsdrKXk4FvpXAc0QgQPE852AGXr8i6K7X iwBCnlCFeOmiH+a5C8iXloPxBDXaLzXw X-Google-Smtp-Source: AOwi7QDOckJ8f5xK/xffwnKK98TsHCKHGIyeoBgWr9wHWxATKtjRjQ47p8YB8wn0/gni2gdxFgNKr8dHKakg/dywrS8= X-Received: by 10.55.102.13 with SMTP id a13mr1820801qkc.320.1504755725539; Wed, 06 Sep 2017 20:42:05 -0700 (PDT) MIME-Version: 1.0 Sender: sepherosa@gmail.com Received: by 10.140.106.102 with HTTP; Wed, 6 Sep 2017 20:42:04 -0700 (PDT) In-Reply-To: References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> From: Sepherosa Ziehau Date: Thu, 7 Sep 2017 11:42:04 +0800 X-Google-Sender-Auth: 1bDlBC0fby4u44eo-9_bhxrq4C4 Message-ID: Subject: Re: 11.1 running on HyperV hn interface hangs To: Julian Elischer Cc: freebsd-stable@freebsd.org, paul.koch137@gmail.com, Hongjiang Zhang Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 03:42:07 -0000 Ignore ths hn_dec_txdesc.diff, please try this done; should be more effective: https://people.freebsd.org/~sephe/hn_inc_txbr.diff On Thu, Sep 7, 2017 at 10:22 AM, Sepherosa Ziehau wrote: > Is it possible to tell me your workload? e.g. TX heavy or RX heavy. > Enabled TSO or not. Details like how the send syscalls are issue will > be interesting. And your Windows version, include the patch level, > etc. > > Please try the following patch: > https://people.freebsd.org/~sephe/hn_dec_txdesc.diff > > Thanks, > sephe > > > On Wed, Sep 6, 2017 at 11:23 PM, Julian Elischer wrote: >> On 6/9/17 7:02 pm, Pete French wrote: >>>> >>>> We recently moved our software from 11.0-p9 to 11.1-p1, but looks like >>>> there >>>> is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 R2) >>>> where >>>> the virtual hn0 interface hangs with the following kernel messages: >>>> >>>> hn0: on vmbus0 >>>> hn0: Ethernet address: 00:15:5d:31:21:0f >>>> hn0: link state changed to UP >>>> ... >>>> hn0: RXBUF ack retry >>>> hn0: RXBUF ack failed >>>> last message repeated 571 times >>>> >>>> It requires a restart of the HyperV VM. >>>> >>>> This is a customer production server (remote customer ~4000km away) >>>> running >>>> fairly critical monitoring software, so we needed to roll it back to >>>> 11.0-p9. >>>> We only have two customers running our software in HyperV, vs lots in >>>> VMware >>>> and a handful on physical hardware. >>>> >>>> 11.0-p9 has been very stable. Has anyone seen this problem before with >>>> 11.1 ? >>> >>> >>> >>> I don't run anything on local hyper-v anymore, but I do run a ot of stuff >>> in Azure, and we havent seen anything like this. I track STABLE for things >>> though, updating after reading the commits and testing locally for a week or >>> so, so the version I am running currently is r320175, which was part of >>> 11.1-BETA2. I am going to upgrade to a more recent STABLE sometime this weke >>> or next though, will do that on a test amchine and let you now how it goes. >>> >>> I seem to recall that there were some large changes to the hn code in >>> August to add virtual function support. When does 11.1-p1 date from ? >> >> make sure you contact the FreeBSD/Microsoft guys. Very responsive.. don't >> know if they watch -stable.. >> I'll cc a couple.. >> >>> >>> -pete. >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >>> >> > > > > -- > Tomorrow Will Never Die -- Tomorrow Will Never Die