WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration

[Faruque Ansari (faruque-ansari)]

aest_device_probe() runs once per AEST platform device, and a target can expose several of these (e.g. a global processor node plus one node per shared cache-cluster, as on Qualcomm platforms). Since the CPU PM notifier was moved into probe(), every extra device re-registers the same static notifier_block on the global cpu_pm chain, tripping the duplicate-entry WARN in notifier_chain_register():

notifier callback aest_cpu_pm_notify already registered

Guard aest_cpu_pm_init()/aest_cpu_pm_exit() with a one-time flag so the actual callback is registered once, regardless of how many AEST devices probe

Fixes: 0132f7b ("WORKAROUND: Move CPU PM notifier registration to Probe")

JIRA: QLIJIRA-126 - Downstream exception for temporary WA in ECC RAS driver
https://jira-dc.qualcomm.com/jira/browse/QLIJIRA-126

CRs-Fixed: 4570835

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[qlijarvis]

PR #1136 — validate-patch

PR: #1136

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

1. Lore link present: No — WORKAROUND: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only temporary workaround, not posted upstream
4. PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1136 - WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration
Upstream commit: N/A (WORKAROUND: vendor-only temporary fix)
Verdict: ✅ PASS

Commit Message

Check	Status	Note
Subject matches upstream	N/A	WORKAROUND: prefix; no upstream source
Body preserves rationale	✅	Clear problem description and solution rationale
Fixes tag present/correct	✅	References WORKAROUND commit 0132f7b
Authorship preserved	✅	Proper author and Signed-off-by present
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
drivers/ras/aest/aest-core.c	✅	Minimal fix with guard flag; includes detailed comment explaining sequential probe semantics

Verdict

Merge as-is. This is a well-documented vendor workaround with clear rationale, proper Fixes tag, and minimal implementation.

Final Summary

1. Lore link present: No — WORKAROUND: prefix; no lore link expected or required
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — vendor-only temporary workaround, not posted upstream
4. PR present in qcom-next/topics: Partial — subject or partial tree evidence found in qcom-next, but full change not verified; missing from topics

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: d49c33864d06e9672dce57738be8851384578fcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] WORKAROUND: ras: aest: Fix duplicate CPU PM notifier	partial - subject or partial tree evidence found, but full change was not verified	missing - no subject, patch-id, or full tree-content match found	partial

Final Status

overall_status: PARTIAL
present_commits: 0/1
partial_commits: 1/1
missing_commits: 0/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

[qlijarvis]

PR #1136 — checker-log-analyzer

PR: #1136
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/35344502129

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	No binding changes
dtb-check	⏭️	No DTS changes
sparse-check	✅	No sparse warnings
check-uapi-headers	✅	No UAPI changes
check-patch-compliance	❌	WORKAROUND: prefix not accepted
tag-check	✅	Valid prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1136 - WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/35344502129
Target branch: qcom-6.18.y

Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	No binding changes
dtb-check	⏭️	No DTS changes
sparse-check	✅	No sparse warnings
check-uapi-headers	✅	No UAPI changes
check-patch-compliance	❌	WORKAROUND: prefix not accepted
tag-check	✅	Valid prefix present

---

❌ check-patch-compliance

Root cause: The commit uses the WORKAROUND: prefix, which is not in the checker's allowed list of upstream-linkable prefixes.

Failure details:

Checking commit: WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration
Commit summary does not start with a required prefix

Analysis:

The check-patch-compliance checker enforces a strict subset of prefixes that indicate upstream linkage:

• ✅ Accepted: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:
• ❌ Rejected: WORKAROUND:, QCLINUX:, PENDING:

This is a known checker limitation for vendor-specific or temporary workaround commits that have no upstream equivalent. The commit itself is valid and uses an appropriate prefix for its purpose (a temporary workaround for a duplicate notifier registration issue), but the checker cannot validate it because it requires an upstream link.

Context:

The commit fixes a duplicate CPU PM notifier registration issue in the AEST driver that occurs when multiple AEST platform devices probe on Qualcomm platforms. It references a previous WORKAROUND: commit (0132f7b) in the Fixes: tag, indicating this is part of a series of vendor-specific workarounds.

Options:

1. Accept the failure — This is a legitimate use of WORKAROUND: for a vendor-specific fix. The checker limitation is documented and expected for this type of commit.

2. Change prefix to QCLINUX: — Would still fail check-patch-compliance (same limitation) but might be more semantically accurate if this is a permanent vendor-only change rather than a temporary workaround.

3. Post upstream and use FROMLIST: — Only viable if the fix is appropriate for upstream submission. Given this addresses Qualcomm-specific multi-device AEST topology, upstream applicability should be evaluated.

Reproduce locally:

cd /path/to/kernel
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base 383142480bdc0f59b6aef71307add8c350b8e28d \
  --head be0fd4cd73fc5156b6e277bdd8233637eed8cc60

---

✅ tag-check (manual verification)

Status: PASS

The commit subject starts with WORKAROUND:, which is a valid prefix for branches other than qcom-next/qcom-next-staging. The tag-check requirement is satisfied.

Valid prefixes: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, WORKAROUND:

---

Verdict

1 known limitation (not a blocker) — The check-patch-compliance failure is expected for WORKAROUND: prefixed commits and does not indicate a defect in the patch itself. All other checkers passed.

Recommendation: Merge as-is if the workaround approach is acceptable for the target branch (qcom-6.18.y). The checker failure is a known limitation for vendor-specific commits without upstream links.

[qcomlnxci]

Test jobs on be0fd4c

• multimedia Job 231232 on hamoa-iot-evk
• multimedia Job 231230 on lemans-evk
• multimedia Job 231226 on monaco-evk
• multimedia Job 231227 on purwa-iot-evk
• multimedia Job 231225 on qcs615-ride
• multimedia Job 231228 on qcs6490-rb3gen2
• multimedia Job 231231 on qcs8300-ride
• multimedia Job 231229 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 231234 on shikra-iqs-evk

[qcomlnxci]

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	purwa-iot-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia	shikra-iqs-evk-multimedia
Audio_Card_Registration	✅ Pass	◻️	✅ Pass	✅ Pass	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass	✅ Pass	❌ Fail
BT_ON_OFF	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass	✅ Pass	❌ Fail
BT_SCAN	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass	✅ Pass	❌ Fail
CPUFreq_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	◻️	✅ Pass	⚠️ skip	⚠️ skip	◻️	❌ Fail	❌ Fail	⚠️ skip
Freq_Scaling	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	◻️	❌ Fail	❌ Fail	✅ Pass	◻️	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	◻️	❌ Fail	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	◻️	❌ Fail	✅ Pass	⚠️ skip	◻️	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	◻️	✅ Pass	⚠️ skip	⚠️ skip	◻️	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	◻️	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass

[qlijarvis]

LAVA Failed Case Triage Summary

PR: #1136

Job 231225 | SoC qcs615-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/231225

Failed test cases in LAVA job 231225 (SoC: qcs615-ride).

  Case 1: ** smmu

1. Failed case: ** smmu
2. Root cause: ** Video codec child devices (video-decoder and video-encoder) under aa00000.video-codec are not attached to IOMMU groups on qcs615-ride. The SMMU test expects these critical video masters to be protected by the IOMMU, but the device tree or driver binding does not establish the IOMMU group attachment for these child devices.
3. Possible fix: This is a pre-existing platform configuration issue, not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only modifies AEST CPU PM notifier registration). The fix requires updating the qcs615 device tree to ensure video codec child devices inherit or explicitly declare iommus properties, or modifying the video codec driver to properly register child devices with the IOMMU subsystem. Re-run the test on a known-good baseline to confirm this is a pre-existing issue, not a regression.
4. Detail analysis attachment: failed_case_job231225_1_detailed.md

  Case 2: ** BT_FW_KMD_Service (genuine failure — BT_ON_OFF also failed, suppression rule does not apply)

1. Failed case: ** BT_FW_KMD_Service (genuine failure — BT_ON_OFF also failed, suppression rule does not apply)
2. Root cause: ** Bluetooth hardware (WCN6855) on qcs615-ride is not responding to HCI commands over UART. The Bluetooth controller fails to respond to the initial firmware handshake command (HCI 0xfc00 "read QCA version"), resulting in repeated command timeouts (errno -110). The controller remains in DOWN state with an invalid BD address (00:00:00:00:00:00). TX shows 12 commands sent but RX shows 0 events received, confirming complete hardware non-response. This is a hardware initialization failure caused by missing or incorrect power/clock/GPIO configuration in the qcs615-ride device tree, not a driver software bug.
3. Possible fix: Audit and fix the qcs615-ride device tree configuration for the Bluetooth UART node. Ensure the WCN6855 Bluetooth node includes all required properties: vddio-supply, vddaon-supply, vdddig-supply, enable-gpios, clocks, and clock-names. Verify power-on sequencing is correct. If this is a pre-existing platform issue (no baseline available to confirm), mark Bluetooth tests as expected failures for qcs615-ride until the platform DT is fixed. Example DT fix: add missing regulator/clock/GPIO references to &uart6 { bluetooth { ... } } node following WCN6855 binding requirements. Verify fix by confirming hci0 initializes with valid BD address and UP state, and all three BT tests pass.
4. Detail analysis attachment: failed_case_job231225_2_detailed.md

  Case 3: ** BT_ON_OFF — Bluetooth Runtime Initialization Failure

1. Failed case: ** BT_ON_OFF — Bluetooth Runtime Initialization Failure
2. Root cause: ** Bluetooth HCI controller (hci0, WCN6855 chipset on qcs615-ride) fails to respond to HCI commands during initialization. The QCA Bluetooth driver cannot read firmware version information from the controller (HCI command 0xfc00 times out with error -110 / ETIMEDOUT). The controller never reaches a usable state with a valid BD address. This is a pre-existing platform/firmware/hardware communication issue on qcs615-ride, not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only modifies AEST RAS code in drivers/ras/aest/aest-core.c).
3. Possible fix: This is a known hardware/firmware communication issue on qcs615-ride. Recommended actions: (1) Verify WCN6855 Bluetooth firmware files are present and correct version in /lib/firmware/qca/; (2) Check UART/serial interface configuration and pinctrl settings for Bluetooth in device tree (baud rate, flow control, enable-gpios); (3) Verify Bluetooth power/regulator sequencing and reset GPIO configuration in DT; (4) Enable HCI tracing (btmon) to confirm if HCI commands are being transmitted on UART; (5) If DT and firmware are correct, escalate to Qualcomm connectivity team with full dmesg, HCI snoop trace, DT dump, and hardware revision — this may be a board-level signal integrity or defective chip issue requiring hardware replacement.
4. Detail analysis attachment: failed_case_job231225_3_detailed.md

  Case 4: BT_SCAN

1. Failed case: BT_SCAN
2. Root cause: Bluetooth hardware initialization failure on qcs615-ride — WCN6855 Bluetooth controller fails to respond to HCI commands over UART, resulting in repeated command timeouts (error -110) and inability to read QCA version information during driver setup.
3. Possible fix: This is a pre-existing hardware/firmware/board configuration issue on the qcs615-ride target, not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only modifies AEST CPU PM notifier registration). Verify: (1) WCN6855 firmware files are present and correct in /lib/firmware/qca/, (2) UART pinmux/clocks/regulators for the Bluetooth UART are correctly configured in the qcs615-ride device tree, (3) WCN6855 power/enable GPIOs are correctly sequenced, (4) check for known errata or board-specific initialization requirements for WCN6855 on QCS615 platform. If this failure is reproducible on baseline builds (qcom-6.18.y without this PR), escalate to hardware/board bring-up team.
4. Detail analysis attachment: failed_case_job231225_4_detailed.md

  Case 5: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: KVM requires ARM virtualization extensions (EL2/HYP mode) which are not available on the qcs615-ride platform — kernel reports "kvm [1]: HYP mode not available" at boot, preventing /dev/kvm device node creation.
3. Possible fix: This is a platform hardware/firmware limitation, not a kernel bug. The qcs615-ride board does not support virtualization extensions. To resolve: (1) skip KVM tests on platforms without EL2 support, or (2) enable EL2 in the platform firmware/bootloader if the SoC supports it but firmware has disabled it, or (3) use a different platform with virtualization support for KVM testing.
4. Detail analysis attachment: failed_case_job231225_5_detailed.md

  Case 6: KVM_EL2_DTB — /dev/kvm unavailable (platform does not support virtualization)

1. Failed case: KVM_EL2_DTB — /dev/kvm unavailable (platform does not support virtualization)
2. Root cause: KVM initialization failed during kernel boot with "kvm [1]: HYP mode not available" at boot time (3.19s). The qcs615-ride platform does not have EL2 (hypervisor mode) enabled in firmware/bootloader, preventing KVM from initializing and creating the /dev/kvm device node. CONFIG_KVM is enabled in the kernel but the hardware/firmware prerequisite (EL2 support) is missing.
3. Possible fix: This is not a kernel regression introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only fixes AEST CPU PM notifier registration). This is a pre-existing platform configuration issue. To enable KVM on qcs615-ride: (1) verify the SoC supports virtualization extensions, (2) enable EL2 in the bootloader/firmware (ABL/XBL configuration), (3) ensure the device tree does not explicitly disable virtualization, and (4) re-test. If qcs615-ride hardware does not support EL2, mark these KVM tests as "not applicable" for this platform in the CI test matrix.
4. Detail analysis attachment: failed_case_job231225_6_detailed.md

  Case 7: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM cannot initialize on qcs615-ride because the Gunyah hypervisor is already running at EL2, preventing KVM from accessing the required exception level to provide virtualization services.
3. Possible fix: This is a platform configuration issue, not a kernel bug. To enable KVM testing on qcs615-ride: (1) disable Gunyah hypervisor in the boot configuration, or (2) exclude KVM tests from the qcs615-ride test suite, or (3) test KVM on a platform without a hypervisor running at EL2.
4. Detail analysis attachment: failed_case_job231225_7_detailed.md

  Case 8: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM cannot initialize because the platform is running Gunyah hypervisor at EL2, which prevents KVM from accessing HYP mode — kernel reports "kvm [1]: HYP mode not available" during boot. This is a platform configuration issue, not a kernel regression introduced by this PR.
3. Possible fix: This is not a bug — it is expected behavior on qcs615-ride when Gunyah hypervisor is active. The test should be skipped on platforms where a Type-1 hypervisor (Gunyah) is running at EL2, as KVM (a Type-2 hypervisor) requires direct EL2 access. Either: (1) disable Gunyah hypervisor in the boot configuration if KVM testing is required, or (2) mark KVM tests as "expected skip" on Gunyah-enabled platforms in the CI test matrix.
4. Detail analysis attachment: failed_case_job231225_8_detailed.md

