[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200908151229.g24j4n4fderlm2pe@linutronix.de>
Date: Tue, 8 Sep 2020 17:12:29 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Mike Galbraith <efault@....de>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
linux-rt-users <linux-rt-users@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: v5.9-rc3-rt3 boot time networking lockdep splat
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.001111] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
> [ 209.001113] turning off the locking correctness validator.
> [ 209.001114] CPU: 2 PID: 3773 Comm: Socket Thread Tainted: G S I E 5.9.0.gc70672d-rt3-rt #8
> [ 209.001117] Hardware name: HP HP Spectre x360 Convertible/804F, BIOS F.47 11/22/2017
> [ 209.001118] Call Trace:
> [ 209.001123] dump_stack+0x77/0x9b
> [ 209.001129] validate_chain+0xf60/0x1230
I have no idea how to debug this based on this report. Can you narrow
it down to something?
Is Lappy new, got a new something or has a new config switch? I'm just
curious if this something or something that was always there but
remained undetected.
(Your other report was about something that was previously always "broken".)
Sebastian
Powered by blists - more mailing lists