From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>,
Ziwei Dai <ziwei.dai@unisoc.com>, Hugh Dickins <hughd@google.com>,
Marcus Seyfarth <m.seyfarth@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux RCU <rcu@vger.kernel.org>
Subject: Fwd: [6.5.1] Slow boot and opening files (RIP: kvfree_rcu_bulk)
Date: Sun, 3 Sep 2023 08:34:44 +0700 [thread overview]
Message-ID: <0e6fc43f-3078-911a-e63d-290c3e6d7b91@gmail.com> (raw)
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> I've just made the transition from 6.4.14 to 6.5.1 and my Haswell-EP X99 machine took way longer to boot (55 seconds instead of 16 seconds). The following trace was seen in dmesg which was also not present on 6.4.14 (and might be the cause for the long boot time); this is on bare metal.
>
> [ +0,000021] CPU: 13 PID: 338 Comm: kworker/13:1 Not tainted 6.5.1-3.1-cachyos-lto #1 c414458bd5e5db6e6f9addca639c3a78811b24e7
> [ +0,000003] Hardware name: LENOVO GAMING TF/X99-TF Gaming, BIOS CX99DE26 10/10/2020
> [ +0,000002] Workqueue: events kfree_rcu_work
> [ +0,000004] RIP: 0010:kvfree_rcu_bulk+0x13b/0x160
> [ +0,000004] Code: 80 04 00 00 80 bf 89 04 00 00 00 75 24 85 c0 75 20 31 f6 ba 02 00 00 00 e8 72 50 bd ff 5b 41 5c 41 5e 41 5f 5d e9 05 df ba ff <0f> 0b e9 54 ff ff ff a9 ff ff ff 7f 74 e5 80 bf 88 04 00 00 >
> [ +0,000002] RSP: 0018:ffff8fe4611cbd90 EFLAGS: 00010206
> [ +0,000002] RAX: 0000000000000048 RBX: ffff8fe8e04f7000 RCX: fffffffffffffffc
> [ +0,000002] RDX: 0000000000000000 RSI: ffff8fe8e04f7000 RDI: ffff8fe9df95cac8
> [ +0,000001] RBP: ffff8fe4611cbe40 R08: 8080808080808080 R09: fefefefefefefeff
> [ +0,000002] R10: 000073746e657665 R11: 8080000000000000 R12: 0000000000000000
> [ +0,000001] R13: ffff8fe4611cbde0 R14: ffff8fe9df95cac8 R15: ffff8fe4611cbdd0
> [ +0,000001] FS: 0000000000000000(0000) GS:ffff8fe9df940000(0000) knlGS:0000000000000000
> [ +0,000002] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ +0,000002] CR2: 00007f8287bff008 CR3: 00000005e8f73001 CR4: 00000000001706e0
> [ +0,000001] Call Trace:
> [ +0,000003] <TASK>
> [ +0,000001] ? __warn+0x9e/0x160
> [ +0,000004] ? kvfree_rcu_bulk+0x13b/0x160
> [ +0,000004] ? report_bug+0x112/0x180
> [ +0,000003] ? handle_bug+0x3d/0x80
> [ +0,000003] ? exc_invalid_op+0x16/0x40
> [ +0,000003] ? asm_exc_invalid_op+0x16/0x20
> [ +0,000005] ? kvfree_rcu_bulk+0x13b/0x160
> [ +0,000003] kfree_rcu_work+0xcd/0x200
> [ +0,000005] process_one_work+0x21a/0x620
> [ +0,000004] ? wake_up_process+0x1d3/0x1720
> [ +0,000004] worker_thread+0x12b/0x4c0
> [ +0,000003] ? compat_get_bitmap+0xa0/0xa0
> [ +0,000003] kthread+0xf1/0x160
> [ +0,000004] ? getreg32+0x1e0/0x1e0
> [ +0,000003] ret_from_fork+0x30/0x40
> [ +0,000005] ? getreg32+0x1e0/0x1e0
> [ +0,000003] ret_from_fork_asm+0x11/0x20
> [ +0,000005] </TASK>
> [ +0,000001] ---[ end trace 0000000000000000 ]---
Later, the reporter came up with another trace:
> I just saw a patch from Hugh Dickins on the LKML (https://www.spinics.net/lists/kernel/msg4919906.html) and indeed, with my self-compiled 6.5.1 Kernel, the trace is now downgraded to a warning (see below). However, the slow boot still remains and also my games won't load up due to missing a rendering device. But that might be a different issue.
>
>
> [ +0,000227] ------------[ cut here ]------------
> [ +0,000002] WARNING: CPU: 21 PID: 345 at kernel/rcu/tree.c:2952 kvfree_rcu_bulk+0x13b/0x160
> [ +0,000011] Modules linked in: pkcs8_key_parser crypto_user fuse loop zram bpf_preload ip_tables x_tables ext4 crc32c_generic mbcache crc16 jbd2 usbhid amdgpu mfd_core drm_buddy drm_suballoc_helper crc32c_i>
> [ +0,000027] CPU: 21 PID: 345 Comm: kworker/21:1 Not tainted 6.5.1-3.1-cachyos-lto #1 de6495663682da00bbe0d80bdc163dd768b25681
> [ +0,000004] Hardware name: LENOVO GAMING TF/X99-TF Gaming, BIOS CX99DE26 10/10/2020
> [ +0,000002] Workqueue: events kfree_rcu_work
> [ +0,000006] RIP: 0010:kvfree_rcu_bulk+0x13b/0x160
> [ +0,000006] Code: 80 04 00 00 80 bf 89 04 00 00 00 75 24 85 c0 75 20 31 f6 ba 02 00 00 00 e8 52 50 bd ff 5b 41 5c 41 5e 41 5f 5d e9 e5 de ba ff <0f> 0b e9 54 ff ff ff a9 ff ff ff 7f 74 e5 80 bf 88 04 00 00 >
> [ +0,000003] RSP: 0018:ffff8df57a5ffd90 EFLAGS: 00010206
> [ +0,000003] RAX: 0000000000000020 RBX: ffff8df44cb40000 RCX: fffffffffffffffc
> [ +0,000003] RDX: 0000000000000000 RSI: ffff8df44cb40000 RDI: ffff8df91fb5cac8
> [ +0,000002] RBP: ffff8df57a5ffe40 R08: 8080808080808080 R09: fefefefefefefeff
> [ +0,000002] R10: 000073746e657665 R11: 8080000000000000 R12: 0000000000000000
> [ +0,000002] R13: ffff8df57a5ffde0 R14: ffff8df91fb5cac8 R15: ffff8df57a5ffdd0
> [ +0,000002] FS: 0000000000000000(0000) GS:ffff8df91fb40000(0000) knlGS:0000000000000000
> [ +0,000003] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ +0,000002] CR2: 000055fe51d3f700 CR3: 000000065de7d002 CR4: 00000000001706e0
> [ +0,000002] Call Trace:
> [ +0,000003] <TASK>
> [ +0,000002] ? __warn+0x9e/0x160
> [ +0,000006] ? kvfree_rcu_bulk+0x13b/0x160
> [ +0,000005] ? report_bug+0x112/0x180
> [ +0,000005] ? handle_bug+0x3d/0x80
> [ +0,000005] ? exc_invalid_op+0x16/0x40
> [ +0,000003] ? asm_exc_invalid_op+0x16/0x20
> [ +0,000007] ? kvfree_rcu_bulk+0x13b/0x160
> [ +0,000006] kfree_rcu_work+0xcd/0x200
> [ +0,000006] process_one_work+0x21a/0x620
> [ +0,000006] ? wake_up_process+0x1d3/0x1720
> [ +0,000005] worker_thread+0x12b/0x4c0
> [ +0,000005] ? compat_get_bitmap+0xa0/0xa0
> [ +0,000004] kthread+0xf1/0x160
> [ +0,000006] ? getreg32+0x1e0/0x1e0
> [ +0,000004] ret_from_fork+0x30/0x40
> [ +0,000007] ? getreg32+0x1e0/0x1e0
> [ +0,000003] ret_from_fork_asm+0x11/0x20
> [ +0,000009] </TASK>
> [ +0,000001] ---[ end trace 0000000000000000 ]---
See Bugzilla for the full thread.
Anyway, I'm adding this regression to be tracked by regzbot:
#regzbot introduced: v6.4..v6.5 https://bugzilla.kernel.org/show_bug.cgi?id=217864
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217864
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-09-03 1:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 1:34 Bagas Sanjaya [this message]
2023-09-03 3:29 ` Fwd: [6.5.1] Slow boot and opening files (RIP: kvfree_rcu_bulk) Hugh Dickins
2023-09-03 10:45 ` Paul E. McKenney
[not found] ` <CA+FbhJOSfqcb3=ecL-y=13j81b1Ts13wHpzBSURyCRQUvd2NWQ@mail.gmail.com>
[not found] ` <c054b588-b029-4380-9ec5-4ae50ee37d08@paulmck-laptop>
[not found] ` <CA+FbhJO1FbOvP=GmUse-r8Yma1tSv6iqppDhz9Ut1JKpjN49qQ@mail.gmail.com>
[not found] ` <CA+FbhJPOkV4Xa7ZJ4QF2y_-5i24F+TkhByr=LzMPt9iy9EshSQ@mail.gmail.com>
[not found] ` <4009a6e0-198c-4f25-8e34-4774dcd8c537@paulmck-laptop>
[not found] ` <CA+FbhJPxU+QKf1tTBd8XcKcSsTeRmJ=ji_L4QYiad--hGqRB5w@mail.gmail.com>
2023-09-03 15:36 ` Paul E. McKenney
[not found] ` <CA+FbhJPtmFG2vKNXWr67Tuh-4HUi8n81PmKxwftv9iK1a3On-A@mail.gmail.com>
2023-09-04 11:23 ` Uladzislau Rezki
[not found] ` <CA+FbhJPNZ-E3e7WBH_jAvi3Rn-2gV4TVk9S9qmheXkqXw+Sakg@mail.gmail.com>
2023-09-04 15:05 ` Uladzislau Rezki
[not found] ` <CA+FbhJMr6LzmOpVNkYyiSERAsNEqqvQwQ7SwJK=CmwvV9d2Z-A@mail.gmail.com>
2023-09-04 16:53 ` Uladzislau Rezki
2023-09-04 19:13 ` Uladzislau Rezki
[not found] ` <CA+FbhJPNK=4s8J5OqOBaDC8EDNQzevQMQ+fwZnfxG92ReabQOA@mail.gmail.com>
[not found] ` <CA+FbhJMEqLycroz=J6VvC=4OBaJSwz8K+K6Zgki80M-5YdYp6A@mail.gmail.com>
2023-09-05 10:41 ` Uladzislau Rezki
2023-09-05 16:46 ` Uladzislau Rezki
[not found] ` <CA+FbhJOekDxBjQH6jUFXusgakRVx_Y0S3s5avko23c6XqCc2Mw@mail.gmail.com>
[not found] ` <CA+FbhJNQfGW5RMJc-WaOmjqmYuTnqdvRPYO_40TP5=P4LFPDYQ@mail.gmail.com>
2023-09-05 18:46 ` Uladzislau Rezki
[not found] ` <CA+FbhJO4xfdrUtZLWMRMaZdM2W-G+ZKtg9ESdwT8DUFJZKmW-Q@mail.gmail.com>
2023-09-06 10:31 ` Uladzislau Rezki
2023-09-11 13:25 ` Bagas Sanjaya
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=0e6fc43f-3078-911a-e63d-290c3e6d7b91@gmail.com \
--to=bagasdotme@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.seyfarth@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=ziwei.dai@unisoc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).