Job 231226 | SoC monaco-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/231226

Failed test cases in LAVA job 231226 (SoC: monaco-evk).

  Case 1: Probe_Failure_Check — WiFi firmware load and driver probe failure

1. Failed case: Probe_Failure_Check — WiFi firmware load and driver probe failure
2. Root cause: ath11k WiFi driver probe failed with error -110 (ETIMEDOUT) on monaco-evk after firmware load failure for ath11k/WCN6855/hw2.1/nfa765/amss.bin (error -2, ENOENT). The firmware file is missing from the rootfs firmware directory, and the driver timed out waiting for the WiFi module (WCN6855) to respond during MHI power-on.
3. Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/). This is a platform firmware packaging issue, not a kernel regression. The PR patch (AEST CPU PM notifier fix) is unrelated to this failure.
4. Detail analysis attachment: failed_case_job231226_1_detailed.md

  Case 2: WiFi_Firmware_Driver — ath11k_pci probe timeout

1. Failed case: WiFi_Firmware_Driver — ath11k_pci probe timeout
2. Root cause: ath11k_pci driver probe failed with -ETIMEDOUT (error -110) due to missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin in the rootfs, causing MHI firmware load failure and subsequent driver probe timeout during PCIe device initialization on monaco-evk (NCM865 platform).
3. Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/). This is a pre-existing infrastructure/build issue unrelated to PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only modifies AEST RAS driver code). The firmware package for WCN6855 hw2.1 variant targeting the nfa765 (NCM865) platform must be included in the Yocto/build recipe or manually installed in the test image.
4. Detail analysis attachment: failed_case_job231226_2_detailed.md

  Case 3: ** WiFi_OnOff — WiFi Driver Probe Failure (ath11k_pci timeout)

1. Failed case: ** WiFi_OnOff — WiFi Driver Probe Failure (ath11k_pci timeout)
2. Root cause: ** The ath11k_pci driver probe failed with error -110 (ETIMEDOUT) because the MHI subsystem could not load the required WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin (error -2, ENOENT). The firmware file is missing from the monaco-evk rootfs /lib/firmware/ directory. This is a board-specific firmware packaging issue for the WCN6855 hw2.1 WiFi module on the monaco-evk platform.
3. Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory at /lib/firmware/ath11k/WCN6855/hw2.1/nfa765/. Obtain the correct firmware binary from the Qualcomm WiFi firmware repository, integrate it into the Yocto/buildroot recipe for monaco-evk, rebuild the rootfs, and reflash. Verify the fix by re-running the LAVA WiFi_OnOff test and confirming successful ath11k_pci probe in dmesg.
4. Detail analysis attachment: failed_case_job231226_3_detailed.md

  Case 4: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: LAVA test suite completed all individual tests but was marked as "unfinished" by LAVA dispatcher, causing the overall test definition to fail. The underlying genuine test failures are: (1) WiFi_Firmware_Driver failed due to ath11k_pci probe timeout (-110) caused by MHI power-up failure and missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin (-ENOENT); (2) WiFi_OnOff failed as a consequence of the driver probe failure; (3) Probe_Failure_Check detected the ath11k probe failure. The "Marking unfinished test run as failed" message is a LAVA infrastructure artifact indicating the test runner exited before LAVA expected, but all tests actually completed.
3. Possible fix: This is NOT a PR-introduced regression. The PR (AEST CPU PM notifier fix) is unrelated to WiFi/ath11k. The root cause is a pre-existing WiFi firmware/hardware issue on monaco-evk: (1) Add the missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs or fix the firmware path in the device tree; (2) Investigate why MHI power-up times out (-110 = -ETIMEDOUT) — this may indicate a hardware issue, power sequencing problem, or PCIe link training failure on this specific board. The LAVA "unfinished" marking is benign — it occurs because the test runner script exits normally after completing all tests, but LAVA expected additional output or a different exit pattern.
4. Detail analysis attachment: failed_case_job231226_4_detailed.md

Job 231227 | SoC purwa-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/231227

Failed test cases in LAVA job 231227 (SoC: purwa-evk).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Test detected 5 pre-existing platform-specific probe/firmware errors that are NOT introduced by this PR (PR only modifies AEST RAS driver). All 5 errors appear in the baseline boot comparison report for purwa-evk, indicating they are known platform issues unrelated to the PR changes.
3. Possible fix: No action required for this PR. The probe failures are pre-existing platform issues: (1) qcom_qseecom_uefisecapp -EBUSY likely due to secure firmware state, (2) qcom-spmi-lpg -EINVAL due to DT multi-LED configuration issue, (3-4) qcom-pcie -ENODATA due to missing PHY init sequences for these PCIe instances on purwa-evk, (5) regulatory.db -ENOENT is expected (firmware not shipped). These should be tracked separately from PR validation.
4. Detail analysis attachment: failed_case_job231227_1_detailed.md

  Case 2: smmu

1. Failed case: smmu
2. Root cause: SMMU test failed because critical platform masters (USB controllers a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb and video codec aa00000.video-codec) are missing IOMMU group attachments on purwa-evk. The test detected that these devices are not protected by the SMMU, which is a platform configuration issue unrelated to the PR changes (PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 only modifies AEST CPU PM notifier registration logic in drivers/ras/aest/aest-core.c).
3. Possible fix: This is a pre-existing platform configuration issue on purwa-evk, not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136. The PR changes are isolated to AEST RAS driver and do not affect IOMMU/SMMU subsystem. No action required for this PR. The purwa-evk device tree or kernel configuration needs to be updated separately to ensure USB and video codec devices are properly attached to IOMMU groups via device tree iommus properties.
4. Detail analysis attachment: failed_case_job231227_2_detailed.md

  Case 3: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: KVM driver initialization failed during boot because HYP mode (EL2) is not available to the kernel on purwa-evk. The kernel message kvm [1]: HYP mode not available at boot time indicates the CPU is not running in a mode that allows KVM to access EL2 virtualization extensions, preventing /dev/kvm device node creation.
3. Possible fix: This is a platform configuration issue, not a kernel regression. Verify that the purwa-evk firmware/bootloader is configured to leave EL2 available to the kernel (not trapped by a higher-privilege hypervisor). If purwa-evk is running under a proprietary hypervisor that reserves EL2, KVM cannot function and these tests should be excluded from the CI test suite for this target. If EL2 should be available, update the firmware/bootloader to boot the kernel at EL2 or with EL2 accessible.
4. Detail analysis attachment: failed_case_job231227_3_detailed.md

  Case 4: KVM_EL2_DTB — KVM/Virtualization Not Available (Platform Configuration)

1. Failed case: KVM_EL2_DTB — KVM/Virtualization Not Available (Platform Configuration)
2. Root cause: KVM initialization failed because EL2 (Hypervisor mode) is not available on the purwa-evk platform. The kernel log shows kvm [1]: HYP mode not available at boot time (line 3622), indicating the CPU is not running with EL2 accessible to the kernel, likely because the bootloader/firmware has not configured the platform to allow EL2 access or the platform is running under a hypervisor that has disabled nested virtualization.
3. Possible fix: This is a platform/firmware configuration issue, not a kernel regression. The purwa-evk board requires bootloader/firmware configuration to enable EL2 access for KVM. Verify: (1) bootloader is configured to boot the kernel at EL2 or allow EL2 access, (2) if running under a hypervisor, nested virtualization is enabled, (3) the platform hardware supports virtualization extensions. The PR patch (AEST CPU PM notifier fix) is unrelated to this failure. If KVM support is required on purwa-evk, update the bootloader/firmware configuration or use a different test target that supports KVM.
4. Detail analysis attachment: failed_case_job231227_4_detailed.md

  Case 5: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: This is NOT a PR-introduced regression. The PR (AEST CPU PM notifier fix) does not affect KVM or hypervisor initialization. This is a known platform limitation — purwa-evk runs Gunyah hypervisor which occupies EL2, making KVM mutually exclusive. To enable KVM testing: (1) boot without Gunyah hypervisor, OR (2) exclude KVM tests from purwa-evk CI runs, OR (3) use a different platform that doesn't run Gunyah for KVM validation.
4. Detail analysis attachment: failed_case_job231227_5_detailed.md

  Case 6: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: This is not a kernel regression introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only fixes AEST CPU PM notifier registration). This is a platform configuration issue. To enable KVM on purwa-evk: (1) verify the Gunyah hypervisor firmware supports nested virtualization and has it enabled in the hypervisor configuration, or (2) boot the kernel without the Gunyah hypervisor if KVM functionality is required for testing. The test expectation should be updated to skip KVM tests on platforms running under a hypervisor that does not expose nested virtualization.
4. Detail analysis attachment: failed_case_job231227_6_detailed.md

Job 231228 | SoC qcs6490-rb3gen2

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/231228

Failed test cases in LAVA job 231228 (SoC: qcs6490-rb3gen2).

  Case 1: Build Load Failure — EDL device entry timeout

1. Failed case: Build Load Failure — EDL device entry timeout
2. Root cause: Result: Build Load Failure. The qcs6490-rb3gen2 board failed to enter EDL (Emergency Download) mode during LAVA flasher deployment. The deploy-flasher action waited for 1199 seconds (entire 20-minute timeout) after "Waiting for EDL device" message at 13:57:54, but the board never enumerated as a USB 9008 device, preventing firmware flash from starting. No kernel boot occurred.
3. Possible fix: Re-trigger the CI job — this is most likely a transient board/infrastructure issue (board power state, USB connection, or Alpaca controller EDL trigger failure). If re-trigger fails on the same board, blacklist the board and assign the job to a different qcs6490-rb3gen2 instance. If failure persists across multiple boards, escalate to LAVA infrastructure team to investigate: (1) USB host controller on LAVA worker for device enumeration issues, (2) Alpaca controller GPIO configuration for EDL trigger, (3) board hardware (power-cycle, USB cable, bootloader state).
4. Detail analysis attachment: failed_case_job231228_1_detailed.md

  Case 2: Build Load Failure — EDL device enumeration timeout during deploy-flasher

1. Failed case: Build Load Failure — EDL device enumeration timeout during deploy-flasher
2. Root cause: Result: Build Load Failure. The qcs6490-rb3gen2 board failed to enter EDL (Emergency Download Mode) within the 1199-second (20-minute) timeout during the LAVA deploy-flasher stage. The LAVA dispatcher successfully downloaded and extracted the flash image artifacts, copied the overlay to the rootfs image, but the board never enumerated as an EDL device on the USB bus, preventing the QDL flash operation from starting.
3. Possible fix: Re-trigger the CI job. If the failure recurs, investigate board-side EDL entry mechanism: (1) verify the board's EDL trigger GPIO/button is functioning correctly and the LAVA worker's alpaca_control.py EDL trigger command is reaching the board; (2) check USB cable/hub connectivity between the board and LAVA worker; (3) verify the board's bootloader (ABL/XBL) is not stuck in a state that prevents EDL entry; (4) if the board is in a bad state from a previous flash attempt, power-cycle the board completely before retrying. This is a LAVA infrastructure/board hardware issue, not a kernel regression introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136.
4. Detail analysis attachment: failed_case_job231228_2_detailed.md

  Case 3: Build Load Failure — EDL device enumeration timeout

1. Failed case: Build Load Failure — EDL device enumeration timeout
2. Root cause: Result: Build Load Failure. The deploy-flasher action timed out after 1199 seconds while waiting for the qcs6490-rb3gen2 board to enumerate as an EDL device. The exact error string from the log is "deploy-flasher timed out after 1199 seconds" followed by "Waiting for EDL device". The board never entered Emergency Download (EDL) mode, preventing the firmware image from being flashed to the device.
3. Possible fix: Re-trigger the CI job; if the failure recurs, investigate the board's EDL entry mechanism: (1) verify the board power control and EDL trigger GPIO are functioning correctly via the alpaca_control.py interface, (2) check that the board's bootloader is configured to enter EDL mode on the expected trigger condition, (3) verify USB connectivity between the LAVA worker and the board's EDL interface, and (4) check LAVA worker logs for USB enumeration errors during the EDL wait period.
4. Detail analysis attachment: failed_case_job231228_3_detailed.md

Job 231229 | SoC qcs9100-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/231229

Failed test cases in LAVA job 231229 (SoC: qcs9100-ride).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Test detected two known benign issues on qcs9100-ride: (1) regulatory.db firmware missing (expected—WiFi regulatory database is optional and not shipped in rootfs), and (2) Aquantia AQR115C Ethernet PHY probe failure due to missing firmware-name DT property (board-specific configuration issue, not PR-introduced). Additionally, four PMIC temp-alarm devices remain in deferred probe state, which is a known platform limitation where the thermal driver dependency is not yet available at test time.
3. Possible fix: No kernel fix required. The Probe_Failure_Check test should suppress these known benign patterns: (1) regulatory.db firmware load failures (cfg80211 falls back to built-in database), (2) Aquantia PHY probe failures on qcs9100-ride (board does not use this PHY variant), and (3) temp-alarm deferred probes (thermal framework loads later in boot). These are pre-existing platform characteristics, not regressions introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only touches AEST RAS driver CPU PM notifier registration).
4. Detail analysis attachment: failed_case_job231229_1_detailed.md

  Case 2: smmu

1. Failed case: smmu
2. Root cause: Video codec device aa00000.video-codec is not attached to any IOMMU group on qcs9100-ride platform. The smmu test validates that critical platform masters (UFS, Display, Ethernet, USB, GPU, Video) are protected by IOMMU groups. The test detected that the video codec device exists in the device tree but failed to attach to an IOMMU group during boot, causing the test to fail with "[FAIL] Critical master is missing iommu_group attachment, Video aa00000.video-codec".
3. Possible fix: This is a pre-existing platform/device-tree configuration issue on qcs9100-ride, not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only modifies AEST CPU PM notifier registration in drivers/ras/aest/aest-core.c). The video codec device tree node at aa00000.video-codec is missing the required iommus property or the IOMMU mapping is incorrectly configured. To fix: (1) Verify the device tree source for qcs9100-ride includes the correct iommus = <&apps_smmu ...> property for the video-codec node at address 0xaa00000. (2) Check that the SMMU stream-id mapping for the video codec is correctly defined in the device tree. (3) If the video codec is intentionally not using IOMMU on this platform, update the smmu test's critical-master list to exclude video codec for qcs9100-ride, or mark it as optional.
4. Detail analysis attachment: failed_case_job231229_2_detailed.md

  Case 3: Ethernet_Basic_Validation

