public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bernhard@bwalle.de>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>, linux-kernel@vger.kernel.org
Subject: Regression in hyperv network driver in 3.14
Date: Tue, 27 May 2014 13:10:03 +0200	[thread overview]
Message-ID: <20140527111003.GA2214@kepler.fritz.box> (raw)

Hello,

using a 3.14 kernel in a Linux VM running on HyperV (Windows Server 2008
R2) we get following error:

   hv_netvsc: hv_netvsc channel opened successfully
   hv_netvsc vmbus_0_9 (unregistered net_device): Unable to complete receive buffer initialization with NetVsp - status 2
   hv_netvsc vmbus_0_9 (unregistered net_device): unable to connect to NetVSP - -22
   hv_netvsc vmbus_0_9 (unregistered net_device): unable to add netvsc device (ret -22)
   hv_netvsc: probe of vmbus_0_9 failed with error -22

Bisecting the problem shows that commit
b679ef73edc251f6d200a7dd2396e9fef9e36fc3 is responsible. Reverting it
fixes the issue. Even only changing NETVSC_RECEIVE_BUFFER_SIZE to 2M
fixes the issue!

The virtual machine has 2 GiB of memory and 4 CPUs.

Can I provide more information to track down the problem?


Regards,
Bernhard


             reply	other threads:[~2014-05-27 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 11:10 Bernhard Walle [this message]
2014-05-27 13:43 ` Regression in hyperv network driver in 3.14 KY Srinivasan
2014-05-27 14:42   ` Bernhard Walle
2014-05-27 15:22     ` Haiyang Zhang
2014-06-26  8:19       ` Non-FIXed in Linux Kernel v3.14.8 2014-06-16 Fw: hyperv: Change the receive buffer size for legacy hosts Re: Regression in hyperv network driver in 3.14 Fw: Debian Bug#748609: ( 3.14-0 : Hyper-V netvsc no networking) Victor Miasnikov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140527111003.GA2214@kepler.fritz.box \
    --to=bernhard@bwalle.de \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox