[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160301200749.GA1611@hudson.localdomain>
Date: Tue, 1 Mar 2016 12:07:49 -0800
From: Jeremiah Mahler <jmmahler@...il.com>
To: Dexuan Cui <decui@...rosoft.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Haiyang Zhang <haiyangz@...rosoft.com>
Subject: Re: linux-next: next-20160301: unregister_netdevice: waiting for lo
to become free. Usage count = 2
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
Powered by blists - more mailing lists