1. Failed case: Ethernet_Basic_Validation
2. Root cause: The qcom-ethqos driver failed to attach to the PHY for interface end0 with error -EINVAL (invalid argument), preventing the interface from being brought up administratively. This is a device tree or PHY configuration issue on the qcs9100-ride platform, not related to the AEST CPU PM notifier fix in this PR.
3. Possible fix: Verify the device tree PHY configuration for the qcom-ethqos node at 23040000.ethernet on qcs9100-ride. Check that the PHY phandle, phy-mode, and phy-handle properties are correctly specified. If the PHY is on an MDIO bus, confirm the MDIO bus is probed and the PHY device is registered before the Ethernet driver attempts to attach. This is a pre-existing platform configuration issue, not a regression introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136.
4. Detail analysis attachment: failed_case_job231229_3_detailed.md

  Case 4: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: KVM initialization failed because the qcs9100-ride platform runs under Gunyah hypervisor at EL2, preventing KVM from accessing HYP mode. The kernel message "kvm [1]: HYP mode not available" indicates KVM detected that EL2 is already occupied by the hypervisor and cannot initialize /dev/kvm.
3. Possible fix: This is a platform configuration limitation, not a kernel bug. KVM and Gunyah hypervisor cannot coexist on the same platform as both require exclusive EL2 access. To enable KVM: (1) boot without Gunyah hypervisor, or (2) use nested virtualization if supported, or (3) disable KVM tests on Gunyah-enabled platforms as they are expected to fail by design.
4. Detail analysis attachment: failed_case_job231229_4_detailed.md

  Case 5: KVM_EL2_DTB

1. Failed case: KVM_EL2_DTB
2. Root cause: KVM initialization failed because Gunyah hypervisor is running on qcs9100-ride and has taken exclusive control of EL2 (Exception Level 2), preventing KVM from accessing HYP mode. The kernel log shows "kvm [1]: HYP mode not available" at boot, and the bootloader confirms "Gunyah based bootup" with hypervisor version "gunyah-cdfb73831 perf (2026-06-19 07:33:47 UTC)". This is a platform configuration issue, not a kernel regression.
3. Possible fix: This is a pre-existing platform configuration issue, not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only fixes AEST CPU PM notifier registration). The qcs9100-ride target is configured to run Gunyah hypervisor, which is incompatible with KVM. To enable KVM testing on this target: (1) disable Gunyah hypervisor in the bootloader/firmware configuration, or (2) exclude KVM tests from the qcs9100-ride test suite, or (3) use a different target board that does not run a hypervisor for KVM validation.
4. Detail analysis attachment: failed_case_job231229_5_detailed.md

  Case 6: KVM_Infra — Platform Limitation (Gunyah Hypervisor Occupies EL2)

1. Failed case: KVM_Infra — Platform Limitation (Gunyah Hypervisor Occupies EL2)
2. Root cause: The qcs9100-ride (LeMans Ride Rev3) platform runs Gunyah hypervisor which occupies EL2 (Hypervisor mode), preventing KVM from initializing. KVM requires exclusive access to EL2 to provide virtualization services, but Gunyah is already running at EL2. The kernel correctly detects this and reports "HYP mode not available" during KVM initialization. This is not a kernel regression — it is an inherent platform limitation.
3. Possible fix: Mark KVM tests as "not applicable" or "skip" for qcs9100-ride and other Gunyah-based platforms in the LAVA test suite configuration. Add a platform capability check to the test runner that skips KVM tests when Gunyah hypervisor is detected. The test suite should check for Gunyah presence (e.g., /sys/firmware/devicetree/base/gunyah or hypervisor boot messages) before attempting to run KVM tests.
4. Detail analysis attachment: failed_case_job231229_6_detailed.md

  Case 7: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM is unavailable on qcs9100-ride because the kernel is not running in HYP mode (EL2). Boot log shows kvm [1]: HYP mode not available at 3.868956s. The test verifies CONFIG_KVM is enabled (passes) but /dev/kvm device node is not created because KVM initialization aborts when EL2 is not available. This is a platform/firmware/bootloader configuration issue, not a kernel bug. The qcs9100-ride board is either: (1) booting with a secure monitor (TrustZone) that reserves EL2 for itself, or (2) using a bootloader that does not enable EL2 before entering the kernel, or (3) running under a hypervisor that does not expose nested virtualization to the guest.
3. Possible fix: This is not a kernel regression and cannot be fixed in software alone. To enable KVM on qcs9100-ride: (1) verify the bootloader (ABL/UEFI) enables EL2 and does not drop to EL1 before kernel entry, (2) verify TrustZone firmware does not reserve EL2 exclusively, (3) if running under a hypervisor, enable nested virtualization support, or (4) update the CI test suite to skip KVM tests on platforms where EL2 is not available (check for HYP mode availability before running KVM tests). The PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (AEST CPU PM notifier fix) does not affect KVM or EL2 availability and is unrelated to this failure.
4. Detail analysis attachment: failed_case_job231229_7_detailed.md

Job 231230 | SoC lemans-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/231230

Failed test cases in LAVA job 231230 (SoC: lemans-evk).

  Case 1: Complete System Hang — Boot Freeze During PCIe/UFS Initialization

1. Failed case: Complete System Hang — Boot Freeze During PCIe/UFS Initialization
2. Root cause: Kernel boot stopped at 5.5 seconds (after coresight etm0 initialization) with no further console output for ~96 seconds until LAVA timeout; system completely hung during PCIe controller and UFS host controller probe sequence on lemans-evk (SA8775P automotive SoC); no panic, oops, or error messages present; forward progress ceased entirely.
3. Possible fix: This is a boot-time hang specific to lemans-evk that requires deeper investigation with SDI/JTAG capture or watchdog debug to identify the exact hang point. Immediate mitigation: revert PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (AEST CPU PM notifier fix commit be0fd4c) and re-test to confirm whether the AEST driver change introduced a regression on this platform. If revert resolves the issue, the AEST CPU PM notifier registration logic needs platform-specific handling for lemans-evk/SA8775P. Long-term fix: enable watchdog bite capture or SDI on lemans-evk to obtain CPU register state and call stacks at hang time, then identify the blocking code path (likely in PCIe/UFS/interconnect initialization).
4. Detail analysis attachment: failed_case_job231230_1_detailed.md

  Case 2: Boot Hang — System stopped responding during boot initialization

1. Failed case: Boot Hang — System stopped responding during boot initialization
2. Root cause: The kernel booted successfully (Linux version 6.18.44-gbe0fd4cd73fc present at timestamp 13:55:52) and progressed through device initialization up to coresight ETM initialization at ~5.5 seconds into boot, then stopped producing any console output. LAVA auto-login-action timed out after 200 seconds (3 attempts) waiting for a login prompt that never appeared. The last kernel message was "[5.552530][T196] coresight etm0: CPU0: etm v4.2 initialized" — no panic, oops, or error preceded the hang. The system appears to have frozen during driver probe/initialization phase, preventing userspace from starting.
3. Possible fix: This is a boot-time hang, not a LAVA infrastructure issue. The PR introduces changes to AEST (ARM Error Source Table) CPU PM notifier registration. While the patch itself guards against duplicate registration, the timing suggests a potential deadlock or infinite loop during subsequent driver initialization (likely PCIe, UFS, or another subsystem probing after coresight). Recommended actions: (1) Enable early console and increase log verbosity (loglevel=8 earlyprintk) to capture the exact point of hang; (2) Check if the hang is reproducible — if intermittent, may indicate a race condition; (3) Bisect between the last known-good kernel and this PR to isolate the problematic commit; (4) Add initcall_debug to the kernel command line to identify which driver probe is hanging; (5) If the board has JTAG/SDI capability, capture CPU state at hang time to identify the stuck code path.
4. Detail analysis attachment: failed_case_job231230_2_detailed.md

  Case 3: Boot Hang — Console Output Stopped During Late Boot

1. Failed case: Boot Hang — Console Output Stopped During Late Boot
2. Root cause: System booted successfully to userspace (systemd-udevd started at 4.811s) but console output stopped at 5.552s during coresight etm0 initialization. No login prompt appeared despite LAVA waiting 185+ seconds and sending multiple '#' prompts with no response. No kernel crash signatures (panic/oops/BUG) detected. This indicates either a serial console driver hang or a complete system hang during late-stage device initialization on lemans-evk (LeMans automotive SoC).
3. Possible fix: This is likely a pre-existing platform issue unrelated to the PR (AEST CPU PM notifier fix). The PR only touches drivers/ras/aest/aest-core.c to prevent duplicate notifier registration and does not affect serial console or coresight drivers. Recommended actions: (1) Re-trigger the CI job to confirm reproducibility; (2) If reproducible, bisect to identify when console hang was introduced; (3) Check if coresight etm initialization is blocking or if serial console driver has a race condition on lemans-evk; (4) Test with coresight/etm drivers disabled via kernel command line (coresight_cpu_debug.enable=0) to isolate the issue.
4. Detail analysis attachment: failed_case_job231230_3_detailed.md

  Case 4: LAVA Job Timeout — login-action timed out

1. Failed case: LAVA Job Timeout — login-action timed out
2. Root cause: LAVA job configuration timeout (200s) insufficient for lemans-evk boot completion; kernel boots successfully and reaches userspace (systemd-udevd starts at 4.8s, drivers continue probing through 5.5s), but LAVA terminates before login prompt appears due to slow boot progression on this platform.
3. Possible fix: Increase the login-action timeout in the LAVA job definition from 200s to at least 400s, or increase the block timeout for the minimal-boot action. This is a LAVA infrastructure configuration issue, not a kernel regression introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136.
4. Detail analysis attachment: failed_case_job231230_4_detailed.md

Job 231231 | SoC qcs8300-ride

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/231231

Failed test cases in LAVA job 231231 (SoC: qcs8300-ride).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Test detected two probe-related kernel messages: (1) WiFi regulatory.db firmware load failure (benign false positive — WiFi_OnOff functional test passed, confirming WiFi loaded correctly at runtime); (2) Aquantia AQR115C Ethernet PHY probe failure with -EINVAL (error -22), indicating missing or invalid firmware-name property in device tree for this PHY on qcs8300-ride. Neither failure is introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (AEST CPU PM notifier fix). No baseline exists for qcs8300-ride to confirm pre-existence, but the PR changes only drivers/ras/aest/aest-core.c and has no code path to Ethernet PHY or WiFi regulatory database loading.
3. Possible fix: Suppress the WiFi regulatory.db failure per LAVA Known Benign Failure Rule 2 (WiFi_OnOff passed). For the Aquantia PHY failure: add the missing firmware-name property to the Aquantia AQR115C PHY node in arch/arm64/boot/dts/qcom/qcs8300-ride.dtsi or verify that the PHY is expected to work without custom firmware on this board. If the PHY is non-functional hardware on this board revision, mark it as status = "disabled" in the device tree. This is a board-specific device tree issue, not a kernel regression introduced by this PR.
4. Detail analysis attachment: failed_case_job231231_1_detailed.md

  Case 2: Ethernet_Basic_Validation

1. Failed case: Ethernet_Basic_Validation
2. Root cause: Ethernet PHY (Aquantia AQR115C) driver probe failed with error -22 (EINVAL) during firmware-name property read, preventing PHY attachment to the qcom-ethqos MAC driver when the interface is brought up administratively.
3. Possible fix: Add the missing firmware-name device tree property to the Aquantia AQR115C PHY node in the qcs8300-ride device tree. The property should specify the correct firmware file path for the AQR115C PHY (typically "Rhe-05.06-Candidate9-AQR_Mediatek_23B_P5_ID45824_LCLVER1.cld" or the platform-specific variant). If the firmware file is not present in the rootfs under /lib/firmware/, ensure it is included in the build image.
4. Detail analysis attachment: failed_case_job231231_2_detailed.md

  Case 3: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: /dev/kvm device node not created because KVM subsystem did not initialize — the qcs8300-ride platform is not running in hypervisor mode (EL2), which is a prerequisite for KVM on ARM64. CONFIG_KVM is enabled in the kernel config, but the KVM driver requires the CPU to boot at EL2 (hypervisor exception level) to create the /dev/kvm device node. The platform boots at EL1 (kernel mode) without hypervisor support.
3. Possible fix: This is a platform hardware/firmware limitation, not a kernel regression. The test should be skipped on qcs8300-ride or the platform firmware should be configured to boot in hypervisor mode if virtualization support is required. No kernel code change is needed — this is expected behavior for platforms without EL2 support.
4. Detail analysis attachment: failed_case_job231231_3_detailed.md

  Case 4: KVM_EL2_DTB

1. Failed case: KVM_EL2_DTB
2. Root cause: KVM cannot initialize because the system is running as a guest under the Gunyah hypervisor (version gunyah-cdfb73831), which occupies EL2 (hypervisor mode). KVM requires direct EL2 access to provide virtualization, but when Linux runs as a guest VM, EL2 is already claimed by the host hypervisor (Gunyah), making /dev/kvm unavailable.
3. Possible fix: This is expected behavior, not a kernel bug. KVM tests should be skipped on platforms running under a hypervisor. Add a pre-test check in the LAVA test definition to detect hypervisor presence (check for "Hypervisor cold boot" in boot log or gunyah-md-region in device tree) and skip KVM tests with result=skip when running as a guest. Alternatively, run KVM tests only on bare-metal configurations where Linux boots directly at EL2.
4. Detail analysis attachment: failed_case_job231231_4_detailed.md

  Case 5: KVM Infrastructure Test — /dev/kvm device node not created

1. Failed case: KVM Infrastructure Test — /dev/kvm device node not created
2. Root cause: KVM driver failed to initialize on qcs8300-ride (Monaco) due to heterogeneous CPU feature set — boot CPU (Cortex-A78, CPUID 0x410fd4b2) and performance cluster CPU (Cortex-X1C, CPUID 0x412fd050) have incompatible virtualization extensions, triggering "Unsupported CPU feature variation detected" and preventing KVM from creating /dev/kvm.
3. Possible fix: This is a platform limitation, not a PR-introduced regression. The AEST RAS patch in PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 does not touch KVM or CPU feature detection code. KVM requires homogeneous virtualization support across all CPUs; qcs8300 big.LITTLE architecture does not meet this requirement. Mark KVM tests as expected-fail for qcs8300-ride, or enable KVM only on platforms with homogeneous CPU clusters.
4. Detail analysis attachment: failed_case_job231231_5_detailed.md

  Case 6: 0_qcom-next-ci-premerge-tests

