From: Laura Nao <laura.nao@collabora.com>
To: regressions@lists.linux.dev
Cc: linux-kernel@vger.kernel.org, kernel@collabora.com,
bpf@vger.kernel.org, chrome-platform@lists.linux.dev
Subject: [REGRESSION] module BTF validation failure (Error -22) on next
Date: Wed, 6 Nov 2024 17:08:20 +0100 [thread overview]
Message-ID: <20241106160820.259829-1-laura.nao@collabora.com> (raw)
Hello,
KernelCI has detected a module loading regression affecting all AMD and
Intel Chromebooks in the Collabora LAVA lab, occurring between
next-20241024 and next-20241025.
The logs indicate a failure in BTF module validation, preventing all
modules from loading correctly (with CONFIG_MODULE_ALLOW_BTF_MISMATCH
unset). The example below is from an AMD Chromebook (HP 14b na0052xx),
with similar errors observed on other AMD and Intel devices:
[ 5.284373] failed to validate module [cros_kbd_led_backlight] BTF: -22
[ 5.291392] failed to validate module [i2c_hid] BTF: -22
[ 5.293958] failed to validate module [chromeos_pstore] BTF: -22
[ 5.302832] failed to validate module [coreboot_table] BTF: -22
[ 5.309175] failed to validate module [raydium_i2c_ts] BTF: -22
[ 5.309264] failed to validate module [i2c_cros_ec_tunnel] BTF: -22
[ 5.322158] failed to validate module [typec] BTF: -22
[ 5.327554] failed to validate module [snd_timer] BTF: -22
[ 5.327573] failed to validate module [cros_usbpd_notify] BTF: -22
[ 5.339272] failed to validate module [elan_i2c] BTF: -22
[ 5.345821] failed to validate module [industrialio] BTF: -22
[ 5.423113] failed to validate module [cfg80211] BTF: -22
[ 5.443074] failed to validate module [cros_ec_dev] BTF: -22
[ 5.448857] failed to validate module [snd_pci_acp3x] BTF: -22
[ 5.454736] failed to validate module [cros_kbd_led_backlight] BTF: -22
[ 5.461458] failed to validate module [regmap_i2c] BTF: -22
[ 5.470228] failed to validate module [i2c_piix4] BTF: -22
[ 5.491123] failed to validate module [i2c_hid] BTF: -22
[ 5.491226] failed to validate module [chromeos_pstore] BTF: -22
[ 5.496519] failed to validate module [coreboot_table] BTF: -22
[ 5.502632] failed to validate module [snd_timer] BTF: -22
[ 5.538916] failed to validate module [gsmi] BTF: -22
[ 5.604971] failed to validate module [mii] BTF: -22
[ 5.604971] failed to validate module [videobuf2_common] BTF: -22
[ 5.604972] failed to validate module [sp5100_tco] BTF: -22
[ 5.616068] failed to validate module [snd_soc_acpi] BTF: -22
[ 5.680553] failed to validate module [bluetooth] BTF: -22
[ 5.749320] failed to validate module [chromeos_pstore] BTF: -22
[ 5.755440] failed to validate module [mii] BTF: -22
[ 5.760522] failed to validate module [snd_timer] BTF: -22
[ 5.783549] failed to validate module [bluetooth] BTF: -22
[ 5.841561] failed to validate module [mii] BTF: -22
[ 5.846699] failed to validate module [snd_timer] BTF: -22
[ 5.892444] failed to validate module [mii] BTF: -22
[ 5.897708] failed to validate module [snd_timer] BTF: -22
[ 5.945507] failed to validate module [snd_timer] BTF: -22
The full kernel log is available on [1]. The config used is available on
[2] and the kernel/modules have been built using gcc-12.
The issue is still present on next-20241105.
I'm sending this report to track the regression while a fix is
identified. The culprit commit hasn't been pinpointed yet, I'll report
back once it's identified.
Any feedback or suggestion for additional debugging steps would be greatly
appreciated.
Best,
Laura
[1] https://pastebin.com/raw/dtvzBkxh
[2] https://pastebin.com/raw/a1MGi3wH
#regzbot introduced: next-20241024..next-20241025
next reply other threads:[~2024-11-06 16:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 16:08 Laura Nao [this message]
2024-11-07 15:05 ` [REGRESSION] module BTF validation failure (Error -22) on next Alan Maguire
2024-11-13 9:37 ` Laura Nao
2024-11-15 17:17 ` Laura Nao
2024-12-04 15:53 ` Laura Nao
2024-12-05 7:36 ` Uros Bizjak
2024-12-14 4:41 ` Cong Wang
2024-12-14 12:15 ` Alan Maguire
2024-12-16 15:19 ` Alan Maguire
2024-12-16 21:28 ` Stephen Brennan
2024-12-17 8:02 ` Jiri Olsa
2025-01-15 17:38 ` Cong Wang
2025-01-16 9:51 ` Alan Maguire
2024-12-05 10:33 ` Jiri Olsa
2024-12-05 10:35 ` Uros Bizjak
2024-12-06 12:35 ` Jiri Olsa
2024-12-10 13:55 ` [REGRESSION] module BTF validation failure (Error -22) on Laura Nao
2024-12-11 21:10 ` Jiri Olsa
2024-12-12 9:22 ` Jiri Olsa
2024-12-12 21:49 ` Stephen Brennan
2024-12-13 9:26 ` Laura Nao
2024-12-10 20:42 ` [REGRESSION] module BTF validation failure (Error -22) on next Kumar Kartikeya Dwivedi
2024-12-05 10:01 ` Jiri Olsa
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=20241106160820.259829-1-laura.nao@collabora.com \
--to=laura.nao@collabora.com \
--cc=bpf@vger.kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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