netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 11 Jul 2014 06:52:59 +0100	[thread overview]
Message-ID: <20140711055259.GA10317@sucs.org> (raw)
In-Reply-To: <20140707181341.GA2646@sucs.org>

On Mon, Jul 07, 2014 at 07:13:41PM +0100, Sitsofe Wheeler wrote:
> On Mon, Jul 07, 2014 at 04:54:20PM +0000, Haiyang Zhang wrote:
> > 
> > > -----Original Message-----
> > > From: Sitsofe Wheeler [mailto:sitsofe@gmail.com]
> > > Sent: Sunday, July 6, 2014 4:18 PM
> > > To: Haiyang Zhang
> > > Cc: KY Srinivasan; David S. Miller; devel@linuxdriverproject.org; linux-
> > > kernel@vger.kernel.org; netdev@vger.kernel.org
> > > Subject: [BISECTED][REGRESSION] Loading Hyper-V network drivers is racy in
> > > 3.14+ on Hyper-V 2012 R2
> > > 
> > > With the 3.14 kernel Hyper-V no longer reliably enables its
> > > networking devices in time on cloud images leading to network
> > > devices permanently remaining offline.
> > > 
> <snip>
> > > the system will usually stop rebooting before 20 passes but the most
> > > extreme cases were always less than 100. With a pre
> > > b679ef73edc251f6d200a7dd2396e9fef9e36fc3 kernel it did over 390
> > > passes before I manually stopped it.
> > > 
> > > Originally filed on https://bugzilla.redhat.com/show_bug.cgi?id=1095387
> > > and then on https://bugzilla.kernel.org/show_bug.cgi?id=78771 but without
> > > reply...
> > > 
> > > Might also be related to
> > > http://thread.gmane.org/gmane.linux.kernel/1711873/focus=1733398
> > > (Regression in hyperv network driver in 3.14).
> > 
> > What's the memory size assigned to the Linux guest? And, have you seen
> > any related messages in the dmesg log after this issue?
> 
> (Feel free to trim my emails when replying - it makes it easier to see
> your reply :-)
> 
> I've had as little as 256 MBytes and as much as 4 GBytes (non-dynamic)
> and still seen the issue.
> 
> See https://bugzilla.kernel.org/attachment.cgi?id=142201 for a recent
> dmesg (an older dmesg snippet can be seen on the Red Hat bugzilla).

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 ).

-- 
Sitsofe | http://sucs.org/~sits/

  reply	other threads:[~2014-07-11  5:52 UTC|newest]

Thread overview: 9+ 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-07 16:54 ` Haiyang Zhang
2014-07-07 18:13   ` Sitsofe Wheeler
2014-07-11  5:52     ` Sitsofe Wheeler [this message]
2014-07-11 15:25       ` Haiyang Zhang
2014-07-14 21:30         ` Sitsofe Wheeler
2014-07-14 22:39           ` Haiyang Zhang
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=20140711055259.GA10317@sucs.org \
    --to=sitsofe@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).