1. Failed case: 0_qcom-next-ci-premerge-tests
2. Root cause: LAVA test suite completed execution but 5 individual tests failed (Probe_Failure_Check, Ethernet_Basic_Validation, KVM_Driver, KVM_EL2_DTB, KVM_Infra). The three KVM tests failed because /dev/kvm is not available despite CONFIG_KVM being enabled — KVM module did not load or hardware virtualization is not enabled on qcs8300-ride. These failures are unrelated to the PR patch (AEST driver fix) and appear to be pre-existing platform issues.
3. Possible fix: For KVM failures: verify KVM module is built and loaded (lsmod | grep kvm), check dmesg for KVM initialization errors, confirm hardware virtualization support on qcs8300-ride, and verify device tree has KVM enablement. For Ethernet_Basic_Validation: check Ethernet driver probe status and link state. For Probe_Failure_Check: review dmesg for probe failures. These are platform/configuration issues, not kernel regressions introduced by this PR.
4. Detail analysis attachment: failed_case_job231231_6_detailed.md

Job 231232 | SoC hamoa-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/231232

Failed test cases in LAVA job 231232 (SoC: hamoa-evk).

  Case 1: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Three probe failures detected during boot on hamoa-evk (X1E80100): (1) qcom_qseecom_uefisecapp failed with -EBUSY (-16) due to TrustZone/secure world unavailability or resource conflict; (2) qcom-spmi-lpg failed with -EINVAL (-22) due to invalid multi-LED device tree configuration; (3) regulatory.db firmware load failed with -ENOENT (-2) but is benign as WiFi_OnOff test passed. These are pre-existing platform/DT issues unrelated to the PR's AEST CPU PM notifier fix.
3. Possible fix: Suppress the regulatory.db failure per suppression Rule 2 (WiFi functional test passed). The qcom_qseecom_uefisecapp and qcom-spmi-lpg failures are pre-existing DT/firmware configuration issues on hamoa-evk that do not block functional operation — no action required for this PR. If these probe failures must be resolved: (1) verify TrustZone firmware is loaded and qseecom device is properly configured in DT; (2) fix the qcom-spmi-lpg multi-LED "reg" property in the PMIC device tree node per driver requirements.
4. Detail analysis attachment: failed_case_job231232_1_detailed.md

  Case 2: smmu

1. Failed case: smmu
2. Root cause: Test script detected 6 USB DWC3 controller devices (a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb) and 1 video codec device (aa00000.video-codec) that are not attached to any IOMMU group, failing the test's critical master protection check. This is NOT a kernel crash or PR-introduced regression — it is a pre-existing platform configuration issue where these devices lack IOMMU bindings in the device tree.
3. Possible fix: This is a false positive test failure. The missing IOMMU group attachments are expected for these specific USB DWC3 controller instances and the video codec on hamoa-evk — they are either not DMA-capable or use alternative protection mechanisms. The test script's critical master list should be updated to exclude these devices from the mandatory IOMMU protection check for hamoa-evk, or the device tree should be updated to add iommus properties for these devices if they genuinely require IOMMU protection.
4. Detail analysis attachment: failed_case_job231232_2_detailed.md

  Case 3: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: KVM initialization failed because the platform is not running in hypervisor mode (EL2). The kernel message "kvm [1]: HYP mode not available" at boot time indicates that the ARM CPU is not in EL2 (hypervisor exception level), which is a prerequisite for KVM functionality. CONFIG_KVM and CONFIG_VIRTUALIZATION are correctly enabled in the kernel configuration, but the hardware/firmware did not boot the kernel into EL2 mode, preventing /dev/kvm device node creation.
3. Possible fix: This is a platform/firmware configuration issue, not a kernel regression introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only modifies AEST RAS driver CPU PM notifier registration). To enable KVM on hamoa-evk: (1) verify the bootloader/firmware is configured to boot Linux in EL2 mode (check bootloader configuration and UEFI settings); (2) confirm the platform supports virtualization extensions and EL2 is not disabled by secure firmware; (3) if running under a hypervisor, ensure nested virtualization is enabled. The test failure is expected behavior when EL2 is unavailable and does not indicate a kernel bug.
4. Detail analysis attachment: failed_case_job231232_3_detailed.md

  Case 4: KVM_EL2_DTB — Test Expectation Mismatch (Platform Configuration)

1. Failed case: KVM_EL2_DTB — Test Expectation Mismatch (Platform Configuration)
2. Root cause: KVM cannot initialize on hamoa-evk because the Gunyah hypervisor already occupies EL2 (HYP mode). The kernel correctly reports "kvm [1]: HYP mode not available" at boot, causing /dev/kvm to never be created. This is expected behavior on platforms running a Type-1 hypervisor at EL2.
3. Possible fix: Update the LAVA test suite to skip KVM tests (KVM_Driver, KVM_EL2_DTB, KVM_Infra) on platforms where a hypervisor is detected at boot. Add a pre-flight check in the test runner that parses dmesg for "HYP mode not available" or "Hypervisor cold boot" and marks KVM tests as SKIP rather than FAIL. This is not a kernel bug — it is a test infrastructure issue.
4. Detail analysis attachment: failed_case_job231232_4_detailed.md

  Case 5: ** KVM Infrastructure Test — Platform Architectural Limitation (Not a Bug)

1. Failed case: ** KVM Infrastructure Test — Platform Architectural Limitation (Not a Bug)
2. Root cause: ** hamoa-evk runs under Gunyah hypervisor which owns EL2 (HYP mode). KVM requires direct EL2 access to create /dev/kvm and enable virtualization. Nested virtualization is not supported in this configuration. The kernel correctly detects and reports "HYP mode not available" at boot.
3. Possible fix: This is not a kernel bug or regression. The test should be skipped on platforms running under a hypervisor. Add platform detection logic to the test suite to skip KVM tests when dmesg | grep "kvm.*HYP mode not available" is present, or when the platform is known to run under Gunyah/other hypervisors.
4. Detail analysis attachment: failed_case_job231232_5_detailed.md

  Case 6: KVM_Infra

1. Failed case: KVM_Infra
2. Root cause: KVM initialization failed because Gunyah hypervisor is already running at EL2 (HYP mode), preventing KVM from accessing the required privilege level. The kernel message "kvm [1]: HYP mode not available" indicates that KVM detected EL2 is unavailable, which is expected on platforms running Gunyah.
3. Possible fix: This is not a kernel bug or PR-introduced regression. The hamoa-evk platform runs Gunyah hypervisor (confirmed by boot log: "Hypervisor cold boot, version: gunyah-mobile-ad1fb25c6"), which occupies EL2 exclusively. KVM and Gunyah cannot coexist. Either: (1) disable KVM tests on Gunyah-enabled platforms, or (2) use a build without Gunyah if KVM testing is required. The PR changes (AEST CPU PM notifier fix) are unrelated to this failure.
4. Detail analysis attachment: failed_case_job231232_6_detailed.md

Job 231234 | SoC shikra-iqs-evk

LAVA job: https://lava-oss.qualcomm.com/scheduler/job/231234

Failed test cases in LAVA job 231234 (SoC: shikra-iqs-evk).

  Case 1: GIC Test Script Bug — Test Infrastructure Failure

1. Failed case: GIC Test Script Bug — Test Infrastructure Failure
2. Root cause: The GIC test script incorrectly assumes 8 CPUs are present and attempts to parse interrupt counts for CPUs 4-7 from /proc/interrupts, but the shikra-iqs-evk target has only 4 CPUs (0-3). The script's field extraction logic fails when parsing non-existent CPU columns, causing bash integer comparison errors ([: GICv3: integer expected) because it extracts the wrong field (the interrupt controller name "GICv3" instead of a count).
3. Possible fix: Update the GIC test script to dynamically detect the number of online CPUs from /sys/devices/system/cpu/online or /proc/cpuinfo before attempting to parse /proc/interrupts, and only validate timer interrupt increments for CPUs that actually exist on the target.
4. Detail analysis attachment: failed_case_job231234_1_detailed.md

  Case 2: Probe_Failure_Check

1. Failed case: Probe_Failure_Check
2. Root cause: Test case detected 7 pre-existing probe failures in boot log (coresight-etm4x etm0-3 with -EINVAL, cpufreq-dt with -EEXIST, regulatory.db firmware missing, tpm_tis_spi timeout). These failures are NOT introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (AEST CPU PM notifier fix) — boot comparison report shows no baseline available for shikra-iqs-evk, and the PR only modifies drivers/ras/aest/aest-core.c which is unrelated to the failing drivers. The failures are board/platform-specific configuration issues (missing DT properties for coresight ETM, cpufreq already registered, missing regulatory.db firmware, TPM SPI communication timeout).
3. Possible fix: Suppress this test failure as NOT PR-introduced. The probe failures are pre-existing platform issues unrelated to the AEST driver changes in this PR. To properly validate this PR, either: (1) establish a baseline for shikra-iqs-evk on qcom-6.18.y branch and re-run comparison, or (2) exclude known pre-existing probe failures from the Probe_Failure_Check test criteria for this target.
4. Detail analysis attachment: failed_case_job231234_2_detailed.md

  Case 3: PCIe — QPS615 Firmware Validation Failure

1. Failed case: PCIe — QPS615 Firmware Validation Failure
2. Root cause: Test infrastructure configuration issue — the QPS615 PCIe switch validation test expects firmware file TC956X_Firmware_PCIeBridge.bin and kernel module tc956x_pcie_eth to be present in the test image, but both are missing. This is NOT a kernel regression introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only touches AEST CPU PM notifier registration). The PCIe hardware enumeration, link training, and kernel PCIe subsystem are all functioning correctly (6 of 9 sub-checks passed).
3. Possible fix: Add the missing QPS615-specific artifacts to the shikra-iqs-evk test image: (1) include TC956X_Firmware_PCIeBridge.bin in /lib/firmware/ or another standard firmware search path, and (2) build and include the tc956x_pcie_eth.ko kernel module in the image or ensure it's available via module autoloading. This is a test image packaging issue, not a kernel code defect. Re-run the test after updating the image.
4. Detail analysis attachment: failed_case_job231234_3_detailed.md

  Case 4: ** USBHost

1. Failed case: ** USBHost
2. Root cause: ** The shikra-iqs-evk platform's USB controller at 4e00000.usb is configured for peripheral/gadget mode only, not host mode. No USB host controller driver (DWC3 in host mode or xHCI) probed during boot. The test failure is expected behavior for this platform configuration: no USB root hubs are exposed because the hardware/DT/kernel config does not enable USB host functionality on this board.
3. Possible fix: This is not a regression introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (AEST CPU PM notifier fix). If USB host mode is required on shikra-iqs-evk, verify: (1) the device tree configures the USB controller with dr_mode = "host" or "otg" with host capability, (2) the kernel config enables CONFIG_USB_DWC3_HOST or CONFIG_USB_XHCI_HCD for this platform, and (3) the board hardware supports USB host mode. If USB host is not supported on this board variant, mark the USBHost test as "not applicable" for shikra-iqs-evk in the CI test matrix.
4. Detail analysis attachment: failed_case_job231234_4_detailed.md

  Case 5: BT_FW_KMD_Service

1. Failed case: BT_FW_KMD_Service
2. Root cause: Bluetooth UART hardware communication failure on shikra-iqs-evk — QCA WCN399x Bluetooth controller not responding to HCI commands over UART, resulting in repeated "command tx timeout" (-110 ETIMEDOUT) errors during firmware version read attempts; BD address remains 00:00:00:00:00:00 and hci0 adapter never reaches operational state.
3. Possible fix: This is a hardware/board-level issue unrelated to PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (AEST CPU PM notifier fix). Verify physical UART connections between AP and BT chip on shikra-iqs-evk board; check BT chip power supply and reset sequencing; confirm BT firmware files are present in rootfs at expected paths (qca/wcn399x); if issue persists across multiple boards, investigate potential kernel UART driver regression in qcom-geni-serial or hci_uart/btqca drivers on this SoC.
4. Detail analysis attachment: failed_case_job231234_5_detailed.md

  Case 6: BT_ON_OFF — Bluetooth Runtime Initialization Failure

1. Failed case: BT_ON_OFF — Bluetooth Runtime Initialization Failure
2. Root cause: Bluetooth HCI adapter hci0 fails to initialize due to persistent command timeouts (-ETIMEDOUT, error -110) when attempting to read QCA (Qualcomm Atheros) version information from the WCN7850 Bluetooth firmware. The adapter never acquires a valid BD (Bluetooth Device) address, rendering the Bluetooth subsystem non-functional. This is a Bluetooth driver/firmware communication failure on the shikra-iqs-evk platform, where the HCI UART transport to the QCA Bluetooth controller is timing out during the initialization handshake.
3. Possible fix: This failure is not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136. The PR changes only drivers/ras/aest/aest-core.c (ARM AEST RAS error reporting), which is unrelated to Bluetooth connectivity. The Bluetooth timeout pattern appears consistently from early boot (before any test execution) and is a pre-existing platform/firmware/driver issue on shikra-iqs-evk. Recommended action: (1) Verify WCN7850 Bluetooth firmware files are present and correct version for this platform (/lib/firmware/qca/ path); (2) Check UART pinctrl/clocking configuration for the Bluetooth UART in the shikra device tree; (3) Verify Bluetooth power/reset GPIO sequencing in device tree and driver; (4) Check for known WCN7850 firmware compatibility issues with kernel 6.18.44; (5) If this is a known infra issue on shikra-iqs-evk CI runners, suppress BT_ON_OFF for this target until the platform Bluetooth stack is fixed.
4. Detail analysis attachment: failed_case_job231234_6_detailed.md

  Case 7: BT_SCAN

1. Failed case: BT_SCAN
2. Root cause: Bluetooth hardware (WCN399x) fails to initialize due to power sequencing issue — the wcn3988-pmu power sequencer cannot find the vddch1 regulator supply (using dummy regulator instead), causing the Bluetooth controller to be non-responsive during HCI command exchanges, resulting in repeated command tx timeouts (-ETIMEDOUT/-110) when attempting to read QCA version information.
3. Possible fix: Add the missing vddch1 regulator supply to the wcn3988-pmu device tree node for shikra-iqs-evk. The regulator should be wired to the actual PMIC rail that powers the WCN399x Bluetooth/WiFi combo chip's CH1 voltage domain. Verify the hardware schematic to identify the correct PMIC regulator (likely a PMICgpio-controlled LDO or SMPS rail) and add it to the DT: vddch1-supply = <&pm8550_l##>; where ## is the correct LDO number.
4. Detail analysis attachment: failed_case_job231234_7_detailed.md

  Case 8: KVM_Driver

