On Fri, Feb 2, 2024 at 10:20 PM Marco Elver <elver@xxxxxxxxxx> 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: dmesg-aaa2c9a97c22af5bf011f6dd8e0538219b45af88.zip>>
