From: Jeremiah Mahler <jmmahler@gmail.com>
To: Dexuan Cui <decui@microsoft.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: linux-next: next-20160301: unregister_netdevice: waiting for lo to become free. Usage count = 2
Date: Tue, 1 Mar 2016 12:07:49 -0800 [thread overview]
Message-ID: <20160301200749.GA1611@hudson.localdomain> (raw)
In-Reply-To: <6c735168f53548a39bd21e6e9857f512@HKXPR3004MB0088.064d.mgd.msft.net>
Hi all,
On Tue, Mar 01, 2016 at 08:11:54AM +0000, Dexuan Cui wrote:
> Hi, I got this line every 10 seconds with today's linux-next in a Hyper-V guest, even
> when I didn't configure any NIC for the guest:
>
> [ 72.604249] unregister_netdevice: waiting for lo to become free. Usage count = 2
> [ 82.708170] unregister_netdevice: waiting for lo to become free. Usage count = 2
> [ 92.788079] unregister_netdevice: waiting for lo to become free. Usage count = 2
> [ 102.808132] unregister_netdevice: waiting for lo to become free. Usage count = 2
> [ 112.928166] unregister_netdevice: waiting for lo to become free. Usage count = 2
> [ 122.952069] unregister_netdevice: waiting for lo to become free. Usage count = 2
>
> I don't think this is related to the underlying host, since it's related to "lo".
>
> This should be a recent regression, as I remember the January linux-next didn't have
> this issue.
>
> Any idea?
>
> The gzip-ed kernel config is attached FYI.
>
> Thanks,
> -- Dexuan
>
Just a "me too", but I have this problem on a Lenovo Carbon X1 when
running linux-next 20160301. It worked with 20160225.
I can test patches and I will try to bisect the problem as time allows.
--
- Jeremiah Mahler
next prev parent reply other threads:[~2016-03-01 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 8:11 linux-next: next-20160301: unregister_netdevice: waiting for lo to become free. Usage count = 2 Dexuan Cui
2016-03-01 20:07 ` Jeremiah Mahler [this message]
2016-03-02 20:31 ` [REGRESSION, bisect] net: ipv6: " Jeremiah Mahler
2016-03-02 21:00 ` David Ahern
2016-03-03 1:23 ` Jeremiah Mahler
2016-03-03 5:25 ` Dexuan Cui
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=20160301200749.GA1611@hudson.localdomain \
--to=jmmahler@gmail.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--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).