1. Failed case: KVM_Driver
2. Root cause: KVM device node /dev/kvm is not present despite CONFIG_KVM being enabled in the kernel, indicating KVM driver did not successfully initialize or create the device node on the Shikra IQS EVK platform.
3. Possible fix: Investigate KVM initialization in kernel boot log for errors; verify KVM is supported on Shikra IQS EVK hardware (check CPU virtualization extensions); if hardware supports it, check for missing device tree nodes or platform-specific KVM enablement requirements for this SoC.
4. Detail analysis attachment: failed_case_job231234_8_detailed.md

  Case 9: KVM_EL2_DTB

1. Failed case: KVM_EL2_DTB
2. Root cause: Could not be determined confidently from available logs.
3. Possible fix: This is a pre-existing platform issue, not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (AEST notifier fix). To resolve: (1) Verify RNG hardware power/clock configuration in Shikra device tree and platform init code; (2) Add runtime PM or clock/regulator dependencies to qcom_rng driver probe for Shikra; (3) If RNG hardware is non-functional on this platform, disable the qcom_hwrng test or mark RNG device as disabled in DT.
4. Detail analysis attachment: failed_case_job231234_9_detailed.md

  Case 10: ** Kernel Crash — Synchronous External Abort in qcom_rng driver

1. Failed case: ** Kernel Crash — Synchronous External Abort in qcom_rng driver
2. Root cause: ** Hardware register access fault in qcom_rng driver at offset +0xc4 in qcom_rng_read() during /dev/hwrng read operation. The driver attempted to read from an unmapped or inaccessible hardware register (likely PRNG_DATA register), triggering a synchronous external abort (bus error). This is a platform-specific hardware access issue on shikra-iqs-evk, not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only modifies AEST CPU PM notifier registration).
3. Possible fix: Verify qcom_rng device tree node for shikra-iqs-evk includes correct register base address and size. Check that PRNG hardware block is powered and clocked before driver access. Add runtime PM and clock enable checks in qcom_rng_read() before register access. If hardware is not present or accessible on this platform, disable qcom_rng in device tree or mark as status="disabled".
4. Detail analysis attachment: failed_case_job231234_10_detailed.md

  Case 11: Kernel Crash — Synchronous External Abort in qcom_rng driver

1. Failed case: Kernel Crash — Synchronous External Abort in qcom_rng driver
2. Root cause: The qcom_hwrng test triggered a synchronous external abort (bus fault) when the qcom_rng driver attempted to read from the RNG hardware register at address 0xffff80008327d004. The CPU received a bus abort, indicating the RNG hardware block was inaccessible (powered down, clock-gated, or incorrectly mapped). The kernel panicked, the board reset into XBL ramdump mode, and the LAVA test shell timed out after 2400 seconds waiting for test completion.
3. Possible fix: This is a pre-existing hardware access issue in the qcom_rng driver on shikra-iqs-evk, NOT introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only modifies AEST error reporting). Verify the RNG device tree node (qcom,prng-ee) register mapping, clock, and power domain configuration for shikra. Ensure the RNG block is properly powered and clocked before driver access. Add runtime PM or clock enable/disable guards in qcom_rng_read() if missing. Re-run the test on a known-good baseline to confirm this is a board/DT configuration issue, not a kernel regression.
4. Detail analysis attachment: failed_case_job231234_11_detailed.md

  Case 12: Kernel Crash — qcom_rng driver page fault leading to system reset

1. Failed case: Kernel Crash — qcom_rng driver page fault leading to system reset
2. Root cause: The kernel crashed with a page fault in qcom_rng_read+0xc4/0x228 while reading from the hardware RNG device. The crash triggered repeated EFI runtime service paging faults, ultimately causing the board to reset into EDL/ramdump mode. The LAVA test timeout occurred because the system was no longer responsive after the crash. This is NOT related to the PR patch (which only touches AEST CPU PM notifier registration) — the crash is in the qcom_rng driver accessing invalid memory.
3. Possible fix: Investigate the qcom_rng driver for memory corruption or invalid pointer dereference at offset 0xc4 in qcom_rng_read(). The crash occurred during a userspace read from /dev/hwrng (likely by a test or system service). Check if the RNG hardware registers are properly mapped and accessible on shikra-iqs-evk. As an immediate workaround, disable the qcom_rng driver or the test that triggers /dev/hwrng reads until the root cause is fixed.
4. Detail analysis attachment: failed_case_job231234_12_detailed.md

  Case 13: ** Kernel Crash — Synchronous External Abort in qcom_rng Driver

1. Failed case: ** Kernel Crash — Synchronous External Abort in qcom_rng Driver
2. Root cause: ** The qcom_rng driver attempted to read from a hardware register (qcom_rng_read+0xc4) that triggered a synchronous external abort (fault code 0x96000010), indicating the hardware block is either not powered, not clocked, or the MMIO address is invalid/inaccessible on shikra-iqs-evk. The crash occurred during the qcom_hwrng test when reading from /dev/hwrng. The subsequent kernel panic prevented the LAVA test shell from completing, causing a 2400-second timeout and lava-test-retry failure.
3. Possible fix: Verify the qcom_rng device tree node for shikra-iqs-evk includes correct clock, power domain, and MMIO address configuration. Check if the RNG hardware block requires explicit power-on or clock enablement that is missing in the current device tree. Add runtime PM or clock/regulator dependencies to the qcom_rng driver probe path to ensure the hardware is accessible before register reads. As an immediate workaround, disable the qcom_hwrng test or blacklist the qcom_rng module on shikra-iqs-evk until the hardware configuration is corrected.
4. Detail analysis attachment: failed_case_job231234_13_detailed.md

  Case 14: ** Kernel Crash — Synchronous External Abort in qcom_rng driver

1. Failed case: ** Kernel Crash — Synchronous External Abort in qcom_rng driver
2. Root cause: ** Hardware access fault (synchronous external abort 0x96000010) in qcom_rng_read+0xc4 when reading RNG hardware registers during /dev/hwrng access. The RNG hardware block was either unpowered, unmapped by SMMU, or in an invalid state when the driver attempted MMIO read. This is a pre-existing platform/hardware/firmware issue on shikra-iqs-evk, not introduced by PR WORKAROUND: ras: aest: Fix duplicate CPU PM notifier registration #1136 (which only modifies AEST CPU PM notifier registration in an unrelated subsystem).
3. Possible fix: This is not a PR-introduced regression. The PR changes (AEST notifier fix) are unrelated to the RNG driver. To resolve the underlying hardware issue: (1) verify RNG hardware block power/clock configuration in device tree and firmware; (2) check SMMU mappings for the RNG device; (3) confirm RNG hardware is present and functional on this board revision; (4) if RNG is non-functional on shikra-iqs-evk, disable the qcom_hwrng test for this target or mark the RNG device as status = "disabled" in the device tree until hardware/firmware is fixed.
4. Detail analysis attachment: failed_case_job231234_14_detailed.md

---

🔎 Boot Log Comparison — PR #1136 vs qcom-6.18.y baseline

PR: #1136
Baseline branch: qcom-6.18.y
Targets compared: 9

Target	Boot lines (PR)	Boot lines (baseline)	New issues	Critical	High	Medium	Low
qcs615-ride	958	no baseline	4	0	0	4	0
monaco-evk	1108	no baseline	11	0	0	11	0
purwa-evk	1528	no baseline	24	0	1	21	2
qcs6490-rb3gen2	2	no baseline	0	0	0	0	0
qcs9100-ride	1219	no baseline	9	0	0	8	1
lemans-evk	774	no baseline	1	0	0	1	0
qcs8300-ride	1098	no baseline	7	0	0	6	1
hamoa-evk	1675	no baseline	30	0	1	29	0
shikra-iqs-evk	899	no baseline	9	0	0	9	0

⚠️ 9 target(s) have no stored baseline — all their issues are listed below but cannot be confirmed as PR-introduced without a baseline.

🟠 High-severity new boot issues: 95 new issue(s) across 9 target(s).

Target: qcs615-ride

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 4 (0 critical, 0 high, 4 medium, 0 low)

🟡 ERROR (medium)

[    7.810109][   T72] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    7.773078][   T91] input: PixArt Lenovo USB Optical Mouse as /devices/platform/soc@0/a800000.usb/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:17EF:600E.0001/input/input2
[    7.781027][  T180] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 15
[    7.792769][   T91] hid-generic 0003:17EF:600E.0001: input: USB HID v1.11 Mouse [PixArt Lenovo USB Optical Mouse] on usb-xhci-hcd.0.auto-1/input0
[    7.810109][   T72] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.810289][  T180] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 16
[    7.811909][  T180] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 17
[    7.821690][   T72] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

[    7.821690][   T72] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    7.810109][   T72] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.810289][  T180] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 16
[    7.811909][  T180] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 17
[    7.821690][   T72] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.827538][  T261] scsi_id (261) used greatest stack depth: 10656 bytes left
[    7.835702][  T180] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 18
[    7.870118][   T72] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator

🟡 ERROR (medium)

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Running /scripts/local-premount ... done.
[   26.060349][  T297] blkid (297) used greatest stack depth: 8696 bytes left
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium)

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   31.281934][  T307] EXT4-fs (sda2): orphan cleanup on readonly fs
[   31.291089][  T307] EXT4-fs (sda2): mounted filesystem 005fdba6-605e-4778-b1f7-ba98dc88617a ro with ordered data mode. Quota mode: none.
done.

Target: monaco-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 11 (0 critical, 0 high, 11 medium, 0 low)

🟡 ERROR (medium)

[    8.518956][  T127] usb usb2-port1: config error

Context

[    8.502317][  T179] NET: Registered PF_BLUETOOTH protocol family
[    8.508625][  T179] Bluetooth: HCI device and connection manager initialized
[    8.515888][  T179] Bluetooth: HCI socket layer initialized
[    8.518956][  T127] usb usb2-port1: config error
[    8.521618][  T179] Bluetooth: L2CAP socket layer initialized
[    8.532280][  T179] Bluetooth: SCO socket layer initialized
[    8.541260][  T179] Bluetooth: HCI UART driver ver 2.3

🟡 ERROR (medium)

[    8.619384][   T10] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    8.602361][  T193] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    8.603664][  T179] Bluetooth: HCI UART protocol QCA registered
[    8.614425][  T172] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 21
[    8.619384][   T10] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.636850][  T190] pca953x 3-003a: supply vcc not found, using dummy regulator
[    8.643217][   T10] cfg80211: failed to load regulatory.db
[    8.658911][  T190] pca953x 3-003a: using no AI

🟡 ERROR (medium)

[    8.780743][  T230] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[    8.765830][  T190] pca953x 3-003c: supply vcc not found, using dummy regulator
[    8.766698][  T250] hub 1-1:1.0: USB hub found
[    8.767260][  T250] hub 1-1:1.0: 4 ports detected
[    8.780743][  T230] tpm tpm0: A TPM error (256) occurred attempting the self test
[    8.798304][  T230] tpm tpm0: starting up the TPM manually
[    8.808904][  T111] Bluetooth: hci0: QCA Product ID   :0x00000013
[    8.815417][  T111] Bluetooth: hci0: QCA SOC Version  :0x400c1211

🟡 ERROR (medium)

[    8.856804][  T111] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2

Context

[    8.828296][  T111] Bluetooth: hci0: QCA Patch Version:0x000038e6
[    8.842805][  T111] Bluetooth: hci0: QCA controller version 0x12110201
[    8.849631][  T111] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.856804][  T111] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.859303][  T190] pca953x 3-003c: using no AI
[    8.866293][  T111] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.866298][  T111] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv

🟡 ERROR (medium)

[    8.866489][  T111] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

Context

[    8.859303][  T190] pca953x 3-003c: using no AI
[    8.866293][  T111] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.866298][  T111] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.866489][  T111] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.873058][  T172] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 24
[    8.879390][  T111] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.893724][  T172] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 25

🟡 ERROR (medium)

[    9.296491][  T111] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2

Context

[    9.288429][  T193] mhi mhi0: Requested to power ON
[    9.291143][   T64] qcom-ethqos 23040000.ethernet: Enabled RFS Flow TC (entries=10)
[    9.296148][  T193] mhi mhi0: Power on setup success
[    9.296491][  T111] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.304144][   T64] qcom-ethqos 23040000.ethernet: Enabling HW TC (entries=128, max_off=64)
[    9.309268][  T111] mhi mhi0: Error loading firmware: -2
[    9.319692][   T64] qcom-ethqos 23040000.ethernet: TSO feature enabled

🟡 ERROR (medium)

[    9.309268][  T111] mhi mhi0: Error loading firmware: -2

Context

[    9.296148][  T193] mhi mhi0: Power on setup success
[    9.296491][  T111] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.304144][   T64] qcom-ethqos 23040000.ethernet: Enabling HW TC (entries=128, max_off=64)
[    9.309268][  T111] mhi mhi0: Error loading firmware: -2
[    9.319692][   T64] qcom-ethqos 23040000.ethernet: TSO feature enabled
[    9.319694][   T64] qcom-ethqos 23040000.ethernet: SPH feature enabled
[    9.319696][   T64] qcom-ethqos 23040000.ethernet: Using 36/40 bits DMA host/device width

🟡 ERROR (medium)

[    9.510854][  T127] usb usb2-port1: config error

Context

[    9.412224][  T189] hub 1-1:1.0: USB hub found
[    9.417782][  T189] hub 1-1:1.0: 4 ports detected
[    9.488470][  T189] onboard-usb-dev a600000.usb:hub@1: supply vdd not found, using dummy regulator
[    9.510854][  T127] usb usb2-port1: config error
[    9.513342][   T64] msm_dpu ae01000.display-controller: bound af54000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    9.513687][  T173] qcom-ethqos 23040000.ethernet end0: renamed from eth0
[    9.537429][   T64] adreno 3d00000.gpu: supply vdd not found, using dummy regulator

🟡 ERROR (medium)

[    9.606946][  T193] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110

Context

[    9.576203][   T64] msm_dpu ae01000.display-controller: bound 3d00000.gpu (ops a3xx_ops [msm])
[    9.585265][   T55] hub 1-1:1.0: 4 ports detected
[    9.587473][   T64] [drm:dpu_kms_hw_init:1201] dpu hardware revision:0x80040000
[    9.606946][  T193] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110
[    9.610755][   T64] [drm] Initialized msm 1.13.0 for ae01000.display-controller on minor 0
[    9.626097][   T64] msm_dpu ae01000.display-controller: [drm:adreno_request_fw [msm]] loaded qcom/a650_sqe.fw from new location
[    9.638657][   T64] msm_dpu ae01000.display-controller: [drm:adreno_request_fw [msm]] loaded qcom/a623_gmu.bin from new location

