[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <de7b03dea71547f995b204ddfe7ceb35710ec951.camel@web.de>
Date: Wed, 11 Dec 2024 21:28:02 +0100
From: Bert Karwatzki <spasswolf@....de>
To: Thomas Gleixner <tglx@...utronix.de>, jstultz@...gle.com
Cc: Metin.Kaya@....com, boqun.feng@...il.com, bsegall@...gle.com,
daniel.lezcano@...aro.org, dave@...olabs.net, dietmar.eggemann@....com,
joelaf@...gle.com, juri.lelli@...hat.com, kernel-team@...roid.com,
kprateek.nayak@....com, linux-kernel@...r.kernel.org, longman@...hat.com,
mgorman@...e.de, mingo@...hat.com, paulmck@...nel.org,
peterz@...radead.org, qyousef@...alina.io, rostedt@...dmis.org,
vincent.guittot@...aro.org, vschneid@...hat.com, will@...nel.org,
xuewen.yan94@...il.com, zezeozue@...gle.com
Subject: Re: commit 894d1b3db41c leads to frequent hangs when booting
Am Mittwoch, dem 11.12.2024 um 20:19 +0100 schrieb Thomas Gleixner:
> On Wed, Dec 11 2024 at 19:25, Bert Karwatzki wrote:
> > I tried to debug this with CONFIG_LOCKDEP=y in v6.13-rc2, but using CONFIG_LOCKDEP=y
> > makes the hangs disappear or far less likely, and I get this warning
> > (2 examples from two boots):
> >
> > [ 17.203857] [ T1337] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
>
> config LOCKDEP_CHAINS_BITS
> int "Bitsize for MAX_LOCKDEP_CHAINS"
> depends on LOCKDEP && !LOCKDEP_SMALL
> range 10 21
> default 16
> help
> Try increasing this value if you hit "BUG: MAX_LOCKDEP_CHAINS too low!" message.
>
> Can you increase the chain bits config and try again?
>
> Thanks,
>
> tglx
With LOCKDEP_CHAINS_BITS=21 I just get and boot with no hang and no error
message from lockdep, CONFIG_LOCKDEP=y yes seems to make the bug go away.
Bert Karwatzki
Powered by blists - more mailing lists