[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 3 Feb 2024 01:14:53 +0500
From: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To: Marco Elver <elver@...gle.com>
Cc: Andrey Konovalov <andreyknvl@...il.com>, glider@...gle.com, dvyukov@...gle.com,
eugenis@...gle.com, Oscar Salvador <osalvador@...e.de>, Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: regression/bisected commit 773688a6cb24b0b3c2ba40354d883348a2befa38
make my system completely unusable under high load
On Fri, Feb 2, 2024 at 10:20 PM Marco Elver <elver@...gle.com> wrote:
>
> Your config has lockdep enabled, right?
Yes.
> Because cc478e0b6bdf was fixing an issue with lockdep, does your kernel
> before that commit show some lockdep errors?
Let's check it, I attached the kernel log of aaa2c9a97c22.
mikhail@...mary-ws ~> uname -r
6.7.0-c11-aaa2c9a97c22af5bf011f6dd8e0538219b45af88+
mikhail@...mary-ws ~> sudo dmesg | grep lockdep
[sudo] password for mikhail:
[ 3.115891] rcu: RCU lockdep checking is enabled.
[ 3.125718] The code is fine but needs lockdep annotation, or maybe
[ 3.125786] ? lockdep_init_map_type+0x1a5/0x840
[ 12.967789] INFO: lockdep is turned off.
> Because if lockdep encounters an error it usually
> turns itself off right away, which would explain the improved
> performance. :-)
You are right.
Thanks for digging into it!
--
Best Regards,
Mike Gavrilov.
Download attachment "dmesg-aaa2c9a97c22af5bf011f6dd8e0538219b45af88.zip" of type "application/zip" (48088 bytes)
Powered by blists - more mailing lists