🟡 ERROR (medium)

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium)

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   32.358741][  T370] EXT4-fs (sda2): orphan cleanup on readonly fs
[   32.367306][  T370] EXT4-fs (sda2): mounted filesystem 513728bc-9c18-4a66-a6fb-01735755aeed ro with ordered data mode. Quota mode: none.
done.

Target: purwa-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 24 (0 critical, 1 high, 21 medium, 2 low)

🟡 WATCHDOG (medium)

[    6.363454][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.

Context

[    6.320342][    T1] usbcore: registered new interface driver usb-storage
[    6.328059][   T87] Freeing initrd memory: 60756K
[    6.344789][    T1] i2c_dev: i2c /dev entries driver
[    6.363454][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.375010][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.382072][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.387390][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium)

[    6.421060][   T87] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    6.408122][    T1] pstore: Registered efi_pstore as persistent store backend
[    6.415683][   T87] efivars: efivars already registered
[    6.415836][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    6.421060][   T87] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    6.428689][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    6.452652][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    6.461384][    T1] usbcore: registered new interface driver usbhid

🔵 FIRMWARE_FAIL (low)

[    9.246666][  T153] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16

Context

[    9.140061][   T72] qcom-pcie 1c08000.pci: supply vddpe-3v3 not found, using dummy regulator
[    9.147594][  T153] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_clock_rates_triplet_out_of_spec]
[    9.207555][  T211] coresight stm0: STM32 initialized
[    9.246666][  T153] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.249078][  T200] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.259249][  T153] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.268260][  T200] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled

🔵 FIRMWARE_FAIL (low)

[    9.259249][  T153] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16

Context

[    9.207555][  T211] coresight stm0: STM32 initialized
[    9.246666][  T153] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.249078][  T200] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.259249][  T153] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.268260][  T200] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[    9.289765][  T200] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled
[    9.304558][  T153] cpu cpu0: EM: created perf domain

🟡 ERROR (medium)

[    9.393560][  T195] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led

Context

[    9.374880][  T200] scsi host0: ufshcd
[    9.386741][  T223] videodev: Linux video capture interface: v2.00
[    9.392765][   T86] scsi 0:0:0:49488: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.393560][  T195] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[    9.395067][  T153] arm-smmu 3da0000.iommu: probing hardware configuration...
[    9.395069][  T153] arm-smmu 3da0000.iommu: SMMUv2 with:
[    9.395090][  T153] arm-smmu 3da0000.iommu: 	stage 1 translation

🟡 ERROR (medium)

[    9.411931][  T195] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22

Context

[    9.411077][   T87] sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[    9.411081][   T87] sd 0:0:0:0: [sda] Optimal transfer size 524288 bytes
[    9.411856][  T203] remoteproc remoteproc0: adsp is available
[    9.411931][  T195] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[    9.412073][  T151] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.412076][  T151] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    9.412142][  T151] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host

🟡 ERROR (medium)

[    9.412142][  T151] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host

Context

[    9.411931][  T195] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[    9.412073][  T151] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.412076][  T151] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    9.412142][  T151] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.412149][  T151] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.415139][   T90] /wifi-bt-connector: Fixed dependency cycle(s) with /soc@0/pci@1c08000/pcie@0
[    9.415207][   T90] /soc@0/pci@1c08000/pcie@0: Fixed dependency cycle(s) with /wifi-bt-connector

🟡 ERROR (medium)

[    9.412149][  T151] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61

Context

[    9.412073][  T151] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.412076][  T151] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    9.412142][  T151] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.412149][  T151] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.415139][   T90] /wifi-bt-connector: Fixed dependency cycle(s) with /soc@0/pci@1c08000/pcie@0
[    9.415207][   T90] /soc@0/pci@1c08000/pcie@0: Fixed dependency cycle(s) with /wifi-bt-connector
[    9.415576][  T203] remoteproc remoteproc1: cdsp is available

🟡 ERROR (medium)

[    9.527067][   T65] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host

Context

[    9.495962][   T65] phy phy-1bfc000.phy.0: phy poweron failed --> -61
[    9.520958][   T88] qcom-pcie 1c00000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[    9.522977][  T153] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a800000.usb for /pmic-glink/connector@1
[    9.527067][   T65] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host
[    9.527661][  T248] qcom-pcie 1c08000.pci: supply vdda not found, using dummy regulator
[    9.527776][  T248] qcom-pcie 1c08000.pci: supply vddpe-3v3 not found, using dummy regulator
[    9.527951][  T248] qcom-pcie 1c08000.pci: host bridge /soc@0/pci@1c08000 ranges:

🟡 ERROR (medium)

[    9.734440][   T65] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61

Context

[    9.527983][  T248] qcom-pcie 1c08000.pci:       IO 0x007c200000..0x007c2fffff -> 0x0000000000
[    9.528008][  T248] qcom-pcie 1c08000.pci:      MEM 0x007c300000..0x007dffffff -> 0x007c300000
[    9.733291][  T255] remoteproc remoteproc0: remote processor adsp is now up
[    9.734440][   T65] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61
[    9.738259][  T248] qcom-pcie 1c08000.pci: supply vdda not found, using dummy regulator
[    9.738347][  T248] qcom-pcie 1c08000.pci: supply vddpe-3v3 not found, using dummy regulator
[    9.738494][  T248] qcom-pcie 1c08000.pci: host bridge /soc@0/pci@1c08000 ranges:

🟡 ERROR (medium)

[   11.362747][  T247] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[   11.341866][  T209] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   11.344332][  T247] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   11.356671][  T209] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.362747][  T247] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.364505][  T209] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.371843][  T247] tpm tpm0: starting up the TPM manually
[   11.380140][  T110] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

🟡 ERROR (medium)

[   11.380140][  T110] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   11.362747][  T247] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.364505][  T209] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.371843][  T247] tpm tpm0: starting up the TPM manually
[   11.380140][  T110] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.396294][  T110] cfg80211: failed to load regulatory.db
[   11.436124][  T226] platform iris_non_pixel.0: Adding to iommu group 16
[   11.437027][  T223] qcom-camss acb7000.isp: Entity type for entity msm_tpg0 was not initialized!

🟡 ERROR (medium)

[   11.784269][   T64] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.747244][  T202] NET: Registered PF_BLUETOOTH protocol family
[   11.751000][  T116] mhi mhi0: Wait for device to enter SBL or Mission mode
[   11.778000][  T202] Bluetooth: HCI device and connection manager initialized
[   11.784269][   T64] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.785244][  T202] Bluetooth: HCI socket layer initialized
[   11.795086][   T64] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.800900][  T202] Bluetooth: L2CAP socket layer initialized

🟡 ERROR (medium)

[   11.795086][   T64] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.778000][  T202] Bluetooth: HCI device and connection manager initialized
[   11.784269][   T64] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.785244][  T202] Bluetooth: HCI socket layer initialized
[   11.795086][   T64] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.800900][  T202] Bluetooth: L2CAP socket layer initialized
[   11.813770][   T64] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.816562][  T202] Bluetooth: SCO socket layer initialized

🟡 ERROR (medium)

[   11.813770][   T64] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.785244][  T202] Bluetooth: HCI socket layer initialized
[   11.795086][   T64] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.800900][  T202] Bluetooth: L2CAP socket layer initialized
[   11.813770][   T64] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.816562][  T202] Bluetooth: SCO socket layer initialized
[   11.832320][   T64] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.845458][   T64] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

[   11.832320][   T64] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.800900][  T202] Bluetooth: L2CAP socket layer initialized
[   11.813770][   T64] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.816562][  T202] Bluetooth: SCO socket layer initialized
[   11.832320][   T64] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.845458][   T64] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.846289][  T202] usbcore: registered new interface driver btusb
[   11.847779][  T298] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin

🟡 ERROR (medium)

[   11.845458][   T64] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.813770][   T64] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.816562][  T202] Bluetooth: SCO socket layer initialized
[   11.832320][   T64] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.845458][   T64] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.846289][  T202] usbcore: registered new interface driver btusb
[   11.847779][  T298] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
[   11.847781][  T298] Bluetooth: hci0: QCA: patch rome 0x190200 build 0x8567, firmware rome 0x190200 build 0x43fb

🟡 ERROR (medium)

[   11.855365][   T64] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.846289][  T202] usbcore: registered new interface driver btusb
[   11.847779][  T298] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
[   11.847781][  T298] Bluetooth: hci0: QCA: patch rome 0x190200 build 0x8567, firmware rome 0x190200 build 0x43fb
[   11.855365][   T64] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.892441][   T64] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.902282][   T64] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.912902][   T64] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel

🟡 ERROR (medium)

[   11.892441][   T64] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.847779][  T298] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
[   11.847781][  T298] Bluetooth: hci0: QCA: patch rome 0x190200 build 0x8567, firmware rome 0x190200 build 0x43fb
[   11.855365][   T64] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.892441][   T64] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.902282][   T64] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.912902][   T64] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   11.930648][   T64] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000

🟡 ERROR (medium)

[   11.902282][   T64] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.847781][  T298] Bluetooth: hci0: QCA: patch rome 0x190200 build 0x8567, firmware rome 0x190200 build 0x43fb
[   11.855365][   T64] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.892441][   T64] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.902282][   T64] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.912902][   T64] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   11.930648][   T64] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   12.141163][   T64] ------------[ cut here ]------------

🟡 WARNING (medium)

[   12.146640][   T64] WARNING: CPU: 6 PID: 64 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   11.912902][   T64] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   11.930648][   T64] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   12.141163][   T64] ------------[ cut here ]------------
[   12.146640][   T64] WARNING: CPU: 6 PID: 64 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   12.158885][   T64] Modules linked in: panel_edp(+) btusb btrtl btintel btbcm bluetooth ecdh_generic ecc ath12k_wifi7 ath12k msm mac80211 qcom_camss ocmem qcom_iris gpu_sched v4l2_fwnode libarc4 sn
[   12.159111][   T64]  pinctrl_sm8550_lpass_lpi qcom_sysmon gpucc_x1p42100 sha1 qcom_common ubwc_config lpasscc_sc8280xp snd_soc_lpass_va_macro libdes phy_qcom_qmp_usb soundwire_qcom pinctrl_lpass_lp
[   12.327681][   T64] CPU: 6 UID: 0 PID: 64 Comm: kworker/u33:0 Not tainted 6.18.44-gbe0fd4cd73fc #1 PREEMPT 

🟠 CALL_TRACE (high)

[   12.458186][   T64] Call trace:

Context

[   12.434079][   T64] x8 : ffff800082eb3468 x7 : 0000000000000000 x6 : 0000000000000001
[   12.442114][   T64] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   12.450149][   T64] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   12.458186][   T64] Call trace:
[   12.461418][   T64]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   12.468304][   T64]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   12.474120][   T64]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium)

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium)

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   33.852991][  T380] EXT4-fs (sda2): orphan cleanup on readonly fs
[   33.859558][  T380] EXT4-fs (sda2): mounted filesystem 2e16df27-6eab-4d72-84b7-a63f5340d8a3 ro with ordered data mode. Quota mode: none.
done.

Target: qcs9100-ride

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 9 (0 critical, 0 high, 8 medium, 1 low)

🟡 ERROR (medium)

[    3.696621][    T1] DT AEST: registered 3 AEST error source(s) from DT

Context

[    3.660201][    T1] DT AEST: node /aest/aest-processor-0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.672290][    T1] DT AEST: node /aest/aest-l3-cluster0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.684313][    T1] DT AEST: node /aest/aest-l3-cluster1: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.696621][    T1] DT AEST: registered 3 AEST error source(s) from DT
[    3.703463][    T1] clocksource: Switched to clocksource arch_sys_counter
[    3.713635][    T1] VFS: Disk quotas dquot_6.6.0
[    3.718423][    T1] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

🟡 ERROR (medium)

[    7.557002][  T190] qcom_eud 88e1000.eud: error -ENODEV: failed to get controller node for path 0

Context

[    7.512235][   T73] qcom-pcie 1c00000.pcie:      MEM 0x0040300000..0x005fffffff -> 0x0040300000
[    7.536653][  T111] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
[    7.546957][  T111] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    7.557002][  T190] qcom_eud 88e1000.eud: error -ENODEV: failed to get controller node for path 0
[    7.558092][  T111] qcom-pcie 1c00000.pcie: host bridge /pcie@1c00000 ranges:
[    7.559545][  T189] coresight cti_sys0: CTI initialized 0
[    7.579115][  T111] qcom-pcie 1c00000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000

🟡 ERROR (medium)

[    9.122931][  T207] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f

Context

[    9.114417][  T206] Bluetooth: HCI UART protocol LL registered
[    9.120545][  T206] Bluetooth: HCI UART protocol QCA registered
[    9.122494][  T109] Bluetooth: hci0: setting up wcn6855
[    9.122931][  T207] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.122931][  T207] :39
[    9.123014][  T207] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.123014][  T207] :43

🟡 ERROR (medium)

[    9.123014][  T207] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

Context

[    9.122494][  T109] Bluetooth: hci0: setting up wcn6855
[    9.122931][  T207] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.122931][  T207] :39
[    9.123014][  T207] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.123014][  T207] :43
[    9.129633][  T202] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.158614][  T207] msm_dpu ae01000.display-controller: bound af54000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium)

[    9.183672][  T137] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    9.158614][  T207] msm_dpu ae01000.display-controller: bound af54000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    9.163725][  T202] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.177134][  T207] msm_dpu ae01000.display-controller: bound af5c000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    9.183672][  T137] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.195582][  T207] msm_dpu ae01000.display-controller: bound ae94000.dsi (ops dsi_ops [msm])
[    9.200194][  T109] Bluetooth: hci0: QCA Product ID   :0x00000013
[    9.200199][  T109] Bluetooth: hci0: QCA SOC Version  :0x400c0210

🔵 FIRMWARE_FAIL (low)

[   10.139988][  T209] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22

Context

[   10.054220][  T184] platform 30000000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 50
[   10.065262][  T184] platform 30000000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 51
[   10.076124][  T184] platform 30000000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 52
[   10.139988][  T209] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   10.161815][  T209] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   10.199834][  T109] Bluetooth: hci0: QCA Downloading qca/QCA6698/hpnv21.b207
[   10.224835][   T89] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x207 soc_id 0x400c0210

🟡 ERROR (medium)

[   10.161815][  T209] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22

Context

[   10.065262][  T184] platform 30000000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 51
[   10.076124][  T184] platform 30000000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 52
[   10.139988][  T209] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   10.161815][  T209] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   10.199834][  T109] Bluetooth: hci0: QCA Downloading qca/QCA6698/hpnv21.b207
[   10.224835][   T89] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x207 soc_id 0x400c0210
[   10.234703][   T89] ath11k_pci 0000:01:00.0: fw_version 0x11021302 fw_build_timestamp 2026-02-04 08:10 fw_build_id WLAN.HSP.1.1-04866.5-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1

