From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: KY Srinivasan <kys@microsoft.com>,
"David S. Miller" <davem@davemloft.net>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [BISECTED][REGRESSION] Loading Hyper-V network drivers is racy in 3.14+ on Hyper-V 2012 R2
Date: Mon, 14 Jul 2014 22:30:32 +0100 [thread overview]
Message-ID: <20140714213032.GA23639@sucs.org> (raw)
In-Reply-To: <52afbe119b1a481aa1c80f909c3a2432@DFM-DB3MBX15-06.exchange.corp.microsoft.com>
On Fri, Jul 11, 2014 at 03:25:11PM +0000, Haiyang Zhang wrote:
>
> > -----Original Message-----
> > From: Sitsofe Wheeler [mailto:sitsofe@gmail.com]
> > Sent: Friday, July 11, 2014 1:53 AM
> > To: Haiyang Zhang
> > Cc: KY Srinivasan; David S. Miller; devel@linuxdriverproject.org; linux-
> > kernel@vger.kernel.org; netdev@vger.kernel.org
> > Subject: Re: [BISECTED][REGRESSION] Loading Hyper-V network drivers is
> > racy in 3.14+ on Hyper-V 2012 R2
>
> > Oops that should have been
> > https://bugzilla.kernel.org/attachment.cgi?id=142351 (either way it's
> > information linked off
> > https://bugzilla.kernel.org/show_bug.cgi?id=78771 ).
>
> Thanks for the dmesg. By looking at it, seems the netvsc driver was
> loaded properly, and 2 NICs are up, one NIC is down (probably not set
> to connected in HyperV manager?). Or, this dmesg wasn't the one when
> bug happens?
This was a dmesg where the bug did happen and your first guess is right
- there are 3 NICs but only the first two are connected and the last is
set to "Not connected" in Hyper-V Manager.
> Since you found the commit b679ef73edc is related to this problem,
> could you do a simple test:
> Reduce the receive buffer size back to 2MB, like below, then re-test
> it, see if the problem goes away?
> drivers/net/hyperv/hyperv_net.h
> #define NETVSC_RECEIVE_BUFFER_SIZE (1024*1024*2) /* 2MB */
After doing this I was able to reach over 900 reboots where the network
connected properly.
--
Sitsofe | http://sucs.org/~sits/
WARNING: multiple messages have this Message-ID (diff)
From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: "devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BISECTED][REGRESSION] Loading Hyper-V network drivers is racy in 3.14+ on Hyper-V 2012 R2
Date: Mon, 14 Jul 2014 22:30:32 +0100 [thread overview]
Message-ID: <20140714213032.GA23639@sucs.org> (raw)
In-Reply-To: <52afbe119b1a481aa1c80f909c3a2432@DFM-DB3MBX15-06.exchange.corp.microsoft.com>
On Fri, Jul 11, 2014 at 03:25:11PM +0000, Haiyang Zhang wrote:
>
> > -----Original Message-----
> > From: Sitsofe Wheeler [mailto:sitsofe@gmail.com]
> > Sent: Friday, July 11, 2014 1:53 AM
> > To: Haiyang Zhang
> > Cc: KY Srinivasan; David S. Miller; devel@linuxdriverproject.org; linux-
> > kernel@vger.kernel.org; netdev@vger.kernel.org
> > Subject: Re: [BISECTED][REGRESSION] Loading Hyper-V network drivers is
> > racy in 3.14+ on Hyper-V 2012 R2
>
> > Oops that should have been
> > https://bugzilla.kernel.org/attachment.cgi?id=142351 (either way it's
> > information linked off
> > https://bugzilla.kernel.org/show_bug.cgi?id=78771 ).
>
> Thanks for the dmesg. By looking at it, seems the netvsc driver was
> loaded properly, and 2 NICs are up, one NIC is down (probably not set
> to connected in HyperV manager?). Or, this dmesg wasn't the one when
> bug happens?
This was a dmesg where the bug did happen and your first guess is right
- there are 3 NICs but only the first two are connected and the last is
set to "Not connected" in Hyper-V Manager.
> Since you found the commit b679ef73edc is related to this problem,
> could you do a simple test:
> Reduce the receive buffer size back to 2MB, like below, then re-test
> it, see if the problem goes away?
> drivers/net/hyperv/hyperv_net.h
> #define NETVSC_RECEIVE_BUFFER_SIZE (1024*1024*2) /* 2MB */
After doing this I was able to reach over 900 reboots where the network
connected properly.
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2014-07-14 21:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-06 20:18 [BISECTED][REGRESSION] Loading Hyper-V network drivers is racy in 3.14+ on Hyper-V 2012 R2 Sitsofe Wheeler
2014-07-06 20:18 ` Sitsofe Wheeler
2014-07-07 16:54 ` Haiyang Zhang
2014-07-07 18:13 ` Sitsofe Wheeler
2014-07-11 5:52 ` Sitsofe Wheeler
2014-07-11 5:52 ` Sitsofe Wheeler
2014-07-11 15:25 ` Haiyang Zhang
2014-07-14 21:30 ` Sitsofe Wheeler [this message]
2014-07-14 21:30 ` Sitsofe Wheeler
2014-07-14 22:39 ` Haiyang Zhang
2014-07-15 5:08 ` Sitsofe Wheeler
2014-07-15 5:08 ` Sitsofe Wheeler
2014-07-18 21:30 ` Haiyang Zhang
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=20140714213032.GA23639@sucs.org \
--to=sitsofe@gmail.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.