Re: v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-08 Thread Mike Galbraith
On Tue, 2020-09-08 at 17:06 +0200, Sebastian Andrzej Siewior wrote: > > This should cure it: It did. -Mike

Re: v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-08 Thread Mike Galbraith
On Tue, 2020-09-08 at 14:19 +0200, Sebastian Andrzej Siewior wrote: > > This has nothing to do with the bridge but with the fact that you use a > non standard queue class (something else than pfifo_fast). That must be SUSE, I don't muck about in network land. I downloaded a whole library of RFCs

Re: v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-08 Thread Sebastian Andrzej Siewior
On 2020-09-08 16:56:20 [+0200], Mike Galbraith wrote: > On Tue, 2020-09-08 at 14:19 +0200, Sebastian Andrzej Siewior wrote: > > > > This has nothing to do with the bridge but with the fact that you use a > > non standard queue class (something else than pfifo_fast). > > That must be SUSE, I don't

Re: v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-08 Thread Sebastian Andrzej Siewior
On 2020-09-05 07:19:10 [+0200], Mike Galbraith wrote: > Lappy, which does not use bridge, boots clean... but lock leakage > pretty darn quickly inspires lockdep to craps its drawers. > > [ 209.00] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! > [ 209.001113] turning off the locking correctness vali

Re: v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-08 Thread Mike Galbraith
On Tue, 2020-09-08 at 17:12 +0200, Sebastian Andrzej Siewior wrote: > On 2020-09-05 07:19:10 [+0200], Mike Galbraith wrote: > > Lappy, which does not use bridge, boots clean... but lock leakage > > pretty darn quickly inspires lockdep to craps its drawers. > > > > [ 209.00] BUG: MAX_LOCKDEP_CH

Re: v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-08 Thread Sebastian Andrzej Siewior
On 2020-09-08 17:59:31 [+0200], Mike Galbraith wrote: > > I have no idea how to debug this based on this report. Can you narrow > > it down to something? > > I instrumented what I presume is still this problem once upon a time, > structures containing locks are allocated/initialized/freed again an

Re: v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-08 Thread Sebastian Andrzej Siewior
On 2020-09-05 06:47:29 [+0200], Mike Galbraith wrote: > [ 22.024936] == > [ 22.024936] WARNING: possible circular locking dependency detected > [ 22.024937] 5.9.0.gc70672d-rt3-rt #8 Tainted: GE > [ 22.024938] --

Re: v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-08 Thread Mike Galbraith
On Tue, 2020-09-08 at 17:06 +0200, Sebastian Andrzej Siewior wrote: > On 2020-09-08 16:56:20 [+0200], Mike Galbraith wrote: > > On Tue, 2020-09-08 at 14:19 +0200, Sebastian Andrzej Siewior wrote: > > > > > > This has nothing to do with the bridge but with the fact that you use a > > > non standard

Re: v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-04 Thread Mike Galbraith
Lappy, which does not use bridge, boots clean... but lock leakage pretty darn quickly inspires lockdep to craps its drawers. [ 209.00] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! [ 209.001113] turning off the locking correctness validator. [ 209.001114] CPU: 2 PID: 3773 Comm: Socket Thread Taint

v5.9-rc3-rt3 boot time networking lockdep splat

2020-09-04 Thread Mike Galbraith
[ 22.004225] r8169 :03:00.0 eth0: Link is Up - 1Gbps/Full - flow control off [ 22.004450] br0: port 1(eth0) entered blocking state [ 22.004473] br0: port 1(eth0) entered forwarding state [ 22.006411] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready [ 22.024936] ===