🟡 ERROR (medium)

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium)

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   30.440875][  T373] EXT4-fs (sda2): orphan cleanup on readonly fs
[   30.447758][  T373] EXT4-fs (sda2): mounted filesystem 57198697-7c20-47a4-944c-71a7b61d6a7e ro with ordered data mode. Quota mode: none.
done.

Target: lemans-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 1 (0 critical, 0 high, 1 medium, 0 low)

🟡 ERROR (medium)

[    3.200178][    T1] DT AEST: registered 3 AEST error source(s) from DT

Context

[    3.163770][    T1] DT AEST: node /aest/aest-processor-0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.175851][    T1] DT AEST: node /aest/aest-l3-cluster0: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.187874][    T1] DT AEST: node /aest/aest-l3-cluster1: failed to map ERI IRQ: -61 (interrupt-names[1]="<missing>", want "eri")
[    3.200178][    T1] DT AEST: registered 3 AEST error source(s) from DT
[    3.207017][    T1] clocksource: Switched to clocksource arch_sys_counter
[    3.214543][    T1] VFS: Disk quotas dquot_6.6.0
[    3.219337][    T1] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

Target: qcs8300-ride

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 7 (0 critical, 0 high, 6 medium, 1 low)

🟡 ERROR (medium)

[    9.421497][  T135] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    9.371647][  T111] Bluetooth: hci0: setting up wcn6855
[    9.405245][  T174] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.412689][  T174] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.421497][  T135] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.424980][  T182] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 16
[    9.431408][  T135] cfg80211: failed to load regulatory.db
[    9.453165][  T111] Bluetooth: hci0: QCA Product ID   :0x00000013

🟡 ERROR (medium)

[    9.734419][   T85] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f

Context

[    9.709132][  T182] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 21
[    9.713276][  T174] mhi mhi0: Power on setup success
[    9.732130][  T182] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 22
[    9.734419][   T85] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.734419][   T85] :39
[    9.743740][  T182] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 23
[    9.755886][   T85] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

🟡 ERROR (medium)

[    9.755886][   T85] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

Context

[    9.734419][   T85] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.734419][   T85] :39
[    9.743740][  T182] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 23
[    9.755886][   T85] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.755886][   T85] :43
[    9.766039][  T182] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 24
[    9.787695][  T182] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 25

🔵 FIRMWARE_FAIL (low)

[   11.433837][  T194] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22

Context

[   10.577091][  T315] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x206 soc_id 0x400c0210
[   10.594246][  T315] ath11k_pci 0000:01:00.0: fw_version 0x11021302 fw_build_timestamp 2026-02-04 08:10 fw_build_id WLAN.HSP.1.1-04866.5-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1
[   11.135222][  T165] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[   11.433837][  T194] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   11.456068][  T194] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   14.861277][  T171] qcom-apm gprsvc:service:2:1: CMD timeout for [1001021] opcode
[   14.878737][  T171] platform 3000000.remoteproc:glink-edge:gpr:service@1:dais: Adding to iommu group 26

🟡 ERROR (medium)

[   11.456068][  T194] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22

Context

[   10.594246][  T315] ath11k_pci 0000:01:00.0: fw_version 0x11021302 fw_build_timestamp 2026-02-04 08:10 fw_build_id WLAN.HSP.1.1-04866.5-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1
[   11.135222][  T165] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[   11.433837][  T194] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   11.456068][  T194] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   14.861277][  T171] qcom-apm gprsvc:service:2:1: CMD timeout for [1001021] opcode
[   14.878737][  T171] platform 3000000.remoteproc:glink-edge:gpr:service@1:dais: Adding to iommu group 26
Begin: Loading essential drivers ... done.

🟡 ERROR (medium)

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium)

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   32.954296][  T382] EXT4-fs (sda2): orphan cleanup on readonly fs
[   32.961177][  T382] EXT4-fs (sda2): mounted filesystem 985e5d67-cfc5-4f20-bc82-74addca41f10 ro with ordered data mode. Quota mode: none.
done.

Target: hamoa-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 30 (0 critical, 1 high, 29 medium, 0 low)

🟡 WATCHDOG (medium)

[    6.971400][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.

Context

[    6.918274][    T1] usbcore: registered new interface driver usb-storage
[    6.938643][  T113] Freeing initrd memory: 61064K
[    6.948278][    T1] i2c_dev: i2c /dev entries driver
[    6.971400][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.983334][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.990399][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.995719][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium)

[    7.029486][  T113] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    7.016504][    T1] pstore: Registered efi_pstore as persistent store backend
[    7.024107][  T113] efivars: efivars already registered
[    7.024226][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    7.029486][  T113] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    7.037090][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    7.061078][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    7.069819][    T1] usbcore: registered new interface driver usbhid

🟡 ERROR (medium)

[   10.614738][  T285] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led

Context

[   10.599795][  T162] arm-smmu 3da0000.iommu: 	stream matching with 24 register groups
[   10.600644][  T362] remoteproc remoteproc0: powering up adsp
[   10.600650][  T362] remoteproc remoteproc0: Booting fw image qcom/x1e80100/adsp.mbn, size 17922440
[   10.614738][  T285] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   10.615463][  T280] remoteproc remoteproc1: cdsp is available
[   10.615741][  T254] input: pmic_pwrkey as /devices/platform/soc@0/c400000.arbiter/spmi-0/0-00/c42d000.spmi:pmic@0:pon@1300/c42d000.spmi:pmic@0:pon@1300:pwrkey/input/input0
[   10.616078][  T248] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier fd5000.phy for /pmic-glink/connector@0

🟡 ERROR (medium)

[   10.627431][  T285] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22

Context

[   10.619304][  T162] arm-smmu 3da0000.iommu: 	Supported page sizes: 0x61311000
[   10.625477][  T137] remoteproc remoteproc1: powering up cdsp
[   10.625481][  T137] remoteproc remoteproc1: Booting fw image qcom/x1e80100/cdsp.mbn, size 3215784
[   10.627431][  T285] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   10.633092][  T162] arm-smmu 3da0000.iommu: 	Stage-1: 48-bit VA -> 40-bit IPA
[   10.676559][  T253] platform iris_non_pixel.0: Adding to iommu group 14
[   10.686024][  T162] arm-smmu 3da0000.iommu: 	preserved 0 boot mappings

🟡 ERROR (medium)

[   10.787397][  T275] tpm tpm0: A TPM error (256) occurred attempting the self test

Context

[   10.771551][  T275] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   10.772225][  T162] platform 3d6a000.gmu: Adding to iommu group 17
[   10.783735][  T137] remoteproc remoteproc1: remote processor cdsp is now up
[   10.787397][  T275] tpm tpm0: A TPM error (256) occurred attempting the self test
[   10.787400][  T275] tpm tpm0: starting up the TPM manually
[   10.794294][  T162] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[   10.796443][  T114] qcom-pcie 1c00000.pci: supply vdda not found, using dummy regulator

🟡 ERROR (medium)

[   11.398193][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.353059][  T115] pci 0006:00:00.0: [17cb:0111] type 01 class 0x060400 PCIe Root Port
[   11.386651][  T162] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a800000.usb for /pmic-glink/connector@1
[   11.390233][  T115] pci 0006:00:00.0: BAR 0 [mem 0x00000000-0x00000fff]
[   11.398193][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.401327][  T115] pci 0006:00:00.0: PCI bridge to [bus 01-ff]
[   11.401332][  T115] pci 0006:00:00.0:   bridge window [io  0x300000-0x300fff]
[   11.401335][  T115] pci 0006:00:00.0:   bridge window [mem 0x00000000-0x000fffff]

🟡 ERROR (medium)

[   11.410412][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.401335][  T115] pci 0006:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[   11.401341][  T115] pci 0006:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   11.401402][  T115] pci 0006:00:00.0: PME# supported from D0 D3hot D3cold
[   11.410412][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.411256][  T388]  sda: sda1 sda2
[   11.411881][  T388] sd 0:0:0:0: [sda] Attached SCSI disk
[   11.421018][  T115] pci 0006:01:00.0: [c0a9:5426] type 00 class 0x010802 PCIe Endpoint

🟡 ERROR (medium)

[   11.429413][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.411256][  T388]  sda: sda1 sda2
[   11.411881][  T388] sd 0:0:0:0: [sda] Attached SCSI disk
[   11.421018][  T115] pci 0006:01:00.0: [c0a9:5426] type 00 class 0x010802 PCIe Endpoint
[   11.429413][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.436202][  T115] pci 0006:01:00.0: BAR 0 [mem 0x00000000-0x00003fff 64bit]
[   11.445417][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.458636][  T115] pci 0006:01:00.0: ASPM: default states L1

🟡 ERROR (medium)

[   11.445417][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.421018][  T115] pci 0006:01:00.0: [c0a9:5426] type 00 class 0x010802 PCIe Endpoint
[   11.429413][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.436202][  T115] pci 0006:01:00.0: BAR 0 [mem 0x00000000-0x00003fff 64bit]
[   11.445417][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.458636][  T115] pci 0006:01:00.0: ASPM: default states L1
[   11.460967][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.468637][  T115] pci 0006:00:00.0: bridge window [mem 0x70300000-0x703fffff]: assigned

🟡 ERROR (medium)

[   11.460967][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.436202][  T115] pci 0006:01:00.0: BAR 0 [mem 0x00000000-0x00003fff 64bit]
[   11.445417][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.458636][  T115] pci 0006:01:00.0: ASPM: default states L1
[   11.460967][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.468637][  T115] pci 0006:00:00.0: bridge window [mem 0x70300000-0x703fffff]: assigned
[   11.468968][  T188] qcom-pcie 1c08000.pci: PCI host bridge to bus 0004:00
[   11.468984][  T188] pci_bus 0004:00: root bus resource [bus 00-ff]

🟡 ERROR (medium)

[   11.475709][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.471780][  T188] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint
[   11.471971][  T188] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]
[   11.472376][  T188] pci 0004:01:00.0: PME# supported from D0 D3hot D3cold
[   11.475709][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.478573][  T188] pci 0004:01:00.0: ASPM: default states L1
[   11.478716][  T188] pci 0004:00:00.0: bridge window [mem 0x7c400000-0x7c5fffff]: assigned
[   11.478719][  T188] pci 0004:00:00.0: BAR 0 [mem 0x7c300000-0x7c300fff]: assigned

🟡 ERROR (medium)

[   11.494608][  T162] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.482587][  T115] pci 0006:00:00.0: BAR 0 [mem 0x70400000-0x70400fff]: assigned
[   11.482605][  T115] pci 0006:01:00.0: BAR 0 [mem 0x70300000-0x70303fff 64bit]: assigned
[   11.482680][  T115] pci 0006:00:00.0: PCI bridge to [bus 01-ff]
[   11.494608][  T162] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.498656][  T115] pci 0006:00:00.0:   bridge window [mem 0x70300000-0x703fffff]
[   11.505538][  T162] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.511888][  T115] pci_bus 0006:00: resource 4 [io  0x300000-0x3fffff]

🟡 ERROR (medium)

[   11.505538][  T162] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.482680][  T115] pci 0006:00:00.0: PCI bridge to [bus 01-ff]
[   11.494608][  T162] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.498656][  T115] pci 0006:00:00.0:   bridge window [mem 0x70300000-0x703fffff]
[   11.505538][  T162] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.511888][  T115] pci_bus 0006:00: resource 4 [io  0x300000-0x3fffff]
[   11.522108][  T162] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   11.529922][  T115] pci_bus 0006:00: resource 5 [mem 0x70300000-0x73ffffff]

🟡 ERROR (medium)

[   11.952238][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.897547][  T115] pcieport 0006:00:00.0: PME: Signaling with IRQ 249
[   11.906456][  T114] qcom-pcie 1c00000.pci: Device not found
[   11.915797][  T115] pcieport 0006:00:00.0: AER: enabled with IRQ 244
[   11.952238][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.959165][  T189] qcom-pcie 1bd0000.pcie: PCI host bridge to bus 0003:00
[   11.965676][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.972303][  T189] pci_bus 0003:00: root bus resource [bus 00-ff]

🟡 ERROR (medium)

[   11.965676][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.915797][  T115] pcieport 0006:00:00.0: AER: enabled with IRQ 244
[   11.952238][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.959165][  T189] qcom-pcie 1bd0000.pcie: PCI host bridge to bus 0003:00
[   11.965676][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.972303][  T189] pci_bus 0003:00: root bus resource [bus 00-ff]
[   11.972308][  T189] pci_bus 0003:00: root bus resource [io  0x200000-0x2fffff] (bus address [0x0000-0xfffff])
[   11.983979][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

[   11.983979][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.965676][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.972303][  T189] pci_bus 0003:00: root bus resource [bus 00-ff]
[   11.972308][  T189] pci_bus 0003:00: root bus resource [io  0x200000-0x2fffff] (bus address [0x0000-0xfffff])
[   11.983979][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.986534][  T189] pci_bus 0003:00: root bus resource [mem 0x78300000-0x7bffffff]
[   11.994784][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.000849][  T189] pci_bus 0003:00: root bus resource [mem 0x740000000-0x77fffffff]

🟡 ERROR (medium)

[   11.994784][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.972308][  T189] pci_bus 0003:00: root bus resource [io  0x200000-0x2fffff] (bus address [0x0000-0xfffff])
[   11.983979][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.986534][  T189] pci_bus 0003:00: root bus resource [mem 0x78300000-0x7bffffff]
[   11.994784][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.000849][  T189] pci_bus 0003:00: root bus resource [mem 0x740000000-0x77fffffff]
[   12.013624][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.018503][  T349] usb 1-1: new full-speed USB device number 2 using xhci-hcd

🟡 ERROR (medium)

[   12.013624][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.986534][  T189] pci_bus 0003:00: root bus resource [mem 0x78300000-0x7bffffff]
[   11.994784][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.000849][  T189] pci_bus 0003:00: root bus resource [mem 0x740000000-0x77fffffff]
[   12.013624][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.018503][  T349] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[   12.018545][  T189] pci 0003:00:00.0: [17cb:0111] type 01 class 0x060400 PCIe Root Port
[   12.018563][  T189] pci 0003:00:00.0: BAR 0 [mem 0x00000000-0x00000fff]

🟡 ERROR (medium)

[   12.028200][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.024684][  T114] pci_bus 0005:00: resource 5 [mem 0x7e300000-0x7fffffff]
[   12.024930][  T114] pcieport 0005:00:00.0: PME: Signaling with IRQ 253
[   12.025282][  T114] pcieport 0005:00:00.0: AER: enabled with IRQ 253
[   12.028200][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.445811][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.455657][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.467229][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

[   12.445811][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.024930][  T114] pcieport 0005:00:00.0: PME: Signaling with IRQ 253
[   12.025282][  T114] pcieport 0005:00:00.0: AER: enabled with IRQ 253
[   12.028200][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.445811][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.455657][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.467229][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.477196][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

[   12.455657][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.025282][  T114] pcieport 0005:00:00.0: AER: enabled with IRQ 253
[   12.028200][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.445811][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.455657][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.467229][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.477196][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.477947][  T114] nvme nvme0: pci function 0006:01:00.0

🟡 ERROR (medium)

[   12.467229][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.028200][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.445811][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.455657][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.467229][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.477196][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.477947][  T114] nvme nvme0: pci function 0006:01:00.0
[   12.486779][  T287] cfg80211: Loading compiled-in X.509 certificates for regulatory database

🟡 ERROR (medium)

[   12.477196][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.445811][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.455657][  T162] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.467229][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.477196][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.477947][  T114] nvme nvme0: pci function 0006:01:00.0
[   12.486779][  T287] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   12.488644][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

[   12.488644][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.477196][  T162] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.477947][  T114] nvme nvme0: pci function 0006:01:00.0
[   12.486779][  T287] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   12.488644][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.492667][  T114] nvme 0006:01:00.0: enabling device (0000 -> 0002)
[   12.494527][  T287] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   12.495623][  T287] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'

🟡 ERROR (medium)

[   12.496173][  T190] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   12.492667][  T114] nvme 0006:01:00.0: enabling device (0000 -> 0002)
[   12.494527][  T287] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   12.495623][  T287] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   12.496173][  T190] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   12.496210][  T190] cfg80211: failed to load regulatory.db
[   12.501381][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.553764][  T114] nvme nvme0: allocated 64 MiB host memory buffer (16 segments).

🟡 ERROR (medium)

[   12.501381][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   12.495623][  T287] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   12.496173][  T190] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   12.496210][  T190] cfg80211: failed to load regulatory.db
[   12.501381][  T162] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.553764][  T114] nvme nvme0: allocated 64 MiB host memory buffer (16 segments).
[   12.567380][  T252] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 18
[   12.568652][  T120] qcom,apr 6800000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1

🟡 WARNING (medium)

[   12.634819][  T249] WARNING: CPU: 0 PID: 249 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   12.632636][  T252] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 25
[   12.633450][  T252] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@10: Adding to iommu group 26
[   12.634273][  T252] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@11: Adding to iommu group 27
[   12.634819][  T249] WARNING: CPU: 0 PID: 249 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   12.635077][  T252] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@12: Adding to iommu group 28
[   12.635886][  T252] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@13: Adding to iommu group 29
[   12.733010][  T249] Modules linked in: ecc snd_q6apm(+) cfg80211 panel_edp(+) nvme rfkill rpmsg_ctrl mhi nvme_core apr fastrpc(+) qrtr_smd rpmsg_char msm qcom_pd_mapper tpm_tis_spi ps883x ocmem qco

🟠 CALL_TRACE (high)

[   13.017248][  T249] Call trace:

Context

[   12.993046][  T249] x8 : ffff8000851fb518 x7 : 0000000000000000 x6 : 0000000000000001
[   13.001115][  T249] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   13.009179][  T249] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   13.017248][  T249] Call trace:
[   13.020503][  T249]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   13.027409][  T249]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   13.033253][  T249]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium)

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2

Context

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium)

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sda2
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   33.011497][  T485] EXT4-fs (sda2): orphan cleanup on readonly fs
[   33.018173][  T485] EXT4-fs (sda2): mounted filesystem 2afe7eee-2d67-4173-9b85-5b1918477db3 ro with ordered data mode. Quota mode: none.
done.

Target: shikra-iqs-evk

• ⚠️ No baseline available — showing all boot issues found in PR run
• New issues: 9 (0 critical, 0 high, 9 medium, 0 low)

🟡 ERROR (medium)

[    7.620572][  T156] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22

Context

[    7.606030][   T46] arm-smmu 59a0000.iommu: 	(IDR0.CTTW overridden by FW configuration)
[    7.610362][   T58] qcom-pcie 45e8000.pcie: host bridge /soc@0/pcie@45e8000 ranges:
[    7.614523][   T46] arm-smmu 59a0000.iommu: 	stream matching with 7 register groups
[    7.620572][  T156] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    7.622563][   T58] qcom-pcie 45e8000.pcie:       IO 0x0060200000..0x00602fffff -> 0x0000000000
[    7.630472][   T46] arm-smmu 59a0000.iommu: 	5 context banks (0 stage-2 only)
[    7.639666][   T58] qcom-pcie 45e8000.pcie:      MEM 0x0060300000..0x0063ffffff -> 0x0060300000

🟡 ERROR (medium)

[    7.672859][  T156] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22

Context

[    7.639666][   T58] qcom-pcie 45e8000.pcie:      MEM 0x0060300000..0x0063ffffff -> 0x0060300000
[    7.648959][   T46] arm-smmu 59a0000.iommu: 	Supported page sizes: 0x61311000
[    7.672833][   T46] arm-smmu 59a0000.iommu: 	Stage-1: 48-bit VA -> 36-bit IPA
[    7.672859][  T156] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.680193][  T156] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.686063][  T156] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.690095][   T46] arm-smmu 59a0000.iommu: 	preserved 0 boot mappings

🟡 ERROR (medium)

[    7.680193][  T156] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22

Context

[    7.648959][   T46] arm-smmu 59a0000.iommu: 	Supported page sizes: 0x61311000
[    7.672833][   T46] arm-smmu 59a0000.iommu: 	Stage-1: 48-bit VA -> 36-bit IPA
[    7.672859][  T156] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.680193][  T156] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.686063][  T156] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.690095][   T46] arm-smmu 59a0000.iommu: 	preserved 0 boot mappings
[    7.718543][   T46] platform 5900000.gpu: Adding to iommu group 12

🟡 ERROR (medium)

[    7.686063][  T156] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22

Context

[    7.672833][   T46] arm-smmu 59a0000.iommu: 	Stage-1: 48-bit VA -> 36-bit IPA
[    7.672859][  T156] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.680193][  T156] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.686063][  T156] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.690095][   T46] arm-smmu 59a0000.iommu: 	preserved 0 boot mappings
[    7.718543][   T46] platform 5900000.gpu: Adding to iommu group 12
[    7.856065][  T141] mc: Linux media interface: v0.10

🟡 ERROR (medium)

[    9.961053][   T46] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17

Context

[    9.927793][  T165] Bluetooth: SCO socket layer initialized
[    9.930061][  T159] pwrseq-qcom_wcn wcn3988-pmu: supply vddch1 not found, using dummy regulator
[    9.954092][   T46] cpufreq-dt cpufreq-dt: failed register driver: -17
[    9.961053][   T46] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17
[    9.985856][  T144] remoteproc remoteproc2: lpaicp is available
[    9.994501][  T158] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   10.014544][  T163] /soc@0/display-subsystem@5e00000/display-controller@5e01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@5e00000/dsi@5e94000

🟡 ERROR (medium)

[   10.131119][    T9] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[   10.108008][  T163] /soc@0/geniqup@4ac0000/i2c@4a90000/lt9611uxd@41: Fixed dependency cycle(s) with /soc@0/display-subsystem@5e00000/dsi@5e94000
[   10.111153][  T158] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.121644][  T163] /soc@0/display-subsystem@5e00000/dsi@5e94000: Fixed dependency cycle(s) with /soc@0/geniqup@4ac0000/i2c@4a90000/lt9611uxd@41
[   10.131119][    T9] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.143203][  T163] /soc@0/display-subsystem@5e00000/dsi@5e94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@5e00000/display-controller@5e01000
[   10.145918][  T104] remoteproc remoteproc1: remote processor cdsp is now up
[   10.147127][  T151] qcom-ethqos 5d20000.ethernet: IRQ eth_wake_irq not found

🟡 ERROR (medium)

[   10.552535][   T58] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110

Context

[   10.158577][  T151] qcom-ethqos 5d20000.ethernet: Using 36/40 bits DMA host/device width
[   10.412979][   T82] Bluetooth: hci0: setting up wcn399x
[   10.512075][   T46] msm_dsi 5e94000.dsi: supply refgen not found, using dummy regulator
[   10.552535][   T58] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110
[   10.585706][   T76] remoteproc remoteproc2: remote processor lpaicp is now up
[   10.598441][  T151] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[   10.613803][  T161] irq: IRQ199: trimming hierarchy from :soc@0:interrupt-controller@f200000-1

🟡 ERROR (medium)

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p53

Context

Begin: Running /scripts/local-premount ... done.
[   22.456490][  T214] blkid (214) used greatest stack depth: 10184 bytes left
Begin: Will now check root file system ... fsck from util-linux 2.41
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p53
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors

🟡 WARNING (medium)

Warning: File system check failed but did not detect errors

Context

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p53
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[   27.739974][  T226] EXT4-fs (mmcblk0p53): orphan cleanup on readonly fs
[   27.749108][  T226] EXT4-fs (mmcblk0p53): mounted filesystem ba2ea611-e006-4021-a0ac-cfac76ce5228 ro with ordered data mode. Quota mode: none.
done.

[qcomlnxci]

Test jobs on be0fd4c

• multimedia Job 231232 on hamoa-iot-evk
• multimedia Job 231237 on lemans-evk
• multimedia Job 231226 on monaco-evk
• multimedia Job 231227 on purwa-iot-evk
• multimedia Job 231225 on qcs615-ride
• multimedia Job 231236 on qcs6490-rb3gen2
• multimedia Job 231231 on qcs8300-ride
• multimedia Job 231229 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 231238 on shikra-iqs-evk

[qcomlnxci]

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	purwa-iot-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia	shikra-iqs-evk-multimedia
Audio_Card_Registration	✅ Pass	◻️	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	❌ Fail
BT_ON_OFF	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	❌ Fail
BT_SCAN	✅ Pass	◻️	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	❌ Fail
CPUFreq_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	◻️	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	❌ Fail	⚠️ skip
Freq_Scaling	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	◻️	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	◻️	❌ Fail	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	◻️	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
shmbridge	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	✅ Pass	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass

[qcomlnxci]

Test jobs on be0fd4c

• multimedia Job 231232 on hamoa-iot-evk
• multimedia Job 231829 on lemans-evk
• multimedia Job 231226 on monaco-evk
• multimedia Job 231227 on purwa-iot-evk
• multimedia Job 231225 on qcs615-ride
• multimedia Job 231236 on qcs6490-rb3gen2
• multimedia Job 231231 on qcs8300-ride
• multimedia Job 231229 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 231830 on shikra-iqs-evk

[qcomlnxci]

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	purwa-iot-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia	shikra-iqs-evk-multimedia
Audio_Card_Registration	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	◻️
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	◻️
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	◻️
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	◻️
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	❌ Fail	◻️
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	◻️
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	◻️
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️

[qcomlnxci]

Test jobs on be0fd4c

• multimedia Job 232144 on hamoa-iot-evk
• multimedia Job 232149 on lemans-evk
• multimedia Job 232141 on monaco-evk
• multimedia Job 232143 on purwa-iot-evk
• multimedia Job 232150 on qcs615-ride
• multimedia Job 232148 on qcs6490-rb3gen2
• multimedia Job 232146 on qcs8300-ride
• multimedia Job 232145 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 232147 on shikra-iqs-evk

[qcomlnxci]

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	purwa-iot-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia	shikra-iqs-evk-multimedia
Audio_Card_Registration	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	⚠️ skip	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️	◻️	⚠️ skip	❌ Fail	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️	◻️	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	◻️	◻️	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass

[qcomlnxci]

Test jobs on be0fd4c

• multimedia Job 232151 on hamoa-iot-evk
• multimedia Job 232153 on lemans-evk
• multimedia Job 232155 on monaco-evk
• multimedia Job 232157 on purwa-iot-evk
• multimedia Job 232159 on qcs615-ride
• multimedia Job 232152 on qcs6490-rb3gen2
• multimedia Job 232156 on qcs8300-ride
• multimedia Job 232154 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 232158 on shikra-iqs-evk

[qcomlnxci]

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	purwa-iot-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia	shikra-iqs-evk-multimedia
Audio_Card_Registration	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️	⚠️ skip	⚠️ skip	◻️
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	◻️	❌ Fail	❌ Fail	◻️
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	◻️
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	◻️
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	◻️
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	◻️
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	◻️	✅ Pass	✅ Pass	◻️
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	◻️	✅ Pass	❌ Fail	◻️
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	◻️

[qcomlnxci]

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	purwa-iot-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia	shikra-iqs-evk-multimedia
Audio_Card_Registration	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	✅ Pass	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass

[qcomlnxci]

Test jobs on be0fd4c

• multimedia Job 232531 on hamoa-iot-evk
• multimedia Job 232535 on lemans-evk
• multimedia Job 232532 on monaco-evk
• multimedia Job 232536 on purwa-iot-evk
• multimedia Job 232537 on qcs615-ride
• multimedia Job 232539 on qcs6490-rb3gen2
• multimedia Job 232533 on qcs8300-ride
• multimedia Job 232538 on qcs9100-ride-r3
• multimedia Job on qrb2210-rb1
• multimedia Job 232534 on shikra-iqs-evk

[qswat-orbit-external]

Dev Completion validation failed

CR: 4570835
Change Task: kernel.qli.2.0
Error: GenAI Assisted field must be set before moving change tasks to Development Complete. Please provide GenAI information.

The change task for this CR could not be moved to Dev Complete because of the error above. Please resolve the issue in Orbit and re-run the failed Orbit check.

[qswat-orbit-external]

Dev Completion validation failed

CR: 4570835
Change Task: kernel.qli.2.0
Error: GenAI Assisted field must be set before moving change tasks to Development Complete. Please provide GenAI information.

The change task for this CR could not be moved to Dev Complete because of the error above. Please resolve the issue in Orbit and re-run the failed Orbit check.

[Dmitry Baryshkov (lumag)]

Why non of this has been sent upstream? Why do we need a global? where are the locks, protecting it from the read-modify happening at the same time? Device probing can happen in parallel.

[Dmitry Baryshkov (lumag)]

Even without async probing, the probe can happen in parallel if they are caused by other devices (e.g. if PCIe is built as a module).