UP squared 6000 board fails at sanity-check

Affected images versions

• not relevant (explain why)
• see the table below (list the build id and the apt or ostree deployment of the tested images in the appropriate cells)

v2021, v2022 and v2023dev3

To find the build id and the variant type you can:

• derive it from the image name
  • for instance, with the apertis_ostree_v2022pre-fixedfunction-amd64-uefi_20211031.0425.img.gz image the build id is 20211031.0425, the variant is fixedfunction the deployment type is ostree
• obtain it from /etc/os-release using the BUILD_ID and VARIANT_ID keys

Testcase

https://qa.apertis.org/v2021/sanity-check.html

Steps to reproduce

Ordered list detailing every step so other developers can reproduce the issue. Include hardware which you used.

• ...

Expected result

Test should pass

Actual result

Test is failing

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

This bug makes a sanity-check to fails which can mask critical issues

Attachments

Add further information about the environment in the form of attachments here. Attach plain text files from log output (from journalctl, systemctl, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.

Screenshots and videos are usually useful for graphic issues.

Root cause

It is not confirmed yet, but the problem seems to be due to a system service is failing to start.

[[0;1;31mFAILED[0m] Failed to start [0;1;39mLoad/Save …s of leds:asus::kbd_backlight[0m.

https://lava.collabora.dev/scheduler/job/7067870#results_246077125

Outcomes

• apertis-image-recipes!538 (merged)

Management data

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

/cc @andrunko @em @sagar @sudarshan @wlozano Up

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