On Wed, Mar 29, 2017 at 09:45:16AM -0700, Florian Fainelli wrote:
> On 02/21/2017 12:38 AM, Maxim Uvarov wrote:
> > Is there any progress on subj issue?
I'm afraid the report got completely ignored. Hope you have better luck.
> > I see it was investigated here:
> > https://www.spinics.net/lists/
On 02/21/2017 12:38 AM, Maxim Uvarov wrote:
> Is there any progress on subj issue?
>
> I see it was investigated here:
> https://www.spinics.net/lists/netdev/msg361434.html
I was just able to reproduce this and will try to look into it. At first
glance, the reason why we usually don't see it, is
On Tue, Feb 21, 2017 at 11:38:24AM +0300, Maxim Uvarov wrote:
> Is there any progress on subj issue?
>
> I see it was investigated here:
> https://www.spinics.net/lists/netdev/msg361434.html
Hi Maxim
Nobody made further investigations. And since i don't see it in my
tests, i've never been annoye
Is there any progress on subj issue?
I see it was investigated here:
https://www.spinics.net/lists/netdev/msg361434.html
But it still exist on later kernels:
[ 37.320301] ip/1047 is trying to acquire lock:
[ 37.324764] (_xmit_ETHER/1){+.}, at: [] dev_mc_sync+0x4c/0x88
[ 37.331882]
[
Adding a vlan to a DSA switch port netdev causes the following lockdep
splat on v4.4. This was caused by:
# vconfig add lan5 2048
# ip link set lan5.2048 up
=
[ INFO: possible recursive locking detected ]
4.4.0+ #41 Not tainted
