AUM tests fail on v2024 for armhf

Affected images versions

v2024pre onwards for armhf

Testcase

• https://qa.apertis.org/testcases/v2024pre/aum-ota-signed.html
• https://qa.apertis.org/testcases/v2024pre/aum-offline-upgrade.html
• https://qa.apertis.org/testcases/v2024pre/aum-ota-api.html

Expected result

Test should pass

Actual result

[   14.470595] imx-sgtl5000 sound: ASoC: driver name too long 'imx6q-sabrelite-sgtl5000' -> 'imx6q-sabrelite'
[  197.204654] workqueue: Failed to create a rescuer kthread for wq "ext4-rsv-conversion": -EINTR
[  197.204707] EXT4-fs: failed to create workqueue
[  197.218454] EXT4-fs (mmcblk0p1): mount failed
[[0;1;31mFAILED[0m] Failed to mount [0;1;39mboot.mount[0m - /boot.
[[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mloca…s.target[0m - Local File Systems.
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more detai

This issue seems to be introduced by the last kernel update in v2024pre (6.6)

https://lava.collabora.dev/scheduler/job/12058855#L11557

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

1. always
2. ✅ often, but not always
3. rarely

Impact of bug

OStree upgrade might fail

Root cause

TBC

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @Balasubramanian @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T10201