From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Marco Elver <elver@google.com>
Cc: Andrey Konovalov <andreyknvl@gmail.com>,
glider@google.com, dvyukov@google.com, eugenis@google.com,
Oscar Salvador <osalvador@suse.de>,
Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: regression/bisected commit 773688a6cb24b0b3c2ba40354d883348a2befa38 make my system completely unusable under high load
Date: Sat, 3 Feb 2024 01:14:53 +0500 [thread overview]
Message-ID: <CABXGCsPB-KEbE+SfymVmqfiomFVngFL2Je81Qyhw1F5_aZX-TQ@mail.gmail.com> (raw)
In-Reply-To: <CANpmjNOnbNw2fRL3_depaAgt81p-VpHh5_O_26kyxofjECgsFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Fri, Feb 2, 2024 at 10:20 PM Marco Elver <elver@google.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@primary-ws ~> uname -r
6.7.0-c11-aaa2c9a97c22af5bf011f6dd8e0538219b45af88+
mikhail@primary-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.
[-- Attachment #2: dmesg-aaa2c9a97c22af5bf011f6dd8e0538219b45af88.zip --]
[-- Type: application/zip, Size: 48088 bytes --]
next prev parent reply other threads:[~2024-02-02 20:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 10:46 Mikhail Gavrilov
2024-01-19 10:54 ` Marco Elver
2024-01-19 10:59 ` Marco Elver
2024-01-19 17:54 ` Mikhail Gavrilov
2024-01-29 22:25 ` Mikhail Gavrilov
2024-01-29 23:14 ` Andrey Konovalov
2024-02-01 22:08 ` Mikhail Gavrilov
2024-02-02 9:00 ` Marco Elver
2024-02-02 16:35 ` Mikhail Gavrilov
2024-02-02 16:47 ` Marco Elver
2024-02-02 17:19 ` Marco Elver
2024-02-02 20:14 ` Mikhail Gavrilov [this message]
2024-02-19 9:48 ` Mikhail Gavrilov
2024-02-19 9:52 ` Marco Elver
2024-02-19 10:09 ` Vlastimil Babka
2024-02-19 23:28 ` Andrew Morton
2024-02-19 23:50 ` Vlastimil Babka
2024-02-20 5:37 ` Mikhail Gavrilov
2024-02-20 17:30 ` Andrew Morton
2024-02-20 18:16 ` Vlastimil Babka
2024-02-20 18:51 ` Marco Elver
2024-02-26 9:25 ` Marco Elver
2024-02-26 10:12 ` Vlastimil Babka
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=CABXGCsPB-KEbE+SfymVmqfiomFVngFL2Je81Qyhw1F5_aZX-TQ@mail.gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
/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