From: Bert Karwatzki <spasswolf@web.de>
To: Thomas Gleixner <tglx@linutronix.de>, jstultz@google.com
Cc: Metin.Kaya@arm.com, boqun.feng@gmail.com, bsegall@google.com,
daniel.lezcano@linaro.org, dave@stgolabs.net,
dietmar.eggemann@arm.com, joelaf@google.com,
juri.lelli@redhat.com, kernel-team@android.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
longman@redhat.com, mgorman@suse.de, mingo@redhat.com,
paulmck@kernel.org, peterz@infradead.org, qyousef@layalina.io,
rostedt@goodmis.org, vincent.guittot@linaro.org,
vschneid@redhat.com, will@kernel.org, xuewen.yan94@gmail.com,
zezeozue@google.com
Subject: Re: commit 894d1b3db41c leads to frequent hangs when booting
Date: Wed, 11 Dec 2024 21:28:02 +0100 [thread overview]
Message-ID: <de7b03dea71547f995b204ddfe7ceb35710ec951.camel@web.de> (raw)
In-Reply-To: <87wmg69gex.ffs@tglx>
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
next prev parent reply other threads:[~2024-12-11 20:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 18:25 commit 894d1b3db41c leads to frequent hangs when booting Bert Karwatzki
2024-12-11 19:19 ` Thomas Gleixner
2024-12-11 20:27 ` John Stultz
2024-12-11 20:43 ` Bert Karwatzki
2024-12-11 21:08 ` John Stultz
2024-12-11 20:28 ` Bert Karwatzki [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 21:35 Bert Karwatzki
2024-12-11 22:46 ` Bert Karwatzki
2024-12-11 23:14 ` John Stultz
2024-12-12 0:16 ` Bert Karwatzki
2024-12-12 2:41 ` John Stultz
2024-12-12 7:40 ` John Stultz
2024-12-12 10:31 ` Bert Karwatzki
2024-12-12 11:56 ` Bert Karwatzki
2024-12-12 12:14 ` Bert Karwatzki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de7b03dea71547f995b204ddfe7ceb35710ec951.camel@web.de \
--to=spasswolf@web.de \
--cc=Metin.Kaya@arm.com \
--cc=boqun.feng@gmail.com \
--cc=bsegall@google.com \
--cc=daniel.lezcano@linaro.org \
--cc=dave@stgolabs.net \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@kernel.org \
--cc=xuewen.yan94@gmail.com \
--cc=zezeozue@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox