From owner-freebsd-stable@freebsd.org Thu Sep 7 02:22:43 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 C19E1E0000D for ; Thu, 7 Sep 2017 02:22:43 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (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 DDF913EF7; Thu, 7 Sep 2017 02:22:42 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-qk0-x235.google.com with SMTP id z143so23984807qkb.3; Wed, 06 Sep 2017 19:22:42 -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=SwaOEFFdQ51OTqezjWjZwTHU/rGgoPFDtui4omi3j2M=; b=mX0IALZEpNSlzFj6iG1rI+HMm2OPXcF6OShQnPZX/rT59ySMVDsO3UbzpsziIHATfr MJGo970/ucH7PGH2kGnfgcjOZoxZR3kDryfEHUZE69780zKczKveCJbz8S06rTpyXlHr cTomLTTu/gIXi6tp2ItPfoykjTiPjvtVMzJ0tmLfQfKmCqWK+DJmdrg0CNT32TxIX3fF SdBQs1w2C+o62Emt78jkKF4cK/s+aaavdzVuzW/Cvh9slgLZCHtXFIfJiuYnkN8gbr4l uVbOc6s5qo/uXtb6kRxpOhzX6zay4MGBc8HCl/chtVUWFWCzUXd79yPvml+syQpeKN01 d6Kg== 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=SwaOEFFdQ51OTqezjWjZwTHU/rGgoPFDtui4omi3j2M=; b=dcO7mygc/QCxGl3G+i6vUmVQJU07VJXh+s5vXZ8+QgSukl57q0/3pjpD/w7N9WvhH1 pczuEIgaFlwxsswzyv+ph4Q2+D4wkdiury+Nv0LvWp80PSImyRij8TTAJ4rvvTbogmZD qjUDyxDR3eZ6BwnG0AR+bLPIjsTkH6tVOYDIEuPvI61xgqNFqH8yUlq/8gTTTJlJ5Z26 Sp5jcdxpbSOWhhBiGBshcUNlIQiIBcD69GaFEC4bowD/Ga1V9XJ0FokZDXcRu1qu2Egr BRxBFh0PFfGLLnGSZMpUJrmrJwsNlAyW0oJXdq+6/np7aAn5HnicZ4UfudfthEUZ+DjO Cilg== X-Gm-Message-State: AHPjjUhuVLnJOorG77I6cif9Ez6YmdGT6ZXNFqCj16QxcgZUFfX0aSHy hZL/Dpns852i5GgV1EPe4MBYNNSBHnev X-Google-Smtp-Source: ADKCNb4g6ZnvBlYVfpEJy5VYXqaXH/oB5f/5TtrbXp74epojzAVC8/1cPPlXc/E8aebqCt6qQCip3E8wObSjtbwe56A= X-Received: by 10.55.167.144 with SMTP id q138mr1607704qke.74.1504750961434; Wed, 06 Sep 2017 19:22:41 -0700 (PDT) MIME-Version: 1.0 Sender: sepherosa@gmail.com Received: by 10.140.106.102 with HTTP; Wed, 6 Sep 2017 19:22:40 -0700 (PDT) In-Reply-To: <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> 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 10:22:40 +0800 X-Google-Sender-Auth: PPEpCA14CrmF5KmwmqnA-YJppIc 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 02:22:43 -0000 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