QCLINUX: arm64: configs: Enable GPU virtualization by shivrawa · Pull Request #1118 · qualcomm-linux/kernel

Shivam Rawat (shivrawa) · 2026-09-15T06:59:21Z

Enable DRM VirtIO GPU configs to support GPU virtualization.

Target milestone: qli-2.1 pull-request freeze.

CRs-fixed: 4677030

Enable DRM VirtIO GPU configs to support GPU virtualization. Signed-off-by: Shivam Rawat <shivrawa@qti.qualcomm.com>

qswat-orbit-external · 2026-09-15T06:59:28Z

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 · 2026-09-15T07:22:02Z

Merge Check Failed: CR Not Eligible for Merge

CR 4677030 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4677030
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

qswat-orbit-external · 2026-09-15T07:26:59Z

Merge Check Failed: CR Not Eligible for Merge

CR 4677030 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4677030
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

Shivam Rawat (shivrawa) · 2026-09-15T07:31:44Z

Shivendra Pratap (@quicAspratap) could you please review

qcomlnxci · 2026-09-15T14:49:10Z

Test jobs on ea0b4ad

qcomlnxci · 2026-09-15T14:49:12Z

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	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_SCAN	✅ Pass	✅ 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	✅ Pass
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	❌ Fail	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ 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	✅ Pass
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	✅ Pass	❌ 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	❌ Fail	❌ Fail	❌ Fail	❌ Fail
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	⚠️ skip	✅ 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

Shivam Rawat (shivrawa) · 2026-09-15T14:52:09Z

Komal Bajaj (@Komal-Bajaj) could you please check and help why these checkers are failing. I don't see the proper error log related to the code changes. If not, can you please override them and merge

qlijarvis · 2026-09-16T11:55:13Z

LAVA Failed Case Triage Summary

PR: #1118

Job 227677 | SoC qcs615-ride

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

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

Case 1: smmu

Failed case: smmu

Root cause: Test expects video-decoder and video-encoder child devices to appear as separate entries in /sys/kernel/iommu_groups/, but the Venus driver with "non legacy binding" on qcs615-ride only registers the parent device (aa00000.video-codec) to IOMMU group 7. The child video-decoder and video-encoder devices are logical V4L2 video nodes, not separate platform devices with independent IOMMU group attachments.

Possible fix: Update the smmu test script to recognize that for Venus video codec with non-legacy binding, the parent device (aa00000.video-codec) IOMMU group attachment is sufficient and child video-decoder/encoder nodes do not require separate IOMMU group entries. Alternatively, verify this is the expected behavior for qcs615 and adjust test expectations accordingly.

Detail analysis attachment: failed_case_job227677_1_detailed.md

Case 2: BT_FW_KMD_Service

Failed case: BT_FW_KMD_Service

Root cause: WCN6855 Bluetooth firmware initialization failure on qcs615-ride — UART communication timeout (-ETIMEDOUT, errno 110) when attempting to read QCA version information during hci0 setup; the Bluetooth controller never responds to HCI commands (command 0xfc00 tx timeout), resulting in invalid BD address (00:00:00:00:00:00) and non-functional Bluetooth stack despite driver and service being loaded.

Possible fix: This is a pre-existing hardware/firmware/platform issue unrelated to the PR (which only enables GPU virtualization configs). Verify: (1) WCN6855 firmware files are present and correct version for qcs615-ride, (2) UART pinctrl/clocks/regulators for the Bluetooth UART (serial@a8c000) are correctly configured in device tree, (3) WCN6855 power sequencing (BT_EN GPIO, regulators) is correct, (4) check for known qcs615-ride board-specific Bluetooth errata or firmware compatibility issues. If this is a known board issue, document as expected failure for qcs615-ride until resolved.

Detail analysis attachment: failed_case_job227677_2_detailed.md

Case 3: BT_ON_OFF

Failed case: BT_ON_OFF

Root cause: Could not be determined confidently from available logs.

Possible fix: This is a pre-existing platform/infrastructure issue, not a PR regression. Recommended actions: (1) Verify WCN6855 Bluetooth firmware is present and correct version for qcs615-ride in the test image (/lib/firmware/qca/). (2) Check UART hardware path: verify Bluetooth UART device tree node is correct, UART controller is functional, and UART pins are properly configured. (3) Check for known WCN6855 Bluetooth errata on qcs615 platform. (4) If this is a known intermittent issue on qcs615-ride lab boards, consider marking BT tests as expected-fail for this platform until hardware/firmware is fixed. (5) Do NOT block PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 merge based on this failure — it is unrelated to the GPU virtualization config changes in the PR.

Detail analysis attachment: failed_case_job227677_3_detailed.md

Case 4: BT_SCAN — Bluetooth Hardware Communication Timeout

Failed case: BT_SCAN — Bluetooth Hardware Communication Timeout

Root cause: Bluetooth driver (btqca) cannot communicate with WCN6855 hardware on qcs615-ride; all HCI commands time out with -ETIMEDOUT (-110). UART serial communication path between AP and BT controller is non-functional. Repeated pattern: "Bluetooth: hci0: command tx timeout" → "Bluetooth: hci0: Reading QCA version information failed (-110)". This is a pre-existing board/infrastructure issue, not a PR-introduced regression (PR only enables GPU virtualization configs with no Bluetooth dependency).

Possible fix: Verify qcs615-ride board hardware: (1) Check UART GPIO/pinctrl configuration in device tree for BT UART pins; (2) Verify BT power regulators are enabled and stable; (3) Check UART clock configuration; (4) Verify BT firmware files are present and correct version; (5) Test with a known-good qcs615-ride board to isolate hardware vs software issue. If board is confirmed functional, bisect kernel to find when BT communication broke.

Detail analysis attachment: failed_case_job227677_4_detailed.md

Case 5: KVM_Driver — Platform Limitation (HYP Mode Not Available)

Failed case: KVM_Driver — Platform Limitation (HYP Mode Not Available)

Root cause: QCS615 platform does not support ARM EL2 (Hypervisor mode), causing KVM driver initialization to fail with "HYP mode not available" at boot, which prevents /dev/kvm device node creation required by the test.

Possible fix: Mark KVM_Driver, KVM_EL2_DTB, and KVM_Infra tests as "skip" or "not applicable" for qcs615-ride platform in the LAVA test suite configuration, as this SoC does not have hardware virtualization support (no EL2/HYP mode).

Detail analysis attachment: failed_case_job227677_5_detailed.md

Case 6: KVM_EL2_DTB — KVM Hypervisor Mode Unavailable

Failed case: KVM_EL2_DTB — KVM Hypervisor Mode Unavailable

Root cause: The qcs615-ride platform is running under the Gunyah hypervisor (version gunyah-cdfb73831), which occupies EL2 (hypervisor mode). KVM requires exclusive access to EL2 to function, but cannot access it when another hypervisor is already running at that privilege level. The kernel message kvm [1]: HYP mode not available at boot time confirms KVM detected this condition and disabled itself, preventing /dev/kvm device node creation.

Possible fix: This is not a PR-introduced regression (the PR only enables GPU virtualization configs). This is a platform configuration issue. To enable KVM on qcs615-ride: (1) boot without the Gunyah hypervisor, or (2) use nested virtualization if Gunyah supports it, or (3) run KVM tests on a platform that boots Linux directly at EL1 without a hypervisor. For CI: either skip KVM tests on Gunyah-enabled platforms or add a platform-specific test gate that checks for /dev/kvm availability before running KVM tests.

Detail analysis attachment: failed_case_job227677_6_detailed.md

Case 7: KVM_Infra — Platform Hardware/Firmware Limitation

Failed case: KVM_Infra — Platform Hardware/Firmware Limitation

Root cause: QCS615 Ride platform does not provide EL2 (ARM Hypervisor mode) access to the Linux kernel. During boot, KVM ARM driver detects "HYP mode not available" and aborts initialization, preventing /dev/kvm device creation. This is a platform/firmware configuration issue specific to QCS615, not a kernel bug or PR regression.

Possible fix: Add platform-specific test skip rule in LAVA CI: if [ "$DEVICE_TYPE" = "qcs615-ride" ]; then skip_test KVM_Infra; fi. QCS615 Ride does not support KVM because firmware boots Linux at EL1 (likely with Gunyah hypervisor at EL2 for automotive use cases). If KVM is required, contact Qualcomm platform team to request firmware update to expose EL2 to Linux or enable VHE.

Detail analysis attachment: failed_case_job227677_7_detailed.md

Case 8: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM is not available on qcs615-ride because the platform does not support HYP (EL2) mode - kernel message "kvm [1]: HYP mode not available" indicates the hardware/firmware does not provide virtualization extensions or EL2 is disabled.

Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The PR enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are guest-side drivers for use inside VMs, but qcs615-ride does not support hosting VMs. Either: (1) skip KVM tests on qcs615-ride in CI, or (2) run KVM tests only on platforms with HYP mode support (e.g., SA8775P, SM8550).

Detail analysis attachment: failed_case_job227677_8_detailed.md

Job 227678 | SoC qcs9100-ride

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Pre-existing platform issues unrelated to PR changes — four PMIC temp-alarm devices remain in deferred probe state (missing thermal zone dependency), regulatory.db firmware file absent from rootfs (benign cfg80211 warning), and Aquantia AQR115C Ethernet PHY probe fails due to missing firmware-name DT property (error -22 / -EINVAL). The PR only enables GPU virtualization config options and does not touch SPMI, thermal, networking, or firmware paths.

Possible fix: These are known platform configuration gaps on qcs9100-ride, not regressions. For temp-alarm: ensure qcom-spmi-temp-alarm driver and thermal zone bindings are present in DT and driver is built-in or loaded early. For regulatory.db: install wireless-regdb package or suppress the warning (non-critical). For Aquantia PHY: add firmware-name property to stmmac-0:08 DT node or provide the required firmware file. No action required on this PR.

Detail analysis attachment: failed_case_job227678_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Video codec device aa00000.video-codec exists in device tree but driver did not probe or bind to IOMMU — device is missing IOMMU group attachment, causing SMMU test validation to fail on qcs9100-ride platform.

Possible fix: Investigate why the video codec driver at aa00000.video-codec is not probing or binding to IOMMU on qcs9100-ride — check device tree iommus property, verify driver is built and loaded, check dmesg for probe failures; if this is expected platform behavior (driver not enabled for this SoC), update the SMMU test's critical master list to exclude aa00000.video-codec for qcs9100-ride.

Detail analysis attachment: failed_case_job227678_2_detailed.md

Case 3: USBHost (Test Infrastructure Issue — No External USB Devices Connected)

Failed case: USBHost (Test Infrastructure Issue — No External USB Devices Connected)

Root cause: Test expects external USB devices (keyboard, mouse, flash drive, etc.) to be physically connected to the board's USB host ports, but the qcs9100-ride board in the LAVA lab has no external devices connected. USB host controllers initialized successfully and root hubs enumerated correctly, confirming the USB subsystem is fully functional. This is a test infrastructure/hardware setup issue, not a kernel regression.

Possible fix: Connect a USB flash drive or other USB device to one of the qcs9100-ride board's USB host ports in the LAVA lab to satisfy the test's hardware expectations. Alternatively, update the USBHost test to validate USB host controller functionality without requiring external devices, or skip the test on boards where external USB devices are not available.

Detail analysis attachment: failed_case_job227678_3_detailed.md

Case 4: ** Driver Probe Failure — Ethernet PHY

Failed case: ** Driver Probe Failure — Ethernet PHY

Root cause: ** The Aquantia AQR115C PHY driver probe failed with error -EINVAL because the device tree node for the PHY (stmmac-0:08) is missing the required firmware-name property, preventing the driver from loading the PHY firmware and causing the end0 Ethernet interface to fail when attempting to attach to the PHY.

Possible fix: Add the firmware-name property to the Aquantia AQR115C PHY device tree node in the qcs9100-ride DTS file (e.g., firmware-name = "Rhe-05.06-Candidate7-AQR_Mediatek_23B_P5_ID45824_LCLVER1.cld"; or the appropriate firmware filename for this PHY). This is a pre-existing device tree issue unrelated to the PR under test (which only modifies kernel config for GPU virtualization).

Detail analysis attachment: failed_case_job227678_4_detailed.md

Case 5: KVM Driver Initialization Failure — HYP mode not available

Failed case: KVM Driver Initialization Failure — HYP mode not available

Root cause: KVM driver initialization failed because EL2 (HYP mode) is occupied by the Gunyah hypervisor running on qcs9100-ride. KVM requires exclusive access to EL2 to provide virtualization support, but Gunyah is already using EL2 as the platform's primary hypervisor. The kernel message kvm [1]: HYP mode not available at boot time (line 2516) indicates KVM detected it cannot access HYP mode, preventing /dev/kvm device node creation.

Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The PR only enables VirtIO GPU drivers (CONFIG_DRM_VIRTIO_GPU) for GPU virtualization under Gunyah, and does not affect KVM. To resolve: (1) Exclude KVM tests from qcs9100-ride CI runs, as this platform uses Gunyah hypervisor and cannot support KVM; or (2) Disable CONFIG_KVM in the kernel config for Gunyah-based platforms to prevent the driver from attempting initialization; or (3) Update the test suite to skip KVM tests when Gunyah hypervisor is detected at boot.

Detail analysis attachment: failed_case_job227678_5_detailed.md

Case 6: KVM_EL2_DTB — KVM/ARM Virtualization Not Available (Gunyah Hypervisor Conflict)

Failed case: KVM_EL2_DTB — KVM/ARM Virtualization Not Available (Gunyah Hypervisor Conflict)

Root cause: The qcs9100-ride platform boots with Gunyah hypervisor in EL2, which prevents KVM/ARM from initializing. KVM requires exclusive EL2 access, but Gunyah occupies EL2 and provides its own virtualization interface. The kernel logs show "kvm [1]: HYP mode not available" at boot, and bootloader logs confirm "Gunyah based bootup" with hypervisor version "gunyah-cdfb73831". This is a platform configuration issue, not a kernel regression introduced by the PR (which only enables DRM VirtIO GPU configs).

Possible fix: This is expected behavior on Gunyah-enabled platforms. KVM/ARM and Gunyah are mutually exclusive hypervisors. To enable KVM testing: (1) flash a non-Gunyah firmware/bootloader configuration that boots Linux directly in EL1 without a hypervisor, OR (2) exclude KVM tests from the qcs9100-ride LAVA job definition, as this platform is configured for Gunyah virtualization, not KVM/ARM. The PR changes (GPU virtualization configs) are unrelated to this failure.

Detail analysis attachment: failed_case_job227678_6_detailed.md

Case 7: KVM_Infra

Failed case: KVM_Infra

Root cause: Could not be determined confidently from available logs.

Possible fix: Suppress KVM_Infra, KVM_Driver, and KVM_EL2_DTB test cases for qcs9100-ride and all other Qualcomm platforms configured with Gunyah hypervisor. KVM host functionality is architecturally incompatible with platforms running under a hypervisor. If KVM guest support is needed, use nested virtualization (if supported by Gunyah) or run KVM tests only on bare-metal configurations without Gunyah.

Detail analysis attachment: failed_case_job227678_7_detailed.md

Case 8: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM infrastructure test fails because /dev/kvm device node is not created; kernel reports "kvm [1]: HYP mode not available" at boot (line 3127 of log), indicating the qcs9100-ride platform does not support ARM virtualization extensions (EL2 hypervisor mode) in its current hardware/firmware configuration.

Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression (PR only enables GPU virtualization config options). Mark KVM tests as expected-fail or skip for qcs9100-ride platform in the LAVA test definition, or enable HYP mode support in the platform firmware/bootloader if virtualization is required.

Detail analysis attachment: failed_case_job227678_8_detailed.md

Job 227679 | SoC hamoa-evk

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

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

Case 1: Probe_Failure_Check — Pre-existing Platform Issues

Failed case: Probe_Failure_Check — Pre-existing Platform Issues

Root cause: Three unrelated driver probe failures detected by zero-tolerance test: (1) qcom_qseecom_uefisecapp failed with -EBUSY (TrustZone resource conflict), (2) qcom-spmi-lpg failed with -EINVAL (DT multi-LED "reg" property validation error), (3) regulatory.db firmware load failed with -ENOENT (missing file, benign with built-in fallback). All three are pre-existing hamoa-evk platform/configuration issues completely unrelated to the PR's GPU virtualization config changes (CONFIG_DRM_VIRTIO_GPU).

Possible fix: Suppress these three known benign failures in the Probe_Failure_Check test for hamoa-evk by adding suppression patterns: qcom_qseecom_uefisecapp.*probe.*failed with error -16, qcom-spmi-lpg.*probe.*failed with error -22, and regulatory: Direct firmware load for regulatory.db failed with error -2. Long-term: (1) investigate TZ resource allocation for QSEE UEFI secure app, (2) fix DT "reg" property in hamoa-evk PMIC LED multi-led node per leds-qcom-lpg.yaml binding, (3) add wireless-regdb package to rootfs or accept built-in fallback.

Detail analysis attachment: failed_case_job227679_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Six USB PHY devices (a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb) and one Video Codec device (aa00000.video-codec) on hamoa-evk lack IOMMU group attachments because their device tree nodes do not include iommus properties, causing the SMMU validation test to fail its critical master protection checks.

Possible fix: Add iommus properties to the device tree nodes for the six USB PHY devices and the Video Codec device in arch/arm64/boot/dts/qcom/x1e80100.dtsi, referencing the appropriate SMMU instance and stream IDs, then verify the devices appear in /sys/kernel/iommu_groups after reboot.

Detail analysis attachment: failed_case_job227679_2_detailed.md

Case 3: KVM_Driver — /dev/kvm not available (driver initialization failure)

Failed case: KVM_Driver — /dev/kvm not available (driver initialization failure)

Root cause: KVM driver initialization failed because the Hamoa IoT EVK (x7181) platform does not support EL2/HYP mode, which is a prerequisite for KVM. Boot log shows kvm [1]: HYP mode not available at kernel initialization. This is a pre-existing platform limitation, not a PR-introduced regression.

Possible fix: This is a pre-existing platform limitation, not a test failure caused by the PR. The PR only adds guest-side VirtIO GPU drivers (CONFIG_DRM_VIRTIO_GPU) and does not modify KVM host functionality. Recommended actions: (1) Mark KVM tests as "expected to fail" or "skip" for Hamoa IoT EVK platform in the LAVA job definition, as this platform does not support virtualization. (2) If KVM support is required, use a different platform that supports EL2/HYP mode (e.g., RB5, RB3Gen2, or other platforms with virtualization extensions enabled in firmware/bootloader).

Detail analysis attachment: failed_case_job227679_3_detailed.md

Case 4: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM driver initialization failed because Linux is running as a guest VM under the Gunyah hypervisor on Hamoa EVK, executing at EL1 without access to EL2 (HYP mode). KVM requires EL2 access to provide virtualization services, which is unavailable in this nested virtualization configuration where Gunyah owns EL2.

Possible fix: This is a platform configuration limitation, not a kernel bug. To enable KVM on Hamoa: (1) boot Linux directly at EL2 without Gunyah hypervisor, OR (2) if nested virtualization is required, configure Gunyah to expose virtual EL2 (VHE) to the guest Linux kernel. The PR change (enabling DRM_VIRTIO_GPU configs) is unrelated and does not cause this failure.

Detail analysis attachment: failed_case_job227679_4_detailed.md

Case 5: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM cannot initialize because HYP (EL2) mode is not available to Linux — the Gunyah hypervisor is running at EL2 and has not configured nested virtualization support for the Primary VM (PVM), preventing KVM from accessing EL2 resources required to create /dev/kvm.

Possible fix: This is a platform/hypervisor configuration issue, not a kernel regression. To enable KVM on hamoa-evk: (1) verify the Gunyah hypervisor firmware version supports nested virtualization for the PVM, (2) ensure the hypervisor configuration grants EL2 access to the PVM, or (3) if nested virtualization is not supported on this platform, mark KVM tests as expected-fail for hamoa-evk in the CI test matrix.

Detail analysis attachment: failed_case_job227679_5_detailed.md

Case 6: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM initialization failed because the Hamoa IoT EVK platform is running under the Gunyah hypervisor, which does not expose EL2 (HYP mode) to the guest OS. The kernel message "kvm [1]: HYP mode not available" indicates that CONFIG_KVM is enabled but the CPU is not running at EL2, preventing /dev/kvm device creation.

Possible fix: This is not a PR-introduced regression (PR only adds GPU virtualization configs). The test failure is expected on this platform. Either: (1) skip KVM tests on Gunyah-based platforms in the CI test suite, or (2) enable nested virtualization support in the Gunyah hypervisor configuration for this board if the hardware supports it.

Detail analysis attachment: failed_case_job227679_6_detailed.md

Job 227680 | SoC purwa-evk

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

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

Case 1: ** Probe_Failure_Check

Failed case: ** Probe_Failure_Check

Root cause: ** Five driver probe failures detected during boot on purwa-evk: qcom_qseecom_uefisecapp (-EBUSY, device busy), qcom-spmi-lpg (-EINVAL, invalid DT configuration), two qcom-pcie instances (-ENODATA, missing PCIe endpoint/link training failure), and regulatory.db firmware (-ENOENT, missing firmware file in rootfs).

Possible fix: These are pre-existing platform/configuration issues unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The PR does not modify any drivers, device trees, or firmware paths. Mark as NOT PR-INTRODUCED. To resolve: (1) qcom_qseecom_uefisecapp: verify TrustZone app availability; (2) qcom-spmi-lpg: fix PWM DT node configuration at c42d000.spmi:pmic@1:pwm; (3) qcom-pcie: verify PCIe endpoint presence and DT regulators for 1bd0000.pcie and 1bf8000.pci; (4) regulatory.db: add wireless-regdb package to rootfs or disable cfg80211 built-in regulatory DB requirement.

Detail analysis attachment: failed_case_job227680_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Test validation failure — six critical devices (five USB controllers at a0f8800, a2f8800, a4f8800, a6f8800, a8f8800 and one Video codec at aa00000) are missing IOMMU group attachments on purwa-evk (X1E80100 SoC), failing the test's strict requirement that all critical masters must be protected by SMMU.

Possible fix: This is a pre-existing platform configuration issue unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options). The missing IOMMU attachments indicate incomplete device tree iommus properties for these USB and Video devices on the purwa-evk platform. Add iommus properties to the device tree nodes for USB controllers a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb and video-codec aa00000.video-codec in arch/arm64/boot/dts/qcom/x1e80100.dtsi.

Detail analysis attachment: failed_case_job227680_2_detailed.md

Case 3: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM driver initialization failed because the platform is running under the Gunyah hypervisor (detected at boot: "Hypervisor cold boot, version: gunyah-mobile-ad1fb25c6"), which prevents KVM from accessing EL2 (HYP mode). The kernel message "kvm [1]: HYP mode not available" at boot time indicates the CPU is not in a state that allows KVM to initialize, as the Gunyah hypervisor is already occupying EL2. This is a platform configuration issue specific to purwa-evk running with Gunyah, not a kernel regression introduced by the PR (which only enables GPU virtualization configs).

Possible fix: This is not a PR-introduced regression. The KVM_Driver test is expected to fail on purwa-evk when running under the Gunyah hypervisor, as KVM and Gunyah cannot coexist (both require EL2). Either: (1) exclude KVM tests from the purwa-evk test suite when Gunyah is enabled, or (2) boot purwa-evk without the Gunyah hypervisor if KVM functionality is required for testing. The PR changes (enabling DRM_VIRTIO_GPU configs) are unrelated to this failure.

Detail analysis attachment: failed_case_job227680_3_detailed.md

Case 4: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM cannot initialize on purwa-evk because the platform is running under the Gunyah hypervisor, which occupies EL2 and prevents nested virtualization. The kernel message "kvm [1]: HYP mode not available" confirms KVM detected it cannot access EL2 hypervisor mode, resulting in /dev/kvm device node not being created.

Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression (the PR only enables GPU virtualization configs). To enable KVM on this platform, either: (1) configure Gunyah to support nested virtualization and expose EL2 to the guest kernel, or (2) boot without Gunyah hypervisor if KVM testing is required. For CI purposes, suppress KVM tests on Gunyah-based platforms or run them only on bare-metal configurations.

Detail analysis attachment: failed_case_job227680_4_detailed.md

Case 5: KVM Infrastructure Limitation — Gunyah Hypervisor Platform

Failed case: KVM Infrastructure Limitation — Gunyah Hypervisor Platform

Root cause: KVM cannot initialize on purwa-evk because the Gunyah hypervisor is already running at EL2 (Hypervisor Exception Level). KVM requires exclusive access to EL2 to function, but Gunyah (a Type-1 hypervisor) occupies this privilege level. The kernel message kvm [1]: HYP mode not available is the expected and correct behavior on Gunyah-based platforms.

Possible fix: This is not a bug — it is a platform architectural limitation. The KVM_Infra, KVM_Driver, and KVM_EL2_DTB tests should be skipped or marked as "not applicable" for purwa-evk and other Gunyah-based platforms. Update the LAVA test job definition to exclude KVM tests for device type purwa-evk, or add platform detection logic to the test scripts to skip KVM tests when Gunyah hypervisor is detected (check for /sys/firmware/devicetree/base/reserved-memory/gunyah-hyp@* or hypervisor boot messages).

Detail analysis attachment: failed_case_job227680_5_detailed.md

Case 6: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM HYP mode is not available on the purwa-evk platform — kernel message "kvm [1]: HYP mode not available" indicates the hardware/firmware does not support EL2 virtualization, preventing /dev/kvm device creation.

Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The PR (GPU virtualization config changes) is unrelated to KVM HYP mode availability. If KVM support is required on purwa-evk, verify that: (1) the bootloader/firmware enables EL2, (2) the device tree does not disable virtualization, and (3) the SoC/board physically supports ARM virtualization extensions. Otherwise, skip KVM tests on this platform.

Detail analysis attachment: failed_case_job227680_6_detailed.md

Job 227681 | SoC monaco-evk

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Could not be determined confidently from available logs.

Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs /lib/firmware directory in the build recipe. Verify the firmware package (e.g., linux-firmware-ath11k or vendor-specific firmware package) is included in the Yocto image recipe for Monaco EVK builds.

Detail analysis attachment: failed_case_job227681_1_detailed.md

Case 2: WiFi Driver Probe Failure — ath11k_pci probe timeout

Failed case: WiFi Driver Probe Failure — ath11k_pci probe timeout

Root cause: ath11k_pci driver probe failed with -ETIMEDOUT (-110) on Monaco EVK because the required WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs (-ENOENT). MHI bus power-up timed out waiting for firmware load, causing the WCN6855 WiFi chip initialization to fail. This is a pre-existing platform/image issue unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization kernel configs).

Possible fix: Add the missing ath11k WCN6855 firmware files to the Monaco EVK rootfs image. The required firmware path is ath11k/WCN6855/hw2.1/nfa765/amss.bin and associated board files. Verify firmware package installation in the Yocto/build recipe for Monaco EVK. This is not a kernel regression introduced by the PR.

Detail analysis attachment: failed_case_job227681_2_detailed.md

Case 3: ** WiFi Driver Probe Failure — ath11k_pci firmware missing

Failed case: ** WiFi Driver Probe Failure — ath11k_pci firmware missing

Root cause: ** WiFi driver probe failed with -110 (ETIMEDOUT) because the required firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs (-ENOENT). MHI cannot power up the WCN6855 WiFi device without firmware, causing probe to time out. This is a pre-existing firmware packaging issue on monaco-evk, not a regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only modifies GPU virtualization configs).

Possible fix: Add the missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/). Verify the firmware package for WCN6855 hw2.1 includes the nfa765 variant for monaco-evk. If the firmware path is incorrect, update the device tree or driver board file to reference the correct firmware variant path.

Detail analysis attachment: failed_case_job227681_3_detailed.md

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

Failed case: 0_qcom-next-ci-premerge-tests

Root cause: LAVA test infrastructure issue — test runner completed and exited normally (<LAVA_TEST_RUNNER EXIT> signal sent), but LAVA dispatcher marked the test definition as failed with "Marking unfinished test run as failed", indicating the dispatcher expected additional output or a different completion signal that was not received.

Possible fix: Re-trigger the CI job. If the issue recurs, review the LAVA job definition to ensure the test runner completion signal matches what the dispatcher expects, or increase the test action timeout if the runner is being terminated prematurely.

Detail analysis attachment: failed_case_job227681_4_detailed.md

Job 227682 | SoC qcs8300-ride

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

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

Case 1: Probe_Failure_Check — Pre-existing Driver/Firmware Issues

Failed case: Probe_Failure_Check — Pre-existing Driver/Firmware Issues

Root cause: The Probe_Failure_Check test detected two pre-existing kernel probe/firmware errors: (1) Aquantia AQR115C Ethernet PHY driver probe failure with -EINVAL (-22) due to missing firmware-name DT property, and (2) cfg80211 regulatory.db firmware load failure with -ENOENT (-2) which is a known benign issue on systems without the regulatory database file. Neither failure is related to the PR changes (GPU virtualization config enablement) and both are platform-specific issues on qcs8300-ride.

Possible fix: These are pre-existing platform issues unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118. (1) For the Aquantia PHY probe failure: add the missing firmware-name property to the Ethernet PHY device tree node in qcs8300-ride DTS, or update the PHY driver to handle missing firmware-name gracefully. (2) For the regulatory.db firmware failure: this is benign and can be suppressed in the test — cfg80211 falls back to built-in regulatory data when the file is missing. The PR should be approved as the failures are not regressions introduced by the GPU virtualization config changes.

Detail analysis attachment: failed_case_job227682_1_detailed.md

Case 2: USBHost — Test Infrastructure Issue (No Physical USB Device Connected)

Failed case: USBHost — Test Infrastructure Issue (No Physical USB Device Connected)

Root cause: The USBHost test expects a functional USB device to be connected to the qcs8300-ride board's USB host port, but only the USB root hub is enumerated (Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub). The USB host controller (xhci-hcd) initialized successfully and detected 1 port, but no physical USB device is plugged into that port. This is a test setup issue, not a kernel regression. The PR changes (CONFIG_DRM_VIRTIO_GPU GPU virtualization configs) are unrelated to USB functionality.

Possible fix: Connect a functional USB device (e.g., USB flash drive, USB keyboard, or USB hub with devices) to the USB host port on the qcs8300-ride board before running the USBHost test. If the board's USB host port is not accessible or not functional in the LAVA lab setup, mark this test as "skip" or "not applicable" for this board configuration, or update the test to verify only that the USB host controller driver loads successfully without requiring a physical device.

Detail analysis attachment: failed_case_job227682_2_detailed.md

Case 3: Ethernet_Basic_Validation

Failed case: Ethernet_Basic_Validation

Root cause: Could not be determined confidently from available logs.

Possible fix: Add the firmware-name property to the Aquantia AQR115C PHY device tree node in the qcs8300-ride DTS file (likely arch/arm64/boot/dts/qcom/qcs8300-ride.dts or overlay). The property should specify the correct firmware file path for the AQR115C PHY chip (e.g., firmware-name = "Rhe-05.06-Candidate9-AQR_Mediatek_23B_P5_ID45824_LCLVER1.cld"; or the appropriate firmware file available in /lib/firmware/). Verify the firmware file exists in the rootfs firmware directory.

Detail analysis attachment: failed_case_job227682_3_detailed.md

Case 4: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM driver failed to initialize on qcs8300-ride (Monaco) platform despite CONFIG_KVM=y — /dev/kvm device node was not created because the KVM subsystem did not probe successfully. No KVM initialization messages appear in the boot log, indicating the ARM KVM driver silently failed to initialize, most likely because EL2 (hypervisor mode) is not available or is disabled by the platform firmware/bootloader on this SoC.

Possible fix: Verify that the qcs8300-ride platform firmware/bootloader enables EL2 (ARM virtualization extensions). Check bootloader logs for EL2 availability and ensure the platform supports KVM. If EL2 is disabled in firmware, update the bootloader configuration to enable virtualization support. If the platform does not support KVM in hardware, mark the KVM tests as SKIP for this SoC in the CI test matrix.

Detail analysis attachment: failed_case_job227682_4_detailed.md

Case 5: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM driver failed to initialize on qcs8300-ride platform because the hardware does not support virtualization extensions (VHE/nVHE) or the bootloader did not boot the kernel at EL2. CONFIG_KVM is enabled but the KVM subsystem silently skipped initialization when it detected the platform lacks the required hypervisor mode support, resulting in no /dev/kvm device node creation.

Possible fix: This is a pre-existing platform limitation, not a regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only adds GPU virtualization configs). Mark the KVM test suite as "not applicable" for qcs8300-ride in the LAVA test configuration, or update the platform firmware/bootloader to enable EL2/hypervisor mode if the hardware supports it. To verify hardware capability, check CPU feature registers (ID_AA64PFR0_EL1) for EL2 support.

Detail analysis attachment: failed_case_job227682_5_detailed.md

Case 6: KVM_Infra — /dev/kvm device node unavailable

Failed case: KVM_Infra — /dev/kvm device node unavailable

Root cause: QCS8300 (Monaco) platform runs as a guest under Gunyah hypervisor (evidenced by gunyah-md-region reservation and arch_timer running in virt mode); KVM requires EL2 hypervisor mode but the kernel is running at EL1 as a guest VM, preventing KVM initialization and /dev/kvm creation despite CONFIG_KVM being enabled.

Possible fix: This is a platform architecture limitation, not a PR-introduced regression. KVM tests should be skipped on QCS8300 targets running under Gunyah hypervisor. Add platform detection to the LAVA test definition to skip KVM tests when running as a hypervisor guest (check for /sys/hypervisor or virt timer mode).

Detail analysis attachment: failed_case_job227682_6_detailed.md

Case 7: LAVA Test Definition Meta-Failure (0_qcom-next-ci-premerge-tests)

Failed case: LAVA Test Definition Meta-Failure (0_qcom-next-ci-premerge-tests)

Root cause: LAVA marked the test definition as failed because 6 individual tests within it failed (KVM_Driver, KVM_EL2_DTB, KVM_Infra, Probe_Failure_Check, USBHost, Ethernet_Basic_Validation); this is standard LAVA behavior, not a kernel crash or infrastructure failure.

Possible fix: This is not a failure that requires a "fix" - it is LAVA's expected behavior. To resolve the overall test definition failure, investigate and fix the 6 individual test failures. The KVM failures are likely due to missing KVM device node creation (CONFIG_KVM enabled but /dev/kvm not present), which may require hypervisor/firmware configuration or additional kernel config. The other failures (Probe_Failure_Check, USBHost, Ethernet) are unrelated to the PR patch and appear to be pre-existing platform issues on qcs8300-ride.

Detail analysis attachment: failed_case_job227682_7_detailed.md

Job 227683 | SoC qcs6490-rb3gen2

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Could not be determined confidently from available logs.

Possible fix: Add the missing firmware file renesas_usb_fw.mem (from the linux-firmware package) to /lib/firmware/ in the LAVA root filesystem image. The firmware is available in the upstream linux-firmware repository at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/renesas_usb_fw.mem. After adding the firmware, rebuild the root filesystem image and re-trigger the LAVA job to verify the xhci-pci-renesas driver probes successfully.

Detail analysis attachment: failed_case_job227683_1_detailed.md

Case 2: USBHost

Failed case: USBHost

Root cause: USB host controller drivers (dwc3-qcom/xhci-hcd) did not probe the on-SoC USB controllers (8c00000.usb, a600000.usb) despite device tree nodes being present and registered. No USB host controller initialization occurred, resulting in zero enumerated USB devices. This is a pre-existing kernel configuration or driver loading issue unrelated to the PR (which only enables GPU virtualization configs).

Possible fix: Verify USB host controller driver configs (CONFIG_USB_DWC3, CONFIG_USB_DWC3_QCOM, CONFIG_USB_XHCI_HCD, CONFIG_USB_XHCI_PLATFORM) are enabled (=y or =m). If built as modules, ensure they are loaded at boot. Check for deferred probe issues by examining /sys/kernel/debug/devices_deferred on the target. This failure is not caused by the PR changes (GPU virtualization) and represents a baseline kernel configuration gap.

Detail analysis attachment: failed_case_job227683_2_detailed.md

Case 3: KVM_Driver — /dev/kvm not available

Failed case: KVM_Driver — /dev/kvm not available

Root cause: KVM initialization failed with "HYP mode not available" because the qcs6490-rb3gen2 platform is running under the Gunyah hypervisor at EL2, preventing the Linux kernel from accessing EL2 to initialize KVM; this is a platform configuration constraint, not a kernel regression.

Possible fix: This is expected behavior on platforms running under a hypervisor. If KVM functionality is required, boot the kernel without the Gunyah hypervisor (bare-metal EL2 access), or use nested virtualization if supported by the hypervisor. The PR (GPU virtualization config changes) did not cause this failure.

Detail analysis attachment: failed_case_job227683_3_detailed.md

Case 4: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: Could not be determined confidently from available logs.

Possible fix: This is expected platform behavior, not a bug. To enable KVM testing on this platform, either: (1) disable Gunyah hypervisor in the firmware/bootloader configuration to allow KVM to own EL2, or (2) exclude KVM tests from the CI test suite for platforms running Gunyah hypervisor, or (3) run KVM tests on a different platform variant without Gunyah enabled.

Detail analysis attachment: failed_case_job227683_4_detailed.md

Case 5: KVM Infrastructure Unavailable — Gunyah Hypervisor Conflict

Failed case: KVM Infrastructure Unavailable — Gunyah Hypervisor Conflict

Root cause: KVM cannot initialize because the Gunyah hypervisor (gunyah-cdfb73831) is already running at EL2 on qcs6490-rb3gen2, preventing KVM from obtaining required HYP mode access; kernel logs "kvm [1]: HYP mode not available" and /dev/kvm is never created.

Possible fix: This is a platform configuration issue, not a PR regression (PR only adds GPU virtualization configs). To enable KVM testing: either (1) boot without Gunyah hypervisor to allow KVM native EL2 access, or (2) configure nested virtualization if Gunyah supports it, or (3) exclude KVM tests from qcs6490-rb3gen2 CI runs since this platform is configured for Gunyah-based virtualization, not KVM.

Detail analysis attachment: failed_case_job227683_5_detailed.md

Case 6: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM host support unavailable on qcs6490-rb3gen2 platform — kernel message "kvm [1]: HYP mode not available" indicates the SoC/firmware does not provide EL2 (hypervisor) mode access required for KVM operation, despite CONFIG_KVM being enabled in the kernel configuration.

Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The qcs6490-rb3gen2 board does not support KVM host mode because the bootloader/firmware does not enable EL2 access. Mark KVM tests as expected-fail for this platform, or enable EL2 in the board's bootloader/firmware configuration if virtualization host support is required.

Detail analysis attachment: failed_case_job227683_6_detailed.md

Job 227684 | SoC shikra-iqs-evk

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

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

Case 1: GIC Test Script Bug — False Failure

Failed case: GIC Test Script Bug — False Failure

Root cause: The GIC test script at line 75 has a parsing bug that incorrectly attempts to extract interrupt counts for CPUs 4-7 when the shikra-iqs-evk platform has only 4 CPUs (0-3). The script parses /proc/interrupts output but treats the "GICv3", "Level", and "arch_timer" descriptor strings as additional CPU columns, causing bash integer comparison errors and false test failures for non-existent CPUs 4-7.

Possible fix: Update the GIC test script to dynamically detect the actual CPU count from /sys/devices/system/cpu/online or /proc/cpuinfo before parsing /proc/interrupts, and only validate interrupt counts for CPUs that actually exist on the platform. The script should parse the /proc/interrupts format correctly by identifying the CPU column count from the header line rather than assuming a fixed 8-CPU layout.

Detail analysis attachment: failed_case_job227684_1_detailed.md

Case 2: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Pre-existing platform-specific probe failures on shikra-iqs-evk unrelated to PR changes (GPU virtualization config). Failures include: coresight-etm4x (-22/EINVAL, likely DT/hardware mismatch), cpufreq-dt (-17/EEXIST, benign duplicate registration), regulatory.db (-2/ENOENT, missing firmware file), and lt9611c display bridge (-5/EIO, hardware communication failure).

Possible fix: These are known baseline issues on shikra-iqs-evk. The Probe_Failure_Check test should be updated to exclude known-benign failures (cpufreq-dt EEXIST, regulatory.db missing firmware) and platform-specific hardware issues (coresight ETM on shikra, lt9611c bridge). PR1118 is not the root cause and should not be blocked by this test failure.

Detail analysis attachment: failed_case_job227684_2_detailed.md

Case 3: ** USBHost

Failed case: ** USBHost

Root cause: ** Test infrastructure issue — the USBHost test failed because no USB device was physically connected to the shikra-iqs-evk board's USB host port during the test run. The USB subsystem initialized correctly (usbcore drivers loaded, USB controller added to IOMMU group 5), and the PR changes (GPU virtualization configs) are unrelated to USB functionality. This is not a kernel bug or regression.

Possible fix: Connect a USB device (flash drive, keyboard, or mouse) to the shikra-iqs-evk board's USB host port in the LAVA lab infrastructure. Alternatively, update the USBHost test script to SKIP (not FAIL) when no USB devices are present, if the test environment does not guarantee a USB device is connected.

Detail analysis attachment: failed_case_job227684_3_detailed.md

Case 4: BT_SCAN — Test Environment Issue (No Scannable Devices)

Failed case: BT_SCAN — Test Environment Issue (No Scannable Devices)

Root cause: BT_SCAN test failed because no Bluetooth devices were available in the LAVA lab environment to be discovered during the scan window (3 attempts × 15 seconds each). The Bluetooth stack is fully functional (hci0 adapter operational, power on/off working, bluetoothctl commands executing correctly), but the test requires at least one nearby Bluetooth device to pass. This is a test infrastructure limitation, not a kernel regression. The PR changes only GPU virtualization config (CONFIG_DRM_VIRTIO_GPU) and has no relationship to Bluetooth functionality.

Possible fix: This is not a kernel bug requiring a code fix. The test failure is environmental. To resolve: (1) Ensure at least one Bluetooth beacon/device is powered on and within range of the shikra-iqs-evk board in the LAVA lab during test execution, OR (2) Mark BT_SCAN as an optional/informational test that does not block PR merge when the test environment lacks scannable devices, OR (3) Add a test environment readiness check that skips BT_SCAN with a clear message when no reference Bluetooth device is detected in the lab.

Detail analysis attachment: failed_case_job227684_4_detailed.md

Case 5: ** KVM_Driver

Failed case: ** KVM_Driver

Root cause: ** Shikra IQS EVK platform does not provide EL2 (HYP mode) access to the kernel — KVM initialization detects "HYP mode not available" during boot and does not create /dev/kvm device node. This is a platform/firmware configuration limitation, not a kernel regression.

Possible fix: Configure the Shikra IQS EVK bootloader/firmware to boot the kernel at EL2 or preserve EL2 access for KVM. This requires updating UEFI/ABL configuration to enable virtualization support. Alternatively, if EL2 support is not available on this platform, mark KVM tests as "not applicable" for Shikra IQS EVK in the CI test matrix.

Detail analysis attachment: failed_case_job227684_5_detailed.md

Case 6: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM hypervisor mode (HYP/EL2) is not available on the Shikra IQS EVK platform, preventing KVM initialization and /dev/kvm device node creation; kernel log shows "kvm [1]: HYP mode not available" at boot time (line 3241, timestamp 3.298864s).

Possible fix: This is a platform hardware/firmware limitation, not a kernel regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only adds DRM virtio-gpu guest driver configs). The Shikra IQS EVK does not support KVM virtualization because it lacks EL2 hypervisor mode support in its boot firmware or CPU configuration. To enable KVM on this platform: (1) verify the SoC supports virtualization extensions (ARMv8.0-A Virtualization Extensions), (2) ensure the bootloader (ABL/UEFI) boots the kernel at EL2 instead of EL1, (3) check if secure firmware (TZ/ATF) allows EL2 access, or (4) use a different platform that supports KVM for virtualization testing.

Detail analysis attachment: failed_case_job227684_6_detailed.md

Case 7: KVM_Infra

Failed case: KVM_Infra

Root cause: Could not be determined confidently from available logs.

Possible fix: This is a platform/firmware limitation, not a kernel bug. The Shikra IQS EVK board firmware does not boot the kernel in EL2 (HYP mode), which is a prerequisite for KVM on ARM64. To enable KVM: (1) Update board firmware/bootloader to boot kernel at EL2, or (2) Use a hypervisor-enabled boot flow, or (3) Skip KVM tests on this platform as KVM is not supported without EL2 access. The PR patch (GPU virtualization config) is unrelated and did not cause this failure.

Detail analysis attachment: failed_case_job227684_7_detailed.md

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

Failed case: ** Kernel Crash — Synchronous External Abort in qcom_rng driver

Root cause: ** Hardware bus error (synchronous external abort) when qcom_rng driver attempted to read from RNG hardware MMIO register at address 0xffff800082c7d004 during qcom_hwrng test execution. The hardware did not respond to the read request, causing the CPU to raise a fatal exception. This is a pre-existing platform/hardware issue on the Shikra IQS EVK board, not introduced by PR1118 (which only adds GPU virtualization config options).

Possible fix: This is not a PR-introduced regression. Recommended actions: (1) Verify RNG hardware power/clock configuration in device tree for Shikra IQS EVK. (2) Check if RNG hardware block is properly powered and clocked during test execution. (3) Inspect the specific LAVA lab board (serial E2030216110A0F24) for hardware defects. (4) Add runtime PM checks in qcom_rng driver to ensure hardware is accessible before MMIO reads. (5) Re-run the test on a different Shikra board to confirm if issue is board-specific.

Detail analysis attachment: failed_case_job227684_8_detailed.md

Case 9: Kernel Crash — synchronous external abort in qcom_rng driver

Failed case: Kernel Crash — synchronous external abort in qcom_rng driver

Root cause: Hardware RNG driver (qcom_rng) triggered a synchronous external abort at PC qcom_rng_read+0xc4 when the qcom_hwrng test attempted to read entropy from /dev/hwrng. The crash occurred at kernel timestamp 1012.954826s during a dd read operation. The board subsequently panicked and rebooted into EDL/ramdump mode, causing the LAVA test shell to time out after 2400 seconds waiting for test completion. This is a pre-existing hardware/driver issue unrelated to the PR (which only enables GPU virtualization configs).

Possible fix: This is a pre-existing kernel crash in the qcom_rng driver on shikra-iqs-evk, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118. The PR changes are limited to enabling CONFIG_DRM_VIRTIO_GPU and CONFIG_DRM_VIRTIO_GPU_KMS in arch/arm64/configs/qcom.config, which do not affect the hardware RNG subsystem. The crash should be triaged separately as a baseport/hardware issue. To unblock PR validation: (1) skip or disable the qcom_hwrng test case in the LAVA job definition for shikra-iqs-evk until the RNG driver issue is resolved, or (2) re-run the job to confirm reproducibility — if the crash is intermittent hardware-related, a retry may pass.

Detail analysis attachment: failed_case_job227684_9_detailed.md

Case 10: lava-test-retry

Failed case: lava-test-retry

Root cause: Could not be determined confidently from available logs.

Possible fix: This is a pre-existing platform/firmware issue, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options). The qcom_rng driver is attempting to access hardware that is not properly initialized or powered on the shikra-iqs-evk platform. Recommended actions: (1) Verify the PRNG/TRNG hardware block is enabled in the device tree for shikra-iqs-evk; (2) Check if the qcom_rng driver probe succeeded and the device is in the correct power state before the test runs; (3) Add error handling in the qcom_rng driver to gracefully handle MMIO access failures instead of crashing; (4) If this is a known shikra-iqs-evk hardware limitation, disable the qcom_hwrng test for this platform or mark it as expected-fail in the LAVA job definition.

Detail analysis attachment: failed_case_job227684_10_detailed.md

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

Failed case: ** Kernel Crash — Synchronous External Abort in qcom_rng driver

Root cause: ** Synchronous external abort at qcom_rng_read+0xc4 during hardware register read from the Qualcomm RNG block; the CPU load instruction faulted, indicating the hardware register was inaccessible (likely due to power/clock gating, incorrect MMIO mapping, or bus path issue on shikra-iqs-evk platform).

Possible fix: Investigate qcom_rng driver runtime PM and clock/power dependencies on shikra platform; verify MMIO mapping correctness; add defensive register access checks; consider enabling CONFIG_IOMMU_DEBUGFS and CONFIG_ARM_SMMU_TESTBUS_DUMP to capture bus state at fault time; re-run test with qcom_rng driver debug enabled.

Detail analysis attachment: failed_case_job227684_11_detailed.md

Job 227685 | SoC lemans-evk

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Four SPMI PMIC temp-alarm devices (pmic@0/2/4/6:temp-alarm@a00) remain in deferred probe state, and three firmware load failures (regulatory.db, qca/wcnhpbtfw21.tlv, qca/hpbtfw21.tlv) are detected; these are pre-existing platform/firmware packaging issues unrelated to the PR (which only enables GPU virtualization configs).

Possible fix: For temp-alarm deferred probes: investigate missing thermal zone dependencies in the lemans-evk device tree or kernel config. For firmware failures: these are known benign (regulatory.db is optional; Bluetooth firmware fallback paths exist) — suppress these patterns in the Probe_Failure_Check test or package the missing firmware files in the rootfs.

Detail analysis attachment: failed_case_job227685_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Test script expects legacy Venus video codec device aa00000.video-codec to be attached to an IOMMU group, but the device did not probe because lemans-evk uses the new Iris video codec driver instead; Iris devices (iris_non_pixel.0, iris_pixel.0) are correctly attached to IOMMU groups 25 and 26.

Possible fix: Update the SMMU test script to recognize Iris video codec devices (iris_non_pixel.0, iris_pixel.0) as valid video codec IOMMU group attachments on platforms that use the Iris driver instead of legacy Venus.

Detail analysis attachment: failed_case_job227685_2_detailed.md

Case 3: smmu

Failed case: smmu

Root cause: The video codec device (aa00000.video-codec) is missing IOMMU group attachment on lemans-evk, causing the SMMU validation test to fail when checking that all critical masters are protected by IOMMU.

Possible fix: This is a pre-existing platform/DT issue unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization kernel configs). The video codec device tree node for lemans-evk needs an iommus property to attach it to an IOMMU group. Verify the device tree for lemans-evk includes proper IOMMU bindings for the video codec at address aa00000, or mark this device as non-critical in the SMMU test if IOMMU protection is not required for this platform.

Detail analysis attachment: failed_case_job227685_3_detailed.md

qcomlnxci · 2026-09-18T17:33:20Z

Test jobs on ea0b4ad

qcomlnxci · 2026-09-18T17:33:22Z

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	✅ Pass	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ 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

qlijarvis · 2026-09-18T18:03:12Z

LAVA Failed Case Triage Summary

PR: #1118

Job 231344 | SoC lemans-evk

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

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

Case 1: Probe_Failure_Check — Deferred probe not resolved for PMIC temp-alarm devices

Failed case: Probe_Failure_Check — Deferred probe not resolved for PMIC temp-alarm devices

Root cause: Four PMIC thermal alarm devices (temp-alarm@a00 on pmic@0, 2 (@2), bene (@4), 6 (@6)) remain in deferred probe state at test time, indicating a missing dependency (likely IIO ADC channel provider or thermal zone configuration) that prevents the qcom-spmi-temp-alarm driver from completing probe on lemans-evk platform.

Possible fix: This is a pre-existing platform configuration issue, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The temp-alarm driver requires IIO ADC channels for temperature monitoring; verify that the lemans-evk device tree includes the required qcom,adc-tm5 or qcom,spmi-adc-tm-hc nodes with proper channel mappings, and that the corresponding drivers are enabled in the kernel config. If this is expected behavior for lemans-evk (thermal monitoring not required), update the Probe_Failure_Check test to exclude these devices from the failure criteria for this platform.

Detail analysis attachment: failed_case_job231344_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Video codec device (aa00000.video-codec) is not attached to any IOMMU group on lemans-evk platform. The SMMU test validates that critical DMA masters are protected by IOMMU, and the video codec device failed this check. This is a platform configuration issue, not a kernel crash or SMMU fault. No SMMU errors, faults, or timeouts were observed in the kernel log.

Possible fix: This is not a PR-introduced regression (PR only adds GPU virtualization configs). The issue is either: (1) a pre-existing platform configuration gap where the video codec device tree node is missing iommus property, or (2) the video codec driver failed to probe/bind, preventing IOMMU attachment. Verify the device tree for aa00000.video-codec includes proper iommus property, and check if the video codec driver (qcom-iris or venus) is enabled in the kernel config and successfully probed during boot.

Detail analysis attachment: failed_case_job231344_2_detailed.md

Case 3: 0_qcom-next-ci-premerge-tests (LAVA Test Infrastructure Failure — Premature Test Runner Exit)

Failed case: 0_qcom-next-ci-premerge-tests (LAVA Test Infrastructure Failure — Premature Test Runner Exit)

Root cause: LAVA test runner exited with <LAVA_TEST_RUNNER EXIT> after completing qcom_hwrng test at 17:21:51, leaving 4 scheduled tests unexecuted (CPU_affinity, Freq_Scaling, irq, smmu). LAVA dispatcher marked the test definition as failed with "Marking unfinished test run as failed" because the test runner terminated before all tests completed. This is a LAVA infrastructure/test-harness issue, not a kernel regression or genuine test failure.

Possible fix: Re-trigger the LAVA job. If the issue recurs, investigate the LAVA test runner script (result_parse.sh) and test definition to determine why the runner exits prematurely after qcom_hwrng instead of continuing to execute the remaining 4 tests. The .res files for the incomplete tests exist on disk, suggesting the tests were scheduled but never invoked by the runner.

Detail analysis attachment: failed_case_job231344_3_detailed.md

Job 231345 | SoC qcs615-ride

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

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

Case 1: Probe_Failure_Check — regulatory.db firmware load failure

Failed case: Probe_Failure_Check — regulatory.db firmware load failure

Root cause: The cfg80211 wireless regulatory subsystem attempted to load the regulatory.db firmware file during boot, but the file is not present in the rootfs. This is a pre-existing infrastructure/image issue, not a PR-introduced regression. The PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU) which are completely unrelated to wireless regulatory database loading. The boot comparison report shows this same error appears across all 9 targets with no baseline available, indicating it is a systemic image packaging issue, not a kernel code defect.

Possible fix: This is not a kernel bug requiring a code fix. The regulatory.db file must be added to the rootfs image. The file is provided by the wireless-regdb package and should be installed at /lib/firmware/regulatory.db. Since this error appears on all targets and is unrelated to the PR changes (GPU virtualization), the test failure should be suppressed as a known infrastructure issue, or the CI image build process should be updated to include the wireless-regdb package.

Detail analysis attachment: failed_case_job231345_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Video codec child devices (video-decoder and video-encoder at aa00000.video-codec) are not attached to IOMMU groups. The parent device aa00000.video-codec is correctly attached to IOMMU group 7, but the test expects the child video decoder and encoder devices to also have explicit IOMMU group attachments. This is a pre-existing platform/device-tree configuration issue on qcs615-ride, not introduced by this PR.

Possible fix: This is a pre-existing issue unrelated to the PR changes (which only add GPU virtualization config options). The failure is specific to the qcs615-ride platform's video codec device tree configuration. To fix: verify the device tree for aa00000.video-codec includes proper iommus properties for the video-decoder and video-encoder child nodes, or update the SMMU test to recognize that child devices inherit IOMMU protection from their parent device when not explicitly listed.

Detail analysis attachment: failed_case_job231345_2_detailed.md

Case 3: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM cannot initialize on qcs615-ride 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" at boot time confirms EL2 is unavailable to KVM. This is a platform configuration issue, not a kernel regression.

Possible fix: This is a pre-existing platform limitation, not a PR-introduced bug. The PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) which are unrelated to KVM availability. No fix is required for the PR. If KVM functionality is needed on qcs615-ride, the platform must be configured to boot without the Gunyah hypervisor, or use nested virtualization if supported.

Detail analysis attachment: failed_case_job231345_3_detailed.md

Case 4: KVM_EL2_DTB — /dev/kvm device node unavailable

Failed case: KVM_EL2_DTB — /dev/kvm device node unavailable

Root cause: KVM initialization failed during boot because the system is running under the Gunyah hypervisor (detected at line 2393: "Hypervisor cold boot, version: gunyah-cdfb73831"), which prevents KVM from accessing EL2 (Hypervisor mode). At line 3003, the kernel reports "kvm [1]: HYP mode not available", causing KVM driver initialization to abort and /dev/kvm device node creation to be skipped. This is a platform/firmware configuration issue specific to qcs615-ride, not a kernel regression introduced by the PR (which only enables GPU virtualization config options).

Possible fix: This is a pre-existing platform limitation, not a test failure. The qcs615-ride target runs under the Gunyah hypervisor in a configuration that does not expose EL2 to Linux, making nested virtualization (KVM) unavailable. The test suite should either: (1) skip KVM tests on qcs615-ride when Gunyah hypervisor is detected, or (2) reconfigure the platform firmware to run Linux at EL2 without an intervening hypervisor if KVM support is required. No kernel code change is needed.

Detail analysis attachment: failed_case_job231345_4_detailed.md

Case 5: KVM_Infra — /dev/kvm not available (KVM disabled due to Gunyah hypervisor)

Failed case: KVM_Infra — /dev/kvm not available (KVM disabled due to Gunyah hypervisor)

Root cause: The qcs615-ride target boots under the Gunyah hypervisor (EL2), which prevents KVM from initializing. KVM requires direct access to EL2/HYP mode, but when a hypervisor is present, the Linux kernel runs at EL1 and cannot access EL2. The kernel log shows "kvm [1]: HYP mode not available" at boot, and the hypervisor boot message confirms "Hypervisor cold boot, version: gunyah-cdfb73831 perf". This is a platform configuration issue, not a kernel regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables DRM VirtIO GPU configs).

Possible fix: This is expected behavior for qcs615-ride when booting under Gunyah. To enable KVM testing on this platform, either: (1) boot without the Gunyah hypervisor (bare-metal boot) to allow KVM to access EL2 directly, or (2) exclude KVM tests from the qcs615-ride test suite when running under Gunyah, or (3) use nested virtualization if Gunyah supports it (requires Gunyah to expose virtual EL2 to the guest kernel). The PR changes are unrelated to this failure — the issue is a pre-existing platform/firmware configuration where Gunyah occupies EL2.

Detail analysis attachment: failed_case_job231345_5_detailed.md

Case 6: KVM_Infra — Test Infrastructure Limitation (Not PR-Introduced)

Failed case: KVM_Infra — Test Infrastructure Limitation (Not PR-Introduced)

Root cause: KVM is not available on qcs615-ride platform because the hardware/firmware does not support HYP (EL2) mode, as evidenced by kernel message "[3.193230][T1] kvm [1]: HYP mode not available" during boot. The test correctly detects that /dev/kvm is not present and fails as expected.

Possible fix: This is not a kernel regression or bug. The PR enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM host support. The test failure is expected on platforms without EL2/HYP support. Recommended action: Mark this test as "skip" or "not applicable" for qcs615-ride in the CI test matrix, as this platform does not support KVM host functionality.

Detail analysis attachment: failed_case_job231345_6_detailed.md

Job 231346 | SoC hamoa-evk

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Three pre-existing platform-specific probe failures detected by the Probe_Failure_Check test: (1) qcom_qseecom_uefisecapp driver probe failed with -EBUSY (-16) due to TrustZone/secure world resource unavailability on hamoa-evk; (2) qcom-spmi-lpg PWM driver probe failed with -EINVAL (-22) due to invalid multi-LED "reg" property in device tree; (3) regulatory.db firmware file missing from rootfs (expected benign failure for wireless regulatory database). None of these failures are introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options); all three appear in the boot comparison report as pre-existing issues across multiple targets with no baseline available for comparison.

Possible fix: These are not PR-introduced regressions. The Probe_Failure_Check test is correctly detecting pre-existing platform issues that should be addressed separately: (1) For qcom_qseecom_uefisecapp: verify TrustZone firmware is loaded and QSEECOM resources are available before driver probe; (2) For qcom-spmi-lpg: fix the device tree multi-LED "reg" property format in arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi to match driver expectations; (3) For regulatory.db: add the wireless-regdb package to the rootfs or suppress this expected failure in the test. PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 can proceed as the GPU virtualization config changes do not cause these probe failures.

Detail analysis attachment: failed_case_job231346_1_detailed.md

Case 2: ** smmu (IOMMU Group Attachment Validation Failure)

Failed case: ** smmu (IOMMU Group Attachment Validation Failure)

Root cause: ** The SMMU test validates that critical DMA masters (USB controllers and video codec) are attached to IOMMU groups for memory protection. Six devices defined in the device tree are not attached to IOMMU groups: five USB wrapper devices (a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb) and one video codec (aa00000.video-codec). These are wrapper/parent nodes in the device tree hierarchy — the actual functional USB controllers (a000000.usb, a200000.usb, a400000.usb, a600000.usb, a800000.usb) are correctly attached to IOMMU groups 10, 11, 12, 9, and 13 respectively. The test is flagging the wrapper nodes, which do not perform DMA themselves and therefore do not require IOMMU protection. This is a pre-existing platform configuration issue (no baseline available for hamoa-evk to confirm, but the PR only adds GPU virtualization config options unrelated to USB/video IOMMU bindings).

Possible fix: This is not a PR-introduced regression. The PR changes only enable CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m for GPU virtualization, which are unrelated to USB or video codec IOMMU bindings. The test expectation should be updated to exclude wrapper/parent device tree nodes that do not perform DMA operations, or the device tree should be corrected to add iommus properties to these wrapper nodes if they are expected to be IOMMU-protected (though this is unlikely necessary for non-DMA wrapper nodes). Recommended action: Update the SMMU test to filter out non-DMA wrapper nodes by checking if the device has child nodes that are the actual DMA masters, or mark this as a known platform-specific test limitation for hamoa-evk until the device tree is clarified.

Detail analysis attachment: failed_case_job231346_2_detailed.md

Case 3: KVM_Driver — /dev/kvm device node missing

Failed case: KVM_Driver — /dev/kvm device node missing

Root cause: KVM cannot initialize on hamoa-evk because the Gunyah hypervisor is already running at EL2, preventing KVM from entering HYP mode; kernel message "kvm [1]: HYP mode not available" at boot confirms EL2 is unavailable to KVM.

Possible fix: This is a platform limitation, not a PR-introduced regression. The PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM host functionality. KVM requires exclusive EL2 access and cannot coexist with Gunyah hypervisor on this platform. To enable KVM, either: (1) disable Gunyah hypervisor in the boot chain/firmware, or (2) use a platform configuration that doesn't load Gunyah, or (3) accept that KVM host functionality is not available on Gunyah-enabled platforms and skip this test for hamoa-evk.

Detail analysis attachment: failed_case_job231346_3_detailed.md

Case 4: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM driver initialization failed at boot with "HYP mode not available" — the hamoa-evk platform is not running at EL2 (hypervisor exception level), which is a mandatory prerequisite for KVM/ARM virtualization support. CONFIG_KVM is enabled in the kernel config, but the hardware/firmware does not provide EL2 access, preventing /dev/kvm device creation.

Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression (PR only adds GPU virtualization configs). To enable KVM on hamoa-evk: (1) verify the SoC supports virtualization extensions, (2) ensure the bootloader (ABL/UEFI) boots the kernel at EL2 instead of EL1, (3) check TrustZone/hypervisor firmware configuration to allow EL2 access to the kernel. If the platform does not support EL2, mark KVM tests as "not applicable" for this target in the CI job definition.

Detail analysis attachment: failed_case_job231346_4_detailed.md

Case 5: ** KVM_Infra — Platform KVM Support Limitation (Hardware Capability Gap)

Failed case: ** KVM_Infra — Platform KVM Support Limitation (Hardware Capability Gap)

Root cause: ** The hamoa-evk platform does not support ARM EL2 (Hypervisor) mode, which is a mandatory hardware prerequisite for KVM. The kernel correctly detects this limitation and reports "kvm [1]: HYP mode not available" at boot, preventing /dev/kvm device creation. CONFIG_KVM is enabled and the driver loads successfully, but the platform firmware/hardware does not provide the required virtualization extensions.

Possible fix: This is NOT a kernel bug or PR-introduced regression. The PR adds GPU virtualization guest support (CONFIG_DRM_VIRTIO_GPU), which is unrelated to KVM host capability. Fix options: (1) Skip KVM tests on hamoa-evk in CI (recommended — add platform exclusion to test suite), (2) Update hamoa-evk firmware to enable EL2 mode if hardware supports it, or (3) Use a different platform with EL2 support for KVM testing. The test failure is expected behavior for this platform.

Detail analysis attachment: failed_case_job231346_5_detailed.md

Case 6: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM infrastructure test failed because /dev/kvm device node is not present — the kernel detected at boot that "HYP mode not available" (line 6.389926 in boot log), meaning the hamoa-evk platform does not support ARM virtualization extensions (EL2 hypervisor mode) required for KVM operation.

Possible fix: This is not a PR-introduced regression — the PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM host support. The hamoa-evk platform lacks hardware virtualization support (no EL2/HYP mode). Either: (1) skip KVM tests on hamoa-evk in CI, or (2) run KVM tests only on platforms with virtualization support (e.g., platforms that boot with a hypervisor or have EL2 enabled in firmware).

Detail analysis attachment: failed_case_job231346_6_detailed.md

Job 231347 | SoC purwa-evk

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Five probe failures detected during boot on purwa-evk platform: (1) qcom_qseecom_uefisecapp probe failed with -EBUSY (error -16) due to secure firmware/TrustZone resource conflict; (2) two qcom-pcie controllers (1bd0000.pcie, 1bf8000.pci) failed with -ENODATA (error -61) because PHY init sequences are not available for this platform; (3) qcom-spmi-lpg PWM driver failed with -EINVAL (error -22) due to invalid "reg" property in multi-LED device tree configuration; (4) regulatory.db firmware file missing (error -2) which is a known benign failure when cfg80211 is built as module. These are pre-existing platform-specific issues unrelated to the PR's GPU virtualization config changes (CONFIG_DRM_VIRTIO_GPU=m).

Possible fix: No action required for PR merge. The probe failures are pre-existing platform issues not introduced by this PR: (1) qcom_qseecom_uefisecapp -EBUSY is a known TZ resource contention issue on X1E platforms requiring firmware coordination; (2) PCIe PHY -ENODATA failures are expected on purwa-evk where certain PCIe lanes lack init sequences in the current PHY driver; (3) qcom-spmi-lpg -EINVAL is a device tree bug in the PMIC PWM LED configuration requiring DT fix; (4) regulatory.db -ENOENT is benign (cfg80211 loads regulatory data from built-in certs). The Boot Log Baseline Comparison confirms no baseline exists for purwa-evk, so these cannot be confirmed as PR-introduced. The PR only enables GPU virtualization kernel configs and does not touch any of the failing subsystems (QSEECOM, PCIe, SPMI-LPG, or cfg80211).

Detail analysis attachment: failed_case_job231347_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Six USB PHY devices (a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb) and one video codec device (aa00000.video-codec) on purwa-evk are not attached to IOMMU groups, failing the SMMU test's critical master protection check. This is a pre-existing platform configuration issue unrelated to the PR's GPU virtualization config changes.

Possible fix: Add iommus property to the device tree nodes for the missing USB PHY (dwc3-qcom wrapper) and video codec devices in arch/arm64/boot/dts/qcom/x1e80100.dtsi, specifying the appropriate SMMU stream IDs. Verify SMMU stream ID allocations in the SoC documentation and ensure drivers request IOMMU attachment during probe.

Detail analysis attachment: failed_case_job231347_2_detailed.md

Case 3: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM cannot initialize because the purwa-evk platform is running under the Gunyah hypervisor at EL2, preventing KVM from accessing HYP mode; kernel reports "kvm [1]: HYP mode not available" at boot.

Possible fix: This is a platform configuration issue, not a PR-introduced regression. The PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM host functionality. To enable KVM on this platform, either: (1) boot without the Gunyah hypervisor to allow KVM direct EL2 access, or (2) use nested virtualization if Gunyah supports it. For CI purposes, mark KVM tests as expected-fail or skip on Gunyah-enabled platforms.

Detail analysis attachment: failed_case_job231347_3_detailed.md

Case 4: KVM_EL2_DTB — /dev/kvm not available (KVM initialization failure)

Failed case: KVM_EL2_DTB — /dev/kvm not available (KVM initialization failure)

Root cause: KVM failed to initialize because HYP (EL2 hypervisor) mode is not available on the purwa-evk platform; the kernel detected kvm [1]: HYP mode not available during boot, preventing /dev/kvm device node creation.

Possible fix: This is a platform hardware/firmware limitation, not a PR-introduced regression. The PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM host support. KVM requires EL2 (hypervisor mode) support in the CPU and firmware, which purwa-evk does not provide. Either: (1) skip KVM tests on purwa-evk in CI (recommended), or (2) enable EL2 support in the platform firmware if the hardware supports it.

Detail analysis attachment: failed_case_job231347_4_detailed.md

Case 5: KVM_Infra — KVM device node unavailable

Failed case: KVM_Infra — KVM device node unavailable

Root cause: KVM initialization failed because the platform does not support EL2 (Hypervisor mode). The kernel log shows kvm [1]: HYP mode not available at boot time, which means the CPU is not running at EL2 or EL2 is not accessible. This is a platform/hardware limitation, not a kernel bug. The purwa-evk target does not have EL2 enabled or accessible in its firmware/bootloader configuration.

Possible fix: This is not a PR-introduced regression. The PR only enables DRM VirtIO GPU configs (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m), which are unrelated to KVM host functionality. The KVM_Infra test should be skipped on platforms that do not support EL2/HYP mode, or the platform firmware should be updated to enable EL2 if virtualization support is required. To skip the test, add a platform capability check in the LAVA job definition or test script to detect HYP mode availability before running KVM tests.

Detail analysis attachment: failed_case_job231347_5_detailed.md

Case 6: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM hypervisor mode (EL2) is not available on the purwa-evk platform — kernel boot log shows "kvm [1]: HYP mode not available" at boot time, preventing /dev/kvm device node creation despite CONFIG_KVM being enabled.

Possible fix: This is a platform limitation, not a PR-introduced regression. The purwa-evk board does not support EL2 hypervisor mode (likely booting at EL1 or running under a hypervisor that does not expose nested virtualization). The KVM_Infra test should be skipped on this platform, or the test framework should treat "HYP mode not available" as an expected skip condition rather than a failure. No kernel code change is required — this is a test infrastructure configuration issue.

Detail analysis attachment: failed_case_job231347_6_detailed.md

Job 231348 | SoC qcs6490-rb3gen2

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: The cfg80211 wireless regulatory subsystem attempted to load the regulatory.db firmware file during boot but the file is not present in the root filesystem. The error "Direct firmware load for regulatory.db failed with error -2" indicates -ENOENT (file not found). This is a pre-existing infrastructure/rootfs packaging issue, not a kernel regression introduced by this PR.

Possible fix: This is a false positive test failure. The regulatory.db file is an optional firmware file for WiFi regulatory domain enforcement. Its absence does not prevent WiFi functionality — the kernel falls back to built-in regulatory rules. The Probe_Failure_Check test should be updated to exclude regulatory.db firmware load failures from its failure criteria, or the rootfs should be updated to include the wireless-regdb package that provides this file. No kernel code changes are required.

Detail analysis attachment: failed_case_job231348_1_detailed.md

Case 2: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM hypervisor mode (EL2) is not available on qcs6490-rb3gen2 platform — kernel boot log shows "kvm [1]: HYP mode not available" at initialization, preventing /dev/kvm device node creation.

Possible fix: This is a platform hardware/firmware limitation, not a kernel bug. The qcs6490-rb3gen2 board does not support KVM virtualization because EL2 (hypervisor exception level) is not available. To resolve: (1) skip KVM tests on this platform in CI configuration, or (2) use a different platform that supports EL2/KVM (e.g., SA8775P, X1E80100), or (3) verify bootloader/TrustZone firmware configuration allows EL2 access (unlikely to be configurable on this SoC).

Detail analysis attachment: failed_case_job231348_2_detailed.md

Case 3: KVM_EL2_DTB — /dev/kvm unavailable (HYP mode not available)

Failed case: KVM_EL2_DTB — /dev/kvm unavailable (HYP mode not available)

Root cause: The qcs6490-rb3gen2 platform boots with Gunyah hypervisor already running at EL2, preventing KVM from initializing because KVM requires exclusive EL2 access; kernel logs show "kvm [1]: HYP mode not available" during boot, which causes /dev/kvm device node creation to be skipped.

Possible fix: This is a pre-existing platform configuration issue, not a PR-introduced regression (PR only adds GPU virtualization configs). To enable KVM on this platform: (1) boot without Gunyah hypervisor (requires bootloader/firmware reconfiguration to not load Gunyah), OR (2) use nested virtualization if Gunyah supports it (requires Gunyah firmware update), OR (3) accept that KVM tests are not applicable on Gunyah-enabled platforms and exclude them from the test suite for this board configuration.

Detail analysis attachment: failed_case_job231348_3_detailed.md

Case 4: KVM_Infra — KVM device node unavailable (pre-existing platform limitation)

Failed case: KVM_Infra — KVM device node unavailable (pre-existing platform limitation)

Root cause: KVM cannot initialize on qcs6490-rb3gen2 because the platform is running under Gunyah hypervisor in HYP mode (EL2), preventing nested virtualization; kernel reports "kvm [1]: HYP mode not available" at boot.

Possible fix: This is not a PR-introduced regression — the PR only adds GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM/ARM virtualization. No fix required for this PR. To enable KVM on this platform, the board would need to boot without a hypervisor or use hardware-assisted nested virtualization if supported by the SoC.

Detail analysis attachment: failed_case_job231348_4_detailed.md

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

Failed case: 0_qcom-next-ci-premerge-tests

Root cause: LAVA test suite marked as failed due to 4 individual test case failures (Probe_Failure_Check, KVM_Driver, KVM_EL2_DTB, KVM_Infra) within the test definition. The test runner completed normally (<LAVA_TEST_RUNNER EXIT> present), but LAVA's dispatcher marked the overall test definition as "fail" because not all test cases passed. This is standard LAVA behavior when a test suite contains failing test cases, not a kernel crash or infrastructure failure.

Possible fix: This is not a single fixable issue but rather a test suite result aggregation. The PR enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m), which may have exposed pre-existing KVM-related test failures on qcs6490-rb3gen2. Investigate the 4 individual failing test cases separately: (1) Probe_Failure_Check — check dmesg for driver probe failures; (2) KVM_Driver, KVM_EL2_DTB, KVM_Infra — these are KVM/virtualization tests that may be failing due to missing KVM support or configuration on this SoC. Review the boot log comparison report which shows no new critical boot issues introduced by this PR (all targets show "no baseline" but no new crashes). The failures are likely pre-existing test infrastructure issues unrelated to the GPU virtualization config change.

Detail analysis attachment: failed_case_job231348_5_detailed.md

Job 231349 | SoC qcs8300-ride

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Could not be determined confidently from available logs.

Possible fix: No kernel fix required**. This is a test infrastructure issue. Recommended actions: (1) Add regulatory.db firmware file to the rootfs/firmware package used in CI, OR (2) Update the Probe_Failure_Check test to exclude known benign firmware load failures (e.g., regulatory.db when cfg80211 falls back successfully), OR (3) Suppress this specific failure pattern in the test harness since it does not indicate a kernel regression.

Detail analysis attachment: failed_case_job231349_1_detailed.md

Case 2: KVM_Driver — /dev/kvm device node unavailable

Failed case: KVM_Driver — /dev/kvm device node unavailable

Root cause: KVM cannot initialize on qcs8300-ride because the Gunyah hypervisor is already running at EL2; ARM architecture allows only one hypervisor at EL2, and Gunyah has claimed it during boot, preventing KVM from creating /dev/kvm.

Possible fix: This is not a kernel regression or PR-introduced issue. The test failure is expected platform behavior. To enable KVM on this target, the boot configuration must be changed to boot without Gunyah hypervisor (requires bootloader/firmware changes to not load Gunyah). Alternatively, exclude KVM tests from the CI test suite for targets that boot with Gunyah hypervisor enabled.

Detail analysis attachment: failed_case_job231349_2_detailed.md

Case 3: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM cannot initialize on qcs8300-ride because the platform is running under the Gunyah Type-1 hypervisor (boot log shows "Hypervisor cold boot, version: gunyah-cdfb73831"), which has already claimed EL2 privilege level. KVM requires exclusive EL2 access to create /dev/kvm, but Gunyah occupies EL2 as the primary hypervisor, preventing KVM from initializing. CONFIG_KVM is enabled in the kernel config, but the KVM driver cannot probe successfully in this nested virtualization scenario.

Possible fix: This is a platform configuration issue, not a kernel regression. The qcs8300-ride target is configured to boot with Gunyah hypervisor, which is incompatible with KVM. To enable KVM testing on this platform: (1) reconfigure the platform to boot without Gunyah hypervisor, OR (2) exclude KVM tests from the qcs8300-ride test suite since this platform is intended for Gunyah-based virtualization, not KVM-based virtualization. The PR changes (enabling DRM_VIRTIO_GPU configs) are unrelated to this failure and did not cause it.

Detail analysis attachment: failed_case_job231349_3_detailed.md

Case 4: KVM_Infra — KVM device node not created

Failed case: KVM_Infra — KVM device node not created

Root cause: The /dev/kvm device node is not present despite CONFIG_KVM being enabled in the kernel configuration, indicating that the KVM kernel module failed to initialize or create the device node during boot on the qcs8300-ride platform.

Possible fix: This is a pre-existing platform/kernel configuration issue, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only adds DRM VirtIO GPU config options). The qcs8300-ride platform may not support KVM/virtualization at EL2, or the KVM driver may require additional platform-specific configuration or device tree entries. Verify that the platform firmware/bootloader enables EL2 virtualization extensions and that the device tree includes the necessary KVM/hypervisor nodes. If KVM is not supported on this platform, mark these tests as expected failures for qcs8300-ride.

Detail analysis attachment: failed_case_job231349_4_detailed.md

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

Failed case: 0_qcom-next-ci-premerge-tests

Root cause: LAVA test suite marked as failed due to multiple individual test failures: (1) Probe_Failure_Check failed on benign regulatory.db firmware load error (faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2); (2) KVM_Driver, KVM_EL2_DTB, and KVM_Infra tests failed because /dev/kvm device node is not present despite CONFIG_KVM and CONFIG_VIRTUALIZATION being enabled in kernel config. The PR changes (adding CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m) are unrelated to these failures.

Possible fix: (1) For regulatory.db: This is a known benign failure - the regulatory.db firmware file is missing from the rootfs but does not impact WiFi/BT functionality (WiFi/BT tests passed). Add regulatory.db to the rootfs image or suppress this probe failure check. (2) For KVM device node: The KVM kernel driver is not loading or creating /dev/kvm. Check dmesg for KVM initialization errors. Verify that the KVM kernel module is being loaded (check lsmod | grep kvm or ensure CONFIG_KVM=y not =m). If CONFIG_KVM=m, ensure the module is loaded via modprobe or initramfs. This is likely a pre-existing platform configuration issue, not introduced by this PR.

Detail analysis attachment: failed_case_job231349_5_detailed.md

Job 231350 | SoC shikra-iqs-evk

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

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

Case 1: GIC

Failed case: GIC

Root cause: Test script bug — the GIC test script assumes 8 CPUs but shikra-iqs-evk has only 4 CPUs (0-3); script attempts to parse non-existent columns 5-8 from /proc/interrupts arch_timer line, causing bash integer comparison errors at line 75 ([: GICv3: integer expected, [: Level: integer expected, [: arch_timer: integer expected).

Possible fix: Update the GIC test script (/lava-231350/0/tests/0_qcom-next-ci-premerge-tests/Runner/suites/Kernel/Baseport/GIC/run.sh) to dynamically detect the number of online CPUs from /sys/devices/system/cpu/online or /proc/cpuinfo instead of hardcoding an 8-CPU assumption; iterate only over CPUs that exist in the /proc/interrupts arch_timer line.

Detail analysis attachment: failed_case_job231350_1_detailed.md

Case 2: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Multiple driver probe failures detected on shikra-iqs-evk: coresight-etm4x (4 instances, error -22/EINVAL), cpufreq-dt (error -17/EEXIST), tpm_tis_spi (error -110/ETIMEDOUT), and regulatory.db firmware load (error -2/ENOENT). These are pre-existing platform issues unrelated to the PR changes (GPU virtualization config). The baseline comparison shows no stored baseline for shikra-iqs-evk, and the same probe failures appear across all 9 targets in the PR run, indicating they are not PR-introduced.

Possible fix: No action required for this PR.** The probe failures are pre-existing platform/infra issues: (1) coresight-etm4x -22 errors are known on shikra due to missing/incomplete ETM DT configuration; (2) cpufreq-dt -17 is a benign duplicate registration attempt; (3) tpm_tis_spi -110 is a known timeout on this board variant; (4) regulatory.db -2 is expected when the firmware file is not shipped in the rootfs. The PR only enables GPU virtualization kernel configs (CONFIG_DRM_VIRTIO_GPU=m) and does not touch any of the failing subsystems (coresight, cpufreq, TPM, or wireless regulatory). Mark this test as SKIP or suppress these known failures in the test framework.

Detail analysis attachment: failed_case_job231350_2_detailed.md

Case 3: PCIe

Failed case: PCIe

Root cause: Could not be determined confidently from available logs.

Possible fix: Add the TC956X_Firmware_PCIeBridge.bin firmware file to the rootfs image under /lib/firmware/ (or another standard firmware path). This firmware is required for the Toshiba TC956X PCIe-to-Ethernet bridge chip used on the QPS615 expansion board. The firmware should be sourced from the vendor or the board support package and included in the Yocto/distro build recipe that generates the test rootfs.

Detail analysis attachment: failed_case_job231350_3_detailed.md

Case 4: USBHost

Failed case: USBHost

Root cause: USB host controller (4e00000.usb) is not probed or initialized at runtime on shikra-iqs-evk; no USB root hubs are exposed in /sys/bus/usb/devices/, and lsusb fails to enumerate the USB bus. The USB controller is added to IOMMU group 5 but no xHCI/DWC3 driver probe messages appear in the kernel log, indicating the USB host driver is either not configured, not loaded, or the hardware is not enabled in the device tree for this platform.

Possible fix: This is a pre-existing platform/board configuration issue, not a PR-introduced regression. The PR (enabling CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m) does not touch USB subsystem code or configuration. To resolve: (1) verify USB host controller DT node is present and enabled in arch/arm64/boot/dts/qcom/qcs615-shikra-iqs-evk.dts; (2) confirm CONFIG_USB_DWC3_QCOM=y and CONFIG_USB_XHCI_HCD=y are enabled in the kernel config; (3) check if USB PHY regulators/clocks are properly defined in DT; (4) if USB host is intentionally disabled on this EVK variant, mark the USBHost test as SKIP for shikra-iqs-evk in the CI configuration.

Detail analysis attachment: failed_case_job231350_4_detailed.md

Case 5: ** BT_FW_KMD_Service

Failed case: ** BT_FW_KMD_Service

Root cause: ** Bluetooth UART communication failure between hci_uart driver and QCA WCN399x chipset — repeated HCI command timeouts (-110 ETIMEDOUT) during QCA version information read, preventing firmware load and BD address initialization. The Bluetooth controller on shikra-iqs-evk is not responding to HCI commands over the UART interface.

Possible fix: This is NOT a PR-introduced regression (PR only enables GPU virtualization configs). This is a pre-existing hardware/firmware/board-specific issue on shikra-iqs-evk. Recommended actions: (1) Verify UART pinmux/GPIO configuration for Bluetooth in shikra-iqs-evk device tree; (2) Check if Bluetooth power/enable GPIO is correctly configured and asserted; (3) Verify QCA WCN399x firmware files are present and correct version for this board; (4) Check for known errata or board-specific initialization requirements for WCN399x on Shikra platform; (5) Test with a known-good baseline kernel on the same hardware to confirm this is not a hardware failure.

Detail analysis attachment: failed_case_job231350_5_detailed.md

Case 6: **Bluetooth Driver Communication Failure — BT_ON_OFF**

Failed case: Bluetooth Driver Communication Failure — BT_ON_OFF

Root cause: Bluetooth HCI command timeout during QCA WCN399x firmware initialization. The hci0 adapter repeatedly fails to read QCA version information with error -110 (ETIMEDOUT), indicating the Bluetooth hardware is not responding to HCI commands. This occurs consistently across multiple power-on retry attempts (0/2, 1/2, 2/2) and recovery cycles, suggesting a hardware communication path failure (UART/serial interface, power/clock/reset sequencing, or firmware handshake issue) rather than a transient error.

Possible fix: This is not a PR-introduced regression — the PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to Bluetooth. The boot log baseline comparison shows no baseline exists for shikra-iqs-evk on qcom-6.18.y, so this cannot be confirmed as new. Recommended actions: (1) Verify Bluetooth hardware is properly powered, clocked, and reset-sequenced in device tree for shikra-iqs-evk; (2) Check UART/serial interface configuration and pinctrl settings for the Bluetooth UART; (3) Verify WCN399x firmware files are present and correct version; (4) Add debug logging to drivers/bluetooth/hci_qca.c around qca_send_power_pulse() and qca_read_soc_version() to capture detailed HCI command/response timing; (5) If hardware is confirmed working on other branches, bisect kernel changes affecting QCA Bluetooth or UART drivers between working and failing commits.

Detail analysis attachment: failed_case_job231350_6_detailed.md

Case 7: BT_SCAN

Failed case: BT_SCAN

Root cause: Bluetooth QCA driver runtime failure — the Bluetooth hardware (hci0) is not responding to driver commands, resulting in repeated command tx timeouts (-110 ETIMEDOUT) and failure to read QCA version information. The adapter has no valid BD address, indicating the Bluetooth firmware/hardware initialization sequence is failing. This is a driver-hardware communication failure, not a test logic issue.

Possible fix: This failure is NOT introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The Bluetooth failure appears to be a pre-existing platform/firmware issue on shikra-iqs-evk. Recommended actions: (1) Verify Bluetooth firmware files are present and correct for WCN7850 on shikra-iqs-evk; (2) Check if this is a known issue on this platform in the baseline; (3) If this is a new regression, bisect to find when Bluetooth stopped working on shikra-iqs-evk; (4) Check hardware/power sequencing for the Bluetooth module.

Detail analysis attachment: failed_case_job231350_7_detailed.md

Case 8: ** Kernel Crash — qcom_rng driver synchronous external abort (hardware access fault)

Failed case: ** Kernel Crash — qcom_rng driver synchronous external abort (hardware access fault)

Root cause: ** The qcom_rng (Qualcomm hardware random number generator) driver attempted to read from hardware registers at offset 0x35c (qcom_rng_read+0xc4) but encountered a synchronous external abort (ESR 0x96000010), indicating the hardware block is not accessible. On the shikra-iqs-evk platform, the qcom_rng hardware is either not powered, not clocked, not present, or the MMIO mapping is incorrect. The crash occurred during the qcom_hwrng test when userspace (dd process) read from /dev/hwrng, triggering the driver to access the hardware.

Possible fix: Verify the qcom_rng device tree node for shikra-iqs-evk includes correct MMIO base address, required clocks (iface, core), and power domain references. Check if the RNG hardware block exists on this SoC variant and is enabled in the device tree (status = "okay"). If the hardware is not present on shikra-iqs-evk, disable the qcom_rng driver for this platform or mark the DT node as status = "disabled". The KVM test failures are a separate, expected issue (KVM not enabled/configured on this platform) and do not require a fix.

Detail analysis attachment: failed_case_job231350_8_detailed.md

Case 9: KVM_EL2_DTB — /dev/kvm device node not present

Failed case: KVM_EL2_DTB — /dev/kvm device node not present

Root cause: KVM kernel driver (CONFIG_KVM=y) is enabled but the /dev/kvm device node is not created at runtime, indicating the KVM driver failed to initialize or probe on the Shikra IQS EVK platform. This is a platform-specific KVM enablement issue, not a kernel crash or PR-introduced regression.

Possible fix: Investigate why the KVM driver does not create /dev/kvm on Shikra IQS EVK: (1) Check dmesg for KVM initialization errors or probe failures during boot; (2) Verify that the platform's device tree includes the necessary KVM/virtualization nodes and that EL2 is accessible; (3) Confirm that the bootloader/firmware enables EL2 and does not restrict virtualization; (4) If KVM is not expected to work on this platform, mark the test as SKIP for Shikra IQS EVK in the CI configuration.

Detail analysis attachment: failed_case_job231350_9_detailed.md

Case 10: ** Kernel Crash — synchronous external abort (hardware bus fault)

Failed case: ** Kernel Crash — synchronous external abort (hardware bus fault)

Root cause: ** The qcom_hwrng test triggered a read from /dev/hwrng, which invoked qcom_rng_read() in the qcom_rng driver. The driver attempted an MMIO read from the hardware RNG register at offset +0x35c (instruction b940035c = ldr w28, [x26, #0x35c]), but the hardware did not respond, causing a synchronous external abort (ESR 0x96000010 = data abort, external fault). This is a hardware/firmware/power issue, not a kernel software bug. The RNG hardware block was either not powered, not clocked, or in a bad state that prevented MMIO access. The crash is unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118, which only enables GPU virtualization kernel configs (CONFIG_DRM_VIRTIO_GPU) and does not touch RNG, power management, or clock drivers.

Possible fix: This is a board/firmware/hardware configuration issue on the shikra-iqs-evk platform, not a kernel regression. The KVM_Infra test failure is a false positive — it failed only because /dev/kvm was not present (expected, as KVM requires EL2 support and proper DT configuration), but the test did not cause the crash. The crash occurred in the subsequent qcom_hwrng test. Recommended actions:

Detail analysis attachment: failed_case_job231350_10_detailed.md

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

Failed case: 0_qcom-next-ci-premerge-tests

Root cause: Kernel crash (synchronous external abort) in qcom_rng driver during hardware RNG read operation. The crash occurred at qcom_rng_read+0xc4 when the qcom_hwrng test attempted to read entropy from /dev/hwrng. This is a hardware access fault (external abort 0x96000010) indicating the RNG hardware registers became inaccessible or the device was in an invalid state. The crash is NOT related to the PR changes (GPU virtualization config) — it is a pre-existing issue in the qcom_rng driver or platform-specific hardware state on shikra-iqs-evk.

Possible fix: This is not a PR-introduced regression. The crash is in the qcom_rng driver which is unrelated to the GPU virtualization config changes in this PR. The test failure should be investigated separately as a platform-specific qcom_rng driver issue on shikra-iqs-evk. The PR can proceed; recommend filing a separate bug for the qcom_rng crash with full crash dump and hardware state analysis.

Detail analysis attachment: failed_case_job231350_11_detailed.md

Case 12: Kernel Crash — synchronous external abort in qcom_rng driver

Failed case: Kernel Crash — synchronous external abort in qcom_rng driver

Root cause: The qcom_hwrng test triggered a synchronous external abort (memory access fault) in the qcom_rng_read function at offset 0xc4, causing a kernel panic. The crash occurred when reading from the hardware RNG device, indicating either a hardware fault, incorrect memory mapping, or a race condition in the qcom_rng driver on the shikra-iqs-evk platform. The subsequent EFI pstore write failures suggest firmware/UEFI runtime services issues during panic handling.

Possible fix: This is a pre-existing kernel/driver/hardware issue unrelated to the PR (which only enables GPU virtualization configs). Immediate mitigation: skip the qcom_hwrng test on shikra-iqs-evk until the root cause is identified. Long-term fix: investigate the qcom_rng driver's memory access at qcom_rng_read+0xc4 (likely a register read via readl/ioread32) — verify the device tree memory mapping for the RNG hardware block on shikra (SA8775P SoC), check if the RNG hardware is properly initialized/clocked, and review recent qcom_rng driver changes that may have introduced a regression on this platform.

Detail analysis attachment: failed_case_job231350_12_detailed.md

Case 13: Kernel Crash — synchronous external abort in qcom_rng driver

Failed case: Kernel Crash — synchronous external abort in qcom_rng driver

Root cause: The lava-test-retry case failed with a 2400-second timeout because the kernel panicked during the qcom_hwrng test execution. The panic occurred at qcom_rng_read+0xc4 with a synchronous external abort (0x96000010), indicating a hardware bus error when the qcom_rng driver attempted to read from the hardware RNG device. This is a pre-existing kernel/hardware issue unrelated to the PR's GPU virtualization config changes.

Possible fix: This is NOT a PR-introduced regression. The PR only enables DRM_VIRTIO_GPU configs and does not touch the qcom_rng driver or hardware RNG subsystem. The crash is a pre-existing issue with the qcom_rng driver on shikra-iqs-evk hardware. Re-trigger the CI job to verify if the crash is reproducible. If it recurs, investigate the qcom_rng driver's MMIO access patterns and hardware state on this specific board revision, as the synchronous external abort suggests the RNG hardware block may be unpowered, clock-gated, or the MMIO mapping is incorrect for this SoC/board combination.

Detail analysis attachment: failed_case_job231350_13_detailed.md

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

Failed case: ** Kernel Crash — Synchronous External Abort in qcom_rng driver

Root cause: ** The qcom_rng driver attempted to read from a hardware register that is either not powered, not clocked, or not accessible, resulting in a synchronous external abort (bus error 0x96000010) at PC qcom_rng_read+0xc4. The crash occurred during a hardware RNG test (dd reading from /dev/hwrng) at timestamp 1232.011674s. The PR changes (enabling DRM_VIRTIO_GPU configs) are unrelated to the qcom_rng driver and did not introduce this failure — this is a pre-existing platform/firmware issue on shikra-iqs-evk.

Possible fix: This is NOT a PR-introduced regression. The failure is a pre-existing hardware/firmware/clock/power configuration issue on the shikra-iqs-evk platform. Recommended actions: (1) Verify qcom_rng hardware block is properly powered and clocked in the device tree for shikra-iqs-evk; (2) Check if the RNG hardware block requires additional firmware initialization or secure-world enablement that is missing; (3) Consider disabling the qcom_hwrng test on shikra-iqs-evk until the platform configuration is fixed, as this is a known board-specific issue unrelated to kernel code changes.

Detail analysis attachment: failed_case_job231350_14_detailed.md

Job 231351 | SoC qcs9100-ride

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Test detected two pre-existing platform issues on qcs9100-ride: (1) Four PMIC temp-alarm devices remain in deferred probe state due to missing thermal zone dependencies, and (2) Aquantia AQR115C Ethernet PHY probe fails with -EINVAL (-22) due to missing firmware-name DT property. Neither issue is introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (GPU virtualization config changes).

Possible fix: These are known platform-specific issues unrelated to the PR changes. No action required for PR QCLINUX: arm64: configs: Enable GPU virtualization #1118. For platform maintainers: (1) Add thermal zone bindings for PMIC temp-alarm devices in qcs9100-ride DT, (2) Add firmware-name property to Aquantia PHY node or provide fallback firmware path in driver.

Detail analysis attachment: failed_case_job231351_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Video codec device aa00000.video-codec is missing IOMMU group attachment on qcs9100-ride platform — the device tree or driver configuration does not bind this critical master to an IOMMU group, causing the SMMU validation test to fail when checking that all critical platform masters are protected by IOMMU.

Possible fix: Add iommus property to the aa00000.video-codec device tree node in arch/arm64/boot/dts/qcom/qcs9100-ride.dtsi (or the appropriate SoC-level DTSI) to bind the video codec to an IOMMU group, following the pattern used by other critical masters (UFS, Display, GPU, USB, Ethernet) that already pass the test.

Detail analysis attachment: failed_case_job231351_2_detailed.md

Case 3: Ethernet_Basic_Validation

Failed case: Ethernet_Basic_Validation

Root cause: Ethernet interface end0 (qcom-ethqos 23040000.ethernet) fails to attach to PHY with error -EINVAL during interface bring-up; no MDIO bus probe messages appear in boot log, indicating PHY device is not discovered or registered on the MDIO bus for this qcs9100-ride platform

Possible fix: This is a pre-existing platform/board/DT configuration issue unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options). The failure is not PR-introduced. Recommended action: (1) Verify device tree MDIO bus node and PHY child node configuration for 23040000.ethernet on qcs9100-ride; (2) Check if PHY reset GPIO or regulator dependencies are missing or misconfigured in DT; (3) Confirm MDIO bus driver probe completes successfully before stmmac/ethqos driver attempts PHY attach; (4) If this is a known board limitation (no PHY physically connected to end0), update test expectations to skip end0 or mark as expected failure for this target

Detail analysis attachment: failed_case_job231351_3_detailed.md

Case 4: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM cannot initialize on qcs9100-ride because the platform is running Gunyah hypervisor, which does not provide KVM-compatible EL2 (HYP mode) virtualization extensions. The kernel message "kvm [1]: HYP mode not available" at boot confirms that KVM detected the absence of required hypervisor support, preventing /dev/kvm device node creation.

Possible fix: This is not a kernel regression — it is a platform configuration limitation. The qcs9100-ride target uses Gunyah hypervisor for secure virtualization, which is incompatible with KVM. To resolve: (1) exclude KVM tests from the qcs9100-ride CI test suite, or (2) if KVM support is required, configure the platform to boot without Gunyah hypervisor (requires bootloader/firmware changes to enable native KVM EL2 mode). The PR changes (enabling DRM_VIRTIO_GPU configs) are unrelated to this failure.

Detail analysis attachment: failed_case_job231351_4_detailed.md

Case 5: KVM_EL2_DTB — KVM Host Initialization Failure (Platform Limitation)

Failed case: KVM_EL2_DTB — KVM Host Initialization Failure (Platform Limitation)

Root cause: qcs9100-ride platform does not support ARM EL2 (Hypervisor mode); KVM driver initialization fails with "HYP mode not available", preventing /dev/kvm device node creation.

Possible fix: This is a platform hardware limitation, not a software bug. The qcs9100-ride board does not have EL2 support and cannot run KVM as a hypervisor host. Mark KVM tests as "not applicable" for this platform, or skip KVM test suite on qcs9100-ride in CI configuration.

Detail analysis attachment: failed_case_job231351_5_detailed.md

Case 6: ** KVM_Infra — KVM device node unavailable (pre-existing platform limitation)

Failed case: ** KVM_Infra — KVM device node unavailable (pre-existing platform limitation)

Root cause: ** The qcs9100-ride platform boots with the Gunyah hypervisor active at EL2, which prevents KVM from initializing. KVM requires exclusive access to EL2/HYP mode to provide virtualization services, but when Gunyah (or any other hypervisor) is already running at EL2, the kernel correctly reports "HYP mode not available" and KVM initialization fails. This is expected behavior on platforms with a Type-1 hypervisor like Gunyah.

Possible fix: This is not a kernel regression or bug — it is a platform architecture constraint. KVM and Gunyah cannot coexist because both require EL2. To enable KVM on this platform, the Gunyah hypervisor must be disabled in the firmware/bootloader configuration. If virtualization is required, choose either Gunyah (Type-1 hypervisor for secure partitioning) or KVM (Type-2 hypervisor for general-purpose VMs), but not both. The PR patch (enabling DRM_VIRTIO_GPU configs) is unrelated to this failure and does not cause it.

Detail analysis attachment: failed_case_job231351_6_detailed.md

Case 7: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM initialization failed because the platform is not booted in EL2 (hypervisor mode) — kernel message "kvm [1]: HYP mode not available" indicates the CPU is running in EL1 (kernel mode) instead of EL2, preventing KVM from enabling virtualization support.

Possible fix: This is a platform/firmware configuration issue, not a kernel regression. The qcs9100-ride target must be configured to boot the kernel in EL2 mode (either via bootloader configuration or by running under a hypervisor). The PR changes (enabling GPU virtualization configs) are unrelated and do not cause this failure. No kernel code fix is required — this is a test environment/platform configuration issue.

Detail analysis attachment: failed_case_job231351_7_detailed.md

Job 231353 | SoC monaco-evk

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs on monaco-evk target, causing ath11k_pci driver probe to fail with -ETIMEDOUT (-110) during MHI power-up. This is a pre-existing infrastructure/rootfs packaging issue, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization kernel configs).

Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs image for monaco-evk. The firmware should be packaged in /lib/firmware/ath11k/WCN6855/hw2.1/nfa765/ directory. This is a CI infrastructure fix, not a kernel code fix.

Detail analysis attachment: failed_case_job231353_1_detailed.md

Case 2: WiFi_Firmware_Driver — WiFi driver probe failure

Failed case: WiFi_Firmware_Driver — WiFi driver probe failure

Root cause: ath11k_pci driver probe failed with error -110 (ETIMEDOUT) on monaco-evk because MHI firmware loading failed — the driver attempted to load firmware from the wrong path ath11k/WCN6855/hw2.1/nfa765/amss.bin which does not exist; the correct firmware is at ath12k/WCN7850/hw2.0/ncm865/amss.bin as detected by the test harness. This is a board-specific firmware path mismatch where the ath11k_pci driver (for WCN6855 hardware) is being used instead of the correct ath12k driver for the WCN7850 hardware present on monaco-evk.

Possible fix: Update the monaco-evk device tree or board configuration to use the ath12k driver instead of ath11k_pci for the PCIe WiFi device at 0000:01:00.0, or ensure the correct firmware symlink/path is configured for the WCN7850 hardware. The test log shows ath12k_wifi7 and ath12k modules are loaded correctly, but ath11k_pci is incorrectly attempting to probe the device. Verify the PCIe device ID binding in the device tree matches WCN7850 (ath12k) not WCN6855 (ath11k).

Detail analysis attachment: failed_case_job231353_2_detailed.md

Case 3: WiFi_OnOff — WiFi driver probe failure (ath11k_pci)

Failed case: WiFi_OnOff — WiFi driver probe failure (ath11k_pci)

Root cause: The ath11k_pci driver probe failed with error -110 (ETIMEDOUT) on monaco-evk because the WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs. The MHI (Modem Host Interface) subsystem attempted to load the firmware during device initialization but failed with error -2 (ENOENT), causing the MHI power-up to timeout after waiting for the firmware to be loaded. This is a pre-existing platform/rootfs issue, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options).

Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs under /lib/firmware/. The firmware binary must be obtained from the Qualcomm firmware package for WCN6855 hw2.1 and placed in the correct directory structure. After adding the firmware, rebuild the rootfs image and reflash the target.

Detail analysis attachment: failed_case_job231353_3_detailed.md

Case 4: WiFi Driver Probe Failure — ath11k_pci probe timeout

Failed case: WiFi Driver Probe Failure — ath11k_pci probe timeout

Root cause: Result: WiFi driver probe failure. The ath11k_pci driver failed to probe the WCN6855 WiFi hardware on monaco-evk because the required firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs, causing MHI (Modem Host Interface) power-up to timeout after failing to load firmware (-2 ENOENT → -110 ETIMEDOUT). This is a pre-existing board/firmware configuration issue, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 which only adds GPU virtualization config options unrelated to WiFi.

Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/ath11k/WCN6855/hw2.1/nfa765/). This firmware should be included in the linux-firmware package or board-specific firmware overlay for monaco-evk. The PR changes (GPU virtualization configs) are unrelated and do not cause this failure.

Detail analysis attachment: failed_case_job231353_4_detailed.md

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

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

Target	Boot lines (PR)	Boot lines (baseline)	New issues	High	Medium	Low
`lemans-evk`	1230	no baseline	11	2	9	0
`qcs615-ride`	966	no baseline	9	0	9	0
`hamoa-evk`	1708	no baseline	18	1	17	0
`purwa-evk`	1573	no baseline	60	1	57	2
`qcs6490-rb3gen2`	1059	no baseline	7	0	7	0
`qcs8300-ride`	1108	no baseline	15	2	13	0
`shikra-iqs-evk`	901	no baseline	9	0	9	0
`qcs9100-ride`	1337	no baseline	15	2	12	1
`monaco-evk`	1058	no baseline	10	0	10	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: 154 new issue(s) across 9 target(s).

Target: `lemans-evk`

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

🟡 ERROR (medium)

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

Context

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

🟡 WARNING (medium)

[    4.260439][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.235657][    T1] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 (0,8000003f) counters available
[    4.254959][    T1] ------------[ cut here ]------------
[    4.260416][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.260439][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.277044][    T1] Modules linked in:
[    4.280905][    T1] CPU: 5 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.44-g30fa759aa108 #1 PREEMPT 
[    4.290448][    T1] Hardware name: Qualcomm Technologies, Inc. Lemans EVK (DT)

🟠 CALL_TRACE (high)

[    4.401641][    T1] Call trace:

Context

[    4.377534][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002c1
[    4.385573][    T1] x5 : 00000000000002c2 x4 : 40000000fffff2c1 x3 : 0000000000000000
[    4.393605][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.401641][    T1] Call trace:
[    4.404873][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.410600][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.416233][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 WARNING (medium)

[    4.513407][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.501088][    T1] ---[ end trace 0000000000000000 ]---
[    4.507939][    T1] ------------[ cut here ]------------
[    4.513394][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.513407][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.530015][    T1] Modules linked in:
[    4.533874][    T1] CPU: 5 UID: 0 PID: 1 Comm: swapper/0 Tainted: G        W           6.18.44-g30fa759aa108 #1 PREEMPT 
[    4.545023][    T1] Tainted: [W]=WARN

🟠 CALL_TRACE (high)

[    4.659982][    T1] Call trace:

Context

[    4.635874][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002eb
[    4.643910][    T1] x5 : 00000000000002ec x4 : 40000000fffff2eb x3 : 0000000000000000
[    4.651946][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.659982][    T1] Call trace:
[    4.663215][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.668938][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.674574][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 ERROR (medium)

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

Context

[    7.826484][  T211] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@af5c000
[    7.827302][  T200] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    7.827524][  T200] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    7.827706][   T55] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    7.827718][   T55] cfg80211: failed to load regulatory.db
[    7.842139][  T206] Bluetooth: HCI UART driver ver 2.3
[    7.848520][  T211] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@af54000

🟡 ERROR (medium)

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

Context

[    8.107601][  T110] Bluetooth: hci0: QCA SOC Version  :0x400c1211
[    8.107604][  T110] Bluetooth: hci0: QCA ROM Version  :0x00000201
[    8.107606][  T110] Bluetooth: hci0: QCA Patch Version:0x000038e6
[    8.107990][   T84] tpm tpm0: A TPM error (256) occurred attempting the self test
[    8.107998][   T84] tpm tpm0: starting up the TPM manually
[    8.117879][  T110] Bluetooth: hci0: QCA controller version 0x12110201
[    8.119513][  T209] /connector-1: Fixed dependency cycle(s) with /soc@0/geniqup@ac0000/i2c@a90000/usb-typec@47

🟡 ERROR (medium)

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

Context

[    8.129946][  T110] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.130076][  T204] usbcore: registered new device driver onboard-usb-dev
[    8.136675][  T209] /soc@0/geniqup@ac0000/i2c@a90000/usb-typec@47: Fixed dependency cycle(s) with /connector-1
[    8.142359][  T110] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.155494][  T204] onboard-usb-dev a800000.usb:hub@1: supply vdd not found, using dummy regulator
[    8.162661][  T110] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.192384][   T85] msm_dpu ae01000.display-controller: bound af54000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium)

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

Context

[    8.162661][  T110] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.192384][   T85] msm_dpu ae01000.display-controller: bound af54000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    8.198997][  T110] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.199183][  T110] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.213222][   T85] msm_dpu ae01000.display-controller: bound af5c000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    8.218906][  T110] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.229414][   T85] adreno 3d00000.gpu: supply vdd not found, using dummy regulator

🟡 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
[   29.469938][  T376] EXT4-fs (sda2): orphan cleanup on readonly fs
[   29.476823][  T376] EXT4-fs (sda2): mounted filesystem 7f081a84-7045-4209-949a-773694ad02be ro with ordered data mode. Quota mode: none.
done.

Target: `qcs615-ride`

⚠️ 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.476840][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[    7.456761][  T226] pci_bus 0000:00: root bus resource [bus 00-ff]
[    7.463127][  T226] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff]
[    7.470283][  T226] pci_bus 0000:00: root bus resource [mem 0x40300000-0x5fffffff]
[    7.476840][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.478207][  T226] pci 0000:00:00.0: [17cb:010a] type 01 class 0x060400 PCIe Root Port
[    7.487936][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.496145][  T226] pci 0000:00:00.0: BAR 0 [mem 0x00000000-0x00000fff]

🟡 ERROR (medium)

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

Context

[    7.470283][  T226] pci_bus 0000:00: root bus resource [mem 0x40300000-0x5fffffff]
[    7.476840][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.478207][  T226] pci 0000:00:00.0: [17cb:010a] type 01 class 0x060400 PCIe Root Port
[    7.487936][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.496145][  T226] pci 0000:00:00.0: BAR 0 [mem 0x00000000-0x00000fff]
[    7.496152][  T226] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    7.518855][  T226] pci 0000:00:00.0:   bridge window [io  0x0000-0x0fff]

🟡 ERROR (medium)

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

Context

[    7.574839][  T226] OF: /soc@0/pcie@1c08000: iommu-map mismatches target #iommu-cells, assuming extra cell of 0
[    7.595571][   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.622180][  T226] pci 0000:00:00.0: Adding to iommu group 20
[    7.631107][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.641690][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.650585][  T174] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 21
[    7.653618][  T153] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f

🟡 ERROR (medium)

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

Context

[    7.595571][   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.622180][  T226] pci 0000:00:00.0: Adding to iommu group 20
[    7.631107][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.641690][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.650585][  T174] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 21
[    7.653618][  T153] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    7.653618][  T153] :39

🟡 ERROR (medium)

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

Context

[    7.631107][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.641690][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.650585][  T174] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 21
[    7.653618][  T153] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    7.653618][  T153] :39
[    7.676373][  T226] pci 0000:01:00.0: [17cb:1103] type 00 class 0x028000 PCIe Endpoint
[    7.677364][   T84] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium)

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

Context

[    7.653618][  T153] :39
[    7.676373][  T226] pci 0000:01:00.0: [17cb:1103] type 00 class 0x028000 PCIe Endpoint
[    7.677364][   T84] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    7.679754][  T153] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    7.679754][  T153] :43
[    7.684211][  T174] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 22
[    7.685037][  T226] pci 0000:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]

🟡 ERROR (medium)

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

Context

[    8.055524][  T156] Bluetooth: SCO socket layer initialized
[    8.075010][  T163] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    8.075125][  T156] Bluetooth: HCI UART driver ver 2.3
[    8.084092][  T195] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.088637][  T156] Bluetooth: HCI UART protocol H4 registered
[    8.098241][  T195] cfg80211: failed to load regulatory.db
[    8.104580][  T156] Bluetooth: HCI UART protocol LL registered

🟡 ERROR (medium)

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

Context

Begin: Running /scripts/local-premount ... done.
[   25.044234][  T311] blkid (311) used greatest stack depth: 8512 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
[   30.222394][  T323] EXT4-fs (sda2): orphan cleanup on readonly fs
[   30.230561][  T323] EXT4-fs (sda2): mounted filesystem 005fdba6-605e-4778-b1f7-ba98dc88617a 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: 18 (0 critical, 1 high, 17 medium, 0 low)

🟡 WATCHDOG (medium)

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

Context

[    6.916611][    T1] usbcore: registered new interface driver uas
[    6.922831][    T1] usbcore: registered new interface driver usb-storage
[    6.947948][    T1] i2c_dev: i2c /dev entries driver
[    6.973564][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.985862][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.992922][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.998261][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium)

[    7.032281][   T88] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    7.019198][    T1] pstore: Registered efi_pstore as persistent store backend
[    7.026903][   T88] efivars: efivars already registered
[    7.027057][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    7.032281][   T88] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    7.039937][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    7.063874][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    7.072683][    T1] usbcore: registered new interface driver usbhid

🟡 ERROR (medium)

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

Context

[   12.036120][  T115] platform 3d00000.gpu: Adding to iommu group 14
[   12.046742][  T115] platform 3d6a000.gmu: Adding to iommu group 15
[   12.047601][  T264] remoteproc remoteproc0: adsp is available
[   12.053294][  T305] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   12.053496][  T289] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier usb-1-ss0-sbu-mux for /pmic-glink/connector@0
[   12.054932][  T306] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: registered as rtc0
[   12.054985][  T306] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: setting system clock to 1980-01-06T00:00:21 UTC (315964821)

🟡 ERROR (medium)

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

Context

[   12.065601][  T116] qcom-pcie 1c08000.pci: host bridge /soc@0/pci@1c08000 ranges:
[   12.065625][  T116] qcom-pcie 1c08000.pci:       IO 0x007c200000..0x007c2fffff -> 0x0000000000
[   12.065638][  T116] qcom-pcie 1c08000.pci:      MEM 0x007c300000..0x007dffffff -> 0x007c300000
[   12.068388][  T305] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   12.095681][  T115] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a000000.usb for /pmic-glink/connector@2
[   12.110211][   T87] remoteproc remoteproc1: powering up cdsp
[   12.110791][  T367] remoteproc remoteproc0: powering up adsp

🟡 ERROR (medium)

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

Context

[   12.663108][  T116] pcieport 0004:00:00.0: AER: enabled with IRQ 246
[   12.694004][  T174] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   12.697125][  T142] nvme nvme0: pci function 0006:01:00.0
[   12.706026][  T174] tpm tpm0: A TPM error (256) occurred attempting the self test
[   12.706524][  T299] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   12.706691][  T142] nvme 0006:01:00.0: enabling device (0000 -> 0002)
[   12.713295][  T299] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'

🟡 ERROR (medium)

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

Context

[   12.713295][  T299] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   12.714162][  T299] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   12.714344][  T174] tpm tpm0: starting up the TPM manually
[   12.714566][  T124] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   12.746100][  T142] nvme nvme0: allocated 64 MiB host memory buffer (16 segments).
[   12.750060][  T124] cfg80211: failed to load regulatory.db
[   12.773187][  T142] nvme nvme0: 12/0/0 default/read/poll queues

🟡 ERROR (medium)

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

Context

[   13.119462][  T264] Bluetooth: HCI socket layer initialized
[   13.139840][  T146] mhi mhi0: Wait for device to enter SBL or Mission mode
[   13.143066][  T264] Bluetooth: L2CAP socket layer initialized
[   13.143244][  T172] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.143248][  T172] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145154][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145156][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.139840][  T146] mhi mhi0: Wait for device to enter SBL or Mission mode
[   13.143066][  T264] Bluetooth: L2CAP socket layer initialized
[   13.143244][  T172] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.143248][  T172] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145154][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145156][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147796][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.143066][  T264] Bluetooth: L2CAP socket layer initialized
[   13.143244][  T172] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.143248][  T172] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145154][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145156][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147796][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147799][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.143244][  T172] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.143248][  T172] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145154][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145156][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147796][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147799][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.150133][  T172] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.143248][  T172] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145154][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145156][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147796][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147799][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.150133][  T172] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.155851][  T264] Bluetooth: SCO socket layer initialized

🟡 ERROR (medium)

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

Context

[   13.145154][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.145156][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147796][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147799][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.150133][  T172] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.155851][  T264] Bluetooth: SCO socket layer initialized
[   13.230539][  T172] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.145156][  T172] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147796][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.147799][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.150133][  T172] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.155851][  T264] Bluetooth: SCO socket layer initialized
[   13.230539][  T172] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.241380][  T172] /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)

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

Context

[   13.147799][  T172] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.150133][  T172] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.155851][  T264] Bluetooth: SCO socket layer initialized
[   13.230539][  T172] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.241380][  T172] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   13.259133][  T172] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   13.283141][  T264] usbcore: registered new interface driver btusb

🟡 WARNING (medium)

[   13.450869][  T172] WARNING: CPU: 0 PID: 172 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   13.289531][  T406] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
[   13.297831][  T406] Bluetooth: hci0: QCA: patch rome 0x190200 build 0x8567, firmware rome 0x190200 build 0x43fb
[   13.445373][  T172] ------------[ cut here ]------------
[   13.450869][  T172] WARNING: CPU: 0 PID: 172 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   13.463223][  T172] Modules linked in: btusb panel_edp(+) btrtl btintel btbcm bluetooth ecdh_generic ecc ath12k_wifi7(+) ath12k msm mac80211 qcom_iris ocmem gpu_sched libarc4 rpmsg_ctrl videobuf2_d
[   13.463471][  T172]  camcc_x1e80100 snd_soc_lpass_wsa_macro drm dispcc_x1e80100 videocc_sm8550 lpasscc_sc8280xp snd_soc_lpass_va_macro phy_qcom_qmp_usb pinctrl_lpass_lpi phy_snps_eusb2 soundwire_qc
[   13.630249][  T172] CPU: 0 UID: 0 PID: 172 Comm: kworker/u49:4 Not tainted 6.18.44-g30fa759aa108 #1 PREEMPT

🟠 CALL_TRACE (high)

[   13.761272][  T172] Call trace:

Context

[   13.737086][  T172] x8 : ffff80008492b468 x7 : 0000000000000000 x6 : 0000000000000001
[   13.745148][  T172] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   13.753209][  T172] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   13.761272][  T172] Call trace:
[   13.764526][  T172]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   13.771439][  T172]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   13.777281][  T172]  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
[   35.337699][  T510] EXT4-fs (sda2): orphan cleanup on readonly fs
[   35.344640][  T510] EXT4-fs (sda2): mounted filesystem 2afe7eee-2d67-4173-9b85-5b1918477db3 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: 60 (0 critical, 1 high, 57 medium, 2 low)

🟡 WATCHDOG (medium)

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

Context

[    6.320563][    T1] usbcore: registered new interface driver usb-storage
[    6.329251][   T89] Freeing initrd memory: 60796K
[    6.349675][    T1] i2c_dev: i2c /dev entries driver
[    6.368353][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.379903][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.386964][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.392285][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium)

[    6.425934][   T89] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    6.413015][    T1] pstore: Registered efi_pstore as persistent store backend
[    6.420558][   T89] efivars: efivars already registered
[    6.420681][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    6.425934][   T89] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    6.433552][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    6.457524][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    6.466264][    T1] usbcore: registered new interface driver usbhid

🔵 FIRMWARE_FAIL (low)

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

Context

[    9.334239][  T225] /soc@0/pci@1c08000/pcie@0: Fixed dependency cycle(s) with /wifi-bt-connector
[    9.343834][   T72] qcom-pcie 1c00000.pci: host bridge /soc@0/pci@1c00000 ranges:
[    9.345178][  T195] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.349169][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.349333][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.351567][   T72] qcom-pcie 1c00000.pci:       IO 0x007e200000..0x007e2fffff -> 0x0000000000
[    9.351580][   T72] qcom-pcie 1c00000.pci:      MEM 0x007e300000..0x007fffffff -> 0x007e300000

🔵 FIRMWARE_FAIL (low)

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

Context

[    9.343834][   T72] qcom-pcie 1c00000.pci: host bridge /soc@0/pci@1c00000 ranges:
[    9.345178][  T195] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.349169][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.349333][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.351567][   T72] qcom-pcie 1c00000.pci:       IO 0x007e200000..0x007e2fffff -> 0x0000000000
[    9.351580][   T72] qcom-pcie 1c00000.pci:      MEM 0x007e300000..0x007fffffff -> 0x007e300000
[    9.352633][   T64] cpu cpu0: EM: created perf domain

🟡 ERROR (medium)

[    9.450901][  T311] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host

Context

[    9.446138][  T311] qcom-pcie 1bd0000.pcie:      MEM 0x0740000000..0x077fffffff -> 0x0740000000
[    9.450838][  T311] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.450841][  T311] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    9.450901][  T311] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.450909][  T311] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.452608][  T312] qcom-pcie 1bf8000.pci: host bridge /soc@0/pci@1bf8000 ranges:
[    9.456185][  T195] scsi host0: ufshcd

🟡 ERROR (medium)

[    9.450909][  T311] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61

Context

[    9.450838][  T311] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.450841][  T311] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    9.450901][  T311] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.450909][  T311] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.452608][  T312] qcom-pcie 1bf8000.pci: host bridge /soc@0/pci@1bf8000 ranges:
[    9.456185][  T195] scsi host0: ufshcd
[    9.458371][  T311] scsi 0:0:0:49488: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6

🟡 ERROR (medium)

[    9.503360][  T312] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host

Context

[    9.490183][  T312] qcom-qmp-pcie-phy 1bfc000.phy: Init sequence not available
[    9.496889][  T311] scsi 0:0:0:0: Direct-Access     KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.503270][  T312] phy phy-1bfc000.phy.0: phy poweron failed --> -61
[    9.503360][  T312] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host
[    9.514099][   T91] sd 0:0:0:0: [sda] 62470144 4096-byte logical blocks: (256 GB/238 GiB)
[    9.514257][  T311] scsi 0:0:0:1: Direct-Access     KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.515620][  T152] sd 0:0:0:1: [sdb] 16384 4096-byte logical blocks: (67.1 MB/64.0 MiB)

🟡 ERROR (medium)

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

Context

[    9.515861][  T152] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.515927][  T152] sd 0:0:0:1: [sdb] Preferred minimum I/O size 4096 bytes
[    9.515942][  T152] sd 0:0:0:1: [sdb] Optimal transfer size 524288 bytes
[    9.520171][  T312] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61
[    9.526453][   T91] sd 0:0:0:0: [sda] Write Protect is off
[    9.785951][   T91] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.795460][   T91] sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes

🟡 ERROR (medium)

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

Context

[   10.940822][  T196] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   10.971133][   T93] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a000000.usb for /pmic-glink/connector@2
[   11.090789][   T75] remoteproc remoteproc1: remote processor cdsp is now up
[   11.100058][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.138145][   T25] remoteproc remoteproc0: remote processor adsp is now up
[   11.140566][   T72] qcom-pcie 1c08000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[   11.146749][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.100058][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.138145][   T25] remoteproc remoteproc0: remote processor adsp is now up
[   11.140566][   T72] qcom-pcie 1c08000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[   11.146749][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.339160][   T72] qcom-pcie 1c08000.pci: PCIe Gen.3 x2 link up
[   11.343350][   T93] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a600000.usb for /pmic-glink/connector@0
[   11.345482][   T72] qcom-pcie 1c08000.pci: PCI host bridge to bus 0004:00

🟡 ERROR (medium)

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

Context

[   11.386569][   T72] pci 0004:00:00.0: [17cb:0111] type 01 class 0x060400 PCIe Root Port
[   11.391114][   T93] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a800000.usb for /pmic-glink/connector@1
[   11.394801][   T72] pci 0004:00:00.0: BAR 0 [mem 0x00000000-0x00000fff]
[   11.410459][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.414342][   T72] pci 0004:00:00.0: PCI bridge to [bus 01-ff]
[   11.424161][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.430241][   T72] pci 0004:00:00.0:   bridge window [io  0x0000-0x0fff]

🟡 ERROR (medium)

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

Context

[   11.394801][   T72] pci 0004:00:00.0: BAR 0 [mem 0x00000000-0x00000fff]
[   11.410459][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.414342][   T72] pci 0004:00:00.0: PCI bridge to [bus 01-ff]
[   11.424161][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.430241][   T72] pci 0004:00:00.0:   bridge window [io  0x0000-0x0fff]
[   11.443514][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.447035][   T72] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff]

🟡 ERROR (medium)

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

Context

[   11.414342][   T72] pci 0004:00:00.0: PCI bridge to [bus 01-ff]
[   11.424161][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.430241][   T72] pci 0004:00:00.0:   bridge window [io  0x0000-0x0fff]
[   11.443514][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.447035][   T72] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[   11.456870][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.464543][   T72] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]

🟡 ERROR (medium)

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

Context

[   11.430241][   T72] pci 0004:00:00.0:   bridge window [io  0x0000-0x0fff]
[   11.443514][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.447035][   T72] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[   11.456870][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.464543][   T72] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   11.478111][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.483071][   T72] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold

🟡 ERROR (medium)

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

Context

[   11.447035][   T72] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[   11.456870][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.464543][   T72] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   11.478111][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.483071][   T72] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold
[   11.492874][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.502138][   T72] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint

🟡 ERROR (medium)

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

Context

[   11.464543][   T72] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   11.478111][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.483071][   T72] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold
[   11.492874][   T93] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.502138][   T72] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint
[   11.510245][   T93] /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.517965][   T72] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]

🟡 ERROR (medium)

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

Context

[   11.597541][   T72] pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned
[   11.605803][   T72] pci 0004:00:00.0: PCI bridge to [bus 01-ff]
[   11.611891][   T72] pci 0004:00:00.0:   bridge window [mem 0x7c400000-0x7c5fffff]
[   11.615651][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.619578][   T72] pci_bus 0004:00: resource 4 [io  0x0000-0xfffff]
[   11.629404][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.635927][   T72] pci_bus 0004:00: resource 5 [mem 0x7c300000-0x7dffffff]

🟡 ERROR (medium)

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

Context

[   11.611891][   T72] pci 0004:00:00.0:   bridge window [mem 0x7c400000-0x7c5fffff]
[   11.615651][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.619578][   T72] pci_bus 0004:00: resource 4 [io  0x0000-0xfffff]
[   11.629404][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.635927][   T72] pci_bus 0004:00: resource 5 [mem 0x7c300000-0x7dffffff]
[   11.635930][   T72] pci_bus 0004:01: resource 1 [mem 0x7c400000-0x7c5fffff]
[   11.647813][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.629404][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.635927][   T72] pci_bus 0004:00: resource 5 [mem 0x7c300000-0x7dffffff]
[   11.635930][   T72] pci_bus 0004:01: resource 1 [mem 0x7c400000-0x7c5fffff]
[   11.647813][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.655686][   T72] pcieport 0004:00:00.0: PME: Signaling with IRQ 235
[   11.660063][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.670329][   T72] pcieport 0004:00:00.0: AER: enabled with IRQ 235

🟡 ERROR (medium)

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

Context

[   11.635930][   T72] pci_bus 0004:01: resource 1 [mem 0x7c400000-0x7c5fffff]
[   11.647813][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.655686][   T72] pcieport 0004:00:00.0: PME: Signaling with IRQ 235
[   11.660063][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.670329][   T72] pcieport 0004:00:00.0: AER: enabled with IRQ 235
[   11.678107][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.702974][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.655686][   T72] pcieport 0004:00:00.0: PME: Signaling with IRQ 235
[   11.660063][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.670329][   T72] pcieport 0004:00:00.0: AER: enabled with IRQ 235
[   11.678107][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.702974][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.704545][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   11.718990][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.660063][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.670329][   T72] pcieport 0004:00:00.0: AER: enabled with IRQ 235
[   11.678107][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.702974][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.704545][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   11.718990][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.722178][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22

🟡 ERROR (medium)

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

Context

[   11.670329][   T72] pcieport 0004:00:00.0: AER: enabled with IRQ 235
[   11.678107][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.702974][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.704545][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   11.718990][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.722178][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   11.731997][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.678107][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.702974][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.704545][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   11.718990][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.722178][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   11.731997][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.753869][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.702974][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.704545][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   11.718990][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.722178][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   11.731997][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.753869][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.763714][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.704545][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   11.718990][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.722178][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   11.731997][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.753869][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.763714][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.775113][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.718990][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.722178][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   11.731997][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.753869][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.763714][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.775113][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.785855][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.722178][  T208] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   11.731997][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.753869][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.763714][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.775113][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.785855][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.797716][  T204] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)

🟡 ERROR (medium)

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

Context

[   11.731997][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.753869][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.763714][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.775113][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.785855][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.797716][  T204] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[   11.802168][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.753869][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.763714][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.775113][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.785855][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.797716][  T204] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[   11.802168][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.807472][  T153] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)

🟡 ERROR (medium)

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

Context

[   11.775113][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.785855][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.797716][  T204] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[   11.802168][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.807472][  T153] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   11.811759][  T153] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.819785][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.797716][  T204] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[   11.802168][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.807472][  T153] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   11.811759][  T153] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.819785][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.826053][  T153] tpm tpm0: starting up the TPM manually
[   11.852196][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.802168][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.807472][  T153] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   11.811759][  T153] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.819785][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.826053][  T153] tpm tpm0: starting up the TPM manually
[   11.852196][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.862231][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.811759][  T153] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.819785][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.826053][  T153] tpm tpm0: starting up the TPM manually
[   11.852196][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.862231][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.873538][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.883364][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.819785][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.826053][  T153] tpm tpm0: starting up the TPM manually
[   11.852196][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.862231][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.873538][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.883364][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.900279][   T93] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller

🟡 ERROR (medium)

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

Context

[   11.826053][  T153] tpm tpm0: starting up the TPM manually
[   11.852196][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.862231][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.873538][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.883364][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.900279][   T93] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[   11.902516][  T195] cfg80211: Loading compiled-in X.509 certificates for regulatory database

🟡 ERROR (medium)

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

Context

[   11.852196][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.862231][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.873538][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.883364][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.900279][   T93] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[   11.902516][  T195] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   11.906817][   T93] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1

🟡 ERROR (medium)

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

Context

[   11.931822][  T208] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 0-0008 for /pmic-glink/connector@2
[   11.937312][   T93] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe65 hci version 0x110 quirks 0x0000808000000010
[   11.944399][  T208] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-0008 for /pmic-glink/connector@0
[   11.945576][  T245] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.957775][   T93] xhci-hcd xhci-hcd.1.auto: irq 237, io mem 0x0a200000
[   11.968105][  T245] cfg80211: failed to load regulatory.db
[   11.981187][   T93] hub 1-0:1.0: USB hub found

🟡 ERROR (medium)

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

Context

[   11.968105][  T245] cfg80211: failed to load regulatory.db
[   11.981187][   T93] hub 1-0:1.0: USB hub found
[   12.007428][   T93] hub 1-0:1.0: 1 port detected
[   12.019225][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.020160][  T191] ------------[ cut here ]------------
[   12.029054][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.031393][  T208] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 3-0008 for /pmic-glink/connector@1

🟡 ERROR (medium)

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

Context

[   12.007428][   T93] hub 1-0:1.0: 1 port detected
[   12.019225][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.020160][  T191] ------------[ cut here ]------------
[   12.029054][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.031393][  T208] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 3-0008 for /pmic-glink/connector@1
[   12.034508][  T191] WARNING: CPU: 5 PID: 191 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   12.051465][   T93] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller

🟡 WARNING (medium)

[   12.034508][  T191] WARNING: CPU: 5 PID: 191 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   12.020160][  T191] ------------[ cut here ]------------
[   12.029054][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.031393][  T208] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 3-0008 for /pmic-glink/connector@1
[   12.034508][  T191] WARNING: CPU: 5 PID: 191 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   12.051465][   T93] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[   12.056645][  T191] Modules linked in: mac80211 libarc4 cfg80211 rfkill mhi rpmsg_ctrl panel_edp(+)
[   12.068969][   T93] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 2

🟠 CALL_TRACE (high)

[   12.461646][  T191] Call trace:

Context

[   12.437496][  T191] x8 : ffff800084f5b518 x7 : 0000000000000000 x6 : 0000000000000001
[   12.445549][  T191] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   12.453593][  T191] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   12.461646][  T191] Call trace:
[   12.464882][  T191]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   12.471773][  T191]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   12.477602][  T191]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium)

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

Context

[   12.597827][  T191] ---[ end trace 0000000000000000 ]---
[   12.603307][  T191] panel-simple-dp-aux aux-aea0000.displayport-controller: Unknown panel BOE 0x0b21, using conservative timings
[   12.604149][  T350] qcom-hamoa-ec 2-0076: Unknown EC event: 0
[   12.604520][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.604523][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605911][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605914][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.603307][  T191] panel-simple-dp-aux aux-aea0000.displayport-controller: Unknown panel BOE 0x0b21, using conservative timings
[   12.604149][  T350] qcom-hamoa-ec 2-0076: Unknown EC event: 0
[   12.604520][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.604523][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605911][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605914][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610634][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.604149][  T350] qcom-hamoa-ec 2-0076: Unknown EC event: 0
[   12.604520][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.604523][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605911][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605914][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610634][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610636][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.604520][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.604523][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605911][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605914][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610634][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610636][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.604523][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605911][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605914][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610634][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610636][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611728][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.605911][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.605914][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610634][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610636][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611728][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612863][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.605914][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610634][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610636][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611728][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612863][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612866][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.610634][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.610636][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611728][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612863][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612866][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.617316][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.610636][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611728][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612863][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612866][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.617316][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.661641][  T195] ath12k_wifi7_pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned

🟡 ERROR (medium)

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

Context

[   12.611726][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.611728][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612863][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612866][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.617316][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.661641][  T195] ath12k_wifi7_pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned
[   12.670323][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.611728][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612863][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.612866][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.617316][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.661641][  T195] ath12k_wifi7_pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned
[   12.670323][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.680144][  T195] ath12k_wifi7_pci 0004:01:00.0: enabling device (0000 -> 0002)

🟡 ERROR (medium)

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

Context

[   12.612866][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.617316][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.661641][  T195] ath12k_wifi7_pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned
[   12.670323][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.680144][  T195] ath12k_wifi7_pci 0004:01:00.0: enabling device (0000 -> 0002)
[   12.690864][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.693840][  T200] Bluetooth: Core ver 2.22

🟡 ERROR (medium)

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

Context

[   12.661641][  T195] ath12k_wifi7_pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned
[   12.670323][   T93] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.680144][  T195] ath12k_wifi7_pci 0004:01:00.0: enabling device (0000 -> 0002)
[   12.690864][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.693840][  T200] Bluetooth: Core ver 2.22
[   12.693878][  T200] NET: Registered PF_BLUETOOTH protocol family
[   12.693880][  T200] Bluetooth: HCI device and connection manager initialized

🟡 ERROR (medium)

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

Context

[   12.693890][  T200] Bluetooth: L2CAP socket layer initialized
[   12.693898][  T200] Bluetooth: SCO socket layer initialized
[   12.699808][  T195] ath12k_wifi7_pci 0004:01:00.0: Wi-Fi 7 Hardware name: wcn7850 hw2.0
[   12.709565][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.720097][  T195] ath12k_wifi7_pci 0004:01:00.0: MSI vectors: 16
[   12.730293][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.794996][  T195] mhi mhi0: Requested to power ON

🟡 ERROR (medium)

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

Context

[   12.699808][  T195] ath12k_wifi7_pci 0004:01:00.0: Wi-Fi 7 Hardware name: wcn7850 hw2.0
[   12.709565][   T93] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.720097][  T195] ath12k_wifi7_pci 0004:01:00.0: MSI vectors: 16
[   12.730293][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.794996][  T195] mhi mhi0: Requested to power ON
[   12.795439][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.796015][  T350] qcom-hamoa-ec 2-0076: Unknown EC event: 0

🟡 ERROR (medium)

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

Context

[   12.720097][  T195] ath12k_wifi7_pci 0004:01:00.0: MSI vectors: 16
[   12.730293][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.794996][  T195] mhi mhi0: Requested to power ON
[   12.795439][   T93] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.796015][  T350] qcom-hamoa-ec 2-0076: Unknown EC event: 0
[   12.801191][  T195] mhi mhi0: Power on setup success
[   12.836608][  T200] usbcore: registered new interface driver btusb

🟡 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
[   34.101134][  T430] EXT4-fs (sda2): orphan cleanup on readonly fs
[   34.107733][  T430] EXT4-fs (sda2): mounted filesystem 2e16df27-6eab-4d72-84b7-a63f5340d8a3 ro with ordered data mode. Quota mode: none.
done.

Target: `qcs6490-rb3gen2`

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

🟡 ERROR (medium)

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

Context

[    6.856178][   T12] cpu cpu7: EM: created perf domain
[    6.860958][  T194] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.861174][  T194] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    6.861351][   T98] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    6.861364][   T98] cfg80211: failed to load regulatory.db
[    6.862502][  T193] CSCFG registered etm2
[    6.865114][  T181] remoteproc remoteproc0: modem is available

🟡 ERROR (medium)

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

Context

[    9.744505][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 21
[    9.774234][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 22
[    9.785412][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 23
[    9.803062][  T186] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.812918][  T186] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.858128][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 24
[    9.873432][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 25

🟡 ERROR (medium)

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

Context

[    9.774234][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 22
[    9.785412][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 23
[    9.803062][  T186] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.812918][  T186] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    9.858128][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 24
[    9.873432][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 25
[    9.899311][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 26

🟡 ERROR (medium)

[   10.020288][  T229] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

Context

[    9.980500][  T190] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator
[    9.991158][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@13: Adding to iommu group 29
[   10.009855][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@14: Adding to iommu group 30
[   10.020288][  T229] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   10.028590][  T229] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   10.085119][  T168] lt9611uxc 0-002b: LT9611 revision: 0x17.04.93
[   10.151835][  T168] lt9611uxc 0-002b: LT9611 version: 0x50

🟡 ERROR (medium)

[   10.028590][  T229] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

Context

[    9.991158][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@13: Adding to iommu group 29
[   10.009855][  T183] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@14: Adding to iommu group 30
[   10.020288][  T229] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   10.028590][  T229] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   10.085119][  T168] lt9611uxc 0-002b: LT9611 revision: 0x17.04.93
[   10.151835][  T168] lt9611uxc 0-002b: LT9611 version: 0x50
[   10.228492][  T168] msm_dpu ae01000.display-controller: bound ae94000.dsi (ops dsi_ops [msm])

🟡 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.131527][  T323] EXT4-fs (sda2): orphan cleanup on readonly fs
[   33.139952][  T323] EXT4-fs (sda2): mounted filesystem 698d30c1-1e68-4325-852e-0d99efa1467f ro with ordered data mode. Quota mode: none.
done.

Target: `qcs8300-ride`

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

🟡 WARNING (medium)

[    5.240637][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98

Context

[    5.236260][  T144] qcom-pcie 1c00000.pci: supply vddpe-3v3 not found, using dummy regulator
[    5.240342][   T64] qcom-pcie 1c10000.pci: supply vdda not found, using dummy regulator
[    5.240635][    T1] ------------[ cut here ]------------
[    5.240637][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98
[    5.240645][    T1] Modules linked in:
[    5.240649][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G S      W           6.18.44-g30fa759aa108 #1 PREEMPT 
[    5.240653][    T1] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN

🟠 CALL_TRACE (high)

[    5.240688][    T1] Call trace:

Context

[    5.240680][    T1] x8 : ffff800082c3bbe8 x7 : 0000000000000000 x6 : 0000000000000001
[    5.240683][    T1] x5 : ffff800080b41778 x4 : 000000000007706c x3 : 000000000007706c
[    5.240685][    T1] x2 : ffff800080b42e88 x1 : 0000000000000001 x0 : 0000000000000001
[    5.240688][    T1] Call trace:
[    5.240689][    T1]  phy_mux_is_enabled+0x7c/0x98 (P)
[    5.240692][    T1]  clk_core_is_enabled+0x44/0x120
[    5.240696][    T1]  clk_disable_unused_subtree+0x88/0x258

🟡 WARNING (medium)

[    5.240734][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98

Context

[    5.240713][    T1]  ret_from_fork+0x10/0x20
[    5.240716][    T1] ---[ end trace 0000000000000000 ]---
[    5.240733][    T1] ------------[ cut here ]------------
[    5.240734][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98
[    5.240737][    T1] Modules linked in:
[    5.240738][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G S      W           6.18.44-g30fa759aa108 #1 PREEMPT 
[    5.240741][    T1] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN

🟠 CALL_TRACE (high)

[    5.240771][    T1] Call trace:

Context

[    5.240764][    T1] x8 : ffff800082c3bbe8 x7 : 0000000000000000 x6 : 0000000000000001
[    5.240766][    T1] x5 : ffff800080b41778 x4 : 00000000000a906c x3 : 00000000000a906c
[    5.240769][    T1] x2 : ffff800080b42e88 x1 : 0000000000000001 x0 : 0000000000000001
[    5.240771][    T1] Call trace:
[    5.240772][    T1]  phy_mux_is_enabled+0x7c/0x98 (P)
[    5.240774][    T1]  clk_core_is_enabled+0x44/0x120
[    5.240777][    T1]  clk_disable_unused_subtree+0x88/0x258

🟡 ERROR (medium)

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

Context

[    9.606754][  T175] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    9.627809][   T12] qcom,apr 3000000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[    9.633270][  T175] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.638677][  T182] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.638677][  T182] :39
[    9.638744][   T12] qcom,apr 3000000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[    9.645243][  T175] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'

🟡 ERROR (medium)

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

Context

[    9.653630][  T251] msm_dpu ae01000.display-controller: bound ae94000.dsi (ops dsi_ops [msm])
[    9.656495][  T251] adreno 3d00000.gpu: supply vdd not found, using dummy regulator
[    9.657226][  T251] adreno 3d00000.gpu: supply vddcx not found, using dummy regulator
[    9.658049][  T182] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.658049][  T182] :43
[    9.668912][   T37] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.681555][  T251] msm_dpu ae01000.display-controller: bound 3d00000.gpu (ops a3xx_ops [msm])

🟡 ERROR (medium)

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

Context

[    9.657226][  T251] adreno 3d00000.gpu: supply vddcx not found, using dummy regulator
[    9.658049][  T182] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.658049][  T182] :43
[    9.668912][   T37] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.681555][  T251] msm_dpu ae01000.display-controller: bound 3d00000.gpu (ops a3xx_ops [msm])
[    9.690803][   T37] cfg80211: failed to load regulatory.db
[    9.700191][  T251] [drm:dpu_kms_hw_init:1201] dpu hardware revision:0x80040000

🟡 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
[   34.316459][  T361] EXT4-fs (sda2): orphan cleanup on readonly fs
[   34.325109][  T361] EXT4-fs (sda2): mounted filesystem 985e5d67-cfc5-4f20-bc82-74addca41f10 ro with ordered data mode. Quota mode: none.
done.

🟡 ERROR (medium)

[   36.173673][  T301] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   35.274720][    T1] Segment Routing with IPv6
[   35.279579][    T1] In-situ OAM (IOAM) with IPv6
[18t[   36.090754][   T43] refgen: disabling
[   36.173673][  T301] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.183970][  T301] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.194706][  T301] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.204000][  T301] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium)

[   36.194706][  T301] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[18t[   36.090754][   T43] refgen: disabling
[   36.173673][  T301] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.183970][  T301] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.194706][  T301] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.204000][  T301] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.211701][  T301] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.222597][  T301] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium)

[   36.222597][  T301] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.194706][  T301] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.204000][  T301] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.211701][  T301] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.222597][  T301] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.232063][  T301] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
7[32766;32766H[6n8[!p]104\[0m[?7h[1G[0J[   36.709985][    T1] systemd[1]: systemd 261.2 running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA +IPE -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +
[   36.743583][    T1] systemd[1]: Detected architecture arm64.

🟡 ERROR (medium)

[   36.758362][  T301] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   36.232063][  T301] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
7[32766;32766H[6n8[!p]104\[0m[?7h[1G[0J[   36.709985][    T1] systemd[1]: systemd 261.2 running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA +IPE -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +
[   36.743583][    T1] systemd[1]: Detected architecture arm64.
[   36.758362][  T301] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.768732][  T301] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.779467][  T301] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.788950][  T301] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium)

[   36.779467][  T301] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.743583][    T1] systemd[1]: Detected architecture arm64.
[   36.758362][  T301] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.768732][  T301] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.779467][  T301] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.788950][  T301] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.796654][  T301] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.796657][  T301] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium)

[   36.796657][  T301] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.779467][  T301] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.788950][  T301] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.796654][  T301] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.796657][  T301] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.796659][  T301] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)

[0;1;39mWelcome to [0m[1mQualcomm Linux Reference Distro 2.99+snapshot-d58a9f2dddfdeb4e74ef99929072ff6721590dc9[0m[0;1;39m![0m

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.554361][  T154] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22

Context

[    7.525623][   T48] qcom-pcie 45e8000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    7.539535][   T48] qcom-pcie 45e8000.pcie: host bridge /soc@0/pcie@45e8000 ranges:
[    7.548453][   T48] qcom-pcie 45e8000.pcie:       IO 0x0060200000..0x00602fffff -> 0x0000000000
[    7.554361][  T154] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    7.557973][   T48] qcom-pcie 45e8000.pcie:      MEM 0x0060300000..0x0063ffffff -> 0x0060300000
[    7.581357][  T142] geni_i2c 4a90000.i2c: Bus frequency not specified, default to 100kHz.
[    7.597816][  T154] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22

🟡 ERROR (medium)

[    7.597816][  T154] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22

Context

[    7.554361][  T154] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    7.557973][   T48] qcom-pcie 45e8000.pcie:      MEM 0x0060300000..0x0063ffffff -> 0x0060300000
[    7.581357][  T142] geni_i2c 4a90000.i2c: Bus frequency not specified, default to 100kHz.
[    7.597816][  T154] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.667195][  T154] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.691621][  T154] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.759568][   T48] qcom-pcie 45e8000.pcie: supply vdda not found, using dummy regulator

🟡 ERROR (medium)

[    7.667195][  T154] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22

Context

[    7.557973][   T48] qcom-pcie 45e8000.pcie:      MEM 0x0060300000..0x0063ffffff -> 0x0060300000
[    7.581357][  T142] geni_i2c 4a90000.i2c: Bus frequency not specified, default to 100kHz.
[    7.597816][  T154] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.667195][  T154] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.691621][  T154] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.759568][   T48] qcom-pcie 45e8000.pcie: supply vdda not found, using dummy regulator
[    7.787589][  T140] videodev: Linux video capture interface: v2.00

🟡 ERROR (medium)

[    7.691621][  T154] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22

Context

[    7.581357][  T142] geni_i2c 4a90000.i2c: Bus frequency not specified, default to 100kHz.
[    7.597816][  T154] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.667195][  T154] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.691621][  T154] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.759568][   T48] qcom-pcie 45e8000.pcie: supply vdda not found, using dummy regulator
[    7.787589][  T140] videodev: Linux video capture interface: v2.00
[    7.795406][   T48] qcom-pcie 45e8000.pcie: supply vddpe-3v3 not found, using dummy regulator

🟡 ERROR (medium)

[    9.881640][   T12] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17

Context

[    9.870224][  T145] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.875414][  T104] remoteproc remoteproc1: Booting fw image qcom/shikra/cdsp.mbn, size 2614680
[    9.881579][   T12] cpufreq-dt cpufreq-dt: failed register driver: -17
[    9.881640][   T12] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17
[    9.895362][  T163] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.912937][  T147] remoteproc remoteproc2: lpaicp is available
[    9.920785][  T163] cfg80211: failed to load regulatory.db

🟡 ERROR (medium)

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

Context

[    9.875414][  T104] remoteproc remoteproc1: Booting fw image qcom/shikra/cdsp.mbn, size 2614680
[    9.881579][   T12] cpufreq-dt cpufreq-dt: failed register driver: -17
[    9.881640][   T12] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17
[    9.895362][  T163] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.912937][  T147] remoteproc remoteproc2: lpaicp is available
[    9.920785][  T163] cfg80211: failed to load regulatory.db
[    9.932433][  T149] qcom-ethqos 5d20000.ethernet: IRQ eth_wake_irq not found

🟡 ERROR (medium)

[   10.456018][   T60] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110

Context

[   10.259568][  T104] remoteproc remoteproc1: remote processor cdsp is now up
[   10.311287][   T76] remoteproc remoteproc2: remote processor lpaicp is now up
[   10.328948][   T60] msm_dsi 5e94000.dsi: supply refgen not found, using dummy regulator
[   10.456018][   T60] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110
[   10.468033][  T155] irq: IRQ197: trimming hierarchy from :soc@0:interrupt-controller@f200000-1
[   10.479810][  T137] irq: IRQ198: trimming hierarchy from :soc@0:interrupt-controller@f200000-1
[   10.558208][  T145] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)

🟡 ERROR (medium)

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

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/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.595843][  T212] EXT4-fs (mmcblk0p53): orphan cleanup on readonly fs
[   27.605136][  T212] EXT4-fs (mmcblk0p53): mounted filesystem ba2ea611-e006-4021-a0ac-cfac76ce5228 ro with ordered data mode. Quota mode: none.
[   27.621903][  T212] mount (212) used greatest stack depth: 10144 bytes left

Target: `qcs9100-ride`

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

🟡 ERROR (medium)

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

Context

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

🟡 WARNING (medium)

[    4.654240][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.629513][    T1] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 (0,8000003f) counters available
[    4.648760][    T1] ------------[ cut here ]------------
[    4.654217][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.654240][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.670851][    T1] Modules linked in:
[    4.674714][    T1] CPU: 5 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.44-g30fa759aa108 #1 PREEMPT 
[    4.684266][    T1] Hardware name: Qualcomm Technologies, Inc. Lemans Ride Rev3 (DT)

🟠 CALL_TRACE (high)

[    4.795983][    T1] Call trace:

Context

[    4.771873][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002c9
[    4.779912][    T1] x5 : 00000000000002ca x4 : 40000000fffff2c9 x3 : 0000000000000000
[    4.787949][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.795983][    T1] Call trace:
[    4.799216][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.804941][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.810576][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 WARNING (medium)

[    4.907794][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.895420][    T1] ---[ end trace 0000000000000000 ]---
[    4.902329][    T1] ------------[ cut here ]------------
[    4.907783][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.907794][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.924391][    T1] Modules linked in:
[    4.928248][    T1] CPU: 5 UID: 0 PID: 1 Comm: swapper/0 Tainted: G        W           6.18.44-g30fa759aa108 #1 PREEMPT 
[    4.939400][    T1] Tainted: [W]=WARN

🟠 CALL_TRACE (high)

[    5.054900][    T1] Call trace:

Context

[    5.030788][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002f3
[    5.038824][    T1] x5 : 00000000000002f4 x4 : 40000000fffff2f3 x3 : 0000000000000000
[    5.046862][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    5.054900][    T1] Call trace:
[    5.058133][    T1]  notifier_chain_register+0x64/0x150 (P)
[    5.063856][    T1]  raw_notifier_chain_register+0x1c/0x30
[    5.069492][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 ERROR (medium)

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

Context

[    8.276574][   T64] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
[    8.285257][   T64] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    8.296950][   T64] qcom-pcie 1c00000.pcie: host bridge /pcie@1c00000 ranges:
[    8.297600][  T196] qcom_eud 88e1000.eud: error -ENODEV: failed to get controller node for path 0
[    8.304319][   T64] qcom-pcie 1c00000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000
[    8.307903][  T198] coresight stm0: STM32 initialized
[    8.309332][  T204] coresight cti_sys0: CTI initialized 0

🟡 ERROR (medium)

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

Context

[    9.611571][  T176] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@2215c000
[    9.628047][  T176] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@22154000
[    9.645777][   T85] qcom-pcie 1c00000.pcie: iATU: unroll T, 32 ob, 8 ib, align 4K, limit 1024G
[    9.646002][   T63] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.646002][   T63] :39
[    9.667822][   T63] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.667822][   T63] :43

🟡 ERROR (medium)

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

Context

[    9.645777][   T85] qcom-pcie 1c00000.pcie: iATU: unroll T, 32 ob, 8 ib, align 4K, limit 1024G
[    9.646002][   T63] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.646002][   T63] :39
[    9.667822][   T63] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.667822][   T63] :43
[    9.669766][  T176] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@22154000
[    9.696419][  T176] /soc@0/display-subsystem@22000000/displayport-controller@22154000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/display-controller@22001000

🟡 ERROR (medium)

[    9.750491][   T63] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f

Context

[    9.696419][  T176] /soc@0/display-subsystem@22000000/displayport-controller@22154000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/display-controller@22001000
[    9.714373][  T176] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@2215c000
[    9.731054][  T176] /soc@0/display-subsystem@22000000/displayport-controller@2215c000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/display-controller@22001000
[    9.750491][   T63] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.750491][   T63] :39
[    9.763520][   T63] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.763520][   T63] :43

🟡 ERROR (medium)

[    9.763520][   T63] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

Context

[    9.731054][  T176] /soc@0/display-subsystem@22000000/displayport-controller@2215c000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/display-controller@22001000
[    9.750491][   T63] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.750491][   T63] :39
[    9.763520][   T63] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.763520][   T63] :43
[    9.856434][   T85] qcom-pcie 1c00000.pcie: PCIe Gen.3 x1 link up
[    9.863012][   T85] qcom-pcie 1c00000.pcie: PCI host bridge to bus 0000:00

🟡 ERROR (medium)

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

Context

[   10.109392][   T63] msm_dpu 22001000.display-controller: bound 2215c000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   10.114713][  T186] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.127202][   T63] [drm:dpu_kms_hw_init:1201] dpu hardware revision:0x80040000
[   10.134822][  T236] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.151695][  T236] cfg80211: failed to load regulatory.db
[   10.159614][   T63] [drm] Initialized msm-kms 1.13.0 for 22001000.display-controller on minor 1
[   10.170920][   T63] msm_dpu 22001000.display-controller: no GPU device was found

🔵 FIRMWARE_FAIL (low)

[   11.360836][  T199] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22

Context

[   10.945402][  T206] platform 21c00000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 52
[   11.137641][  T261] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x207 soc_id 0x400c0210
[   11.147486][  T261] 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.360836][  T199] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   11.383106][  T199] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   11.550170][  T179] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[   12.240375][  T199] hwmon hwmon51: temp1_input not attached to any thermal zone

🟡 ERROR (medium)

[   11.383106][  T199] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22

Context

[   11.137641][  T261] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x207 soc_id 0x400c0210
[   11.147486][  T261] 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.360836][  T199] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   11.383106][  T199] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   11.550170][  T179] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[   12.240375][  T199] hwmon hwmon51: temp1_input not attached to any thermal zone
[   12.309404][  T179] qcom-ethqos 23000000.ethernet end1: renamed from eth0

🟡 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
[   31.405842][  T390] EXT4-fs (sda2): orphan cleanup on readonly fs
[   31.412447][  T390] EXT4-fs (sda2): mounted filesystem 57198697-7c20-47a4-944c-71a7b61d6a7e 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: 10 (0 critical, 0 high, 10 medium, 0 low)

🟡 ERROR (medium)

[    8.286921][  T126] usb usb2-port1: config error

Context

[    8.248607][  T202] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    8.267447][  T171] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 23
[    8.286038][  T202] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    8.286921][  T126] usb usb2-port1: config error
[    8.293031][  T202] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    8.305857][  T106] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.315532][  T106] cfg80211: failed to load regulatory.db

🟡 ERROR (medium)

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

Context

[    8.286038][  T202] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    8.286921][  T126] usb usb2-port1: config error
[    8.293031][  T202] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    8.305857][  T106] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.315532][  T106] cfg80211: failed to load regulatory.db
[    8.323925][  T184] Bluetooth: Core ver 2.22
[    8.324624][  T171] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 24

🟡 ERROR (medium)

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

Context

[    8.365503][  T184] Bluetooth: L2CAP socket layer initialized
[    8.368784][  T248] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)
[    8.371428][  T184] Bluetooth: SCO socket layer initialized
[    8.390315][  T248] tpm tpm0: A TPM error (256) occurred attempting the self test
[    8.394518][  T204] lt8713sx 2-004f: supply vcc not found, using dummy regulator
[    8.398114][  T248] tpm tpm0: starting up the TPM manually
[    8.411600][  T203] at24 1-0050: supply vcc not found, using dummy regulator

🟡 ERROR (medium)

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

Context

[    8.664984][  T171] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 27
[    8.686740][  T112] Bluetooth: hci0: QCA controller version 0x12110201
[    8.693482][  T112] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.700592][  T112] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.710083][  T112] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.718892][  T112] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.723169][  T126] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd

🟡 ERROR (medium)

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

Context

[    8.710083][  T112] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.718892][  T112] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.723169][  T126] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci-hcd
[    8.725724][  T112] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.743314][  T112] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.751468][  T112] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.753464][  T171] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 28

🟡 ERROR (medium)

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

Context

[    9.163434][  T126] hub 2-1:1.0: USB hub found
[    9.164681][  T126] hub 2-1:1.0: 4 ports detected
[    9.165093][  T202] mhi mhi0: Power on setup success
[    9.165309][  T112] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.165324][  T112] mhi mhi0: Error loading firmware: -2
[    9.171941][  T172] usbcore: registered new device driver onboard-usb-dev
[    9.173340][  T248] qcom-ethqos 23040000.ethernet: TX Checksum insertion supported

🟡 ERROR (medium)

[    9.165324][  T112] mhi mhi0: Error loading firmware: -2

Context

[    9.164681][  T126] hub 2-1:1.0: 4 ports detected
[    9.165093][  T202] mhi mhi0: Power on setup success
[    9.165309][  T112] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.165324][  T112] mhi mhi0: Error loading firmware: -2
[    9.171941][  T172] usbcore: registered new device driver onboard-usb-dev
[    9.173340][  T248] qcom-ethqos 23040000.ethernet: TX Checksum insertion supported
[    9.177984][  T202] ath11k_pci 0000:01:00.0: failed to power up mhi: -110

🟡 ERROR (medium)

[    9.584893][  T202] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110

Context

[    9.445250][  T185] qcom-ethqos 23040000.ethernet end0: renamed from eth0
[    9.531803][   T64] hub 1-1:1.0: USB hub found
[    9.537187][   T64] hub 1-1:1.0: 4 ports detected
[    9.584893][  T202] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110
[    9.755744][   T64] hub 1-1:1.0: USB hub found
[    9.756943][  T172] hub 2-1:1.0: USB hub found
[    9.761105][   T64] hub 1-1:1.0: 4 ports detected

🟡 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
[   31.879186][  T357] EXT4-fs (sda2): orphan cleanup on readonly fs
[   31.887951][  T357] EXT4-fs (sda2): mounted filesystem 513728bc-9c18-4a66-a6fb-01735755aeed ro with ordered data mode. Quota mode: none.
done.

qcomlnxci · 2026-09-18T20:34:31Z

Test jobs on ea0b4ad

qcomlnxci · 2026-09-18T20:34:33Z

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
BT_FW_KMD_Service	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
BT_ON_OFF	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
BT_SCAN	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
CPUFreq_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	◻️	✅ Pass	⚠️ skip	◻️	◻️	❌ Fail	❌ Fail	⚠️ skip
Freq_Scaling	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	◻️	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	◻️	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	◻️	✅ Pass	❌ Fail	◻️	◻️	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	◻️	❌ Fail	❌ Fail	◻️	◻️	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	◻️	❌ Fail	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	◻️	❌ Fail	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	◻️	✅ Pass	⚠️ skip	◻️	◻️	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	◻️	✅ Pass	❌ Fail	◻️	◻️	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	◻️	✅ Pass	✅ Pass	◻️	◻️	✅ Pass	✅ Pass	✅ Pass

qcomlnxci · 2026-09-18T23:19:39Z

Test jobs on ea0b4ad

qcomlnxci · 2026-09-18T23:19:42Z

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	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ 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	✅ Pass	◻️	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	❌ Fail	✅ 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	✅ 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	❌ Fail
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	◻️	❌ Fail	❌ 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	✅ Pass	❌ Fail	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass	✅ 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	✅ Pass	◻️	⚠️ 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	✅ Pass
shmbridge	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	❌ Fail	✅ Pass	◻️	❌ Fail	✅ Pass	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass

Salendarsingh Gaud (sgaud-quic) · 2026-09-19T04:00:42Z

Shivam Rawat (@shivrawa) please check crash on purwa device :
https://lava-oss.qualcomm.com/scheduler/job/232514

[   39.147708][  T801] CPU: 3 UID: 0 PID: 801 Comm: cdsprpcd Tainted: G        W           6.18.44-g9a727a423861 #1 PREEMPT 
[   39.147710][  T801] Tainted: [W]=WARN
[   39.147711][  T801] Hardware name: Qualcomm Technologies, Inc. Purwa IoT EVK (DT)
[   39.147712][  T801] pstate: 81400005 (Nzcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
[   39.147714][  T801] pc : dma_unmap_sg_attrs+0x15c/0x1b0
[   39.147720][  T801] lr : system_heap_unmap_dma_buf+0x38/0x50
[   39.147724][  T801] sp : ffff80009e76bab0
[   39.147725][  T801] x29: ffff80009e76bab0 x28: ffff0008416514c0 x27: 0000000000000000
[   39.147727][  T801] x26: 0000000000000000 x25: 6b6b6b6b6b6b6b6b x24: 0000000000000000
[   39.147730][  T801] x23: 0000000000000000 x22: 0000000000000004 x21: ffff000825776e00
[   39.147732][  T801] x20: 0000000000000000 x19: ffff000815704c10 x18: 00000000ffffffff
[   39.147734][  T801] x17: 632d657475706d6f x16: 633a637072747361 x15: 663a656764652d6b
[   39.147736][  T801] x14: 6e696c673a636f72 x13: 205d313038542020 x12: 5b5d313934353231
[   39.147738][  T801] x11: 3064656537666666 x10: ffff800082692860 x9 : ffff800080b661b8
[   39.147740][  T801] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 0000000000000001
[   39.147742][  T801] x5 : ffff00082d55f948 x4 : 0000000000000000 x3 : 0000000000000000
[   39.147744][  T801] x2 : 0000000000000004 x1 : ffff000825776e00 x0 : 6b6b6b6b6b6b6b6b
[   39.147746][  T801] Call trace:
[   39.147748][  T801]  dma_unmap_sg_attrs+0x15c/0x1b0 (P)
[   39.147750][  T801]  system_heap_unmap_dma_buf+0x38/0x50
[   39.147752][  T801]  dma_buf_unmap_attachment+0x7c/0xb8
[   39.147755][  T801]  dma_buf_unmap_attachment_unlocked+0x80/0xa8
[   39.147757][  T801]  fastrpc_free_map+0x94/0x160 [fastrpc]
[   39.147761][  T801]  fastrpc_req_mem_map+0x2a8/0x2c0 [fastrpc]
[   39.147763][  T801]  fastrpc_device_ioctl+0x114/0x1210 [fastrpc]
[   39.147764][  T801]  __arm64_sys_ioctl+0xb4/0x118
[   39.147768][  T801]  invoke_syscall+0x4c/0xf8
[   39.147771][  T801]  el0_svc_common.constprop.0+0x48/0xf0
[   39.147772][  T801]  do_el0_svc+0x24/0x38
[   39.147774][  T801]  el0_svc+0x3c/0x110
[   39.147777][  T801]  el0t_64_sync_handler+0xa0/0xe8
[   39.147779][  T801]  el0t_64_sync+0x19c/0x1a0
[   39.147782][  T801] Code: f94023f9 a8c57bfd d50323bf d65f03c0 (f9402725) 
[   39.147784][  T801] ---[ end trace 0000000000000000 ]---
[   39.151157][   T93] qcom_q6v5_pas 32300000.remoteproc: failed to shutdown dtb: -22
[   39.615400][   T93] remoteproc remoteproc1: can't stop rproc: -22
         Starting [0;1;39mEthernet Bridge Filtering Tables[0m...
         Starting [0;1;39mIPv6 Packet Filtering Framework[0m...
         Starting [0;1;39mIPv4 Packet Filtering Framework[0m...
         Starting [0;1;39mTelephony service[0m...
[[0;32m  OK  [0m] Started [0;1;39mPipeWire Multimedia Service[0m.
[   50.569704][  T801] Kernel panic - not syncing: Oops: Fatal exception

Salendarsingh Gaud (sgaud-quic) · 2026-09-19T06:03:54Z

Bluetooth failure on shikra is baseline issue.

Shivam Rawat (shivrawa) · 2026-09-19T06:35:16Z

Salendarsingh Gaud (@sgaud-quic) okay so this PR is not the culprit, right?

(just wondering how the Bluetooth issue on shikra will crash the purwa )

Shivam Rawat (shivrawa) · 2026-09-19T07:24:46Z

Salendarsingh Gaud (@sgaud-quic) by looking at the call trace of the crash, the failure comes from the fastrpc not from the Graphics. fastrpc team to check the issue. ( It's highly unlikely that enabling the configs related to the GPU virtualization will cause a crash.)

[ 39.147757][ T801] fastrpc_free_map+0x94/0x160 [fastrpc]
[ 39.147761][ T801] fastrpc_req_mem_map+0x2a8/0x2c0 [fastrpc]
[ 39.147763][ T801] fastrpc_device_ioctl+0x114/0x1210 [fastrpc]

Salendarsingh Gaud (sgaud-quic) · 2026-09-19T07:50:37Z

Salendarsingh Gaud (Salendarsingh Gaud (@sgaud-quic)) by looking at the call trace of the crash, the failure comes from the fastrpc not from the Graphics. fastrpc team to check the issue. ( It's highly unlikely that enabling the configs related to the GPU virtualization will cause a crash.)

[ 39.147757][ T801] fastrpc_free_map+0x94/0x160 [fastrpc] [ 39.147761][ T801] fastrpc_req_mem_map+0x2a8/0x2c0 [fastrpc] [ 39.147763][ T801] fastrpc_device_ioctl+0x114/0x1210 [fastrpc]

Tracking this issue with : #1138

qcomlnxci · 2026-09-19T08:19:30Z

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 · 2026-09-19T08:19:31Z

Test jobs on ea0b4ad

qlijarvis · 2026-09-19T23:51:33Z

LAVA Failed Case Triage Summary

PR: #1118

Job 232133 | SoC hamoa-evk

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Could not be determined confidently from available logs.

Possible fix: No action required for PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 — all failures are pre-existing and unrelated to GPU virtualization config changes. To clean up the test results: (1) Add QSEE UEFI secure app DT node or disable the driver if not needed on hamoa-evk, (2) Fix the LPG multi-LED DT reg property in arch/arm64/boot/dts/qcom/x1e80100.dtsi or board DTS, (3) Add regulatory.db to rootfs firmware directory or suppress this known-benign failure in the test script.

Detail analysis attachment: failed_case_job232133_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Test expects USB PHY devices (a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb) and video codec (aa00000.video-codec) to have IOMMU group attachments, but these devices are not present in the device tree or are not configured with IOMMU bindings on hamoa-evk platform.

Possible fix: This is a test expectation issue, not a kernel regression. The SMMU subsystem is functioning correctly (no SMMU/IOMMU errors in dmesg, 35 platform devices properly attached to IOMMU groups). The failing devices appear to be USB PHY controllers and video codec that may not require IOMMU protection on this platform. Update the smmu test to exclude these optional devices from the critical master check on hamoa-evk, or add IOMMU bindings to the device tree if these devices should be protected.

Detail analysis attachment: failed_case_job232133_2_detailed.md

Case 3: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM subsystem cannot initialize on hamoa-evk because EL2/HYP mode is not available to the kernel — kernel log shows kvm [1]: HYP mode not available at boot; this is a platform hardware/firmware limitation where the CPU hypervisor extensions are not accessible, likely due to secure firmware running at EL2 or bootloader policy.

Possible fix: This is NOT a kernel bug or PR-introduced regression. The PR only enables DRM VirtIO GPU configs which are unrelated to KVM host functionality. The test failure is expected on this platform. To resolve: (1) verify if hamoa-evk is intended to support KVM — if not, exclude KVM tests from this target's CI suite; (2) if KVM support is required, work with firmware/bootloader team to enable EL2 access for Linux kernel (check secure boot policy, TrustZone configuration, and bootloader EL2 handoff); (3) as a workaround, disable CONFIG_KVM in the kernel config for this platform if virtualization is not a requirement.

Detail analysis attachment: failed_case_job232133_3_detailed.md

Case 4: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM driver initialization failed with "HYP mode not available" because the hamoa-evk platform boots without EL2 (hypervisor) access — the hypervisor (hypvm.mbn) is running at EL2 and the Linux kernel is running as a guest at EL1, preventing KVM from initializing the /dev/kvm device node.

Possible fix: This is not a kernel regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables DRM VirtIO GPU config options). The failure is a pre-existing platform limitation: hamoa-evk does not support nested virtualization (KVM requires EL2 access, but the kernel runs under a hypervisor at EL1). The KVM tests should be excluded from the hamoa-evk CI test suite, or the platform firmware should be configured to boot Linux at EL2 (non-virtualized mode) if KVM testing is required.

Detail analysis attachment: failed_case_job232133_4_detailed.md

Case 5: KVM Infrastructure Test Failure — KVM driver initialization blocked by hypervisor

Failed case: KVM Infrastructure Test Failure — KVM driver initialization blocked by hypervisor

Root cause: KVM driver reports "HYP mode not available" because the Gunyah hypervisor is already running at EL2 (HYP mode), preventing the Linux kernel from initializing KVM. On hamoa-evk (X1E80100), the Gunyah hypervisor boots at EL2 before the kernel, occupying the privilege level required for KVM operation. This is a platform-specific configuration where the hypervisor and KVM cannot coexist — only one can control EL2.

Possible fix: This is not a kernel bug or PR-introduced regression. The PR only enables GPU virtualization drivers (CONFIG_DRM_VIRTIO_GPU) and does not affect KVM or hypervisor initialization. To enable KVM on hamoa-evk, the platform must boot without the Gunyah hypervisor, or KVM must be disabled in the kernel config. For CI purposes, either: (1) exclude KVM tests from hamoa-evk test suite since the platform runs Gunyah hypervisor by design, or (2) provide a separate boot configuration without Gunyah for KVM testing.

Detail analysis attachment: failed_case_job232133_5_detailed.md

Case 6: KVM_Infra — KVM infrastructure test

Failed case: KVM_Infra — KVM infrastructure test

Root cause: The hamoa-evk platform does not support EL2 (Hypervisor) mode, which is a hardware/firmware prerequisite for KVM. The kernel correctly detects this at boot time and reports "HYP mode not available", preventing the creation of /dev/kvm. This is a platform limitation, not a kernel regression.

Possible fix: This is not a bug that can be fixed in the kernel. The test should be skipped on platforms that do not support EL2/HYP mode. Add a platform capability check to the LAVA job definition to skip KVM tests on hamoa-evk, or update the test to report SKIP instead of FAIL when /dev/kvm is unavailable due to missing HYP mode support.

Detail analysis attachment: failed_case_job232133_6_detailed.md

Job 232134 | SoC qcs8300-ride

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Two pre-existing probe failures detected by the test: (1) cfg80211 regulatory.db firmware file missing from rootfs (benign - WiFi driver loads successfully without it), and (2) Aquantia AQR115C Ethernet PHY driver probe failure due to missing firmware-name DT property (error -22 = -EINVAL). Neither failure is introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (GPU virtualization config changes). No baseline available to confirm, but both failures are unrelated to DRM VirtIO GPU config additions.

Possible fix: These are pre-existing platform issues unrelated to the PR. (1) regulatory.db: benign - cfg80211 falls back to built-in regulatory data; no action needed unless regulatory compliance requires the file. (2) Aquantia PHY: add firmware-name property to the stmmac-0:08 PHY node in qcs8300-ride DT, or confirm the PHY variant does not require firmware. The Probe_Failure_Check test should be updated to suppress known-benign firmware load failures (regulatory.db) to reduce false positives.

Detail analysis attachment: failed_case_job232134_1_detailed.md

Case 2: ** Ethernet_Basic_Validation — PHY Probe Failure

Failed case: ** Ethernet_Basic_Validation — PHY Probe Failure

Root cause: ** Aquantia AQR115C PHY driver probe failed with error -22 (EINVAL) at boot time due to missing firmware-name device tree property. When the Ethernet test attempts to bring up eth0, the stmmac driver cannot attach to the PHY because the PHY device was never successfully probed and registered on the MDIO bus.

Possible fix: This is a pre-existing platform/device-tree issue, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only adds GPU virtualization config). Add the missing firmware-name property to the qcs8300-ride device tree PHY node: firmware-name = "Rhe-05.06-Candidate9-AQR_Mediatek_23B_P5_ID45824_LCLVER1.cld"; (or the appropriate firmware file for this PHY revision). Ensure the firmware file is present in /lib/firmware/ on the rootfs. Alternatively, if firmware loading is not required for this PHY configuration, patch the Aquantia driver to tolerate the missing property and continue probe without firmware.

Detail analysis attachment: failed_case_job232134_2_detailed.md

Case 3: KVM_Driver

Failed case: KVM_Driver

Root cause: Could not be determined confidently from available logs.

Possible fix: This is a test environment configuration issue, not a kernel regression. The KVM_Driver test should be skipped on platforms that run Linux as a hypervisor guest (qcs8300-ride, and likely other platforms in the same family). Add a platform-specific test skip rule in the LAVA test definition for qcs8300-ride and similar Gunyah-guest platforms. Alternatively, if nested virtualization is a requirement, enable it in the Gunyah hypervisor configuration and verify that KVM can operate in nested mode.

Detail analysis attachment: failed_case_job232134_3_detailed.md

Case 4: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM driver failed to initialize on qcs8300-ride (Monaco SoC) — CONFIG_KVM is enabled but /dev/kvm device node was never created, indicating KVM initialization silently failed during boot, likely due to missing VHE (Virtualization Host Extensions) support or EL2 hypervisor mode unavailability on this platform.

Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression (PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 only adds GPU virtualization configs). Verify whether qcs8300-ride/Monaco SoC supports ARM virtualization extensions (VHE/EL2) in hardware and firmware. If supported, check bootloader/firmware configuration to ensure EL2 mode is enabled. If not supported, mark KVM tests as "skip" for this platform in the CI test matrix.

Detail analysis attachment: failed_case_job232134_4_detailed.md

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

Failed case: KVM Infrastructure Test Failure — /dev/kvm device node not created

Root cause: KVM kernel module failed to initialize on qcs8300-ride (Monaco) platform because the SoC does not support ARM Virtualization Host Extensions (VHE) or EL2 hypervisor mode required for KVM operation; CONFIG_KVM is enabled in kernel config but KVM driver silently skips initialization when hardware virtualization support is absent, resulting in no /dev/kvm device node creation.

Possible fix: This is not a kernel regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables DRM VirtIO GPU configs). The KVM test failure is a pre-existing platform limitation — qcs8300 (Monaco) SoC does not provide the ARM virtualization extensions required for KVM. The test suite should either: (1) skip KVM tests on platforms without VHE/EL2 support by checking CPU features before running tests, or (2) mark qcs8300-ride as a known-unsupported platform for KVM tests in the CI configuration. No kernel code fix is required.

Detail analysis attachment: failed_case_job232134_5_detailed.md

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

Failed case: 0_qcom-next-ci-premerge-tests

Root cause: KVM driver fails to create /dev/kvm device node despite CONFIG_KVM=y being enabled in kernel config; all three KVM test cases (KVM_Driver, KVM_EL2_DTB, KVM_Infra) fail with "device not available" error on qcs8300-ride platform.

Possible fix: Investigate why KVM driver is not initializing on qcs8300-ride: check dmesg for KVM probe failures or missing hypervisor support; verify platform supports EL2/VHE extensions; ensure KVM module is loaded (lsmod | grep kvm); check if hypervisor is blocking KVM initialization; if KVM is not supported on this platform, mark these tests as expected failures for qcs8300-ride.

Detail analysis attachment: failed_case_job232134_6_detailed.md

Job 232135 | SoC qcs9100-ride

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Test detected pre-existing probe failures and deferred probe issues on qcs9100-ride: (1) Four SPMI PMIC temp-alarm devices remain in deferred probe state due to missing thermal zone dependencies; (2) WiFi regulatory database firmware file (regulatory.db) not present in rootfs; (3) Aquantia AQR115C Ethernet PHY probe fails with -EINVAL (-22) due to missing or malformed firmware-name device tree property.

Possible fix: These are pre-existing platform/infrastructure issues unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). No kernel code fix required. To resolve: (1) For temp-alarm deferred probes — ensure thermal zone device tree nodes are present and probe before PMIC temp-alarm drivers, or suppress these warnings if thermal monitoring is not required on this platform; (2) For regulatory.db — add wireless-regdb package to rootfs or suppress this benign warning (WiFi functional tests pass despite this); (3) For Aquantia PHY — add correct firmware-name property to device tree node for stmmac-0:08, or confirm PHY firmware is not required for this board configuration.

Detail analysis attachment: failed_case_job232135_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: The smmu test detected that the video codec device aa00000.video-codec is missing IOMMU group attachment, while the test expects all critical masters (including video codec) to be protected by IOMMU. The device node aa00000.video-codec exists in the test's expected device list but is not present in the runtime system, likely because the video codec driver (iris) did not probe or bind to this device node. The iris driver created virtual devices iris_non_pixel.0 and iris_pixel.0 which are correctly attached to IOMMU groups 20 and 22, but the parent device aa00000.video-codec itself is not attached to any IOMMU group.

Possible fix: This is a pre-existing test infrastructure issue, not a regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The test expects the legacy device node naming aa00000.video-codec but the iris video driver creates child devices with different names. Update the smmu test's expected device list to check for iris_non_pixel.0 and iris_pixel.0 instead of aa00000.video-codec, or ensure the parent video codec device is also registered with IOMMU groups during driver probe.

Detail analysis attachment: failed_case_job232135_2_detailed.md

Case 3: Ethernet_Basic_Validation

Failed case: Ethernet_Basic_Validation

Root cause: The qcom-ethqos driver for interface end0 (23040000.ethernet) fails to attach to its PHY with error -EINVAL during interface bring-up; the PHY attachment failure prevents the interface from transitioning to an operational state, causing the test to fail when attempting to bring the interface administratively up.

Possible fix: This is a pre-existing platform/board configuration issue unrelated to the PR changes (PR only enables GPU virtualization config options). The -EINVAL error from PHY attach typically indicates a device tree mismatch between the Ethernet controller's phy-handle property and the actual PHY node, or missing/incorrect PHY configuration. Verify the qcs9100-ride device tree: (1) confirm the phy-handle phandle in the ethernet@23040000 node points to a valid PHY node, (2) check that the PHY node has correct reg/compatible properties, (3) ensure the MDIO bus is properly configured and the PHY address matches hardware. If DT is correct, check for PHY driver probe failures earlier in boot. This is a board-specific hardware/DT issue, not a kernel regression introduced by this PR.

Detail analysis attachment: failed_case_job232135_3_detailed.md

Case 4: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM cannot initialize on qcs9100-ride because the platform is running under the Gunyah hypervisor in EL2, preventing KVM from accessing HYP mode. The kernel message kvm [1]: HYP mode not available at boot confirms that KVM detected it cannot run because EL2 is already occupied by the hypervisor.

Possible fix: This is a platform/board configuration issue, not a kernel regression. The KVM_Driver test should be skipped on qcs9100-ride when running under Gunyah hypervisor. Add a test precondition check for hypervisor presence (detect "Hypervisor cold boot" in dmesg or check /sys/hypervisor/type) and skip KVM tests when a hypervisor is active. Alternatively, configure the board to boot without Gunyah if KVM testing is required.

Detail analysis attachment: failed_case_job232135_4_detailed.md

Case 5: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM cannot initialize on qcs9100-ride because the platform boots under the Gunyah hypervisor, which occupies EL2 (Hypervisor mode). The kernel message "kvm [1]: HYP mode not available" at boot confirms that KVM detected EL2 is unavailable, preventing /dev/kvm creation. This is a platform/firmware configuration issue, not a kernel regression.

Possible fix: This is not a PR-introduced failure. The qcs9100-ride platform is configured to run under Gunyah hypervisor (boot log shows "Hypervisor cold boot, version: gunyah-cdfb73831"), which prevents nested virtualization. To enable KVM on this platform, either: (1) disable Gunyah hypervisor in the firmware/bootloader configuration to allow Linux to run at EL2, or (2) if nested virtualization is required, configure Gunyah to expose virtual EL2 to the guest kernel (requires Gunyah firmware support for nested virtualization). The PR (enabling DRM VirtIO GPU configs) is unrelated to this failure.

Detail analysis attachment: failed_case_job232135_5_detailed.md

Case 6: KVM Infrastructure Test — Platform Limitation

Failed case: KVM Infrastructure Test — Platform Limitation

Root cause: qcs9100-ride platform does not provide EL2 (hypervisor) mode support; bootloader skips hypervisor DT setup for non-Gunyah configurations, and kernel reports "HYP mode not available", preventing KVM initialization and /dev/kvm creation.

Possible fix: This is a platform hardware/firmware limitation, not a kernel bug. To enable KVM on qcs9100-ride: (1) verify the SoC supports virtualization extensions, (2) configure the bootloader/firmware to boot in EL2 mode with hypervisor support enabled, (3) ensure the device tree includes proper hypervisor nodes. If the platform does not support EL2, KVM tests should be excluded from the CI test suite for this target.

Detail analysis attachment: failed_case_job232135_6_detailed.md

Case 7: KVM_Infra

Failed case: KVM_Infra

Root cause: /dev/kvm device node is not present on qcs9100-ride platform despite CONFIG_KVM being enabled in kernel config — KVM driver did not create the device node, indicating either: (1) KVM initialization failed silently during boot, (2) platform lacks hardware virtualization support (EL2/VHE), or (3) hypervisor/firmware blocked KVM from initializing.

Possible fix: Check dmesg for KVM initialization messages (grep -i kvm /var/log/dmesg or dmesg | grep -i kvm); verify CPU supports virtualization extensions (grep -E 'vhe|el2' /proc/cpuinfo); confirm no hypervisor is already running that would prevent KVM from loading (dmesg | grep -i hyp); if KVM module failed to load, check modprobe kvm output and kernel logs for the specific error.

Detail analysis attachment: failed_case_job232135_7_detailed.md

Job 232136 | SoC shikra-iqs-evk

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

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

Case 1: GIC (Test Infrastructure Bug — Not a Kernel Issue)

Failed case: GIC (Test Infrastructure Bug — Not a Kernel Issue)

Root cause: The GIC test script hardcodes an assumption of 8 CPUs and attempts to parse interrupt counts for CPUs 4-7 from /proc/interrupts, but the shikra-iqs-evk board only has 4 CPUs (0-3). When the script tries to extract the 5th-8th columns (CPUs 4-7), it instead reads non-numeric fields like "GICv3", "Level", and "arch_timer", causing bash integer comparison errors at line 75. All 4 actual CPUs (0-3) passed the timer increment test correctly.

Possible fix: Update the GIC test script to dynamically detect the number of online CPUs from /sys/devices/system/cpu/online or /proc/cpuinfo instead of hardcoding 8 CPUs. The script should only validate timer increments for CPUs that actually exist on the target platform. This is a test infrastructure fix, not a kernel fix — the PR changes (GPU virtualization config) are unrelated and do not cause this failure.

Detail analysis attachment: failed_case_job232136_1_detailed.md

Case 2: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Pre-existing platform-specific driver probe failures on shikra-iqs-evk unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (GPU virtualization config changes). The PR only enables DRM_VIRTIO_GPU kernel config options which do not affect coresight-etm4x, cpufreq-dt, tpm_tis_spi, or regulatory.db firmware loading. All probe failures are hardware/platform-specific issues: coresight-etm4x fails with -EINVAL (-22) due to missing/incorrect ETM device tree configuration, cpufreq-dt fails with -EEXIST (-17) indicating duplicate registration attempt, tpm_tis_spi fails with -ETIMEDOUT (-110) indicating SPI communication timeout, and regulatory.db firmware load fails with -ENOENT (-2) as the file is not present in the rootfs.

Possible fix: These are known pre-existing platform issues on shikra-iqs-evk and should be suppressed in CI or fixed independently. The PR is not the root cause. To confirm: (1) Check baseline logs for shikra-iqs-evk on qcom-6.18.y branch — these failures should be present there too (baseline comparison shows "no baseline available" so cannot confirm, but the boot comparison report lists 9 medium-severity boot issues for shikra-iqs-evk, all unrelated to GPU virtualization). (2) The Probe_Failure_Check test should be updated to exclude known benign probe failures or platform-specific issues that do not indicate kernel regressions. (3) For proper fixes: coresight-etm4x requires DT correction for ETM nodes, cpufreq-dt needs investigation of duplicate driver registration, tpm_tis_spi needs SPI bus/timing investigation, regulatory.db needs to be added to rootfs or the test should ignore this benign firmware-missing error.

Detail analysis attachment: failed_case_job232136_2_detailed.md

Case 3: PCIe — Missing QPS615 PCIe Switch Firmware

Failed case: PCIe — Missing QPS615 PCIe Switch Firmware

Root cause: The PCIe test failed because the required firmware file TC956X_Firmware_PCIeBridge.bin for the QPS615 PCIe switch (Toshiba TC956X) is not present in the rootfs /lib/firmware directory. This is a test infrastructure/rootfs packaging issue, not a kernel driver or PCIe hardware failure — all PCIe functional checks passed (link up, devices enumerated, drivers bound, MSI working).

Possible fix: Add the TC956X_Firmware_PCIeBridge.bin firmware file to the rootfs image under /lib/firmware/ or /lib/firmware/qcom/ directory. This firmware is required for the QPS615 PCIe switch validation test but is not needed for basic PCIe functionality. This failure is not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs) — it is a pre-existing rootfs/test infrastructure issue.

Detail analysis attachment: failed_case_job232136_3_detailed.md

Case 4: USBHost — USB Host Controller Not Initialized

Failed case: USBHost — USB Host Controller Not Initialized

Root cause: USB host controller driver (DWC3/xHCI) did not probe or initialize on shikra-iqs-evk; the USB platform device (4e00000.usb) was registered and added to IOMMU group 5, but no USB root hubs were exposed, and lsusb failed to enumerate the bus, indicating the host controller driver never completed initialization despite no kernel errors being logged for USB/DWC3/xHCI modules.

Possible fix: This is a pre-existing platform/board configuration issue unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The shikra-iqs-evk board's USB controller is configured in device/gadget mode by default (systemd reached "Hardware activated USB gadget" target), not host mode. To enable USB host mode: (1) verify the device tree USB node has dr_mode = "host" or dr_mode = "otg" with appropriate role-switch configuration; (2) if using OTG, ensure the USB role switch driver is enabled and the board is configured for host role; (3) check that DWC3 and xHCI drivers are built-in or loaded as modules; (4) verify USB PHY (phy@1615000) is properly initialized. Since this failure also occurs on the baseline (no baseline available for comparison, but the issue pattern suggests a board-specific configuration), this is NOT a PR-introduced regression.

Detail analysis attachment: failed_case_job232136_4_detailed.md

Case 5: BT_FW_KMD_Service

Failed case: BT_FW_KMD_Service

Root cause: Bluetooth HCI UART driver (hci_uart/btqca) cannot communicate with WCN399x Bluetooth hardware on shikra-iqs-evk — repeated "command 0xfc00 tx timeout" and "Reading QCA version information failed (-110)" errors indicate the UART transport to the Bluetooth chip is non-functional or the chip is not powered/clocked correctly.

Possible fix: Verify shikra-iqs-evk device tree Bluetooth UART node (serial port, pinctrl, clocks, regulators, enable-gpios) and confirm WCN399x chip power sequencing; check if PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (GPU virtualization config changes) inadvertently disabled a shared dependency (e.g., a regulator, clock, or pinctrl config) required by both GPU and Bluetooth subsystems; if DT is correct, investigate UART hardware/firmware initialization on this SoC.

Detail analysis attachment: failed_case_job232136_5_detailed.md

Case 6: **Bluetooth Driver Runtime Communication Failure — BT_ON_OFF**

Failed case: Bluetooth Driver Runtime Communication Failure — BT_ON_OFF

Root cause: Bluetooth hci0 adapter (Qualcomm WCN399x) fails to respond to HCI commands during runtime initialization, producing repeated command tx timeouts (-110 ETIMEDOUT) when attempting to read QCA version information; the Bluetooth hardware/firmware is not responding to driver commands, preventing the adapter from acquiring a valid BD address and becoming operational.

Possible fix: This is a hardware/firmware communication failure on the shikra-iqs-evk platform, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs unrelated to Bluetooth). Recommended actions: (1) Verify WCN399x Bluetooth hardware is properly powered and clocked on the shikra-iqs-evk board — check regulators, clocks, and reset lines in the device tree for the Bluetooth node; (2) Confirm Bluetooth firmware files (qca/.tlv, qca/.bin) are present and correct for WCN399x hw2.0; (3) Check for known errata or firmware bugs for WCN399x on this SoC revision; (4) If the issue persists, capture detailed HCI traces and UART logs to determine if the hardware is responding at all or if there is a lower-level bus/power issue; (5) Since no baseline exists for shikra-iqs-evk, establish a known-good baseline build to confirm whether this is a regression or a pre-existing platform limitation.

Detail analysis attachment: failed_case_job232136_6_detailed.md

Case 7: BT_SCAN — Bluetooth Runtime Initialization Failure

Failed case: BT_SCAN — Bluetooth Runtime Initialization Failure

Root cause: Bluetooth HCI controller (WCN399x on shikra-iqs-evk) fails to respond to HCI commands during initialization; repeated command tx timeouts (-110 ETIMEDOUT) when attempting to read QCA version information prevent firmware loading and BD address assignment, leaving adapter hci0 in unusable state with invalid BD address 00:00:00:00:00:00.

Possible fix: This is a pre-existing hardware/firmware communication issue unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (GPU virtualization config changes). The failure occurs consistently from early boot (10.6s) through all test recovery attempts. Recommended actions: (1) Verify WCN399x Bluetooth hardware power/clock/reset sequencing on shikra-iqs-evk; (2) Check UART/transport layer configuration between AP and BT controller; (3) Validate BT firmware binaries in /lib/firmware/qca match WCN399x hardware revision; (4) Review device tree bluetooth node for correct GPIO/regulator/clock assignments; (5) If issue persists across multiple boards, escalate to Bluetooth subsystem maintainers with full dmesg and device tree.

Detail analysis attachment: failed_case_job232136_7_detailed.md

Case 8: KVM_Driver

Failed case: KVM_Driver

Root cause: The KVM_Driver test failed because /dev/kvm device node is not present on the shikra-iqs-evk target. This is not a test failure but rather an expected configuration state — the kernel has CONFIG_KVM=y but KVM functionality requires additional platform support (EL2/hypervisor mode, proper device tree configuration) that is not available or enabled on this specific SoC/board combination. The test failure is a false positive; the actual kernel crash that occurred during the qcom_hwrng test (synchronous external abort in qcom_rng_read) is unrelated to KVM and is a separate pre-existing hardware access issue.

Possible fix: The KVM_Driver test should be updated to skip (not fail) when /dev/kvm is not present on platforms where KVM is not expected to be functional, or the test should be excluded from the shikra-iqs-evk test suite. The test correctly validates that CONFIG_KVM is enabled but incorrectly treats the absence of /dev/kvm as a failure rather than a skip condition for platforms without hypervisor support.

Detail analysis attachment: failed_case_job232136_8_detailed.md

Case 9: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM is not available on shikra-iqs-evk because the platform does not support EL2 (hypervisor mode). The kernel boot log shows kvm [1]: HYP mode not available at boot time, which means the CPU is not running in a mode that allows KVM to initialize. CONFIG_KVM is enabled in the kernel config, but /dev/kvm device node is never created because the KVM driver probe fails due to missing EL2 support.

Possible fix: This is not a PR-introduced regression. The PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM host support. The KVM_EL2_DTB test failure is a pre-existing platform limitation — shikra-iqs-evk does not have EL2 enabled in its firmware/bootloader configuration. To fix: either (1) exclude KVM tests from the shikra-iqs-evk test suite, or (2) enable EL2 support in the platform's bootloader/firmware configuration if the hardware supports it.

Detail analysis attachment: failed_case_job232136_9_detailed.md

Case 10: ** KVM_Infra — Test Infrastructure Limitation (Missing /dev/kvm)

Failed case: ** KVM_Infra — Test Infrastructure Limitation (Missing /dev/kvm)

Root cause: ** The KVM_Infra test expects /dev/kvm device node, but the kernel does not create it. CONFIG_KVM=y is enabled, but KVM subsystem does not instantiate the device on shikra-iqs-evk. This is likely due to missing hardware virtualization support (EL2 not available/configured) or missing CONFIG_KVM_ARM_HOST=y.

Possible fix: This is NOT a bug from PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization guest drivers: CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m). To resolve:

Detail analysis attachment: failed_case_job232136_10_detailed.md

Case 11: Kernel Crash — synchronous external abort in qcom_rng driver

Failed case: Kernel Crash — synchronous external abort in qcom_rng driver

Root cause: The qcom_hwrng test triggered a synchronous external abort (data abort) at PC qcom_rng_read+0xc4 when attempting to read from the hardware RNG registers. The crash occurred during a memory-mapped I/O read operation (b940035c = ldr w28, [x26]) to address in x26 (0xffff800082c65004), indicating the RNG hardware block is either not powered, not clocked, or the MMIO mapping is invalid on shikra-iqs-evk. The system then panicked and entered EDL/ramdump mode, causing the LAVA test to timeout after 40 minutes.

Possible fix: This is a pre-existing platform/board issue unrelated to the PR changes (GPU virtualization config). The PR only enables DRM_VIRTIO_GPU configs and does not touch RNG, clocks, or power domains. The shikra-iqs-evk board likely has incomplete RNG hardware support (missing clock/power domain bindings in DT, or hardware not present). Recommended action: Skip the qcom_hwrng test on shikra-iqs-evk until the platform RNG support is fixed, or investigate the device tree and driver probe logs to confirm RNG hardware availability. This failure should not block the PR.

Detail analysis attachment: failed_case_job232136_11_detailed.md

Case 12: Kernel Crash — synchronous external abort

Failed case: Kernel Crash — synchronous external abort

Root cause: Synchronous external abort (hardware bus error) in qcom_rng driver when reading from hardware RNG device at address 0xffff800082c65000 during qcom_hwrng test execution. The abort occurred in qcom_rng_read+0xc4 when attempting to access MMIO registers of the PRNG hardware block. This is a hardware/platform-specific issue where the PRNG hardware block is either not powered, not clocked, or the MMIO mapping is incorrect for the shikra-iqs-evk platform.

Possible fix: This is NOT a PR-introduced regression (PR only enables GPU virtualization configs). This is a pre-existing platform/driver issue. Recommended actions: (1) Verify PRNG hardware block power/clock configuration in device tree for shikra-iqs-evk, (2) Check if PRNG MMIO base address mapping is correct for this SoC variant, (3) Add runtime PM or clock enable/disable handling in qcom_rng driver probe path, (4) Consider skipping qcom_hwrng test on shikra-iqs-evk until hardware configuration is fixed, or (5) Disable CONFIG_HW_RANDOM_QCOM for this platform if PRNG hardware is not functional.

Detail analysis attachment: failed_case_job232136_12_detailed.md

Case 13: Kernel Crash — synchronous external abort in qcom_rng driver

Failed case: Kernel Crash — synchronous external abort in qcom_rng driver

Root cause: Hardware random number generator (qcom_rng) driver triggered a synchronous external abort (bus error) at address 0x0000011ee81a5c17 during register read operation in qcom_rng_read(). The crash occurred during the qcom_hwrng test execution when reading from /dev/hwrng. This is a pre-existing platform-specific hardware access issue on shikra-iqs-evk, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options).

Possible fix: This is a pre-existing hardware/driver issue unrelated to the PR changes. The PR only modifies GPU virtualization config (CONFIG_DRM_VIRTIO_GPU) and does not touch the qcom_rng driver or hardware RNG subsystem. Recommended actions: (1) Re-trigger the CI job to confirm reproducibility; (2) If reproducible, investigate qcom_rng driver register mapping and clock/power dependencies on shikra-iqs-evk platform; (3) Check if the RNG hardware block requires specific firmware or power domain initialization that may be missing on this platform; (4) Consider disabling the qcom_hwrng test on shikra-iqs-evk until the hardware access issue is resolved.

Detail analysis attachment: failed_case_job232136_13_detailed.md

Case 14: Kernel Crash — Synchronous External Abort (Hardware Access Fault)

Failed case: Kernel Crash — Synchronous External Abort (Hardware Access Fault)

Root cause: Hardware register access fault in qcom_rng driver at qcom_rng_read+0xc4 — the driver attempted to read from an MMIO register (likely the RNG hardware status or data register) that triggered a synchronous external abort (ESR 0x96000010), indicating the hardware block was not accessible (powered down, clocked off, or SMMU-blocked). The crash occurred during the qcom_hwrng test when userspace (dd process) read from /dev/hwrng, triggering qcom_rng_read → hardware register read → external abort → kernel panic. This is a pre-existing platform/driver issue on shikra-iqs-evk, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options).

Possible fix: This is NOT a PR-introduced regression. The PR only adds CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m to arch/arm64/configs/qcom.config, which are unrelated to the RNG hardware driver. The root cause is a platform-specific issue where the qcom_rng hardware block is not properly initialized, powered, or clocked on shikra-iqs-evk. Recommended actions: (1) Skip or disable the qcom_hwrng test on shikra-iqs-evk until the platform RNG hardware support is fixed. (2) Investigate shikra device tree and clock/power domain configuration for the RNG hardware block (qcom,prng-ee compatible node). (3) Check if RNG hardware requires explicit clock/regulator/power-domain enablement that is missing in the shikra DT. (4) Verify SMMU configuration for the RNG hardware block if it is behind an SMMU. (5) Re-run the LAVA job to confirm this is reproducible and not a transient hardware fault.

Detail analysis attachment: failed_case_job232136_14_detailed.md

Job 232137 | SoC qcs6490-rb3gen2

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

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

Case 1: Board Hang/Crash/Reset — Warm reset into EDL/download mode during boot

Failed case: Board Hang/Crash/Reset — Warm reset into EDL/download mode during boot

Root cause: The qcs6490-rb3gen2 board experienced a warm reset approximately 11.2 seconds after kernel boot (last kernel message at [ 11.206751]), triggering entry into EDL/download mode (boot_dload_entry). The TCSR register value 0x10 confirms download mode was configured. The board underwent multiple warm resets (PM: Warm reset count:0x2 and PM: Warm reset count:0x1) before entering ramdump collection flow. No kernel panic, oops, or crash signature was captured in the log, indicating the system stopped abruptly without kernel-level crash handling.

Possible fix: This is NOT a PR-introduced regression. The PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m) which are unrelated to the observed warm reset behavior. The failure is a pre-existing board/infrastructure issue. Recommended actions: (1) Re-trigger the CI job to confirm if this is a transient hardware/lab issue. (2) If the issue reproduces, collect the ramdump/crashdump artifacts to identify what triggered the warm reset. (3) Check for known qcs6490-rb3gen2 board stability issues in the lab environment (power supply, thermal, firmware version). (4) Review baseline boot logs for this SoC to determine if warm resets during boot are a known pattern.

Detail analysis attachment: failed_case_job232137_1_detailed.md

Case 2: auto-login-action

Failed case: auto-login-action

Root cause: System hang/crash approximately 11.2 seconds after kernel boot on qcs6490-rb3gen2, causing a warm reboot before userspace initialization completed and before the login prompt could appear. The kernel booted successfully (Linux version 6.18.44-g3802097e712a detected at timestamp 0.0), device drivers initialized normally through ~11.2s, but the system then stopped producing console output and rebooted ~20 seconds later (fresh bootloader sequence observed at 19:26:24). The PR enables CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m, which are virtualization-related GPU drivers not applicable to this bare-metal qcs6490-rb3gen2 platform; however, as modules they should not load automatically unless explicitly requested, making a direct causal link unlikely. The boot compare report shows 3 new medium-severity issues for qcs6490-rb3gen2 (regulatory.db load failure, adsp/cdsp firmware initialization errors with -EINVAL/-22), but these are non-fatal driver probe failures that do not explain a system-wide hang. No kernel panic, oops, BUG, or crash signature was captured in the serial log, suggesting either a silent hang (deadlock, infinite loop, or hardware wedge) or a watchdog-triggered reset without kernel-side logging.

Possible fix: Re-trigger the CI job to determine reproducibility. If the hang recurs on qcs6490-rb3gen2, capture additional debug artifacts: enable early console and persistent logging (pstore/ramoops), enable lockdep and hung task detection (CONFIG_LOCKDEP, CONFIG_DETECT_HUNG_TASK), enable watchdog with bark-before-bite to capture a backtrace (CONFIG_QCOM_WDT, watchdog.open_timeout), and collect the full serial log including any watchdog bark or secure-world reset reason. Cross-reference the hang timestamp (~11.2s) with driver probe order and any deferred work or async init that may be blocking. If non-reproducible, classify as a transient hardware or firmware glitch and proceed with PR merge after one successful re-run.

Detail analysis attachment: failed_case_job232137_2_detailed.md

Case 3: Boot Hang — Login Prompt Timeout (remoteproc firmware initialization failure)

Failed case: Boot Hang — Login Prompt Timeout (remoteproc firmware initialization failure)

Root cause: System booted successfully but hung before reaching userspace login prompt. ADSP and CDSP remoteproc subsystems failed to initialize firmware with error -22 (EINVAL) at kernel timestamp ~9.8s. The error strings "qcom_q6v5_pas 3700000.remoteproc: error -22 initializing firmware qcom/qcs6490/adsp.mbn" and "qcom_q6v5_pas a300000.remoteproc: error -22 initializing firmware qcom/qcs6490/cdsp.mbn" indicate firmware validation or authentication failure. WPSS remoteproc succeeded, but ADSP/CDSP failures likely blocked critical system services from starting, preventing the system from reaching a login-ready state. LAVA dispatcher waited for login prompt patterns but received no console output after kernel timestamp ~11.2s, timing out after 161 seconds across 3 retry attempts.

Possible fix: This is NOT a PR-introduced regression. The PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) which are unrelated to remoteproc firmware loading. The remoteproc firmware initialization failure (error -22) indicates a pre-existing platform/firmware issue on qcs6490-rb3gen2. Recommended actions: (1) Verify firmware files qcom/qcs6490/adsp.mbn and qcom/qcs6490/cdsp.mbn are present in the rootfs /lib/firmware/ directory and have correct permissions. (2) Check firmware authentication certificates/keys are correctly provisioned for this board. (3) Review bootloader/TrustZone logs for secure boot policy changes that might reject these firmware images. (4) If this is a known intermittent issue on this board, re-trigger the CI job. (5) Test the same kernel build on a different qcs6490-rb3gen2 board to isolate hardware vs software cause.

Detail analysis attachment: failed_case_job232137_3_detailed.md

Case 4: Boot Hang — Silent system freeze during kernel initialization

Failed case: Boot Hang — Silent system freeze during kernel initialization

Root cause: System hung silently at approximately 11 seconds into kernel boot (last message: PCIe iATU initialization at 11.206751s), followed by hardware reset/reboot approximately 20 seconds later. No kernel panic, oops, or crash signature present. The hang occurred during device initialization phase after wpss remoteproc came up and while PCIe subsystem was initializing. LAVA login-action timed out after 3 retry attempts (total 9m23s) because the system never reached userspace to present a login prompt.

Possible fix: This appears to be a boot-time hang during device initialization. The PR introduces GPU virtualization driver modules (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) which may be triggering a deadlock or infinite loop during module loading or device probing. Recommended actions: (1) Boot the target with initcall_debug and ignore_loglevel kernel parameters to capture detailed initialization sequence before the hang; (2) Add module_blacklist=virtio_gpu to kernel cmdline to confirm if the new GPU virtualization driver is the trigger; (3) If confirmed, investigate virtio-gpu driver probe/init path for qcs6490-rb3gen2 platform-specific issues (missing DT nodes, resource conflicts, or incompatible firmware expectations).

Detail analysis attachment: failed_case_job232137_4_detailed.md

Job 232138 | SoC qcs615-ride

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

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

Case 1: Kernel Crash — Synchronous External Abort (USB DMA mapping)

Failed case: Kernel Crash — Synchronous External Abort (USB DMA mapping)

Root cause: Kernel panic triggered by synchronous external abort (data abort exception 0x96000010) during USB device enumeration when attempting DMA mapping via SWIOTLB bounce buffer; memcpy accessed invalid physical memory address 0xffff000090a99f20, causing fatal exception at 7.49s into boot on qcs615-ride platform.

Possible fix: This is a hardware/platform-specific memory access violation during USB initialization, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options). The crash occurs in the USB/IOMMU/SWIOTLB path when enumerating a low-speed USB device (likely keyboard/mouse). Recommended actions: (1) Verify USB device hardware compatibility with qcs615-ride; (2) Check IOMMU/SMMU configuration for USB controller in device tree; (3) Verify SWIOTLB buffer allocation and physical address ranges; (4) Test with USB device disconnected to confirm hardware trigger; (5) Check if recent platform firmware/bootloader changes affected USB/IOMMU setup. This is NOT a PR-introduced regression — the GPU virtualization config changes cannot cause USB DMA mapping failures.

Detail analysis attachment: failed_case_job232138_1_detailed.md

Case 2: Kernel Crash — Synchronous External Abort during USB enumeration

Failed case: Kernel Crash — Synchronous External Abort during USB enumeration

Root cause: Kernel panicked at 7.49s during USB hub device enumeration (hub_port_init) when attempting to copy data via SWIOTLB bounce buffer (__pi_memcpy_generic). The crash is a synchronous external abort (ESR 0x96000010), indicating an invalid physical memory access during DMA bounce buffer operation for USB device descriptor read. On qcs615-ride, this crash is PR-introduced (boot comparison shows 1 new CRITICAL issue for this target).

Possible fix: Revert PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (GPU virtualization config changes: CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m). The config changes likely altered memory layout or SWIOTLB allocation, causing USB DMA bounce buffer to reference invalid physical memory. After revert, verify USB enumeration completes successfully and system reaches login prompt.

Detail analysis attachment: failed_case_job232138_2_detailed.md

Case 3: Kernel Crash — Synchronous External Abort during USB DMA mapping

Failed case: Kernel Crash — Synchronous External Abort during USB DMA mapping

Root cause: Synchronous external abort (ESR 0x96000010) triggered during __pi_memcpy_generic while copying data from SWIOTLB bounce buffer during USB device enumeration. The crash occurs in the USB hub worker thread when attempting to DMA-map a URB for a low-speed USB device (likely a keyboard/mouse based on the hub_port_init path). The fault address (x0=ffff00007ff7f000, x1=ffff000090a99f20) suggests an invalid physical memory access during the SWIOTLB bounce operation, indicating either: (1) SWIOTLB buffer corruption/misconfiguration, (2) IOMMU mapping issue for the USB controller, or (3) a hardware-level bus fault when accessing the DMA buffer. The qcs615-ride platform uses an ARM SMMU (50a0000.iommu) for USB DMA, and the crash happens immediately after the USB host controller (xhci-hcd.0.auto) detects a device on port 1.

Possible fix: This is a pre-existing platform/hardware issue unrelated to the PR (which only enables GPU virtualization config options). The crash is not PR-introduced. To debug: (1) Check SWIOTLB size and allocation in kernel command line (add swiotlb=65536 if not present), (2) Verify IOMMU domain setup for USB controller in device tree, (3) Check for USB hardware errata on qcs615-ride EVK, (4) Add debug prints in swiotlb_bounce and iommu_dma_map_swiotlb to trace the failing DMA address, (5) Test with iommu.passthrough=1 to bypass IOMMU and isolate the fault source. If the issue persists across reboots, suspect a hardware fault on the USB bus or SMMU configuration mismatch in firmware/device-tree.

Detail analysis attachment: failed_case_job232138_3_detailed.md

Case 4: Kernel Crash — Synchronous External Abort during USB DMA mapping

Failed case: Kernel Crash — Synchronous External Abort during USB DMA mapping

Root cause: CPU attempted to access invalid/unmapped physical address 0x0000000110a99f20 during SWIOTLB bounce buffer copy for USB device enumeration, triggering a bus-level synchronous external abort and kernel panic. The faulting address is in a physical memory region that is either unmapped, powered down, or inaccessible due to platform configuration. This is a pre-existing platform/hardware issue unrelated to the PR (which only enables GPU virtualization config options).

Possible fix: This is a hardware/platform configuration issue on qcs615-ride, not a kernel regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118. The PR only adds GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU) and does not touch USB, DMA, SWIOTLB, or memory mapping code. Recommended actions: (1) Verify qcs615-ride hardware is functioning correctly and all power rails are stable; (2) Check if SWIOTLB buffer range overlaps with reserved/protected memory regions in the device tree; (3) Verify USB controller power/clock configuration; (4) Re-run the test on a known-good qcs615-ride board to confirm if this is board-specific; (5) Check if this failure reproduces on the baseline branch without the PR changes.

Detail analysis attachment: failed_case_job232138_4_detailed.md

Job 232139 | SoC purwa-evk

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

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

Case 1: ** Probe_Failure_Check — Multiple driver probe failures detected

Failed case: ** Probe_Failure_Check — Multiple driver probe failures detected

Root cause: ** Six platform drivers failed to probe during boot due to missing hardware resources, firmware files, or device tree configuration issues. These are pre-existing platform/board configuration issues unrelated to the PR changes (GPU virtualization config enabling CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m).

Possible fix: These probe failures are expected and benign on the purwa-evk platform. Update the Probe_Failure_Check test to suppress these known-benign failures for purwa-evk by adding suppression patterns for: qcom_qseecom_uefisecapp (-16), qcom-pcie 1bd0000/1bf8000 (-61), rtc-pm8xxx (-5), qcom-spmi-lpg (-22), and regulatory.db firmware (-2). Alternatively, fix the platform DT/firmware configuration if these peripherals are intended to be functional.

Detail analysis attachment: failed_case_job232139_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Test validation failure — multiple critical masters (USB PHY devices a0f8800.usb, a2f8800.usb, a4f8800.usb, a6f8800.usb, a8f8800.usb and video codec aa00000.video-codec) are missing IOMMU group attachments on purwa-evk (x1e80100 SoC), indicating incomplete device tree IOMMU bindings for these peripherals.

Possible fix: Add missing iommus properties to the device tree nodes for USB PHY devices (a0f8800, a2f8800, a4f8800, a6f8800, a8f8800) and video codec (aa00000) in arch/arm64/boot/dts/qcom/x1e80100.dtsi to attach them to appropriate SMMU stream IDs; this is a device tree configuration issue unrelated to the PR's GPU virtualization config changes.

Detail analysis attachment: failed_case_job232139_2_detailed.md

Case 3: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM host support unavailable on purwa-evk (x1e80100) — kernel booted at EL1 under Gunyah hypervisor, preventing KVM from initializing; /dev/kvm device node not created because kvm_init() returned early with "HYP mode not available" at boot time (line 5.777418 in dmesg).

Possible fix: This is a pre-existing platform limitation, not a PR-introduced regression. The PR (GPU virtualization config changes) does not affect KVM host support. To enable KVM on this platform: (1) configure the Gunyah hypervisor to allow nested virtualization or boot Linux at EL2, or (2) use a different platform with native EL2 support for KVM host testing. No kernel code change required — this is an expected test skip for platforms without EL2 access.

Detail analysis attachment: failed_case_job232139_3_detailed.md

Case 4: KVM_EL2_DTB — KVM unavailable (pre-existing platform limitation)

Failed case: KVM_EL2_DTB — KVM unavailable (pre-existing platform limitation)

Root cause: KVM initialization failed with "HYP mode not available" because the Gunyah hypervisor is already running at EL2 on purwa-evk, preventing KVM from accessing the required privilege level. The /dev/kvm device node was never created because kvm_arch_init() failed during boot.

Possible fix: This is not a PR-introduced regression. The PR only enables GPU virtualization driver configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM host functionality. To run KVM tests on purwa-evk, either: (1) boot without the Gunyah hypervisor to free EL2 for KVM, or (2) skip KVM tests on platforms where Gunyah is enabled, as nested virtualization (KVM under Gunyah) is not supported in this configuration.

Detail analysis attachment: failed_case_job232139_4_detailed.md

Case 5: KVM_Infra — KVM host unavailable (HYP mode not available)

Failed case: KVM_Infra — KVM host unavailable (HYP mode not available)

Root cause: KVM driver initialization failed because the kernel detected "HYP mode not available" at boot time (log line: [5.777418][T1] kvm [1]: HYP mode not available). On ARM64, KVM requires the CPU to boot into EL2 (hypervisor mode) to enable virtualization. The purwa-evk platform either: (1) booted directly into EL1 (kernel mode) bypassing EL2, or (2) has EL2 disabled in firmware/bootloader configuration, or (3) is running under a hypervisor that does not expose EL2 to the guest kernel.

Possible fix: This is not a PR-introduced regression — the PR only enables DRM VirtIO GPU guest drivers (CONFIG_DRM_VIRTIO_GPU), which are unrelated to KVM host functionality. The fix depends on the platform boot configuration: (1) If purwa-evk is intended to support KVM, configure the bootloader (ABL/UEFI) to boot the kernel at EL2 instead of EL1. (2) If the platform is running under a hypervisor, ensure nested virtualization is enabled or accept that KVM host mode is unavailable. (3) Verify the platform's TrustZone/secure firmware configuration allows EL2 access. This is a known platform limitation for purwa-evk if EL2 boot is not configured.

Detail analysis attachment: failed_case_job232139_5_detailed.md

Case 6: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM hypervisor mode (EL2) is not available on the purwa-evk platform — kernel reports "kvm [1]: HYP mode not available" during boot, preventing /dev/kvm device creation despite CONFIG_KVM being enabled.

Possible fix: This is a platform/firmware limitation, not a kernel regression. The purwa-evk board either: (1) boots at EL1 instead of EL2, (2) has EL2 disabled in firmware/bootloader, or (3) lacks hardware virtualization support. To resolve: verify bootloader configuration enables EL2, confirm firmware supports virtualization extensions, or exclude KVM tests from purwa-evk CI runs if the platform does not support virtualization.

Detail analysis attachment: failed_case_job232139_6_detailed.md

Job 232140 | SoC monaco-evk

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: WiFi ath11k_pci driver probe failure (-110 timeout) due to missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin in the rootfs; Bluetooth firmware load failures are benign (BT_ON_OFF test passed); regulatory.db firmware absence is expected and benign.

Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory. This is a pre-existing platform/infra issue unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The Bluetooth firmware failures can be suppressed as known benign per LAVA suppression rules (BT_ON_OFF functional test passed).

Detail analysis attachment: failed_case_job232140_1_detailed.md

Case 2: WiFi_Firmware_Driver

Failed case: WiFi_Firmware_Driver

Root cause: ath11k_pci WiFi driver probe failed with error -110 (ETIMEDOUT) on monaco-evk because MHI firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs (error -2 / ENOENT). The WCN6855 WiFi chip requires this firmware to initialize the MHI (Modem Host Interface) transport layer before the ath11k driver can complete probe.

Possible fix: Add the missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/ath11k/WCN6855/hw2.1/nfa765/). This firmware is part of the linux-firmware package or Qualcomm's proprietary firmware distribution for WCN6855 WiFi 6E chips. Verify the firmware is present in the build image before flashing to the target.

Detail analysis attachment: failed_case_job232140_2_detailed.md

Case 3: ** WiFi_OnOff — ath11k_pci driver probe failure

Failed case: ** WiFi_OnOff — ath11k_pci driver probe failure

Root cause: ** The ath11k_pci WiFi driver probe failed with -ETIMEDOUT (-110) during MHI (Modem Host Interface) firmware loading on monaco-evk. The MHI subsystem attempted to load firmware from path ath11k/WCN6855/hw2.1/nfa765/amss.bin but the file was not found (-ENOENT), causing MHI power-up to timeout. This is a pre-existing platform/firmware packaging issue, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options).

Possible fix: Add the missing WCN6855 firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs firmware directory (/lib/firmware/), or update the device tree / driver board-data configuration to use the correct firmware path for the monaco-evk platform's WiFi module variant. Verify the WiFi module hardware variant (nfa765 vs other SKUs) matches the firmware path expected by the driver.

Detail analysis attachment: failed_case_job232140_3_detailed.md

Case 4: ** 0_qcom-next-ci-premerge-tests (LAVA test suite — not a build load failure)

Failed case: ** 0_qcom-next-ci-premerge-tests (LAVA test suite — not a build load failure)

Root cause: ** WiFi driver probe failure due to missing firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin (error -2: ENOENT), causing MHI power-up timeout (error -110: ETIMEDOUT) and cascading test failures in Probe_Failure_Check, WiFi_Firmware_Driver, and WiFi_OnOff. This is a pre-existing infrastructure/firmware packaging issue, NOT a regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118.

Possible fix: Add the missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the rootfs build recipe for monaco-evk. This is a Yocto/build-system packaging fix, not a kernel code change. PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs) is unrelated to this failure and should be approved for merge.

Detail analysis attachment: failed_case_job232140_4_detailed.md

Job 232142 | SoC lemans-evk

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

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

Case 1: Board Hang — System stopped making forward progress after PCIe initialization

Failed case: Board Hang — System stopped making forward progress after PCIe initialization

Root cause: Kernel boot progressed normally until ~8 seconds (PCIe host bridge initialization), then completely stopped producing console output. No login prompt appeared despite 3 retry attempts over 10 minutes. This is a complete system hang on lemans-evk where the kernel froze during late-stage device initialization, likely during PCIe enumeration or a subsequent driver probe that depends on PCIe.

Possible fix: This is a genuine kernel hang, not a LAVA infrastructure issue. The PR enables GPU virtualization (CONFIG_DRM_VIRTIO_GPU=m) which may have introduced a dependency or timing issue during boot. Recommended actions: (1) Revert the PR and confirm lemans-evk boots successfully without the GPU virtualization config changes. (2) If revert fixes it, investigate whether the virtio-gpu driver or its dependencies are causing a deadlock/hang during probe on this SoC. (3) Collect SDI/watchdog dump if available to identify which CPU/thread is stuck and where. (4) Check if lemans-evk device tree has any virtio-gpu or related device nodes that might be triggering unexpected probe behavior.

Detail analysis attachment: failed_case_job232142_1_detailed.md

Case 2: Board Hang During Boot — PCIe initialization stall

Failed case: Board Hang During Boot — PCIe initialization stall

Root cause: System hung at ~8 seconds into boot during PCIe controller initialization (qcom-pcie 1c10000.pcie and 1c00000.pcie probe); no further console output for 95+ seconds until LAVA timeout; no login prompt ever appeared; lemans-evk platform-specific issue where PCIe enumeration or link training appears to have deadlocked the system.

Possible fix: This is a pre-existing platform/infra issue unrelated to the PR (PR only adds DRM_VIRTIO_GPU config options). Investigate PCIe controller firmware/hardware state on lemans-evk board NNPMP51S00AG; check if PCIe devices are properly seated; verify PCIe PHY clocks and power rails; consider adding PCIe debug logging or disabling PCIe controllers in DT to isolate the hang; check if other lemans-evk boards in the lab exhibit the same behavior; this may require board-level debug or replacement.

Detail analysis attachment: failed_case_job232142_2_detailed.md

Case 3: minimal-boot — System hang during userspace initialization (login prompt never appeared)

Failed case: minimal-boot — System hang during userspace initialization (login prompt never appeared)

Root cause: System hung after kernel successfully booted and systemd-udevd started (~8 seconds into boot); no login prompt appeared despite 3 retry attempts over ~10 minutes; last kernel message was PCIe PHY initialization at [7.968s]; no kernel panic, oops, or crash signature detected — system stopped making forward progress during early userspace initialization on lemans-evk platform.

Possible fix: This is NOT a PR-introduced regression. The PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) which are loaded as modules and would not affect early boot. The boot comparison report shows lemans-evk has no baseline, so this cannot be confirmed as PR-introduced. The hang pattern (systemd-udevd starts, then silence) suggests a platform-specific issue with lemans-evk hardware initialization or a pre-existing boot instability. Recommended actions: (1) Re-trigger the CI job to check if this is a transient hardware/lab issue; (2) If reproducible, collect serial console logs with earlyprintk and debug kernel parameters to capture any missing kernel messages; (3) Check if lemans-evk has known boot stability issues in the lab; (4) Test the same kernel image on a different lemans-evk board to rule out hardware failure.

Detail analysis attachment: failed_case_job232142_3_detailed.md

Case 4: LAVA Infrastructure Timeout — Boot Hang (Login Prompt Never Appeared)

Failed case: LAVA Infrastructure Timeout — Boot Hang (Login Prompt Never Appeared)

Root cause: The kernel booted successfully but the system stopped producing console output at ~8 seconds into boot (during PCIe/UFS initialization). LAVA waited for a login prompt for 185+ seconds across 3 retries but it never appeared. The exact error from LAVA: "login-action timed out after 185 seconds" and "No time left for remaining 2 retries."

Possible fix: Re-trigger the LAVA job to rule out transient infrastructure issues. If the failure persists, enable kernel debug output (earlyprintk=serial loglevel=8 initcall_debug) to identify which driver or init call is hanging. Compare with qcom-6.18.y baseline on lemans-evk to determine if this is PR-introduced or a pre-existing target issue. If PR-introduced by GPU virtualization configs, investigate why CONFIG_DRM_VIRTIO_GPU=m causes a hang and fix the root cause before re-enabling.

Detail analysis attachment: failed_case_job232142_4_detailed.md

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

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

Target	Boot lines (PR)	Boot lines (baseline)	New issues	Critical	High	Medium	Low
`hamoa-evk`	1597	no baseline	22	0	1	21	0
`qcs8300-ride`	1030	no baseline	7	0	0	6	1
`qcs9100-ride`	1415	no baseline	13	0	2	10	1
`shikra-iqs-evk`	904	no baseline	9	0	0	9	0
`qcs6490-rb3gen2`	988	no baseline	3	0	0	3	0
`qcs615-ride`	1054	no baseline	17	1	1	15	0
`purwa-evk`	1458	no baseline	33	0	1	30	2
`monaco-evk`	1063	no baseline	11	0	0	11	0
`lemans-evk`	1085	no baseline	5	0	2	3	0

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

🔴 CRITICAL new boot issues: 120 new issue(s) across 9 target(s).

Target: `hamoa-evk`

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

🟡 WATCHDOG (medium)

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

Context

[    6.920380][    T1] usbcore: registered new interface driver uas
[    6.929184][    T1] usbcore: registered new interface driver usb-storage
[    6.953626][    T1] i2c_dev: i2c /dev entries driver
[    6.976707][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.988623][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.995695][    T1] sdhci: Copyright(c) Pierre Ossman
[    7.000999][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium)

[    7.034792][  T114] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    7.021769][    T1] pstore: Registered efi_pstore as persistent store backend
[    7.029422][  T114] efivars: efivars already registered
[    7.029502][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    7.034792][  T114] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    7.042416][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    7.066383][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    7.075124][    T1] usbcore: registered new interface driver usbhid

🟡 ERROR (medium)

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

Context

[   10.787575][  T258] remoteproc remoteproc0: adsp is available
[   10.787736][  T296] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier usb-1-ss0-sbu-mux for /pmic-glink/connector@0
[   10.793895][  T283] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: setting system clock to 1980-01-06T00:00:20 UTC (315964820)
[   10.794121][  T277] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   10.794125][  T277] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   10.833853][  T258] remoteproc remoteproc1: cdsp is available
[   10.833892][  T116] qcom-pcie 1c08000.pci: supply vdda not found, using dummy regulator

🟡 ERROR (medium)

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

Context

[   10.787736][  T296] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier usb-1-ss0-sbu-mux for /pmic-glink/connector@0
[   10.793895][  T283] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: setting system clock to 1980-01-06T00:00:20 UTC (315964820)
[   10.794121][  T277] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   10.794125][  T277] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   10.833853][  T258] remoteproc remoteproc1: cdsp is available
[   10.833892][  T116] qcom-pcie 1c08000.pci: supply vdda not found, using dummy regulator
[   10.833998][  T116] qcom-pcie 1c08000.pci: supply vddpe-3v3 not found, using dummy regulator

🟡 ERROR (medium)

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

Context

[   11.425473][  T116] pcieport 0004:00:00.0: AER: enabled with IRQ 244
[   11.456427][  T198] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   11.468800][  T121] nvme nvme0: pci function 0006:01:00.0
[   11.470280][  T198] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.474420][  T121] nvme 0006:01:00.0: enabling device (0000 -> 0002)
[   11.488875][  T198] tpm tpm0: starting up the TPM manually
[   11.495420][  T121] nvme nvme0: allocated 64 MiB host memory buffer (16 segments).

🟡 ERROR (medium)

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

Context

[   11.633446][  T253] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   11.639748][  T253] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.640108][  T253] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.640300][  T142] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.640313][  T142] cfg80211: failed to load regulatory.db
[   11.692390][  T206] hub 1-0:1.0: USB hub found
[   11.692665][  T257] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae90000

🟡 ERROR (medium)

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

Context

[   11.968285][  T206] xhci-hcd xhci-hcd.2.auto: irq 277, io mem 0x0a200000
[   11.976344][  T206] hub 3-0:1.0: USB hub found
[   11.980984][  T206] hub 3-0:1.0: 1 port detected
[   11.992770][  T206] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.002623][  T206] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.014560][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.024536][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.976344][  T206] hub 3-0:1.0: USB hub found
[   11.980984][  T206] hub 3-0:1.0: 1 port detected
[   11.992770][  T206] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.002623][  T206] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.014560][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.024536][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.035768][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.980984][  T206] hub 3-0:1.0: 1 port detected
[   11.992770][  T206] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.002623][  T206] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.014560][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.024536][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.035768][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045630][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.992770][  T206] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.002623][  T206] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.014560][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.024536][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.035768][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045630][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045679][  T145] mhi mhi0: Wait for device to enter SBL or Mission mode

🟡 ERROR (medium)

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

Context

[   12.002623][  T206] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.014560][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.024536][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.035768][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045630][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045679][  T145] mhi mhi0: Wait for device to enter SBL or Mission mode
[   12.057606][  T206] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.014560][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.024536][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.035768][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045630][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045679][  T145] mhi mhi0: Wait for device to enter SBL or Mission mode
[   12.057606][  T206] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.072593][  T206] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.035768][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045630][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045679][  T145] mhi mhi0: Wait for device to enter SBL or Mission mode
[   12.057606][  T206] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.072593][  T206] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.082954][  T206] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   12.100700][  T206] /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)

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

Context

[   12.045630][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.045679][  T145] mhi mhi0: Wait for device to enter SBL or Mission mode
[   12.057606][  T206] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.072593][  T206] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.082954][  T206] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   12.100700][  T206] /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.241832][  T213] usb 3-1: new full-speed USB device number 2 using xhci-hcd

🟡 WARNING (medium)

[   12.325259][  T206] WARNING: CPU: 9 PID: 206 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   12.100700][  T206] /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.241832][  T213] usb 3-1: new full-speed USB device number 2 using xhci-hcd
[   12.319769][  T206] ------------[ cut here ]------------
[   12.325259][  T206] WARNING: CPU: 9 PID: 206 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   12.337614][  T206] Modules linked in: panel_edp(+) ath12k_wifi7(+) ath12k mac80211 libarc4 cfg80211 rpmsg_ctrl qrtr_smd(+) fastrpc(+) apr ps883x qcom_hamoa_ec phy_nxp_ptn3222 rpmsg_char qcom_pd_ma
[   12.337863][  T206]  spi_geni_qcom snd_soc_lpass_wsa_macro dispcc_x1e80100 drm phy_qcom_edp soundwire_qcom camcc_x1e80100 ubwc_config videocc_sm8550 phy_qcom_qmp_usb qcom_glink_smem pinctrl_lpass_l
[   12.499908][  T206] CPU: 9 UID: 0 PID: 206 Comm: kworker/u51:2 Not tainted 6.18.44-g3802097e712a #1 PREEMPT

🟠 CALL_TRACE (high)

[   12.630920][  T206] Call trace:

Context

[   12.606735][  T206] x8 : ffff800085023468 x7 : 0000000000000000 x6 : 0000000000000001
[   12.614796][  T206] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   12.622857][  T206] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   12.630920][  T206] Call trace:
[   12.634173][  T206]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   12.641085][  T206]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   12.646926][  T206]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium)

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

Context

[   12.790131][  T206]  ret_from_fork+0x10/0x20
[   12.794551][  T206] ---[ end trace 0000000000000000 ]---
[   12.801995][  T206] panel-simple-dp-aux aux-aea0000.displayport-controller: Unknown panel BOE 0x0b21, using conservative timings
[   12.818020][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.823097][  T260] Bluetooth: Core ver 2.22
[   12.827893][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.832339][  T260] NET: Registered PF_BLUETOOTH protocol family

🟡 ERROR (medium)

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

Context

[   12.801995][  T206] panel-simple-dp-aux aux-aea0000.displayport-controller: Unknown panel BOE 0x0b21, using conservative timings
[   12.818020][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.823097][  T260] Bluetooth: Core ver 2.22
[   12.827893][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.832339][  T260] NET: Registered PF_BLUETOOTH protocol family
[   12.843876][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.848295][  T260] Bluetooth: HCI device and connection manager initialized

🟡 ERROR (medium)

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

Context

[   12.823097][  T260] Bluetooth: Core ver 2.22
[   12.827893][  T206] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.832339][  T260] NET: Registered PF_BLUETOOTH protocol family
[   12.843876][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.848295][  T260] Bluetooth: HCI device and connection manager initialized
[   12.858167][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.865400][  T260] Bluetooth: HCI socket layer initialized

🟡 ERROR (medium)

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

Context

[   12.832339][  T260] NET: Registered PF_BLUETOOTH protocol family
[   12.843876][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.848295][  T260] Bluetooth: HCI device and connection manager initialized
[   12.858167][  T206] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.865400][  T260] Bluetooth: HCI socket layer initialized
[   12.874633][  T125] ath12k_wifi7_pci 0004:01:00.0: qmi dma allocation failed (7274496 B type 1), will try later with small size
[   12.878846][  T206] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 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
[   34.320126][  T501] EXT4-fs (sda2): orphan cleanup on readonly fs
[   34.326909][  T501] EXT4-fs (sda2): mounted filesystem 3206df9e-e263-42d7-9d46-ed111600e54a ro with ordered data mode. Quota mode: none.
done.

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.401987][   T74] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    9.399684][  T173] Bluetooth: HCI socket layer initialized
[    9.399703][  T173] Bluetooth: L2CAP socket layer initialized
[    9.399754][  T173] Bluetooth: SCO socket layer initialized
[    9.401987][   T74] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.434095][  T166] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/dsi@ae94000
[    9.435913][   T74] cfg80211: failed to load regulatory.db
[    9.442012][  T166] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@af54000

🟡 ERROR (medium)

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

Context

[    9.613312][  T111] Bluetooth: hci0: QCA controller version 0x02100201
[    9.613338][  T111] Bluetooth: hci0: QCA Downloading qca/QCA6698/hpbtfw21.tlv
[    9.619416][  T172] ath11k_pci 0000:01:00.0: MSI vectors: 32
[    9.646423][  T294] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.646423][  T294] :39
[    9.659377][  T172] ath11k_pci 0000:01:00.0: qca6698aq hw2.1
[    9.666202][  T294] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

🟡 ERROR (medium)

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

Context

[    9.646423][  T294] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.646423][  T294] :39
[    9.659377][  T172] ath11k_pci 0000:01:00.0: qca6698aq hw2.1
[    9.666202][  T294] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.666202][  T294] :43
[    9.719341][  T294] msm_dpu ae01000.display-controller: bound af54000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    9.731363][  T294] msm_dpu ae01000.display-controller: bound ae94000.dsi (ops dsi_ops [msm])

🔵 FIRMWARE_FAIL (low)

[   10.539303][  T195] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22

Context

[   10.066143][  T112] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes
[   10.126147][  T112] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes
[   10.353255][  T111] Bluetooth: hci0: QCA Downloading qca/QCA6698/hpnv21.b206
[   10.539303][  T195] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   10.560885][  T195] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   10.616016][  T111] Bluetooth: hci0: QCA FW build version: BTFW.HSP.2.1.2-00072-PATCHZ-2
[   10.625755][  T111] Bluetooth: hci0: QCA setup on UART is completed

🟡 ERROR (medium)

[   10.560885][  T195] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22

Context

[   10.126147][  T112] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes
[   10.353255][  T111] Bluetooth: hci0: QCA Downloading qca/QCA6698/hpnv21.b206
[   10.539303][  T195] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   10.560885][  T195] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   10.616016][  T111] Bluetooth: hci0: QCA FW build version: BTFW.HSP.2.1.2-00072-PATCHZ-2
[   10.625755][  T111] Bluetooth: hci0: QCA setup on UART is completed
[   10.633253][  T111] Bluetooth: hci0: HFP non-HCI data transport is supported

🟡 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.175744][  T382] EXT4-fs (sda2): orphan cleanup on readonly fs
[   33.184192][  T382] EXT4-fs (sda2): mounted filesystem 7f34933b-dff4-418b-85ae-4949149befdd 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: 13 (0 critical, 2 high, 10 medium, 1 low)

🟡 ERROR (medium)

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

Context

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

🟡 WARNING (medium)

[    4.645959][    T1] WARNING: CPU: 2 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.621539][    T1] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 (0,8000003f) counters available
[    4.640482][    T1] ------------[ cut here ]------------
[    4.645937][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.645959][    T1] WARNING: CPU: 2 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.662563][    T1] Modules linked in:
[    4.666425][    T1] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.44-g3802097e712a #1 PREEMPT 
[    4.675979][    T1] Hardware name: Qualcomm Technologies, Inc. Lemans Ride Rev3 (DT)

🟠 CALL_TRACE (high)

[    4.787706][    T1] Call trace:

Context

[    4.763594][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002c9
[    4.771630][    T1] x5 : 00000000000002ca x4 : 40000000fffff2c9 x3 : 0000000000000000
[    4.779667][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.787706][    T1] Call trace:
[    4.790939][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.796663][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.802295][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 WARNING (medium)

[    4.899271][    T1] WARNING: CPU: 2 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.887148][    T1] ---[ end trace 0000000000000000 ]---
[    4.893807][    T1] ------------[ cut here ]------------
[    4.899259][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.899271][    T1] WARNING: CPU: 2 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.915867][    T1] Modules linked in:
[    4.919723][    T1] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Tainted: G        W           6.18.44-g3802097e712a #1 PREEMPT 
[    4.930869][    T1] Tainted: [W]=WARN

🟠 CALL_TRACE (high)

[    5.046346][    T1] Call trace:

Context

[    5.022243][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002f3
[    5.030276][    T1] x5 : 00000000000002f4 x4 : 40000000fffff2f3 x3 : 0000000000000000
[    5.038314][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    5.046346][    T1] Call trace:
[    5.049578][    T1]  notifier_chain_register+0x64/0x150 (P)
[    5.055302][    T1]  raw_notifier_chain_register+0x1c/0x30
[    5.060936][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 ERROR (medium)

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

Context

[    8.604020][  T191] coresight cti_sys0: CTI initialized 0
[    8.614211][  T111] qcom-pcie 1c00000.pcie: host bridge /pcie@1c00000 ranges:
[    8.622167][  T111] qcom-pcie 1c00000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000
[    8.624136][  T213] qcom_eud 88e1000.eud: error -ENODEV: failed to get controller node for path 0
[    8.631132][  T111] qcom-pcie 1c00000.pcie:      MEM 0x0040300000..0x005fffffff -> 0x0040300000
[    8.650835][  T248] NET: Registered PF_QIPCRTR protocol family
[    8.675085][  T205] remoteproc remoteproc0: gpdsp0 is available

🟡 ERROR (medium)

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

Context

[   10.234190][  T186] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.241021][  T186] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.245824][  T188] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 19
[   10.249357][   T37] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.256940][  T216] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[   10.256940][  T216] :39
[   10.257029][  T216] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

🟡 ERROR (medium)

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

Context

[   10.241021][  T186] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.245824][  T188] platform 20c00000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 19
[   10.249357][   T37] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.256940][  T216] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[   10.256940][  T216] :39
[   10.257029][  T216] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[   10.257029][  T216] :43

🟡 ERROR (medium)

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

Context

[   10.249357][   T37] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.256940][  T216] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[   10.256940][  T216] :39
[   10.257029][  T216] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[   10.257029][  T216] :43
[   10.260132][  T212] platform iris_non_pixel.0: Adding to iommu group 20
[   10.268765][   T37] cfg80211: failed to load regulatory.db

🔵 FIRMWARE_FAIL (low)

[   12.280378][  T210] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22

Context

[   11.354254][   T12] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x207 soc_id 0x400c0210
[   11.364120][   T12] 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.748146][  T216] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[   12.280378][  T210] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   12.303208][  T210] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   13.155967][  T210] hwmon hwmon51: temp1_input not attached to any thermal zone
[   13.179409][  T186] qcom-ethqos 23000000.ethernet end1: renamed from eth0

🟡 ERROR (medium)

[   12.303208][  T210] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22

Context

[   11.364120][   T12] 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.748146][  T216] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[   12.280378][  T210] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   12.303208][  T210] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   13.155967][  T210] hwmon hwmon51: temp1_input not attached to any thermal zone
[   13.179409][  T186] qcom-ethqos 23000000.ethernet end1: renamed from eth0
[   13.188045][  T216] qcom-ethqos 23040000.ethernet end0: renamed from eth1

🟡 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
[   31.719566][  T381] EXT4-fs (sda2): orphan cleanup on readonly fs
[   31.726392][  T381] EXT4-fs (sda2): mounted filesystem a4a4bf86-e165-485f-8307-e1ae0f65a7e1 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)

[    8.177435][  T139] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22

Context

[    8.047760][  T136] geni_i2c 4a8c000.i2c: Bus frequency not specified, default to 100kHz.
[    8.134593][  T150]  cs_system_cfg: CoreSight Configuration manager initialised
[    8.169749][  T156] mc: Linux media interface: v0.10
[    8.177435][  T139] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    8.222243][  T139] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    8.231511][   T67] arm-smmu 59a0000.iommu: probing hardware configuration...
[    8.231528][   T67] arm-smmu 59a0000.iommu: SMMUv2 with:

🟡 ERROR (medium)

[    8.222243][  T139] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22

Context

[    8.134593][  T150]  cs_system_cfg: CoreSight Configuration manager initialised
[    8.169749][  T156] mc: Linux media interface: v0.10
[    8.177435][  T139] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    8.222243][  T139] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    8.231511][   T67] arm-smmu 59a0000.iommu: probing hardware configuration...
[    8.231528][   T67] arm-smmu 59a0000.iommu: SMMUv2 with:
[    8.231598][   T67] arm-smmu 59a0000.iommu: 	stage 1 translation

🟡 ERROR (medium)

[    8.321391][  T139] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22

Context

[    8.299029][   T67] arm-smmu 59a0000.iommu: 	preserved 0 boot mappings
[    8.301562][  T156] videodev: Linux video capture interface: v2.00
[    8.311819][   T67] platform 5900000.gpu: Adding to iommu group 12
[    8.321391][  T139] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    8.331745][  T139] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    8.347490][   T58] qcom-pcie 45e8000.pcie: supply vdda not found, using dummy regulator
[    8.356995][   T58] qcom-pcie 45e8000.pcie: supply vddpe-3v3 not found, using dummy regulator

🟡 ERROR (medium)

[    8.331745][  T139] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22

Context

[    8.301562][  T156] videodev: Linux video capture interface: v2.00
[    8.311819][   T67] platform 5900000.gpu: Adding to iommu group 12
[    8.321391][  T139] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    8.331745][  T139] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    8.347490][   T58] qcom-pcie 45e8000.pcie: supply vdda not found, using dummy regulator
[    8.356995][   T58] qcom-pcie 45e8000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    8.367774][   T58] qcom-pcie 45e8000.pcie: host bridge /soc@0/pcie@45e8000 ranges:

🟡 ERROR (medium)

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

Context

[   10.331981][  T133] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.347186][  T147] qcom-ethqos 5d20000.ethernet: IRQ eth_wake_irq not found
[   10.364053][  T147] qcom-ethqos 5d20000.ethernet: IRQ sfty not found
[   10.369576][   T37] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.380504][   T37] cfg80211: failed to load regulatory.db
[   10.385002][  T147] qcom-ethqos 5d20000.ethernet: User ID: 0x51, Synopsys ID: 0x54
[   10.394310][  T168] remoteproc remoteproc1: remote processor cdsp is now up

🟡 ERROR (medium)

[   10.568922][   T67] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17

Context

[   10.494584][  T147] qcom-ethqos 5d20000.ethernet: Using 36/40 bits DMA host/device width
[   10.544320][   T67] msm_dsi 5e94000.dsi: supply refgen not found, using dummy regulator
[   10.561967][   T67] cpufreq-dt cpufreq-dt: failed register driver: -17
[   10.568922][   T67] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17
[   10.625681][  T191] Bluetooth: hci0: setting up wcn399x
[   10.721705][  T157] remoteproc remoteproc2: remote processor lpaicp is now up
[   10.864751][   T58] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110

🟡 ERROR (medium)

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

Context

[   10.568922][   T67] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17
[   10.625681][  T191] Bluetooth: hci0: setting up wcn399x
[   10.721705][  T157] remoteproc remoteproc2: remote processor lpaicp is now up
[   10.864751][   T58] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110
[   10.900404][  T128] irq: IRQ197: trimming hierarchy from :soc@0:interrupt-controller@f200000-1
[   10.921680][  T150] irq: IRQ198: trimming hierarchy from :soc@0:interrupt-controller@f200000-1
[   10.956231][  T152] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)

🟡 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.793480][  T204] blkid (204) used greatest stack depth: 10168 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
[   28.084866][  T216] EXT4-fs (mmcblk0p53): orphan cleanup on readonly fs
[   28.093620][  T216] EXT4-fs (mmcblk0p53): mounted filesystem e08630cf-4d63-44c2-b6c3-bc59f32cda93 ro with ordered data mode. Quota mode: none.
[   28.108259][  T216] mount (216) used greatest stack depth: 10144 bytes left

Target: `qcs6490-rb3gen2`

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

🟡 ERROR (medium)

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

Context

[    9.814568][   T75] arm-smmu 3da0000.iommu: 	Stage-2: 36-bit IPA -> 36-bit PA
[    9.814664][   T75] arm-smmu 3da0000.iommu: 	preserved 0 boot mappings
[    9.818557][  T184] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.819543][   T69] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.819588][   T69] cfg80211: failed to load regulatory.db
[    9.821373][  T167] remoteproc remoteproc3: cdsp is available
[    9.825753][  T159] coresight etm0: CPU0: etm v4.2 initialized

🟡 ERROR (medium)

[    9.827242][   T72] qcom_q6v5_pas 3700000.remoteproc: error -22 initializing firmware qcom/qcs6490/adsp.mbn

Context

[    9.819588][   T69] cfg80211: failed to load regulatory.db
[    9.821373][  T167] remoteproc remoteproc3: cdsp is available
[    9.825753][  T159] coresight etm0: CPU0: etm v4.2 initialized
[    9.827242][   T72] qcom_q6v5_pas 3700000.remoteproc: error -22 initializing firmware qcom/qcs6490/adsp.mbn
[    9.828128][  T205] remoteproc remoteproc3: powering up cdsp
[    9.828136][  T205] remoteproc remoteproc3: Booting fw image qcom/qcs6490/cdsp.mbn, size 3641344
[    9.831251][   T72] remoteproc remoteproc1: can't start rproc adsp: -22

🟡 ERROR (medium)

[    9.837152][  T205] qcom_q6v5_pas a300000.remoteproc: error -22 initializing firmware qcom/qcs6490/cdsp.mbn

Context

[    9.828136][  T205] remoteproc remoteproc3: Booting fw image qcom/qcs6490/cdsp.mbn, size 3641344
[    9.831251][   T72] remoteproc remoteproc1: can't start rproc adsp: -22
[    9.831882][   T75] platform 3d00000.gpu: Adding to iommu group 13
[    9.837152][  T205] qcom_q6v5_pas a300000.remoteproc: error -22 initializing firmware qcom/qcs6490/cdsp.mbn
[    9.843785][   T75] platform 3d6a000.gmu: Adding to iommu group 14
[    9.849274][  T205] remoteproc remoteproc3: can't start rproc cdsp: -22
[    9.857258][  T159] CSCFG registered etm1

Target: `qcs615-ride`

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

🟡 ERROR (medium)

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

Context

[    7.082760][  T173] /soc@0/display-subsystem@ae00000/dsi@ae94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[    7.091686][   T70] qcom-pcie 1c08000.pcie: host bridge /soc@0/pcie@1c08000 ranges:
[    7.092468][  T173] msm_dsi_phy ae94400.phy: supply vdda not found, using dummy regulator
[    7.097606][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.097624][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.106002][  T184] Bluetooth: HCI device and connection manager initialized
[    7.106018][  T184] Bluetooth: HCI socket layer initialized

🟡 ERROR (medium)

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

Context

[    7.091686][   T70] qcom-pcie 1c08000.pcie: host bridge /soc@0/pcie@1c08000 ranges:
[    7.092468][  T173] msm_dsi_phy ae94400.phy: supply vdda not found, using dummy regulator
[    7.097606][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.097624][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.106002][  T184] Bluetooth: HCI device and connection manager initialized
[    7.106018][  T184] Bluetooth: HCI socket layer initialized
[    7.106025][  T184] Bluetooth: L2CAP socket layer initialized

🟡 ERROR (medium)

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

Context

[    7.106042][  T184] Bluetooth: SCO socket layer initialized
[    7.110267][  T223] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[    7.114968][   T70] qcom-pcie 1c08000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000
[    7.129580][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.143018][   T70] qcom-pcie 1c08000.pcie:      MEM 0x0040300000..0x005fffffff -> 0x0040300000
[    7.155052][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.293459][  T184] Bluetooth: HCI UART driver ver 2.3

🟡 ERROR (medium)

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

Context

[    7.114968][   T70] qcom-pcie 1c08000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000
[    7.129580][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.143018][   T70] qcom-pcie 1c08000.pcie:      MEM 0x0040300000..0x005fffffff -> 0x0040300000
[    7.155052][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.293459][  T184] Bluetooth: HCI UART driver ver 2.3
[    7.314173][  T181] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 13
[    7.316174][  T184] Bluetooth: HCI UART protocol H4 registered

🟡 ERROR (medium)

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

Context

[    7.316174][  T184] Bluetooth: HCI UART protocol H4 registered
[    7.321084][   T70] qcom-pcie 1c08000.pcie: supply vdda not found, using dummy regulator
[    7.326354][   T70] qcom-pcie 1c08000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    7.327075][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.327092][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.334420][  T103] usb 1-1: new low-speed USB device number 2 using xhci-hcd
[    7.344990][   T72] qcom,apr 62400000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1

🟡 ERROR (medium)

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

Context

[    7.321084][   T70] qcom-pcie 1c08000.pcie: supply vdda not found, using dummy regulator
[    7.326354][   T70] qcom-pcie 1c08000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    7.327075][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.327092][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.334420][  T103] usb 1-1: new low-speed USB device number 2 using xhci-hcd
[    7.344990][   T72] qcom,apr 62400000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[    7.348907][  T184] Bluetooth: HCI UART protocol LL registered

🟡 ERROR (medium)

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

Context

[    7.334420][  T103] usb 1-1: new low-speed USB device number 2 using xhci-hcd
[    7.344990][   T72] qcom,apr 62400000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[    7.348907][  T184] Bluetooth: HCI UART protocol LL registered
[    7.357294][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.364650][  T184] Bluetooth: HCI UART protocol QCA registered
[    7.366595][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.370228][   T72] qcom,apr 62400000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2

🟡 ERROR (medium)

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

Context

[    7.348907][  T184] Bluetooth: HCI UART protocol LL registered
[    7.357294][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.364650][  T184] Bluetooth: HCI UART protocol QCA registered
[    7.366595][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.370228][   T72] qcom,apr 62400000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[    7.370473][   T70] qcom-pcie 1c08000.pcie: host bridge /soc@0/pcie@1c08000 ranges:
[    7.370520][   T70] qcom-pcie 1c08000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000

🟡 ERROR (medium)

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

Context

[    7.399241][  T181] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 14
[    7.452306][  T107] Bluetooth: hci0: setting up wcn6855
[    7.462047][  T168] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (POLLED)
[    7.468503][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.472803][  T187] irq: IRQ154: trimming hierarchy from :soc@0:interrupt-controller@b220000-9
[    7.482065][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.491489][  T103] Internal error: synchronous external abort: 0000000096000010 [#1]  SMP

🟡 ERROR (medium)

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

Context

[    7.462047][  T168] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (POLLED)
[    7.468503][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.472803][  T187] irq: IRQ154: trimming hierarchy from :soc@0:interrupt-controller@b220000-9
[    7.482065][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.491489][  T103] Internal error: synchronous external abort: 0000000096000010 [#1]  SMP
[    7.495405][  T181] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 15
[    7.501106][  T181] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 16

🟡 ERROR (medium)

[    7.491489][  T103] Internal error: synchronous external abort: 0000000096000010 [#1]  SMP

Context

[    7.468503][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.472803][  T187] irq: IRQ154: trimming hierarchy from :soc@0:interrupt-controller@b220000-9
[    7.482065][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.491489][  T103] Internal error: synchronous external abort: 0000000096000010 [#1]  SMP
[    7.495405][  T181] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 15
[    7.501106][  T181] platform 62400000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 16
[    7.506004][  T103] Modules linked in: anx7625 pinctrl_sx150x(+) videobuf2_memops qcom_edac apr qcom_pd_mapper pdr_interface qrtr_smd qcom_pdr_msg fastrpc(+) rpmsg_ctrl hci_uart rpmsg_char qmi_cool

🟡 ERROR (medium)

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

Context

[    7.506137][  T103] sp : ffff800083833640
[    7.506138][  T103] x29: ffff800083833640 x28: 0000000000000000 x27: ffff0000846d7a00
[    7.506143][  T103] x26: ffff8000826b8f68 x25: 0000000000000fff x24: 0000000000000000
[    7.522541][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.527200][  T103] 
[    7.527201][  T103] x23: ffff000081820410 x22: ffff00007ff7f000 x21: 0000000000000001
[    7.527204][  T103] x20: 0000000000001000 x19: 0000000110a99f20 x18: 0000000000004800

🟠 CALL_TRACE (high)

[    7.527225][  T103] Call trace:

Context

[    7.527216][  T103] x8 : 0000000000000018 x7 : 0000000000000000 x6 : 0000000000000000
[    7.527219][  T103] x5 : ffff00007ff7f012 x4 : ffff000090a99f32 x3 : 0000000000000001
[    7.527221][  T103] x2 : 0000000000000012 x1 : ffff000090a99f20 x0 : ffff00007ff7f000
[    7.527225][  T103] Call trace:
[    7.527226][  T103]  __pi_memcpy_generic+0x2c/0x230 (P)
[    7.527231][  T103]  swiotlb_tbl_map_single+0x160/0x2c8
[    7.527235][  T103]  iommu_dma_map_swiotlb+0x70/0x1f8

🟡 ERROR (medium)

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

Context

[    7.527246][  T103]  dma_map_page_attrs+0xa0/0x200
[    7.527249][  T103]  usb_hcd_map_urb_for_dma+0x39c/0x4a8
[    7.527252][  T103]  xhci_map_urb_for_dma+0x164/0x1a8
[    7.536131][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.545904][  T103]  usb_hcd_submit_urb+0x7c/0x350
[    7.545907][  T103]  usb_submit_urb+0x1b8/0x630
[    7.545910][  T103]  usb_start_wait_urb+0x80/0x1d8

🟡 ERROR (medium)

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

Context

[    7.545920][  T103]  hub_port_init+0x6d0/0xc00
[    7.545924][  T103]  hub_port_connect+0x34c/0xa18
[    7.545928][  T103]  hub_port_connect_change+0xc0/0x2a0
[    7.558761][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.560600][  T181] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 17
[    7.564312][  T103]  port_event+0x6b8/0x7e8
[    7.564316][  T103]  hub_event+0x154/0x4a8

🟡 ERROR (medium)

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

Context

[    7.564337][  T103] Code: f100405f 540000c3 a9401c26 a97f348c (a9001c06) 
[    7.564341][  T103] ---[ end trace 0000000000000000 ]---
[    7.565593][  T181] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 18
[    7.574253][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.685466][  T103] Kernel panic - not syncing: synchronous external abort: Fatal exception
[    7.685471][  T103] SMP: stopping secondary CPUs
[    7.885624][  T103] Kernel Offset: disabled

🔴 KERNEL_PANIC (critical)

[    7.685466][  T103] Kernel panic - not syncing: synchronous external abort: Fatal exception

Context

[    7.564341][  T103] ---[ end trace 0000000000000000 ]---
[    7.565593][  T181] platform 8300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 18
[    7.574253][  T223] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    7.685466][  T103] Kernel panic - not syncing: synchronous external abort: Fatal exception
[    7.685471][  T103] SMP: stopping secondary CPUs
[    7.885624][  T103] Kernel Offset: disabled
[    7.885625][  T103] CPU features: 0x100000,00426000,40046281,0400720b

Target: `purwa-evk`

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

🟡 WATCHDOG (medium)

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

Context

[    6.317595][    T1] usbcore: registered new interface driver usb-storage
[    6.323209][   T87] Freeing initrd memory: 60796K
[    6.345046][    T1] i2c_dev: i2c /dev entries driver
[    6.363789][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.375345][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.382407][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.387732][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium)

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

Context

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

🟡 ERROR (medium)

[    8.977457][   T87] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host

Context

[    8.942572][   T64] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_perf_level_get_fc_force]
[    8.951394][   T87] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    8.967921][   T64] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_clock_rates_triplet_out_of_spec]
[    8.977457][   T87] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.000346][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.000524][   T87] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.010516][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16

🔵 FIRMWARE_FAIL (low)

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

Context

[    8.951394][   T87] phy phy-1bd4000.phy.3: phy poweron failed --> -61
[    8.967921][   T64] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_clock_rates_triplet_out_of_spec]
[    8.977457][   T87] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.000346][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.000524][   T87] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.010516][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.053076][  T212] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified

🟡 ERROR (medium)

[    9.000524][   T87] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61

Context

[    8.967921][   T64] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_clock_rates_triplet_out_of_spec]
[    8.977457][   T87] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.000346][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.000524][   T87] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.010516][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.053076][  T212] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.062301][  T212] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled

🔵 FIRMWARE_FAIL (low)

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

Context

[    8.977457][   T87] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.000346][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.000524][   T87] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.010516][   T64] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.053076][  T212] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.062301][  T212] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[    9.074107][  T212] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled

🟡 ERROR (medium)

[    9.310016][  T222] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: probe with driver rtc-pm8xxx failed with error -5

Context

[    9.226669][   T75] remoteproc remoteproc0: Booting fw image qcom/x1e80100/adsp.mbn, size 17922440
[    9.309001][  T157] qcom-pcie 1bf8000.pci: supply vdda not found, using dummy regulator
[    9.309329][  T164] scsi 0:0:0:49476: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.310016][  T222] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: probe with driver rtc-pm8xxx failed with error -5
[    9.311366][  T221] remoteproc remoteproc1: cdsp is available
[    9.311493][  T199] 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
[    9.312348][  T314] qcom-pcie 1c00000.pci: supply vdda not found, using dummy regulator

🟡 ERROR (medium)

[    9.412228][  T157] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host

Context

[    9.385050][   T88] sd 0:0:0:1: [sdb] 16384 4096-byte logical blocks: (67.1 MB/64.0 MiB)
[    9.392137][  T157] phy phy-1bfc000.phy.0: phy poweron failed --> -61
[    9.404526][   T88] sd 0:0:0:1: [sdb] Write Protect is off
[    9.412228][  T157] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host
[    9.420689][  T274] remoteproc remoteproc1: remote processor cdsp is now up
[    9.424734][  T314] qcom-pcie 1c00000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[    9.429546][  T157] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61

🟡 ERROR (medium)

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

Context

[    9.412228][  T157] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host
[    9.420689][  T274] remoteproc remoteproc1: remote processor cdsp is now up
[    9.424734][  T314] qcom-pcie 1c00000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[    9.429546][  T157] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61
[    9.436795][   T88] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    9.439480][   T86]  sda: sda1 sda2
[    9.439714][   T86] sd 0:0:0:0: [sda] Attached SCSI disk

🟡 ERROR (medium)

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

Context

[   10.505381][  T314] pci_bus 0005:00: resource 5 [mem 0x7e300000-0x7fffffff]
[   10.512991][  T314] pcieport 0005:00:00.0: PME: Signaling with IRQ 217
[   10.522192][  T314] pcieport 0005:00:00.0: AER: enabled with IRQ 217
[   10.534848][  T209] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   10.544384][  T209] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   10.564907][  T211] qcom-camss acb7000.isp: Entity type for entity msm_tpg0 was not initialized!
[   10.565073][  T201] platform iris_non_pixel.0: Adding to iommu group 16

🟡 ERROR (medium)

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

Context

[   10.512991][  T314] pcieport 0005:00:00.0: PME: Signaling with IRQ 217
[   10.522192][  T314] pcieport 0005:00:00.0: AER: enabled with IRQ 217
[   10.534848][  T209] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   10.544384][  T209] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   10.564907][  T211] qcom-camss acb7000.isp: Entity type for entity msm_tpg0 was not initialized!
[   10.565073][  T201] platform iris_non_pixel.0: Adding to iommu group 16
[   10.574007][  T211] qcom-camss acb7000.isp: Entity type for entity msm_tpg1 was not initialized!

🟡 ERROR (medium)

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

Context

[   10.618654][  T209] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[   10.641542][   T88] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   10.644470][  T160] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a600000.usb for /pmic-glink/connector@0
[   10.654305][   T88] tpm tpm0: A TPM error (256) occurred attempting the self test
[   10.669073][   T88] tpm tpm0: starting up the TPM manually
[   10.671263][  T219] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae9a000
[   10.690881][  T219] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000

🟡 ERROR (medium)

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

Context

[   10.887635][  T219] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   10.893943][  T230] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.909986][  T219] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   10.918083][    T9] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.935506][  T219] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   10.945171][    T9] cfg80211: failed to load regulatory.db
[   10.961679][  T219] /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.176524][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.151389][  T160] hub 3-0:1.0: USB hub found
[   11.155491][  T230] mhi mhi0: Power on setup success
[   11.160075][  T160] hub 3-0:1.0: 2 ports detected
[   11.176524][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.186409][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.199043][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.208898][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.155491][  T230] mhi mhi0: Power on setup success
[   11.160075][  T160] hub 3-0:1.0: 2 ports detected
[   11.176524][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.186409][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.199043][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.208898][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.220404][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.160075][  T160] hub 3-0:1.0: 2 ports detected
[   11.176524][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.186409][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.199043][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.208898][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.220404][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.230403][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.176524][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.186409][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.199043][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.208898][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.220404][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.230403][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.235573][  T114] mhi mhi0: Wait for device to enter SBL or Mission mode

🟡 ERROR (medium)

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

Context

[   11.186409][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.199043][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.208898][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.220404][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.230403][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.235573][  T114] mhi mhi0: Wait for device to enter SBL or Mission mode
[   11.241881][  T160] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.199043][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.208898][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.220404][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.230403][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.235573][  T114] mhi mhi0: Wait for device to enter SBL or Mission mode
[   11.241881][  T160] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.257336][  T160] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.220404][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.230403][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.235573][  T114] mhi mhi0: Wait for device to enter SBL or Mission mode
[   11.241881][  T160] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.257336][  T160] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.267668][  T160] /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.285553][  T160] /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.257336][  T160] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.230403][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.235573][  T114] mhi mhi0: Wait for device to enter SBL or Mission mode
[   11.241881][  T160] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.257336][  T160] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.267668][  T160] /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.285553][  T160] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   11.310949][  T161] usb 1-1: new full-speed USB device number 2 using xhci-hcd

🟡 WARNING (medium)

[   11.474035][  T160] WARNING: CPU: 3 PID: 160 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   11.285553][  T160] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   11.310949][  T161] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[   11.468556][  T160] ------------[ cut here ]------------
[   11.474035][  T160] WARNING: CPU: 3 PID: 160 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   11.486384][  T160] Modules linked in: panel_edp(+) ath12k_wifi7(+) ath12k mac80211 libarc4 cfg80211 rfkill mhi apr rpmsg_ctrl fastrpc(+) qcom_hamoa_ec phy_nxp_ptn3222 qrtr_smd(+) rpmsg_char tpm_ti
[   11.486668][  T160]  ubwc_config mc videocc_x1p42100 qcom_pil_info qcom_q6v5 qcom_sysmon qcom_common qcom_glink_smem pinctrl_sm8550_lpass_lpi snd_soc_lpass_wsa_macro phy_qcom_qmp_usb phy_snps_eusb2
[   11.650925][  T160] CPU: 3 UID: 0 PID: 160 Comm: kworker/u33:5 Not tainted 6.18.44-g3802097e712a #1 PREEMPT

🟠 CALL_TRACE (high)

[   11.781622][  T160] Call trace:

Context

[   11.757492][  T160] x8 : ffff80008419b468 x7 : 0000000000000000 x6 : 0000000000000001
[   11.765535][  T160] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   11.773578][  T160] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   11.781622][  T160] Call trace:
[   11.784858][  T160]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   11.791736][  T160]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   11.797548][  T160]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium)

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

Context

[   11.940026][  T160]  ret_from_fork+0x10/0x20
[   11.944425][  T160] ---[ end trace 0000000000000000 ]---
[   11.950709][  T160] panel-simple-dp-aux aux-aea0000.displayport-controller: Unknown panel BOE 0x0b21, using conservative timings
[   11.966554][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.968177][   T97] ath12k_wifi7_pci 0004:01:00.0: qmi dma allocation failed (7274496 B type 1), will try later with small size
[   11.969348][  T211] Bluetooth: Core ver 2.22
[   11.969403][  T211] NET: Registered PF_BLUETOOTH protocol family

🟡 ERROR (medium)

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

Context

[   11.969413][  T211] Bluetooth: HCI socket layer initialized
[   11.969417][  T211] Bluetooth: L2CAP socket layer initialized
[   11.969425][  T211] Bluetooth: SCO socket layer initialized
[   11.976506][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.995789][   T97] ath12k_wifi7_pci 0004:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0x10e soc_id 0x40170200
[   12.000943][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.005997][   T97] ath12k_wifi7_pci 0004:01:00.0: fw_version 0x1103006c fw_build_timestamp 2026-03-06 09:10 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_

🟡 ERROR (medium)

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

Context

[   11.969425][  T211] Bluetooth: SCO socket layer initialized
[   11.976506][  T160] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.995789][   T97] ath12k_wifi7_pci 0004:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0x10e soc_id 0x40170200
[   12.000943][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.005997][   T97] ath12k_wifi7_pci 0004:01:00.0: fw_version 0x1103006c fw_build_timestamp 2026-03-06 09:10 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_
[   12.011731][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.083187][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.995789][   T97] ath12k_wifi7_pci 0004:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0x10e soc_id 0x40170200
[   12.000943][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.005997][   T97] ath12k_wifi7_pci 0004:01:00.0: fw_version 0x1103006c fw_build_timestamp 2026-03-06 09:10 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_
[   12.011731][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.083187][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.093019][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.094196][  T211] usbcore: registered new interface driver btusb

🟡 ERROR (medium)

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

Context

[   12.000943][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.005997][   T97] ath12k_wifi7_pci 0004:01:00.0: fw_version 0x1103006c fw_build_timestamp 2026-03-06 09:10 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_
[   12.011731][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.083187][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.093019][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.094196][  T211] usbcore: registered new interface driver btusb
[   12.095754][  T114] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin

🟡 ERROR (medium)

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

Context

[   12.005997][   T97] ath12k_wifi7_pci 0004:01:00.0: fw_version 0x1103006c fw_build_timestamp 2026-03-06 09:10 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_
[   12.011731][  T160] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.083187][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.093019][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.094196][  T211] usbcore: registered new interface driver btusb
[   12.095754][  T114] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
[   12.095757][  T114] Bluetooth: hci0: QCA: patch rome 0x190200 build 0x8567, firmware rome 0x190200 build 0x43fb

🟡 ERROR (medium)

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

Context

[   12.094196][  T211] usbcore: registered new interface driver btusb
[   12.095754][  T114] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
[   12.095757][  T114] Bluetooth: hci0: QCA: patch rome 0x190200 build 0x8567, firmware rome 0x190200 build 0x43fb
[   12.107458][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.137645][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.150401][  T160] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   12.163622][  T160] msm_dpu ae01000.display-controller: bound ae98000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium)

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

Context

[   12.095754][  T114] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
[   12.095757][  T114] Bluetooth: hci0: QCA: patch rome 0x190200 build 0x8567, firmware rome 0x190200 build 0x43fb
[   12.107458][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.137645][  T160] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.150401][  T160] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   12.163622][  T160] msm_dpu ae01000.display-controller: bound ae98000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   12.175937][  T160] msm_dpu ae01000.display-controller: bound aea0000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 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.370749][  T420] EXT4-fs (sda2): orphan cleanup on readonly fs
[   33.377476][  T420] EXT4-fs (sda2): mounted filesystem f1f5fdbb-ab85-4468-8081-b18e35b78a3c 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.542646][  T234] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2

Context

[    8.526633][    T9] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    8.531009][  T176] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    8.535634][  T182] Bluetooth: HCI UART protocol QCA registered
[    8.542646][  T234] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.557997][  T234] cfg80211: failed to load regulatory.db
[    8.558022][  T170] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 21
[    8.578636][  T113] Bluetooth: hci0: setting up wcn6855

🟡 ERROR (medium)

[    8.590486][   T85] usb usb2-port1: config error

Context

[    8.557997][  T234] cfg80211: failed to load regulatory.db
[    8.558022][  T170] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 21
[    8.578636][  T113] Bluetooth: hci0: setting up wcn6855
[    8.590486][   T85] usb usb2-port1: config error
[    8.604131][  T181] irq: IRQ337: trimming hierarchy from :soc@0:interrupt-controller@b220000-9
[    8.613230][  T181] pca953x 3-003c: supply vcc not found, using dummy regulator
[    8.626674][  T181] pca953x 3-003c: using no AI

🟡 ERROR (medium)

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

Context

[    8.685847][  T181] pca953x 3-003d: supply vcc not found, using dummy regulator
[    8.694313][  T113] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.711389][  T230] qcom,apr 3000000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[    8.716212][  T113] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.716929][  T170] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 23
[    8.726866][  T181] pca953x 3-003d: using no AI
[    8.736596][  T113] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)

🟡 ERROR (medium)

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

Context

[    8.726866][  T181] pca953x 3-003d: using no AI
[    8.736596][  T113] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.759097][  T113] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.766063][  T113] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.766551][  T176] ath11k_pci 0000:01:00.0: BAR 0 [mem 0x40400000-0x405fffff 64bit]: assigned
[    8.776218][  T113] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.784470][  T176] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002)

🟡 ERROR (medium)

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

Context

[    9.119551][  T192] hd3ss3220 2-0047: probed revision=0x2
[    9.127053][  T192] dwc3-qcom a600000.usb: Failed to create device link (0x180) with supplier 2-0047 for /soc@0/usb@a600000/hub@2
[    9.140307][  T163] usbcore: registered new device driver onboard-usb-dev
[    9.142883][  T199] tpm tpm0: A TPM error (256) occurred attempting the self test
[    9.155257][  T199] tpm tpm0: starting up the TPM manually
[    9.158208][  T170] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 29
[    9.170150][  T176] mhi mhi0: Requested to power ON

🟡 ERROR (medium)

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

Context

[    9.158208][  T170] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 29
[    9.170150][  T176] mhi mhi0: Requested to power ON
[    9.175988][  T176] mhi mhi0: Power on setup success
[    9.176252][  T113] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.192153][  T113] mhi mhi0: Error loading firmware: -2
[    9.198179][  T176] ath11k_pci 0000:01:00.0: failed to power up mhi: -110
[    9.198906][  T169] at24 1-0050: supply vcc not found, using dummy regulator

🟡 ERROR (medium)

[    9.192153][  T113] mhi mhi0: Error loading firmware: -2

Context

[    9.170150][  T176] mhi mhi0: Requested to power ON
[    9.175988][  T176] mhi mhi0: Power on setup success
[    9.176252][  T113] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.192153][  T113] mhi mhi0: Error loading firmware: -2
[    9.198179][  T176] ath11k_pci 0000:01:00.0: failed to power up mhi: -110
[    9.198906][  T169] at24 1-0050: supply vcc not found, using dummy regulator
[    9.199196][  T170] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 30

🟡 ERROR (medium)

[    9.590471][   T85] usb usb2-port1: config error

Context

[    9.558771][   T64] qcom-ethqos 23040000.ethernet: TSO feature enabled
[    9.565484][   T64] qcom-ethqos 23040000.ethernet: SPH feature enabled
[    9.572252][   T64] qcom-ethqos 23040000.ethernet: Using 36/40 bits DMA host/device width
[    9.590471][   T85] usb usb2-port1: config error
[    9.617924][  T176] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110
[    9.684500][  T163] hub 1-1:1.0: USB hub found
[    9.690180][  T163] hub 1-1:1.0: 4 ports detected

🟡 ERROR (medium)

[    9.617924][  T176] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110

Context

[    9.565484][   T64] qcom-ethqos 23040000.ethernet: SPH feature enabled
[    9.572252][   T64] qcom-ethqos 23040000.ethernet: Using 36/40 bits DMA host/device width
[    9.590471][   T85] usb usb2-port1: config error
[    9.617924][  T176] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110
[    9.684500][  T163] hub 1-1:1.0: USB hub found
[    9.690180][  T163] hub 1-1:1.0: 4 ports detected
[    9.742847][  T189] qcom-ethqos 23040000.ethernet end0: renamed from eth0

🟡 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.557014][  T340] EXT4-fs (sda2): orphan cleanup on readonly fs
[   32.565570][  T340] EXT4-fs (sda2): mounted filesystem 6f3786c7-63b0-4804-bf44-b718db137539 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: 5 (0 critical, 2 high, 3 medium, 0 low)

🟡 ERROR (medium)

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

Context

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

🟡 WARNING (medium)

[    4.260748][    T1] WARNING: CPU: 4 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.237749][    T1] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 (0,8000003f) counters available
[    4.255277][    T1] ------------[ cut here ]------------
[    4.260727][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.260748][    T1] WARNING: CPU: 4 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.277346][    T1] Modules linked in:
[    4.281200][    T1] CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.44-g3802097e712a #1 PREEMPT 
[    4.290750][    T1] Hardware name: Qualcomm Technologies, Inc. Lemans EVK (DT)

🟠 CALL_TRACE (high)

[    4.401876][    T1] Call trace:

Context

[    4.377777][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002c1
[    4.385816][    T1] x5 : 00000000000002c2 x4 : 40000000fffff2c1 x3 : 0000000000000000
[    4.393844][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.401876][    T1] Call trace:
[    4.405103][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.410821][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.416450][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 WARNING (medium)

[    4.513424][    T1] WARNING: CPU: 4 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.501275][    T1] ---[ end trace 0000000000000000 ]---
[    4.507964][    T1] ------------[ cut here ]------------
[    4.513415][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.513424][    T1] WARNING: CPU: 4 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.530021][    T1] Modules linked in:
[    4.533871][    T1] CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Tainted: G        W           6.18.44-g3802097e712a #1 PREEMPT 
[    4.545020][    T1] Tainted: [W]=WARN

🟠 CALL_TRACE (high)

[    4.659893][    T1] Call trace:

Context

[    4.635800][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002eb
[    4.643830][    T1] x5 : 00000000000002ec x4 : 40000000fffff2eb x3 : 0000000000000000
[    4.651862][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.659893][    T1] Call trace:
[    4.663120][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.668837][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.674463][    T1]  cpu_pm_register_notifier+0x44/0x78

qlijarvis · 2026-09-20T00:43:09Z

LAVA Failed Case Triage Summary

PR: #1118

Job 232513 | SoC qcs8300-ride

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

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

Case 1: Probe_Failure_Check — Suppressed (Known Benign: WiFi/BT Firmware False Positive)

Failed case: Probe_Failure_Check — Suppressed (Known Benign: WiFi/BT Firmware False Positive)

Root cause: The Probe_Failure_Check test detected a regulatory.db firmware load failure (error -2) during cfg80211 initialization. However, this is a known false positive: the regulatory database is loaded successfully at runtime when the WiFi driver fully initializes, as evidenced by the WiFi_OnOff and BT_ON_OFF functional tests both passing.

Possible fix: No action required. This is a known benign test failure per LAVA suppression Rule 2. The test framework checks firmware load status before the driver has completed initialization, causing a false negative. The actual WiFi and Bluetooth subsystems are functioning correctly.

Detail analysis attachment: failed_case_job232513_1_detailed.md

Case 2: KVM Infrastructure Failure — /dev/kvm device node not created

Failed case: KVM Infrastructure Failure — /dev/kvm device node not created

Root cause: QCS8300 platform is running under Gunyah hypervisor (nested virtualization scenario). KVM requires EL2 access but the kernel is running as a guest under Gunyah, preventing KVM from initializing. The hypervisor boot message "Hypervisor cold boot, version: gunyah-cdfb73831" confirms the system is running in a virtualized environment where KVM cannot create /dev/kvm because it lacks the required EL2 privileges.

Possible fix: This is not a kernel regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables DRM VirtIO GPU config options). The KVM_Driver test failure is expected behavior on QCS8300-ride when running under Gunyah hypervisor. The test should either be skipped on platforms running under a hypervisor, or the test framework should detect nested virtualization scenarios and mark the test as "SKIP" rather than "FAIL". To fix the test: add a pre-check in the KVM test suite to detect if the system is running under a hypervisor (check for hypervisor boot messages or /sys/hypervisor presence) and skip KVM tests with appropriate messaging.

Detail analysis attachment: failed_case_job232513_2_detailed.md

Case 3: KVM_EL2_DTB — /dev/kvm device node unavailable

Failed case: KVM_EL2_DTB — /dev/kvm device node unavailable

Root cause: KVM is not supported on the qcs8300-ride (Monaco) platform. CONFIG_KVM is enabled in the kernel configuration, but the /dev/kvm device node is not created because the platform does not support hardware virtualization (VHE/nVHE) at EL2. This is a pre-existing platform limitation, not a regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118.

Possible fix: This is not a bug requiring a fix. The KVM_EL2_DTB test failure is expected on qcs8300-ride because this SoC does not support KVM/virtualization. The test should either be skipped on this platform or the CI job definition should exclude KVM tests for qcs8300-ride. No kernel changes are required. The PR changes (enabling DRM_VIRTIO_GPU configs) are unrelated to KVM host support and do not cause this failure.

Detail analysis attachment: failed_case_job232513_3_detailed.md

Case 4: KVM_Infra

Failed case: KVM_Infra

Root cause: /dev/kvm device node is not present on qcs8300-ride platform despite CONFIG_KVM being enabled in the kernel configuration, indicating that KVM/ARM virtualization support is not functional on this SoC/platform combination.

Possible fix: This is a pre-existing platform/infrastructure issue unrelated to the PR changes (which only add GPU virtualization config options). The qcs8300-ride platform either: (1) does not support ARM virtualization extensions (VHE/nVHE) in hardware/firmware, (2) has virtualization disabled in the bootloader/secure firmware, or (3) requires additional platform-specific KVM enablement patches. No action required for this PR — the failure is not PR-introduced. To enable KVM on qcs8300-ride: verify CPU supports EL2/virtualization extensions, check bootloader does not disable EL2, ensure secure firmware allows EL2 access, and confirm platform-specific KVM initialization code is present in the kernel.

Detail analysis attachment: failed_case_job232513_4_detailed.md

Case 5: ** 0_qcom-next-ci-premerge-tests

Failed case: ** 0_qcom-next-ci-premerge-tests

Root cause: ** LAVA infrastructure false-positive failure. The test suite completed successfully (all tests ran to completion, <LAVA_TEST_RUNNER EXIT> signal sent, lava_test_shell seems to have completed), but LAVA's completion detection logic incorrectly marked the run as "unfinished" and failed it. This is not a kernel issue — it's a LAVA dispatcher/harness bug where the completion signal was not properly recognized despite being present in the log.

Possible fix: Re-trigger the LAVA job. If the issue persists, investigate LAVA dispatcher completion detection logic — the test runner is correctly signaling completion but LAVA is not recognizing it. Check LAVA job definition for timeout/completion signal configuration issues.

Detail analysis attachment: failed_case_job232513_5_detailed.md

Job 232514 | SoC purwa-evk

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

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

Case 1: Kernel Crash — fastrpc use-after-free during cdsp recovery

Failed case: Kernel Crash — fastrpc use-after-free during cdsp recovery

Root cause: The kernel booted successfully but crashed at 39 seconds due to a use-after-free bug in the fastrpc driver. The cdsp (compute DSP) remoteproc crashed with a fatal error ("sleep_statsi.c:537"), triggering recovery. During recovery, the fastrpc driver attempted to unmap DMA buffers but accessed freed memory (poison pattern 0x6b6b6b6b6b6b6bb3), causing a kernel panic. The system then entered ramdump mode and Sahara protocol to collect crash artifacts, preventing LAVA from reaching the login prompt.

Possible fix: This is a pre-existing kernel bug in the fastrpc driver's error handling path during remoteproc recovery, unrelated to the PR changes (which only enable GPU virtualization configs). The fastrpc driver must be fixed to properly handle DMA buffer cleanup during cdsp recovery. Specifically, fastrpc_free_map() is being called on already-freed memory during fastrpc_req_mem_map() error path. The fix should ensure proper reference counting or state tracking to prevent double-free scenarios during remoteproc crash recovery.

Detail analysis attachment: failed_case_job232514_1_detailed.md

Case 2: ** Kernel Crash — Use-after-free in fastrpc DMA unmapping

Failed case: ** Kernel Crash — Use-after-free in fastrpc DMA unmapping

Root cause: ** The cdsprpcd daemon triggered a kernel panic at boot time (~39s) due to a use-after-free bug in the fastrpc driver's DMA buffer unmapping path. The faulting address 0x006b6b6b6b6b6bb3 contains the SLAB poison pattern (0x6b), indicating the code attempted to dereference a freed memory object. This crash occurred in dma_unmap_sg_attrs called from fastrpc_free_map, preventing the system from reaching the login prompt and causing all three auto-login attempts to timeout.

Possible fix: This is a pre-existing kernel bug in the fastrpc driver, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The crash should be reported to the fastrpc maintainers. As a workaround for CI: (1) Disable or blacklist the fastrpc module if CDSP functionality is not required for this test, or (2) Apply an upstream fix if available for this use-after-free issue in the fastrpc DMA unmapping path.

Detail analysis attachment: failed_case_job232514_2_detailed.md

Case 3: Kernel Crash — fastrpc use-after-free during CDSP remoteproc recovery

Failed case: Kernel Crash — fastrpc use-after-free during CDSP remoteproc recovery

Root cause: The kernel panicked at ~39 seconds into boot due to a use-after-free bug in the fastrpc driver (Unable to handle kernel paging request at virtual address 006b6b6b6b6b6bb3 - poison pattern 0x6b indicates freed memory access) during CDSP remoteproc crash recovery. After the panic-induced warm reboot, the system failed to reach login prompt within the 3-minute LAVA timeout across 3 retry attempts, causing the minimal-boot test to fail.

Possible fix: This is a pre-existing kernel bug in the fastrpc driver's memory management during remoteproc recovery, unrelated to the PR's GPU virtualization config changes (CONFIG_DRM_VIRTIO_GPU). The PR is not the root cause. To proceed with PR validation: (1) re-trigger the CI job to confirm if the crash is reproducible or transient; (2) if reproducible on purwa-evk, investigate the fastrpc driver's handling of DMA buffer cleanup during CDSP recovery (specifically fastrpc_free_map → dma_buf_unmap_attachment_unlocked path); (3) consider increasing LAVA login timeout from 3m to 5m to allow slower post-panic boot recovery on this platform.

Detail analysis attachment: failed_case_job232514_3_detailed.md

Case 4: Kernel Crash — Oops in fastrpc DMA buffer unmapping

Failed case: Kernel Crash — Oops in fastrpc DMA buffer unmapping

Root cause: Kernel Oops at 39.147590s in dma_unmap_sg_attrs+0x15c/0x1b0 triggered by fastrpc driver (cdsprpcd process) attempting to unmap a DMA buffer with a poisoned/freed scatterlist pointer (0x6b6b6b6b6b6b6b6b = SLUB poison pattern). The system panicked with "Oops: Fatal exception" and halted at 59.768365s, preventing login. This is a use-after-free bug in the fastrpc driver's DMA buffer lifecycle management.

Possible fix: This is a pre-existing kernel bug in the fastrpc driver, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The crash occurs in fastrpc_free_map → dma_buf_unmap_attachment_unlocked → system_heap_unmap_dma_buf → dma_unmap_sg_attrs, where a freed scatterlist is dereferenced. Recommended action: (1) Report this fastrpc driver bug to the kernel maintainers with the full crash log; (2) Re-run the LAVA job on the baseline branch (qcom-6.18.y without this PR) to confirm the crash reproduces independently of the PR changes; (3) If baseline also crashes, suppress this failure as a known pre-existing issue unrelated to GPU virtualization config changes.

Detail analysis attachment: failed_case_job232514_4_detailed.md

Job 232515 | SoC qcs615-ride

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

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

Case 1: Probe_Failure_Check — WiFi regulatory firmware false positive

Failed case: Probe_Failure_Check — WiFi regulatory firmware false positive

Root cause: The Probe_Failure_Check test detected a firmware load error for regulatory.db (cfg80211 wireless regulatory database). This is a known benign false positive — the error occurs because the test scans system logs for firmware-related errors before the WiFi driver has fully initialized. The WiFi_OnOff functional test passed, confirming that WiFi firmware loaded correctly at runtime and the subsystem is fully operational.

Possible fix: No fix required.** This is a known benign test artifact per LAVA suppression Rule 2. The Probe_Failure_Check test should be updated to exclude regulatory.db firmware load errors when the WiFi_OnOff test passes, or the test should run after all drivers have fully initialized. The PR (GPU virtualization config changes) is not related to this failure and should not be blocked by it.

Detail analysis attachment: failed_case_job232515_1_detailed.md

Case 2: smmu (IOMMU/SMMU test validation)

Failed case: smmu (IOMMU/SMMU test validation)

Root cause: The smmu test failed because two video codec sub-devices (aa00000.video-codec:video-decoder and aa00000.video-codec:video-encoder) are not attached to IOMMU groups, despite the parent video codec device (aa00000.video-codec) being correctly attached to IOMMU group 7. This is a test expectation issue, not a kernel regression introduced by the PR.

Possible fix: This is a false positive test failure. The PR only adds GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m) which are unrelated to IOMMU/SMMU or video codec device attachment. The test should be updated to reflect that video codec sub-devices (decoder/encoder) on qcs615-ride do not require separate IOMMU group attachments when the parent device is properly protected. No kernel fix is required.

Detail analysis attachment: failed_case_job232515_2_detailed.md

Case 3: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM is not available on qcs615-ride because the platform boots in a Gunyah-based hypervisor environment where HYP mode (EL2) is not available to the Linux kernel. The kernel log shows kvm [1]: HYP mode not available at boot time, which prevents the creation of /dev/kvm device node. This is a platform/firmware limitation, not a kernel bug.

Possible fix: This is expected behavior on qcs615-ride when running under Gunyah hypervisor. The test should be skipped on platforms where KVM is not supported due to hypervisor configuration. Add qcs615-ride to the KVM test exclusion list, or modify the test to check for HYP mode availability before reporting failure. The PR changes (enabling DRM_VIRTIO_GPU configs) are unrelated to this failure.

Detail analysis attachment: failed_case_job232515_3_detailed.md

Case 4: KVM_EL2_DTB — /dev/kvm unavailable (pre-existing platform limitation)

Failed case: KVM_EL2_DTB — /dev/kvm unavailable (pre-existing platform limitation)

Root cause: KVM hypervisor mode (EL2) is not available on qcs615-ride platform; kernel boot log shows "kvm [1]: HYP mode not available" at early boot, preventing /dev/kvm device node creation. This is a firmware/bootloader/hypervisor configuration issue where the platform is not booting Linux at EL2 or a Gunyah hypervisor is running at EL2 preventing KVM from taking control.

Possible fix: This is NOT a PR-introduced regression (PR only adds GPU virtualization config options unrelated to KVM). The failure is a pre-existing platform limitation. To enable KVM on qcs615-ride: (1) verify bootloader boots Linux at EL2 (not EL1), (2) if Gunyah hypervisor is present, ensure it exposes nested virtualization or is disabled for KVM testing, (3) verify device tree has no "no-map" or reserved-memory conflicts preventing EL2 usage, (4) check that CONFIG_KVM_ARM_HOST=y is set (not just CONFIG_KVM=m). For CI: suppress this test on qcs615-ride or mark as expected-fail until platform firmware is updated to support KVM.

Detail analysis attachment: failed_case_job232515_4_detailed.md

Case 5: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM cannot initialize on qcs615-ride because the Gunyah hypervisor is running at EL2, preventing Linux from accessing HYP mode; the kernel detects "HYP mode not available" during KVM initialization, causing /dev/kvm device node creation to fail.

Possible fix: This is a platform configuration issue, not a PR-introduced regression. The qcs615-ride target runs Gunyah hypervisor at EL2 by default, which blocks KVM host functionality. To enable KVM on this platform: (1) disable Gunyah hypervisor in the firmware/bootloader configuration, OR (2) use a nested virtualization configuration if supported by the platform, OR (3) exclude KVM tests from the qcs615-ride CI test suite as this platform is not intended to run as a KVM host.

Detail analysis attachment: failed_case_job232515_5_detailed.md

Case 6: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM is unavailable on qcs615-ride because the platform does not support HYP (EL2) mode — kernel message "[3.194781][T1] kvm [1]: HYP mode not available" indicates the CPU is not running with virtualization extensions enabled or the bootloader did not enter the kernel at EL2.

Possible fix: This is a platform/firmware limitation, not a PR-introduced regression. The PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM host support. To enable KVM on qcs615-ride: (1) verify the SoC supports virtualization extensions, (2) ensure the bootloader (ABL/XBL) is configured to enter the kernel at EL2, (3) if the platform does not support EL2, mark KVM tests as expected-fail for this target in the CI configuration.

Detail analysis attachment: failed_case_job232515_6_detailed.md

Job 232516 | SoC monaco-evk

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

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

Case 1: ** Probe_Failure_Check

Failed case: ** Probe_Failure_Check

Root cause: ** WiFi firmware file (ath11k/WCN6855/hw2.1/nfa765/amss.bin) missing from rootfs, causing ath11k_pci probe to fail with error -110 (ETIMEDOUT). BT firmware load errors are benign false positives because BT ON/OFF functional test passed.

Possible fix: Add missing WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin to the monaco-evk rootfs image. This is a rootfs packaging issue, not a kernel regression. PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (GPU virtualization config changes: CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) did not introduce this failure — these config changes are completely unrelated to WiFi/BT firmware loading subsystems.

Detail analysis attachment: failed_case_job232516_1_detailed.md

Case 2: WiFi_Firmware_Driver — WiFi driver probe failure

Failed case: WiFi_Firmware_Driver — WiFi driver probe failure

Root cause: ath11k_pci driver probe failed with error -110 (ETIMEDOUT) on monaco-evk; the WiFi PCIe device (0000:01:00.0) failed to respond during initialization, likely due to a timeout waiting for the device to become ready or firmware to load via MHI transport.

Possible fix: This is NOT a PR-introduced regression — the PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU) which are unrelated to WiFi/PCIe/ath11k. The failure is a pre-existing platform/board/firmware issue on monaco-evk. Re-run the test on a known-good baseline to confirm; if the issue persists, investigate PCIe link training, MHI firmware loading, or board-specific WiFi hardware/power sequencing on monaco-evk.

Detail analysis attachment: failed_case_job232516_2_detailed.md

Case 3: WiFi Driver Probe Failure — ath11k_pci probe timeout

Failed case: WiFi Driver Probe Failure — ath11k_pci probe timeout

Root cause: ath11k_pci driver probe failed with error -110 (ETIMEDOUT) on monaco-evk because MHI firmware (ath11k/WCN6855/hw2.1/nfa765/amss.bin) failed to load with error -2 (ENOENT), causing MHI power-up to timeout after the driver successfully completed "Power on setup success" but could not proceed without firmware.

Possible fix: This is a pre-existing infrastructure/firmware packaging issue unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The WiFi firmware file ath11k/WCN6855/hw2.1/nfa765/amss.bin is missing from the rootfs firmware directory. To resolve: (1) verify the firmware file exists in the build artifacts and is correctly packaged into the rootfs /lib/firmware/ directory, (2) if missing, add the firmware file to the firmware package or build configuration, (3) re-trigger the CI job with the corrected rootfs image.

Detail analysis attachment: failed_case_job232516_3_detailed.md

Case 4: LAVA Test Infrastructure Issue — Test run marked as unfinished

Failed case: LAVA Test Infrastructure Issue — Test run marked as unfinished

Root cause: LAVA dispatcher detected that the test definition 0_qcom-next-ci-premerge-tests completed its test runner (<LAVA_TEST_RUNNER EXIT> signal received) but LAVA's internal state tracking determined the test run was "unfinished", triggering an automatic failure marking with the error message "Marking unfinished test run as failed" at line 6717 of the log.

Possible fix: This is a LAVA infrastructure/dispatcher issue, not a kernel regression. The kernel booted successfully (Linux version 6.18.44-g9a727a423861 present at boot), and 44 out of 47 individual test cases passed. The three genuine test failures (Probe_Failure_Check, WiFi_Firmware_Driver, WiFi_OnOff) should be analyzed separately. To resolve the LAVA "unfinished" state: (1) Re-trigger the LAVA job to verify if this is a transient dispatcher state issue; (2) If the issue persists, check the LAVA job definition for missing test completion signals or timeout misconfigurations; (3) Review the test runner script (result_parse.sh) to ensure it properly signals completion to LAVA before exiting.

Detail analysis attachment: failed_case_job232516_4_detailed.md

Job 232517 | SoC shikra-iqs-evk

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

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

Case 1: GIC (Test Script Bug — Not a Kernel Issue)

Failed case: GIC (Test Script Bug — Not a Kernel Issue)

Root cause: The GIC test script contains a bash parsing error at line 75 that fails to correctly parse /proc/interrupts output when extracting per-CPU timer interrupt counts. The script attempts to use non-numeric fields (GICv3, Level, arch_timer) as integers in a comparison, causing bash "[: integer expected" errors. Additionally, the script incorrectly attempts to validate timer interrupts for CPUs 4-7, which do not exist on this shikra-iqs-evk platform (only CPUs 0-3 are present).

Possible fix: Fix the GIC test script /lava-232517/0/tests/0_qcom-next-ci-premerge-tests/Runner/suites/Kernel/Baseport/GIC/run.sh at line 75 to correctly parse /proc/interrupts by using proper field extraction (e.g., awk '{print $2, $3, $4, $5}' to get only the numeric interrupt counts for each CPU column). Additionally, the script must dynamically detect the number of online CPUs from /sys/devices/system/cpu/online instead of hardcoding CPU IDs, to avoid testing non-existent CPUs.

Detail analysis attachment: failed_case_job232517_1_detailed.md

Case 2: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: The Probe_Failure_Check test detected 7 kernel driver probe failures and 3 unresolved deferred probes on shikra-iqs-evk; all failures are pre-existing platform/configuration issues unrelated to the PR's GPU virtualization config changes (DRM_VIRTIO_GPU).

Possible fix: No kernel fix required — all probe failures are known platform limitations or expected behavior: (1) coresight-etm4x failures (-EINVAL) are due to missing/incomplete ETM device tree configuration for this SoC; (2) cpufreq-dt failure (-EEXIST) indicates another cpufreq driver already registered; (3) regulatory.db firmware missing is expected when wireless regulatory database is not installed in rootfs; (4) tpm_tis_spi timeout (-ETIMEDOUT) suggests TPM hardware not present or not responding; (5) deferred probes for audio codec/sound card are expected when audio subsystem dependencies are not fully met. The PR only adds GPU virtualization config options and does not touch any of the failing subsystems. Mark test as expected-fail or update test to exclude known platform-specific probe failures.

Detail analysis attachment: failed_case_job232517_2_detailed.md

Case 3: PCIe

Failed case: PCIe

Root cause: PCIe test failed due to missing QPS615 PCIe switch firmware file (TC956X_Firmware_PCIeBridge.bin) in the root filesystem — this is a pre-existing test infrastructure issue, not a kernel regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118

Possible fix: Add TC956X_Firmware_PCIeBridge.bin to the root filesystem firmware directory (/lib/firmware or equivalent) in the LAVA test image; this is a test infrastructure fix, not a kernel code fix

Detail analysis attachment: failed_case_job232517_3_detailed.md

Case 4: USBHost

Failed case: USBHost

Root cause: USB host mode is not available on shikra-iqs-evk platform — the USB controller at 4e00000.usb is configured in device/gadget mode only, with no xHCI host controller or USB root hubs exposed in sysfs, and the test cannot confirm an inactive device role to validate host capability.

Possible fix: This is a platform configuration issue, not a PR-introduced regression. The PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which do not affect USB subsystem. The shikra-iqs-evk board's USB controller is configured for gadget mode only (evidenced by "Hardware activated USB gadget" systemd target and absence of xHCI/root hub initialization). To enable USB host mode, the device tree for shikra-iqs-evk must be updated to configure the DWC3 USB controller's dr_mode property to "host" or "otg" instead of "peripheral", and the xHCI host controller driver must be enabled in the kernel config.

Detail analysis attachment: failed_case_job232517_4_detailed.md

Case 5: BT_FW_KMD_Service

Failed case: BT_FW_KMD_Service

Root cause: Bluetooth HCI UART communication failure on shikra-iqs-evk — QCA Bluetooth controller (wcn399x) fails to respond to HCI commands during firmware setup, resulting in repeated command tx timeouts (-110 ETIMEDOUT) and inability to read QCA version information, preventing firmware load and leaving hci0 in DOWN state with invalid BD address 00:00:00:00:00:00.

Possible fix: This is a hardware/firmware communication issue specific to the shikra-iqs-evk platform's Bluetooth UART interface. The PR changes (GPU virtualization config) are unrelated to Bluetooth. Recommended actions: (1) Verify UART pinmux/GPIO configuration for Bluetooth in shikra device tree, (2) Check if Bluetooth power/enable GPIO is correctly configured and asserted, (3) Verify wcn399x firmware files are present and correct version for this hardware, (4) Check for known errata with wcn399x on this SoC revision, (5) Test with a known-good kernel baseline to confirm if this is a pre-existing platform issue or a regression.

Detail analysis attachment: failed_case_job232517_5_detailed.md

Case 6: **Bluetooth Driver Communication Failure — BT_ON_OFF**

Failed case: Bluetooth Driver Communication Failure — BT_ON_OFF

Root cause: Bluetooth HCI adapter hci0 (WCN399x) fails to communicate with the Qualcomm Bluetooth firmware during initialization; repeated command timeouts (-ETIMEDOUT, error -110) when attempting to read QCA version information prevent the adapter from acquiring a valid BD address, leaving the Bluetooth runtime unusable despite multiple recovery attempts.

Possible fix: This is a hardware/firmware/platform integration issue unrelated to the PR changes (GPU virtualization config). The PR only enables CONFIG_DRM_VIRTIO_GPU and CONFIG_DRM_VIRTIO_GPU_KMS which have no dependency on or interaction with the Bluetooth subsystem. Recommended action: (1) Verify UART/transport layer connectivity between AP and Bluetooth SoC on shikra-iqs-evk hardware; (2) Confirm WCN399x firmware files are present and accessible at expected paths; (3) Check for known errata or board-specific initialization sequences required for WCN399x on Shikra IQS EVK; (4) If this is a known board/lab infrastructure issue, add BT_ON_OFF to the suppression list for shikra-iqs-evk until hardware/firmware is fixed.

Detail analysis attachment: failed_case_job232517_6_detailed.md

Case 7: ** BT_SCAN

Failed case: ** BT_SCAN

Root cause: ** Bluetooth QCA driver (btqca) fails to initialize the WCN399x Bluetooth controller on shikra-iqs-evk from boot onwards. The driver repeatedly times out attempting to read QCA version information (error -110 = -ETIMEDOUT), indicating the Bluetooth firmware/controller is not responding to HCI commands. This is a pre-existing hardware/firmware communication failure, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options).

Possible fix: This is a platform-specific Bluetooth bring-up issue on shikra-iqs-evk. Recommended actions: (1) Verify Bluetooth firmware files are present in /lib/firmware/qca/ for WCN399x; (2) Check device tree configuration for the Bluetooth UART node and associated regulators/clocks/GPIOs; (3) Verify the Bluetooth controller is powered and clocked correctly; (4) Check for any board-specific errata or known issues with WCN399x on this platform. The PR changes (GPU virtualization config) are unrelated to Bluetooth and did not cause this failure.

Detail analysis attachment: failed_case_job232517_7_detailed.md

Case 8: ** Kernel Crash — Synchronous External Abort (Bus Error)

Failed case: ** Kernel Crash — Synchronous External Abort (Bus Error)

Root cause: ** Hardware RNG (qcom_rng) driver attempted to read from an MMIO register (0xffff800082e05004) that triggered a bus-level external abort, indicating the RNG hardware block was either not powered/clocked correctly, in a bad power state, experiencing a hardware fault, or accessed at the wrong address due to platform-specific configuration mismatch.

Possible fix: This is a platform/hardware configuration issue on shikra-iqs-evk, not a kernel regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118. The PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) which are unrelated to RNG hardware. Recommended actions:

Detail analysis attachment: failed_case_job232517_8_detailed.md

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

Failed case: Kernel Crash — Synchronous External Abort in qcom_rng driver

Root cause: Hardware access fault in qcom_rng_read() at offset +0xc4 when reading from MMIO register during HWRNG test execution. The crash signature synchronous external abort: 0000000096000010 indicates a bus-level fault accessing the RNG hardware registers, followed by cascading EFI runtime service failures during panic handling. This is a pre-existing hardware/driver issue unrelated to the PR's GPU virtualization config changes.

Possible fix: This is not a PR-introduced regression. The PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) which have no relationship to the RNG hardware driver. The crash occurs in the qcom_rng module when accessing hardware registers, suggesting either: (1) hardware not properly initialized/powered, (2) incorrect MMIO mapping in device tree for shikra-iqs-evk, or (3) clock/power domain issue. Recommended action: investigate shikra-iqs-evk device tree RNG node configuration, verify RNG hardware power/clock dependencies, and check if this is a known board-specific issue. The KVM_EL2_DTB test failure (missing /dev/kvm) is a separate pre-existing issue — KVM device node creation requires proper hypervisor/EL2 support which may not be configured on this platform.

Detail analysis attachment: failed_case_job232517_9_detailed.md

Case 10: Kernel Crash — Synchronous External Abort (Hardware Access Fault)

Failed case: Kernel Crash — Synchronous External Abort (Hardware Access Fault)

Root cause: The qcom_rng driver triggered a synchronous external abort (bus error) at offset +0xc4 in qcom_rng_read() while attempting to read from the hardware RNG MMIO registers on the Shikra IQS EVK platform. The crash occurred during the qcom_hwrng test execution when userspace (dd command via /dev/hwrng) attempted to read random data. The abort indicates the hardware RNG block was either not powered, not clocked, inaccessible due to incorrect MMIO mapping, or the hardware itself is in a fault state.

Possible fix: Verify that the qcom_rng device tree node for Shikra (QCM2290) includes correct MMIO base address, size, and all required dependencies (clocks, power domains, interconnects). Check that the RNG hardware block is properly powered and clocked before driver access. Add runtime PM calls or explicit clock/power domain enablement in the qcom_rng driver probe path if missing. If the hardware is known to be non-functional on this platform, disable CONFIG_HW_RANDOM_QCOM or mark the DT node as status="disabled" for Shikra.

Detail analysis attachment: failed_case_job232517_10_detailed.md

Case 11: Kernel Crash — synchronous external abort in qcom_rng driver

Failed case: Kernel Crash — synchronous external abort in qcom_rng driver

Root cause: The qcom_rng driver attempted to read from an unmapped or inaccessible hardware register (synchronous external abort at PC: qcom_rng_read+0xc4), causing a fatal exception during the qcom_hwrng test execution. The crash occurred at timestamp [1233.398299] when the dd command was reading from /dev/hwrng, triggering a hardware access fault in the qcom_rng module.

Possible fix: This is NOT a PR-introduced regression. The PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) which are unrelated to the RNG hardware driver. The qcom_rng driver crash is a pre-existing platform/firmware issue on shikra-iqs-evk where the RNG hardware registers are not properly mapped or accessible. Recommended action: (1) Verify RNG device tree configuration for shikra-iqs-evk includes correct register mappings; (2) Check if RNG hardware is powered/clocked correctly; (3) Consider disabling qcom_hwrng test on shikra-iqs-evk until hardware access is fixed; (4) The PR itself is safe to merge as it does not touch RNG subsystem.

Detail analysis attachment: failed_case_job232517_11_detailed.md

Case 12: Kernel Crash — synchronous external abort in qcom_rng driver

Failed case: Kernel Crash — synchronous external abort in qcom_rng driver

Root cause: The kernel panicked with a synchronous external abort (bus error) at PC qcom_rng_read+0xc4/0x228 while the qcom_hwrng test was reading entropy from /dev/hwrng. The crash occurred when the qcom_rng driver attempted to access a hardware register (instruction b940035c = ldr w28, [x26, #0]), indicating the MMIO mapping for the RNG hardware is invalid, inaccessible, or the hardware is not powered/clocked correctly on shikra-iqs-evk.

Possible fix: This is a pre-existing platform-specific driver bug, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization configs). The qcom_rng driver probe or runtime power/clock management is broken on shikra-iqs-evk. Recommended actions: (1) Disable the qcom_hwrng test on shikra-iqs-evk until the driver is fixed, or (2) investigate the qcom_rng driver's MMIO base address, clock/regulator dependencies, and device tree bindings for shikra (QCM2290) to identify why the hardware register access faults.

Detail analysis attachment: failed_case_job232517_12_detailed.md

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

Failed case: ** Kernel Crash — Synchronous External Abort in qcom_rng driver

Root cause: ** The qcom_hwrng test triggered a synchronous external abort at PC qcom_rng_read+0xc4 when attempting to read from the hardware RNG MMIO register at address 0x000a03783443d000. The abort indicates the hardware RNG block was either not powered/clocked correctly, or the MMIO address mapping is invalid for shikra-iqs-evk. The crash occurred during a load instruction (ldr w28, [x26, #0]), suggesting the RNG hardware block did not respond to the bus transaction.

Possible fix: This is a pre-existing hardware/driver issue on shikra-iqs-evk, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables GPU virtualization config options CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m). Recommended actions: (1) Disable the qcom_hwrng test for shikra-iqs-evk in the LAVA test suite until the RNG driver is fixed; (2) Investigate whether the RNG hardware block requires explicit power domain or clock enablement in the device tree for this platform; (3) Verify the RNG MMIO base address in the device tree matches the hardware specification for shikra SoC.

Detail analysis attachment: failed_case_job232517_13_detailed.md

Case 14: ** Test Timeout — Kernel Crash (synchronous external abort in qcom_rng driver)

Failed case: ** Test Timeout — Kernel Crash (synchronous external abort in qcom_rng driver)

Root cause: ** Result: The LAVA test suite timed out after 2400 seconds because the kernel panicked during the qcom_hwrng test with a synchronous external abort (hardware bus error code 0x96000010) at PC qcom_rng_read+0xc4/0x228 when the qcom_rng driver attempted to read from hardware RNG MMIO register at virtual address 0xffff800082e05004. The faulting instruction was ldr w28, [x26, #0] (opcode b940035c). This indicates the RNG hardware block either failed to respond to the MMIO read, was not clocked/powered correctly, or the MMIO mapping is incorrect for shikra-iqs-evk. This is a hardware/platform-specific issue unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118.

Possible fix: This is a pre-existing platform/hardware issue on shikra-iqs-evk, NOT a kernel regression introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118. The PR changes are limited to enabling two GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m in arch/arm64/configs/qcom.config) and cannot cause a synchronous external abort in the RNG driver. Recommended action: Mark this test failure as NOT BLOCKING for PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 merge. File a separate bug for the shikra-iqs-evk RNG hardware access issue with the platform/board bring-up team. The RNG driver or device tree for shikra may need fixes: verify MMIO base address in device tree, add missing clock/power dependencies, or implement hardware errata workaround.

Detail analysis attachment: failed_case_job232517_14_detailed.md

Job 232518 | SoC qcs9100-ride

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

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

Case 1: Probe_Failure_Check — Ethernet PHY probe failure

Failed case: Probe_Failure_Check — Ethernet PHY probe failure

Root cause: Aquantia AQR115C Ethernet PHY driver probe failed with error -22 (EINVAL) on qcs9100-ride because the device tree node is missing the required firmware-name property that the driver expects to read for PHY firmware configuration

Possible fix: Add the firmware-name property to the Aquantia AQR115C PHY device tree node in arch/arm64/boot/dts/qcom/qcs9100-ride.dts (or the appropriate board DTS file) with the correct firmware filename, or update the driver to make this property optional if firmware loading is not required for basic PHY operation on this platform

Detail analysis attachment: failed_case_job232518_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Video codec device aa00000.video-codec is not attached to any IOMMU group on qcs9100-ride platform; the SMMU test detected this missing IOMMU protection for a critical master device during runtime validation.

Possible fix: This is NOT a PR-introduced regression — the PR only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU) which are unrelated to video codec IOMMU attachment. This is a pre-existing platform/DT configuration issue where the video codec device tree node lacks proper iommus property binding. To fix: add the appropriate iommus property to the aa00000.video-codec device tree node in arch/arm64/boot/dts/qcom/qcs9100.dtsi referencing the correct SMMU context bank.

Detail analysis attachment: failed_case_job232518_2_detailed.md

Case 3: Ethernet_Basic_Validation

Failed case: Ethernet_Basic_Validation

Root cause: The end0 Ethernet interface (qcom-ethqos driver at 23040000.ethernet) fails to attach to its PHY during interface bring-up with error -EINVAL, preventing the interface from becoming administratively up. This is a pre-existing platform/hardware configuration issue unrelated to the PR changes (which only enable GPU virtualization config options).

Possible fix: Investigate the PHY configuration for the end0 interface on qcs9100-ride. Check device tree bindings for the Ethernet PHY node at 23040000.ethernet, verify PHY address/MDIO bus configuration, and ensure PHY driver is loaded. The error -EINVAL typically indicates a mismatch between the MAC driver's expectations and the PHY configuration (e.g., incorrect phy-handle, missing PHY node, or incompatible PHY mode). This is a board-specific hardware/DT issue, not a kernel regression introduced by this PR.

Detail analysis attachment: failed_case_job232518_3_detailed.md

Case 4: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM hypervisor mode (EL2) is not available on the qcs9100-ride platform — kernel reports "kvm [1]: HYP mode not available" during boot, preventing /dev/kvm device node creation despite CONFIG_KVM=y being enabled.

Possible fix: This is a platform/firmware configuration issue, not a kernel regression introduced by this PR. The PR only enables DRM_VIRTIO_GPU configs for GPU virtualization and does not touch KVM core code. The failure is pre-existing: the qcs9100-ride platform firmware does not boot the kernel in EL2 (hypervisor mode), which is a prerequisite for KVM functionality on ARM64. To resolve: (1) verify the bootloader/firmware boots the kernel at EL2 by checking the boot chain configuration; (2) if the platform does not support EL2, mark KVM tests as "not applicable" for this target in the CI test matrix; (3) if EL2 support is expected, update the firmware/bootloader to enable hypervisor mode.

Detail analysis attachment: failed_case_job232518_4_detailed.md

Case 5: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM is not available on qcs9100-ride because the Gunyah hypervisor is running at EL2, preventing KVM from initializing. The kernel message "kvm [1]: HYP mode not available" at boot time confirms that KVM detected it cannot run because EL2 is already occupied by the Gunyah hypervisor.

Possible fix: This is a platform configuration issue, not a kernel bug or PR-introduced regression. The qcs9100-ride platform runs the Gunyah hypervisor by default, which prevents KVM from operating. To enable KVM testing on this platform: (1) disable Gunyah hypervisor in the firmware/bootloader configuration, OR (2) exclude KVM tests from the CI test suite for qcs9100-ride and other Gunyah-enabled platforms, OR (3) use nested virtualization if Gunyah supports it (requires Gunyah configuration changes, not kernel changes).

Detail analysis attachment: failed_case_job232518_5_detailed.md

Case 6: KVM_Infra — /dev/kvm device node unavailable (platform lacks EL2/HYP mode support)

Failed case: KVM_Infra — /dev/kvm device node unavailable (platform lacks EL2/HYP mode support)

Root cause: The qcs9100-ride platform does not support KVM virtualization because the hardware/firmware does not provide EL2 (Hypervisor mode) access, as evidenced by the kernel boot message kvm [1]: HYP mode not available at initialization.

Possible fix: This is not a kernel bug or PR-introduced regression. The qcs9100-ride platform does not support KVM virtualization due to hardware/firmware limitations. To resolve: (1) exclude KVM tests from the CI test suite for qcs9100-ride, or (2) if KVM support is required, verify that the platform firmware enables EL2 and that the bootloader is not dropping to EL1 before kernel entry.

Detail analysis attachment: failed_case_job232518_6_detailed.md

Case 7: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM device node /dev/kvm is not created at runtime despite CONFIG_KVM being enabled in the kernel configuration, indicating either KVM initialization failed silently during boot or the platform (qcs9100-ride/LeMans) does not support KVM virtualization extensions (EL2/VHE) required for /dev/kvm creation.

Possible fix: Check dmesg for KVM initialization messages (dmesg | grep -i kvm) to determine if KVM failed to initialize; if no KVM messages appear, verify that the qcs9100-ride platform firmware and hardware support ARM virtualization extensions (EL2) and that the kernel is booted at EL2 (not EL1); if KVM init failed, investigate the specific error; if platform lacks EL2 support, mark KVM tests as not applicable for this target.

Detail analysis attachment: failed_case_job232518_7_detailed.md

Job 232519 | SoC qcs6490-rb3gen2

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

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

Case 1: GIC Test Failure — Test Script Bug (CPU Offline Detection)

Failed case: GIC Test Failure — Test Script Bug (CPU Offline Detection)

Root cause: The GIC test script fails on qcs6490-rb3gen2 because CPUs 6 and 7 failed to boot during kernel initialization (PSCI error -22: -EINVAL), but the test script does not handle offline CPUs correctly. The script parses /proc/interrupts expecting 8 columns (one per possible CPU 0-7), but only 6 columns exist (CPUs 0-5 online). At line 75, the script attempts integer comparison on the string "GICv3" (the 7th field), causing a bash syntax error and incorrectly reporting CPUs 6-7 as failed.

Possible fix: This is a test infrastructure bug, not a kernel regression. The GIC test script must be updated to: (1) read /sys/devices/system/cpu/online to determine which CPUs are actually online, (2) skip timer interrupt validation for offline CPUs, and (3) report SKIP (not FAIL) for offline CPUs. The kernel behavior is correct — CPUs 6-7 are legitimately offline due to platform/firmware configuration (PSCI boot failure is expected on this board configuration).

Detail analysis attachment: failed_case_job232519_1_detailed.md

Case 2: ** Probe_Failure_Check

Failed case: ** Probe_Failure_Check

Root cause: ** The test detected 2 probe/firmware errors in dmesg: (1) regulatory.db firmware load failure (benign — cfg80211 regulatory database missing from rootfs), and (2) xhci-pci-renesas driver probe failure with error -2 (ENOENT — Renesas USB firmware renesas_usb_fw.mem missing from rootfs). Both are pre-existing firmware packaging issues in the test rootfs, NOT regressions introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables DRM VirtIO GPU kernel configs).

Possible fix: This is a false positive. The PR changes (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) do not touch USB, PCIe, or regulatory subsystems. The Probe_Failure_Check test should either (1) suppress known-missing firmware errors (regulatory.db, renesas_usb_fw.mem) as benign, or (2) the test rootfs should be updated to include these firmware files. No kernel code fix is required.

Detail analysis attachment: failed_case_job232519_2_detailed.md

Case 3: Freq_Scaling

Failed case: Freq_Scaling

Root cause: Test script logic error — the test successfully validated cpufreq interfaces for all 7 CPUs (cpu0-cpu6) on qcs6490-rb3gen2, but then incorrectly printed "CPUFreq interface not found. Test Failed" and reported FAIL despite all individual CPU checks passing.

Possible fix: Fix the test script logic in Runner/suites/Kernel/DCVS/Freq_Scaling/run.sh — the script appears to check for an 8th CPU (cpu7) which does not exist on this 7-CPU SoC, or has incorrect loop termination logic that causes it to report failure after successfully validating all present CPUs.

Detail analysis attachment: failed_case_job232519_3_detailed.md

Case 4: KVM_Driver — /dev/kvm device node not created

Failed case: KVM_Driver — /dev/kvm device node not created

Root cause: KVM failed to initialize because the Gunyah hypervisor is running at EL2, preventing Linux KVM from taking control of HYP mode. The kernel log shows "kvm [1]: HYP mode not available" at boot time, which occurs when KVM detects that EL2 is already occupied by another hypervisor. On qcs6490-rb3gen2, the Gunyah hypervisor boots first and remains resident at EL2, making HYP mode unavailable to the Linux kernel's KVM subsystem.

Possible fix: This is a platform configuration issue, not a kernel regression introduced by the PR. The PR only enables DRM_VIRTIO_GPU configs for GPU virtualization support and does not modify KVM or hypervisor initialization. To enable KVM on this platform, either: (1) disable the Gunyah hypervisor in the boot chain (ABL/UEFI) to allow Linux KVM to take EL2, or (2) use nested virtualization if Gunyah supports it, or (3) accept that KVM is not available on platforms where Gunyah is the primary hypervisor. This is a known platform limitation, not a PR-introduced bug.

Detail analysis attachment: failed_case_job232519_4_detailed.md

Case 5: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM cannot initialize on qcs6490-rb3gen2 because the platform does not support HYP (Hypervisor) mode at EL2. The kernel boot log shows kvm [1]: HYP mode not available at initialization, preventing /dev/kvm device node creation. This is a platform hardware/firmware limitation, not a kernel software issue.

Possible fix: This is a pre-existing platform limitation unrelated to PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only adds GPU virtualization config options). The qcs6490-rb3gen2 platform does not support KVM virtualization. To resolve: (1) Skip KVM tests on this platform in CI configuration, or (2) Use a platform with EL2/HYP support (e.g., platforms with virtualization extensions enabled in firmware/bootloader). No kernel code fix is required.

Detail analysis attachment: failed_case_job232519_5_detailed.md

Case 6: KVM_Infra — /dev/kvm not available (HYP mode unavailable)

Failed case: KVM_Infra — /dev/kvm not available (HYP mode unavailable)

Root cause: KVM initialization failed because the qcs6490-rb3gen2 platform booted without EL2/HYP mode available. The kernel message kvm [1]: HYP mode not available at boot time (4.6s) indicates the CPU did not enter or was not configured to support hypervisor mode, preventing KVM driver from creating /dev/kvm. This is a platform/firmware/bootloader configuration issue, not a kernel regression.

Possible fix: This is a pre-existing platform limitation, not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only adds GPU virtualization config). To enable KVM on qcs6490-rb3gen2: (1) verify bootloader/firmware supports EL2 mode and is configured to boot kernel at EL2; (2) check device tree for hypervisor node and EL2 enablement; (3) if platform does not support EL2, mark KVM tests as "skip" for this target in CI configuration rather than "fail".

Detail analysis attachment: failed_case_job232519_6_detailed.md

Case 7: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM infrastructure test failed because /dev/kvm device node is not present; kernel reports "kvm [1]: HYP mode not available" at boot, indicating the qcs6490-rb3gen2 (Kodiak) platform does not support hardware virtualization (EL2/HYP mode is not available on this SoC).

Possible fix: This is not a PR-introduced regression — the PR only enables DRM VirtIO GPU config options (CONFIG_DRM_VIRTIO_GPU=m, CONFIG_DRM_VIRTIO_GPU_KMS=m) which are unrelated to KVM/hypervisor availability. The failure is a pre-existing platform limitation: qcs6490-rb3gen2 does not support KVM because the hardware/firmware does not provide EL2 (hypervisor) mode. Either (1) skip KVM tests on this platform, or (2) run KVM tests only on platforms with EL2 support (e.g., SA8775P, SA8540P, or other automotive/server-class SoCs).

Detail analysis attachment: failed_case_job232519_7_detailed.md

Job 232520 | SoC hamoa-evk

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Three pre-existing platform-specific probe failures unrelated to the PR changes (GPU virtualization config): (1) qcom_qseecom_uefisecapp probe failure (-EBUSY) due to TrustZone resource unavailability on hamoa-evk, (2) qcom-spmi-lpg probe failure (-EINVAL) due to invalid multi-LED device tree configuration, (3) regulatory.db firmware load failure (-ENOENT) due to missing optional wireless regulatory database file in rootfs.

Possible fix: These failures are not introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 (which only enables CONFIG_DRM_VIRTIO_GPU=m and CONFIG_DRM_VIRTIO_GPU_KMS=m). All three failures are pre-existing platform/configuration issues visible across the baseline: (1) qcom_qseecom_uefisecapp failure is a known TrustZone resource contention issue on X Elite platforms — no kernel fix required, this is expected behavior when TZ resources are in use; (2) qcom-spmi-lpg failure requires device tree fix to correct the "reg" property of the multi-LED node under c42d000.spmi:pmic@1:pwm; (3) regulatory.db failure is benign — the kernel falls back to built-in regulatory rules and WiFi functionality is unaffected (cfg80211 loaded successfully). Recommendation: Mark this test case as PASS with suppression note, as none of the failures are regressions introduced by this PR.

Detail analysis attachment: failed_case_job232520_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: The smmu test failed because 6 critical device masters (5 USB TCSR controllers at addresses a0f8800, a2f8800, a4f8800, a6f8800, a8f8800 and 1 video codec at aa00000) are missing IOMMU group attachments on hamoa-evk platform. This is a pre-existing platform/device-tree configuration issue, NOT introduced by PR QCLINUX: arm64: configs: Enable GPU virtualization #1118 which only enables GPU virtualization config options (CONFIG_DRM_VIRTIO_GPU).

Possible fix: This is a known platform configuration issue on hamoa-evk where certain USB TCSR (Top-Level Control and Status Register) controllers and the video codec device are not properly described in the device tree with IOMMU bindings. The PR changes (enabling DRM_VIRTIO_GPU) do not affect SMMU/IOMMU device attachment. No action required for this PR — the failure is a pre-existing baseline issue that should be tracked separately for hamoa-evk platform DT fixes.

Detail analysis attachment: failed_case_job232520_2_detailed.md

Case 3: KVM_Driver

Failed case: KVM_Driver

Root cause: KVM initialization failed because the hamoa-evk platform does not support EL2 hypervisor mode — kernel message kvm [1]: HYP mode not available at boot indicates the CPU is not running in or cannot enter HYP mode, preventing /dev/kvm device node creation.

Possible fix: This is a platform hardware/firmware limitation, not a kernel regression. The hamoa-evk board either lacks EL2 support in its CPU configuration or the bootloader/firmware has not enabled EL2. No kernel-side fix is possible. To enable KVM on this platform: (1) verify the SoC supports virtualization extensions (ARMv8-A with EL2), (2) ensure the bootloader (ABL/UEFI) boots the kernel at EL2 instead of EL1, (3) check secure firmware (TZ) configuration allows EL2 access. If the platform fundamentally lacks EL2 support, KVM tests should be excluded from the CI test suite for this target.

Detail analysis attachment: failed_case_job232520_3_detailed.md

Case 4: KVM_EL2_DTB

Failed case: KVM_EL2_DTB

Root cause: KVM cannot initialize because the kernel is running under the Gunyah hypervisor at EL1, not at EL2 (HYP mode). The kernel message "kvm [1]: HYP mode not available" at boot time confirms KVM initialization failed. Without KVM initialization, the /dev/kvm device node is never created, causing all KVM-dependent tests to fail.

Possible fix: This is not a PR-introduced regression. The PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM host functionality. The failure is a pre-existing platform limitation: hamoa-evk boots with Gunyah hypervisor ("Gunyah based bootup", "Hypervisor cold boot, version: gunyah-mobile-ad1fb25c6"), which prevents nested virtualization. To enable KVM on this platform, either: (1) boot without the Gunyah hypervisor (bare-metal mode), or (2) configure Gunyah to support nested virtualization (if supported). The test expectation should be updated to skip KVM tests on Gunyah-based boots.

Detail analysis attachment: failed_case_job232520_4_detailed.md

Case 5: KVM_Infra — /dev/kvm not available (platform limitation, not PR-introduced)

Failed case: KVM_Infra — /dev/kvm not available (platform limitation, not PR-introduced)

Root cause: The hamoa-evk platform does not support KVM because HYP mode (EL2 hypervisor) is not available on this hardware. The kernel message kvm [1]: HYP mode not available at boot time indicates that the ARM virtualization extensions required for KVM are not enabled or accessible on this SoC/board configuration.

Possible fix: This is not a kernel bug or PR-introduced regression. The KVM_Infra test should be skipped on platforms that do not support virtualization. Add hamoa-evk to the test exclusion list for KVM-related tests, or modify the test framework to detect HYP mode not available and mark the test as SKIP rather than FAIL.

Detail analysis attachment: failed_case_job232520_5_detailed.md

Case 6: KVM_Infra

Failed case: KVM_Infra

Root cause: KVM cannot initialize on hamoa-evk because the platform is running under the Gunyah hypervisor in EL1 mode, preventing KVM from accessing EL2 (HYP mode). The kernel log shows "kvm [1]: HYP mode not available" at boot, and CONFIG_KVM is enabled but /dev/kvm device node is never created because kvm_init() fails when it detects the system is already running under a hypervisor.

Possible fix: This is not a PR-introduced regression. The PR only enables GPU virtualization configs (CONFIG_DRM_VIRTIO_GPU) which are unrelated to KVM availability. The hamoa-evk platform uses Gunyah hypervisor by design (evidenced by reserved memory regions "gunyah-hyp@80000000" and "hyp-elf-package@80800000" in device tree, and hypervisor boot messages). KVM tests should be skipped on this platform, or the platform should be configured to run without Gunyah if native KVM support is required. No kernel code fix is needed — this is a test infrastructure / platform configuration issue.

Detail analysis attachment: failed_case_job232520_6_detailed.md

Job 232521 | SoC lemans-evk

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

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

Case 1: Probe_Failure_Check

Failed case: Probe_Failure_Check

Root cause: Test detected four SPMI PMIC temp-alarm devices stuck in deferred probe state and three benign firmware load failures (regulatory.db and Bluetooth firmware files) that are known false positives on lemans-evk platform

Possible fix: The deferred probe warnings for temp-alarm devices (c440000.spmi:pmic@{0,2,4,6}:temp-alarm@a00) are pre-existing platform issues not introduced by this PR (GPU virtualization config change). The Bluetooth firmware failures are suppressed per known-benign rules since BT_ON_OFF functional test passed. No action required for this PR — the Probe_Failure_Check test should be updated to exclude these known platform-specific deferred probe patterns for lemans-evk

Detail analysis attachment: failed_case_job232521_1_detailed.md

Case 2: smmu

Failed case: smmu

Root cause: Test infrastructure failure — the SMMU test script encountered an output truncation or buffer overflow while dumping IOMMU kernel log lines (40-line cap), causing the test result file to be malformed and triggering a FAIL signal despite all functional checks passing.

Possible fix: This is a test infrastructure issue, not a kernel regression. The PR changes (enabling DRM_VIRTIO_GPU configs) are unrelated to SMMU functionality. Re-run the test; if the issue persists, increase the IOMMU log line cap in the test script or investigate the test harness output buffering.

Detail analysis attachment: failed_case_job232521_2_detailed.md

Case 3: ** Test Suite Incomplete — LAVA test runner exited prematurely

Failed case: ** Test Suite Incomplete — LAVA test runner exited prematurely

Root cause: ** The LAVA test runner completed execution but marked the test definition as failed because not all planned tests were executed. The test runner listed 4 remaining test result files (CPU_affinity.res, Freq_Scaling.res, irq.res, smmu.res) immediately before exiting, indicating these tests ran but their results were not properly reported to LAVA before the runner terminated.

Possible fix: This is a LAVA test infrastructure issue, not a kernel regression. The test runner's result parsing or reporting mechanism failed to process all test results before exit. Re-trigger the CI job. If the issue persists, investigate the LAVA test runner's result collection logic in the qcom-linux-testkit repository (Runner/utils/result_parse.sh) to ensure all .res files are processed before the runner signals completion.

Detail analysis attachment: failed_case_job232521_3_detailed.md

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

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

Target	Boot lines (PR)	Boot lines (baseline)	New issues	High	Medium	Low
`qcs8300-ride`	1141	no baseline	29	2	27	0
`purwa-evk`	1532	no baseline	38	1	35	2
`qcs615-ride`	963	no baseline	5	0	5	0
`monaco-evk`	1069	no baseline	10	0	10	0
`shikra-iqs-evk`	902	no baseline	9	0	9	0
`qcs9100-ride`	1306	no baseline	15	2	12	1
`qcs6490-rb3gen2`	1047	no baseline	17	0	16	1
`hamoa-evk`	1727	no baseline	24	1	23	0
`lemans-evk`	1707	no baseline	15	2	12	1

⚠️ 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: 162 new issue(s) across 9 target(s).

Target: `qcs8300-ride`

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

🟡 WARNING (medium)

[    5.230006][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98

Context

[    5.228979][   T63] qcom-pcie 1c10000.pci: supply vdda not found, using dummy regulator
[    5.229460][    T1] clk: Disabling unused clocks
[    5.230004][    T1] ------------[ cut here ]------------
[    5.230006][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98
[    5.230013][    T1] Modules linked in:
[    5.230018][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G S      W           6.18.44-g9a727a423861 #1 PREEMPT 
[    5.230021][    T1] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN

🟠 CALL_TRACE (high)

[    5.230054][    T1] Call trace:

Context

[    5.230047][    T1] x8 : ffff800082c3bbe8 x7 : 0000000000000000 x6 : 0000000000000001
[    5.230049][    T1] x5 : ffff800080b41778 x4 : 000000000007706c x3 : 000000000007706c
[    5.230051][    T1] x2 : ffff800080b42e88 x1 : 0000000000000001 x0 : 0000000000000001
[    5.230054][    T1] Call trace:
[    5.230055][    T1]  phy_mux_is_enabled+0x7c/0x98 (P)
[    5.230057][    T1]  clk_core_is_enabled+0x44/0x120
[    5.230061][    T1]  clk_disable_unused_subtree+0x88/0x258

🟡 WARNING (medium)

[    5.230100][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98

Context

[    5.230079][    T1]  ret_from_fork+0x10/0x20
[    5.230081][    T1] ---[ end trace 0000000000000000 ]---
[    5.230100][    T1] ------------[ cut here ]------------
[    5.230100][    T1] WARNING: CPU: 0 PID: 1 at drivers/clk/qcom/clk-regmap-phy-mux.c:32 phy_mux_is_enabled+0x7c/0x98
[    5.230103][    T1] Modules linked in:
[    5.230105][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G S      W           6.18.44-g9a727a423861 #1 PREEMPT 
[    5.230107][    T1] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN

🟠 CALL_TRACE (high)

[    5.230136][    T1] Call trace:

Context

[    5.230129][    T1] x8 : ffff800082c3bbe8 x7 : 0000000000000000 x6 : 0000000000000001
[    5.230131][    T1] x5 : ffff800080b41778 x4 : 00000000000a906c x3 : 00000000000a906c
[    5.230134][    T1] x2 : ffff800080b42e88 x1 : 0000000000000001 x0 : 0000000000000001
[    5.230136][    T1] Call trace:
[    5.230137][    T1]  phy_mux_is_enabled+0x7c/0x98 (P)
[    5.230138][    T1]  clk_core_is_enabled+0x44/0x120
[    5.230141][    T1]  clk_disable_unused_subtree+0x88/0x258

🟡 ERROR (medium)

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

Context

[    9.931062][  T188] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    9.962254][  T188] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.969045][  T188] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.977380][  T105] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.987056][  T105] cfg80211: failed to load regulatory.db
[    9.993474][   T12] qcom,apr 3000000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[   10.011502][   T12] qcom,apr 3000000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2

🟡 ERROR (medium)

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

Context

[   10.185212][  T171] Bluetooth: HCI UART protocol QCA registered
[   10.191250][  T175] /soc@0/display-subsystem@ae00000/displayport-controller@af54000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   10.244471][  T111] Bluetooth: hci0: setting up wcn6855
[   10.253221][  T203] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[   10.253221][  T203] :39
[   10.266189][  T203] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[   10.266189][  T203] :43

🟡 ERROR (medium)

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

Context

[   10.244471][  T111] Bluetooth: hci0: setting up wcn6855
[   10.253221][  T203] dummy 1-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[   10.253221][  T203] :39
[   10.266189][  T203] dummy 1-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[   10.266189][  T203] :43
[   10.288844][  T203] msm_dpu ae01000.display-controller: bound af54000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   10.290293][  T188] mhi mhi0: Requested to power ON

🟡 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
[   34.845969][  T360] EXT4-fs (sda2): orphan cleanup on readonly fs
[   34.854781][  T360] EXT4-fs (sda2): mounted filesystem 985e5d67-cfc5-4f20-bc82-74addca41f10 ro with ordered data mode. Quota mode: none.
done.

🟡 ERROR (medium)

[   36.117975][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   35.780601][    T1] Segment Routing with IPv6
[   35.785512][    T1] In-situ OAM (IOAM) with IPv6
[   36.112749][  T125] refgen: disabling
[   36.117975][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.128204][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.138969][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.148305][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium)

[   36.138969][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.112749][  T125] refgen: disabling
[   36.117975][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.128204][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.138969][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.148305][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.156010][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.166903][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium)

[   36.166903][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.138969][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.148305][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.156010][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.166903][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.176369][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.486471][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.496693][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium)

[   36.486471][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   36.156010][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.166903][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.176369][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.486471][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.496693][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.507426][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.516727][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium)

[   36.507426][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.176369][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.486471][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.496693][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.507426][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.516727][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.524522][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.535431][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium)

[   36.535431][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.507426][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.516727][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.524522][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.535431][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.544994][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.553880][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.564083][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium)

[   36.553880][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   36.524522][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.535431][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.544994][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.553880][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.564083][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.574802][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.584107][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium)

[   36.574802][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.544994][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.553880][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.564083][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.574802][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.584107][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.591821][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.602729][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium)

[   36.602729][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.574802][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.584107][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.591821][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.602729][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.612214][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.620121][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0 (no details found
[18t[   36.697604][  T291] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:00:00.0

🟡 ERROR (medium)

[   36.620121][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0 (no details found

Context

[   36.591821][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.602729][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.612214][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.620121][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0 (no details found
[18t[   36.697604][  T291] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:00:00.0
[   36.707003][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.717719][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

🟡 ERROR (medium)

[   36.717719][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.620121][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0 (no details found
[18t[   36.697604][  T291] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:00:00.0
[   36.707003][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.717719][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.727016][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.734706][  T291] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   36.744100][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium)

[   36.754991][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.727016][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.734706][  T291] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[   36.744100][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.754991][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.764462][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.772366][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.782543][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium)

[   36.772366][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   36.744100][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.754991][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.764462][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.772366][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.782543][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.793249][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.802536][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium)

[   36.793249][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.764462][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
[   36.772366][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.782543][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.793249][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.802536][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.915889][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.926136][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

🟡 ERROR (medium)

[   36.915889][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   36.782543][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.793249][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.802536][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.915889][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.926136][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.936894][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.946191][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium)

[   36.936894][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   36.802536][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.915889][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   36.926136][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.936894][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.946191][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.953896][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.964790][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium)

[   36.964790][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   36.936894][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   36.946191][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   36.953896][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   36.964790][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   36.974255][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
7[32766;32766H[6n8[!p]104\[0m[?7h[1G[0J[   37.332424][    T1] systemd[1]: systemd 261.2 running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA +IPE -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +
[   37.365933][    T1] systemd[1]: Detected architecture arm64.

🟡 ERROR (medium)

[   37.381817][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0

Context

[   36.974255][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)
7[32766;32766H[6n8[!p]104\[0m[?7h[1G[0J[   37.332424][    T1] systemd[1]: systemd 261.2 running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA +IPE -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +
[   37.365933][    T1] systemd[1]: Detected architecture arm64.
[   37.381817][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   37.392178][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.402915][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   37.412397][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)

🟡 ERROR (medium)

[   37.402915][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000

Context

[   37.365933][    T1] systemd[1]: Detected architecture arm64.
[   37.381817][  T291] pcieport 0000:00:00.0: AER: Multiple Correctable error message received from 0000:00:00.0
[   37.392178][  T291] pcieport 0000:00:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.402915][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   37.412397][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   37.420102][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.420105][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

🟡 ERROR (medium)

[   37.420105][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000

Context

[   37.402915][  T291] pcieport 0000:00:00.0:   device [17cb:0115] error status/mask=00000001/0000e000
[   37.412397][  T291] pcieport 0000:00:00.0:    [ 0] RxErr                  (First)
[   37.420102][  T291] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   37.420105][  T291] ath11k_pci 0000:01:00.0:   device [17cb:1103] error status/mask=00000001/0000e000
[   37.420107][  T291] ath11k_pci 0000:01:00.0:    [ 0] RxErr                  (First)

[0;1;39mWelcome to [0m[1mQualcomm Linux Reference Distro 2.99+snapshot-d58a9f2dddfdeb4e74ef99929072ff6721590dc9[0m[0;1;39m![0m

Target: `purwa-evk`

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

🟡 WATCHDOG (medium)

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

Context

[    6.299775][    T1] usbcore: registered new interface driver usb-storage
[    6.310955][   T65] Freeing initrd memory: 60796K
[    6.328950][    T1] i2c_dev: i2c /dev entries driver
[    6.347608][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.359161][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.366224][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.371536][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium)

[    6.405220][   T65] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    6.392275][    T1] pstore: Registered efi_pstore as persistent store backend
[    6.399842][   T65] efivars: efivars already registered
[    6.399981][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    6.405220][   T65] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    6.412847][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    6.436815][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    6.445557][    T1] usbcore: registered new interface driver usbhid

🔵 FIRMWARE_FAIL (low)

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

Context

[    9.248873][   T91] arm-scmi arm-scmi.0.auto: Enabling SCMI Quirk [quirk_clock_rates_triplet_out_of_spec]
[    9.330606][  T215] coresight stm0: STM32 initialized
[    9.353079][  T210] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.425361][   T91] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.430655][  T210] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[    9.441138][   T91] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.452669][  T210] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled

🔵 FIRMWARE_FAIL (low)

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

Context

[    9.353079][  T210] ufshcd-qcom 1d84000.ufshc: freq-table-hz property not specified
[    9.425361][   T91] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.430655][  T210] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
[    9.441138][   T91] arm-scmi arm-scmi.0.auto: [Firmware Bug]: Failed to add opps_by_lvl at 3244800 for NCC1 - ret:-16
[    9.452669][  T210] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled
[    9.478859][  T208] mc: Linux media interface: v0.10
[    9.484997][   T91] cpu cpu0: EM: created perf domain

🟡 ERROR (medium)

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

Context

[    9.571067][   T64] scsi 0:0:0:49488: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.587683][  T206] remoteproc remoteproc0: adsp is available
[    9.589089][  T230] 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
[    9.589554][  T239] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[    9.589558][  T239] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[    9.589796][   T64] scsi 0:0:0:49476: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.590712][   T64] scsi 0:0:0:49456: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6

🟡 ERROR (medium)

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

Context

[    9.587683][  T206] remoteproc remoteproc0: adsp is available
[    9.589089][  T230] 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
[    9.589554][  T239] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[    9.589558][  T239] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[    9.589796][   T64] scsi 0:0:0:49476: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.590712][   T64] scsi 0:0:0:49456: Well-known LUN    KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6
[    9.592086][   T64] scsi 0:0:0:0: Direct-Access     KIOXIA   THGJFJT1E45BATPC 0300 PQ: 0 ANSI: 6

🟡 ERROR (medium)

[    9.978298][  T171] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host

Context

[    9.977744][  T311] qcom-pcie 1bf8000.pci: host bridge /soc@0/pci@1bf8000 ranges:
[    9.978236][  T171] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.978238][  T171] phy phy-1bd4000.phy.4: phy poweron failed --> -61
[    9.978298][  T171] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.978829][  T171] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.986046][   T75] qcom-pcie 1c00000.pci: host bridge /soc@0/pci@1c00000 ranges:
[    9.994318][  T311] qcom-pcie 1bf8000.pci:       IO 0x0070200000..0x00702fffff -> 0x0000000000

🟡 ERROR (medium)

[    9.978829][  T171] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61

Context

[    9.978236][  T171] qcom-qmp-pcie-phy 1bd4000.phy: Init sequence not available
[    9.978238][  T171] phy phy-1bd4000.phy.4: phy poweron failed --> -61
[    9.978298][  T171] qcom-pcie 1bd0000.pcie: error -ENODATA: cannot initialize host
[    9.978829][  T171] qcom-pcie 1bd0000.pcie: probe with driver qcom-pcie failed with error -61
[    9.986046][   T75] qcom-pcie 1c00000.pci: host bridge /soc@0/pci@1c00000 ranges:
[    9.994318][  T311] qcom-pcie 1bf8000.pci:       IO 0x0070200000..0x00702fffff -> 0x0000000000
[   10.001156][   T91] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a000000.usb for /pmic-glink/connector@2

🟡 ERROR (medium)

[   10.147265][  T311] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host

Context

[   10.069443][   T91] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier a800000.usb for /pmic-glink/connector@1
[   10.070711][  T311] phy phy-1bfc000.phy.0: phy poweron failed --> -61
[   10.138559][   T64] qcom-pcie 1c08000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[   10.147265][  T311] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host
[   10.151287][   T75] qcom-pcie 1c00000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[   10.238790][  T311] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61
[   10.360851][   T64] qcom-pcie 1c08000.pci: PCIe Gen.3 x2 link up

🟡 ERROR (medium)

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

Context

[   10.138559][   T64] qcom-pcie 1c08000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[   10.147265][  T311] qcom-pcie 1bf8000.pci: error -ENODATA: cannot initialize host
[   10.151287][   T75] qcom-pcie 1c00000.pci: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[   10.238790][  T311] qcom-pcie 1bf8000.pci: probe with driver qcom-pcie failed with error -61
[   10.360851][   T64] qcom-pcie 1c08000.pci: PCIe Gen.3 x2 link up
[   10.367650][   T64] qcom-pcie 1c08000.pci: PCI host bridge to bus 0004:00
[   10.374658][   T64] pci_bus 0004:00: root bus resource [bus 00-ff]

🟡 ERROR (medium)

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

Context

[   11.429500][  T222] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae98000
[   11.434787][  T336] scsi_id (336) used greatest stack depth: 10656 bytes left
[   11.435063][  T311] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   11.439151][  T311] tpm tpm0: A TPM error (256) occurred attempting the self test
[   11.439154][  T311] tpm tpm0: starting up the TPM manually
[   11.445647][  T222] /soc@0/display-subsystem@ae00000/displayport-controller@ae98000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   11.490859][  T222] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae9a000

🟡 ERROR (medium)

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

Context

[   11.533641][  T222] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   11.539331][  T206] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.539610][  T206] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.539761][  T139] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   11.539771][  T139] cfg80211: failed to load regulatory.db
[   11.543891][  T340] qcom,apr 6800000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[   11.552668][  T222] /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.765796][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.737515][  T206] ath12k_wifi7_pci 0004:01:00.0: Wi-Fi 7 Hardware name: wcn7850 hw2.0
[   11.748228][  T210] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 22
[   11.756177][  T206] ath12k_wifi7_pci 0004:01:00.0: MSI vectors: 16
[   11.765796][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.781492][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.793530][  T208] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 3-0008 for /pmic-glink/connector@1
[   11.807836][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.748228][  T210] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 22
[   11.756177][  T206] ath12k_wifi7_pci 0004:01:00.0: MSI vectors: 16
[   11.765796][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.781492][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.793530][  T208] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 3-0008 for /pmic-glink/connector@1
[   11.807836][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.817703][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.765796][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.781492][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.793530][  T208] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 3-0008 for /pmic-glink/connector@1
[   11.807836][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.817703][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.828107][  T206] mhi mhi0: Requested to power ON
[   11.830416][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.781492][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.793530][  T208] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 3-0008 for /pmic-glink/connector@1
[   11.807836][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.817703][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.828107][  T206] mhi mhi0: Requested to power ON
[   11.830416][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.833140][  T206] mhi mhi0: Power on setup success

🟡 ERROR (medium)

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

Context

[   11.807836][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.817703][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.828107][  T206] mhi mhi0: Requested to power ON
[   11.830416][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.833140][  T206] mhi mhi0: Power on setup success
[   11.842957][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.860325][   T75] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   11.828107][  T206] mhi mhi0: Requested to power ON
[   11.830416][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.833140][  T206] mhi mhi0: Power on setup success
[   11.842957][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.860325][   T75] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.870166][   T75] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.881023][   T75] /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.860325][   T75] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.830416][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.833140][  T206] mhi mhi0: Power on setup success
[   11.842957][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.860325][   T75] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.870166][   T75] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.881023][   T75] /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.898765][   T75] /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.870166][   T75] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

Context

[   11.833140][  T206] mhi mhi0: Power on setup success
[   11.842957][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.860325][   T75] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.870166][   T75] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   11.881023][   T75] /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.898765][   T75] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   11.933177][  T118] mhi mhi0: Wait for device to enter SBL or Mission mode

🟡 WARNING (medium)

[   12.089302][   T75] WARNING: CPU: 3 PID: 75 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   11.898765][   T75] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   11.933177][  T118] mhi mhi0: Wait for device to enter SBL or Mission mode
[   12.083819][   T75] ------------[ cut here ]------------
[   12.089302][   T75] WARNING: CPU: 3 PID: 75 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   12.101557][   T75] Modules linked in: panel_edp(+) ath12k_wifi7(+) ath12k mac80211 snd_q6apm(+) libarc4 cfg80211 rfkill rpmsg_ctrl mhi qrtr_smd fastrpc apr phy_nxp_ptn3222 tpm_tis_spi rpmsg_char q
[   12.101839][   T75]  qcom_glink_smem dispcc_x1e80100 phy_qcom_edp phy_qcom_qmp_usb snd_soc_lpass_rx_macro authenc pinctrl_lpass_lpi phy_snps_eusb2 snd_soc_lpass_va_macro snd_soc_lpass_tx_macro snd_
[   12.266712][   T75] CPU: 3 UID: 0 PID: 75 Comm: kworker/u33:2 Not tainted 6.18.44-g9a727a423861 #1 PREEMPT

🟠 CALL_TRACE (high)

[   12.397402][   T75] Call trace:

Context

[   12.373255][   T75] x8 : ffff800082f43468 x7 : 0000000000000000 x6 : 0000000000000001
[   12.381304][   T75] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   12.389353][   T75] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   12.397402][   T75] Call trace:
[   12.400644][   T75]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   12.407543][   T75]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   12.413365][   T75]  panel_edp_dp_aux_ep_probe+0x40/0x60 [panel_edp]

🟡 ERROR (medium)

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

Context

[   12.737258][   T75] hub 2-0:1.0: 2 ports detected
[   12.743524][   T75] hub 3-0:1.0: USB hub found
[   12.748139][   T75] hub 3-0:1.0: 2 ports detected
[   12.759309][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.769463][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.781237][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.791078][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.743524][   T75] hub 3-0:1.0: USB hub found
[   12.748139][   T75] hub 3-0:1.0: 2 ports detected
[   12.759309][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.769463][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.781237][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.791078][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.804099][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.748139][   T75] hub 3-0:1.0: 2 ports detected
[   12.759309][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.769463][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.781237][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.791078][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.804099][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.813961][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.759309][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.769463][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.781237][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.791078][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.804099][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.813961][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.828758][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.769463][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.781237][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.791078][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.804099][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.813961][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.828758][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.838598][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.781237][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.791078][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.804099][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.813961][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.828758][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.838598][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.850804][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.791078][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.804099][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.813961][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.828758][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.838598][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.850804][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.860818][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.804099][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.813961][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.828758][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.838598][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.850804][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.860818][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.873131][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.813961][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.828758][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.838598][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.850804][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.860818][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.873131][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.882956][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.828758][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.838598][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.850804][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.860818][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.873131][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.882956][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.897758][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.838598][   T75] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.850804][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.860818][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.873131][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.882956][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.897758][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.907658][   T31] usb 1-1: new full-speed USB device number 2 using xhci-hcd

🟡 ERROR (medium)

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

Context

[   12.850804][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.860818][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.873131][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.882956][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.897758][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.907658][   T31] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[   12.907776][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.860818][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.873131][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.882956][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.897758][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.907658][   T31] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[   12.907776][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.928839][   T75] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium)

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

Context

[   12.882956][   T75] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.897758][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.907658][   T31] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[   12.907776][   T75] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.928839][   T75] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[   12.942317][  T238] ath12k_wifi7_pci 0004:01:00.0 wlP4p1s0: renamed from wlan0
[   12.942345][   T75] msm_dpu ae01000.display-controller: bound ae98000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 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.108342][  T419] EXT4-fs (sda2): orphan cleanup on readonly fs
[   32.114909][  T419] EXT4-fs (sda2): mounted filesystem 2e16df27-6eab-4d72-84b7-a63f5340d8a3 ro with ordered data mode. Quota mode: none.
done.

Target: `qcs615-ride`

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

🟡 ERROR (medium)

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

Context

[    7.840207][  T154] Bluetooth: SCO socket layer initialized
[    7.848305][  T170] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    7.859629][  T177] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/dsi@ae94000
[    7.867664][   T49] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    7.875457][  T177] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae90000
[    7.886585][   T49] cfg80211: failed to load regulatory.db
[    7.908781][  T177] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae90000

🟡 ERROR (medium)

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

Context

[    8.063362][   T84] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[    8.063455][  T170] ath11k_pci 0000:01:00.0: MSI vectors: 32
[    8.077693][  T170] ath11k_pci 0000:01:00.0: qca6698aq hw2.1
[    8.077995][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    8.093810][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    8.106983][  T105] Bluetooth: hci0: QCA Product ID   :0x00000013
[    8.113551][  T105] Bluetooth: hci0: QCA SOC Version  :0x400c0210

🟡 ERROR (medium)

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

Context

[    8.063455][  T170] ath11k_pci 0000:01:00.0: MSI vectors: 32
[    8.077693][  T170] ath11k_pci 0000:01:00.0: qca6698aq hw2.1
[    8.077995][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    8.093810][   T84] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[    8.106983][  T105] Bluetooth: hci0: QCA Product ID   :0x00000013
[    8.113551][  T105] Bluetooth: hci0: QCA SOC Version  :0x400c0210
[    8.119419][   T84] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops msm_dp_display_comp_ops [msm])

🟡 ERROR (medium)

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

Context

Begin: Running /scripts/local-premount ... done.
[   25.107569][  T310] blkid (310) used greatest stack depth: 8512 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
[   30.256769][  T322] EXT4-fs (sda2): orphan cleanup on readonly fs
[   30.264959][  T322] 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: 10 (0 critical, 0 high, 10 medium, 0 low)

🟡 ERROR (medium)

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

Context

[    8.312599][  T167] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    8.318520][  T124] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    8.362478][  T168] /soc@0/display-subsystem@ae00000/displayport-controller@af54000: Fixed dependency cycle(s) with /soc@0/geniqup@9c0000/i2c@980000/bridge@4f
[    8.369996][  T276] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.371049][  T188] Bluetooth: HCI UART driver ver 2.3
[    8.371071][  T188] Bluetooth: HCI UART protocol H4 registered
[    8.371366][  T188] Bluetooth: HCI UART protocol LL registered

🟡 ERROR (medium)

[    8.406811][  T126] usb usb2-port1: config error

Context

[    8.378897][  T188] Bluetooth: HCI UART protocol QCA registered
[    8.386756][  T168] /soc@0/display-subsystem@ae00000/displayport-controller@af54000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[    8.393998][  T276] cfg80211: failed to load regulatory.db
[    8.406811][  T126] usb usb2-port1: config error
[    8.442838][  T262] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)
[    8.444797][  T173] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 21
[    8.445363][  T175] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)

🟡 ERROR (medium)

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

Context

[    8.475280][  T173] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 22
[    8.479308][  T181] pca953x 3-003d: supply vcc not found, using dummy regulator
[    8.479948][  T181] pca953x 3-003d: using no AI
[    8.523047][  T262] tpm tpm0: A TPM error (256) occurred attempting the self test
[    8.524157][  T173] platform 3000000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 23
[    8.527448][  T181] pca953x 3-003e: supply vcc not found, using dummy regulator
[    8.531210][  T262] tpm tpm0: starting up the TPM manually

🟡 ERROR (medium)

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

Context

[    8.590923][  T109] Bluetooth: hci0: QCA controller version 0x12110201
[    8.592780][  T124] hub 1-1:1.0: 4 ports detected
[    8.598845][  T109] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.599067][  T109] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.602624][  T173] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 24
[    8.616008][  T173] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 25
[    8.620560][  T109] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)

🟡 ERROR (medium)

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

Context

[    8.616008][  T173] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 25
[    8.620560][  T109] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.648711][  T109] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.655537][  T109] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.664781][  T109] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.668892][  T173] platform 26300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 26
[    8.672923][  T109] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)

🟡 ERROR (medium)

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

Context

[    8.977198][  T166] dwc3-qcom a600000.usb: Failed to create device link (0x180) with supplier 2-0047 for /soc@0/usb@a600000/hub@2
[    9.054161][  T167] mhi mhi0: Requested to power ON
[    9.059213][  T167] mhi mhi0: Power on setup success
[    9.059456][  T109] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.074824][  T109] mhi mhi0: Error loading firmware: -2
[    9.076690][  T266] qcom-ethqos 23040000.ethernet: User ID: 0x20, Synopsys ID: 0x52
[    9.082525][  T167] ath11k_pci 0000:01:00.0: failed to power up mhi: -110

🟡 ERROR (medium)

[    9.074824][  T109] mhi mhi0: Error loading firmware: -2

Context

[    9.054161][  T167] mhi mhi0: Requested to power ON
[    9.059213][  T167] mhi mhi0: Power on setup success
[    9.059456][  T109] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/nfa765/amss.bin failed with error -2
[    9.074824][  T109] mhi mhi0: Error loading firmware: -2
[    9.076690][  T266] qcom-ethqos 23040000.ethernet: User ID: 0x20, Synopsys ID: 0x52
[    9.082525][  T167] ath11k_pci 0000:01:00.0: failed to power up mhi: -110
[    9.088417][  T266] qcom-ethqos 23040000.ethernet: 	DWMAC4/5

🟡 ERROR (medium)

[    9.462396][  T167] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110

Context

[    9.409609][  T266] adreno 3d00000.gpu: supply vddcx not found, using dummy regulator
[    9.436818][  T165] hub 1-1:1.0: USB hub found
[    9.442017][  T165] hub 1-1:1.0: 4 ports detected
[    9.462396][  T167] ath11k_pci 0000:01:00.0: probe with driver ath11k_pci failed with error -110
[    9.463994][  T266] msm_dpu ae01000.display-controller: bound 3d00000.gpu (ops a3xx_ops [msm])
[    9.485826][  T266] [drm:dpu_kms_hw_init:1201] dpu hardware revision:0x80040000
[    9.512043][  T266] [drm] Initialized msm 1.13.0 for ae01000.display-controller on minor 0

🟡 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.581165][  T384] EXT4-fs (sda2): orphan cleanup on readonly fs
[   32.589348][  T384] EXT4-fs (sda2): mounted filesystem 513728bc-9c18-4a66-a6fb-01735755aeed 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.350145][  T128] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22

Context

[    7.135457][   T12] qcom-pcie 45e8000.pcie:       IO 0x0060200000..0x00602fffff -> 0x0000000000
[    7.145457][   T12] qcom-pcie 45e8000.pcie:      MEM 0x0060300000..0x0063ffffff -> 0x0060300000
[    7.255637][  T144]  cs_system_cfg: CoreSight Configuration manager initialised
[    7.350145][  T128] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    7.360319][  T140] geni_i2c 4a8c000.i2c: Bus frequency not specified, default to 100kHz.
[    7.381606][  T146] mc: Linux media interface: v0.10
[    7.423206][  T128] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22

🟡 ERROR (medium)

[    7.423206][  T128] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22

Context

[    7.350145][  T128] coresight-etm4x etm0: probe with driver coresight-etm4x failed with error -22
[    7.360319][  T140] geni_i2c 4a8c000.i2c: Bus frequency not specified, default to 100kHz.
[    7.381606][  T146] mc: Linux media interface: v0.10
[    7.423206][  T128] coresight-etm4x etm1: probe with driver coresight-etm4x failed with error -22
[    7.442681][   T48] arm-smmu 59a0000.iommu: probing hardware configuration...
[    7.450396][   T48] arm-smmu 59a0000.iommu: SMMUv2 with:
[    7.459923][   T48] arm-smmu 59a0000.iommu: 	stage 1 translation

🟡 ERROR (medium)

[    7.503484][  T128] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22

Context

[    7.475355][   T48] arm-smmu 59a0000.iommu: 	(IDR0.CTTW overridden by FW configuration)
[    7.485992][   T48] arm-smmu 59a0000.iommu: 	stream matching with 7 register groups
[    7.494341][   T48] arm-smmu 59a0000.iommu: 	5 context banks (0 stage-2 only)
[    7.503484][  T128] coresight-etm4x etm2: probe with driver coresight-etm4x failed with error -22
[    7.503685][   T48] arm-smmu 59a0000.iommu: 	Supported page sizes: 0x61311000
[    7.531597][   T12] qcom-pcie 45e8000.pcie: supply vdda not found, using dummy regulator
[    7.535732][   T48] arm-smmu 59a0000.iommu: 	Stage-1: 48-bit VA -> 36-bit IPA

🟡 ERROR (medium)

[    7.617489][  T128] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22

Context

[    7.574921][   T48] platform 5900000.gpu: Adding to iommu group 12
[    7.583390][   T12] qcom-pcie 45e8000.pcie:       IO 0x0060200000..0x00602fffff -> 0x0000000000
[    7.606962][   T12] qcom-pcie 45e8000.pcie:      MEM 0x0060300000..0x0063ffffff -> 0x0060300000
[    7.617489][  T128] coresight-etm4x etm3: probe with driver coresight-etm4x failed with error -22
[    7.756388][  T140] geni_i2c 4a90000.i2c: Bus frequency not specified, default to 100kHz.
[    7.777692][  T146] videodev: Linux video capture interface: v2.00
[    7.812198][   T48] qcom-pcie 45e8000.pcie: supply vdda not found, using dummy regulator

🟡 ERROR (medium)

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

Context

[    9.940650][  T145] Bluetooth: HCI UART driver ver 2.3
[    9.946617][  T145] Bluetooth: HCI UART protocol H4 registered
[    9.967987][   T46] cpufreq-dt cpufreq-dt: failed register driver: -17
[    9.974984][   T46] cpufreq-dt cpufreq-dt: probe with driver cpufreq-dt failed with error -17
[    9.977829][  T131] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.984746][  T145] Bluetooth: HCI UART protocol LL registered
[    9.992715][   T76] remoteproc remoteproc1: remote processor cdsp is now up

🟡 ERROR (medium)

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

Context

[    9.992715][   T76] remoteproc remoteproc1: remote processor cdsp is now up
[   10.004174][  T131] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.004630][  T145] Bluetooth: HCI UART protocol QCA registered
[   10.018216][   T67] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.028428][   T67] cfg80211: failed to load regulatory.db
[   10.034091][  T136] qcom-ethqos 5d20000.ethernet: IRQ eth_wake_irq not found
[   10.041986][  T136] qcom-ethqos 5d20000.ethernet: IRQ sfty not found

🟡 ERROR (medium)

[   10.448851][   T48] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110

Context

[   10.219169][  T187] Bluetooth: hci0: setting up wcn399x
[   10.328173][   T80] remoteproc remoteproc2: remote processor lpaicp is now up
[   10.329144][   T48] msm_dsi 5e94000.dsi: supply refgen not found, using dummy regulator
[   10.448851][   T48] tpm_tis_spi spi0.0: probe with driver tpm_tis_spi failed with error -110
[   10.501630][  T145] irq: IRQ199: trimming hierarchy from :soc@0:interrupt-controller@f200000-1
[   10.563302][  T130] irq: IRQ200: trimming hierarchy from :soc@0:interrupt-controller@f200000-1
[   10.564414][  T146] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)

🟡 ERROR (medium)

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

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/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.697452][  T213] EXT4-fs (mmcblk0p53): orphan cleanup on readonly fs
[   27.706883][  T213] EXT4-fs (mmcblk0p53): mounted filesystem ba2ea611-e006-4021-a0ac-cfac76ce5228 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: 15 (0 critical, 2 high, 12 medium, 1 low)

🟡 ERROR (medium)

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

Context

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

🟡 WARNING (medium)

[    4.649468][    T1] WARNING: CPU: 7 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.624319][    T1] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 (0,8000003f) counters available
[    4.643985][    T1] ------------[ cut here ]------------
[    4.649446][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.649468][    T1] WARNING: CPU: 7 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.666069][    T1] Modules linked in:
[    4.669929][    T1] CPU: 7 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.44-g9a727a423861 #1 PREEMPT 
[    4.679474][    T1] Hardware name: Qualcomm Technologies, Inc. Lemans Ride Rev3 (DT)

🟠 CALL_TRACE (high)

[    4.791217][    T1] Call trace:

Context

[    4.767098][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002c9
[    4.775134][    T1] x5 : 00000000000002ca x4 : 40000000fffff2c9 x3 : 0000000000000000
[    4.783175][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.791217][    T1] Call trace:
[    4.794450][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.800177][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.805812][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 WARNING (medium)

[    4.903020][    T1] WARNING: CPU: 7 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.890656][    T1] ---[ end trace 0000000000000000 ]---
[    4.897555][    T1] ------------[ cut here ]------------
[    4.903008][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.903020][    T1] WARNING: CPU: 7 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.919622][    T1] Modules linked in:
[    4.923481][    T1] CPU: 7 UID: 0 PID: 1 Comm: swapper/0 Tainted: G        W           6.18.44-g9a727a423861 #1 PREEMPT 
[    4.934633][    T1] Tainted: [W]=WARN

🟠 CALL_TRACE (high)

[    5.050106][    T1] Call trace:

Context

[    5.026006][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002f3
[    5.034041][    T1] x5 : 00000000000002f4 x4 : 40000000fffff2f3 x3 : 0000000000000000
[    5.042074][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    5.050106][    T1] Call trace:
[    5.053339][    T1]  notifier_chain_register+0x64/0x150 (P)
[    5.059065][    T1]  raw_notifier_chain_register+0x1c/0x30
[    5.064696][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 ERROR (medium)

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

Context

[    7.938258][  T210] coresight stm0: STM32 initialized
[    7.938509][   T73] qcom-pcie 1c00000.pcie: host bridge /pcie@1c00000 ranges:
[    7.950871][   T73] qcom-pcie 1c00000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000
[    7.953287][  T198] qcom_eud 88e1000.eud: error -ENODEV: failed to get controller node for path 0
[    7.959944][   T73] qcom-pcie 1c00000.pcie:      MEM 0x0040300000..0x005fffffff -> 0x0040300000
[    7.981191][  T191] pca953x 18-0074: supply vcc not found, using dummy regulator
[    7.989077][  T191] pca953x 18-0074: using no AI

🟡 ERROR (medium)

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

Context

[    9.240697][   T83] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
[    9.244543][   T64] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[    9.249381][   T83] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
[    9.260825][   T64] dummy 19-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.260825][   T64] :39
[    9.264358][  T199] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@2215c000
[    9.264374][  T199] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@22154000

🟡 ERROR (medium)

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

Context

[    9.268645][  T199] /soc@0/display-subsystem@22000000/displayport-controller@22154000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/display-controller@22001000
[    9.270101][  T199] /soc@0/display-subsystem@22000000/display-controller@22001000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/displayport-controller@2215c000
[    9.270282][  T199] /soc@0/display-subsystem@22000000/displayport-controller@2215c000: Fixed dependency cycle(s) with /soc@0/display-subsystem@22000000/display-controller@22001000
[    9.279050][   T64] dummy 19-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.279050][   T64] :43
[    9.295440][   T83] qcom-pcie 1c00000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000
[    9.314463][   T64] msm_dsi ae96000.dsi: supply refgen not found, using dummy regulator

🟡 ERROR (medium)

[    9.343444][   T64] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f

Context

[    9.295440][   T83] qcom-pcie 1c00000.pcie:       IO 0x0040200000..0x00402fffff -> 0x0000000000
[    9.314463][   T64] msm_dsi ae96000.dsi: supply refgen not found, using dummy regulator
[    9.319145][   T83] qcom-pcie 1c00000.pcie:      MEM 0x0040300000..0x005fffffff -> 0x0040300000
[    9.343444][   T64] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.343444][   T64] :39
[    9.372091][  T111] Bluetooth: hci0: QCA Downloading qca/QCA6698/hpnv21.b207
[    9.385045][   T64] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

🟡 ERROR (medium)

[    9.385045][   T64] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f

Context

[    9.343444][   T64] dummy 20-003f: [drm:i2c_access_workaround.isra.0 [anx7625]] *ERROR* fail to access i2c id=3f
[    9.343444][   T64] :39
[    9.372091][  T111] Bluetooth: hci0: QCA Downloading qca/QCA6698/hpnv21.b207
[    9.385045][   T64] dummy 20-003f: [drm:anx7625_i2c_probe [anx7625]] *ERROR* fail to write i2c id=3f
[    9.385045][   T64] :43
[    9.519029][   T83] qcom-pcie 1c00000.pcie: iATU: unroll T, 32 ob, 8 ib, align 4K, limit 1024G
[    9.579405][  T111] Bluetooth: hci0: QCA FW build version: BTFW.HSP.2.1.2-00072-PATCHZ-2

🟡 ERROR (medium)

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

Context

[    9.980405][   T64] msm_dpu ae01000.display-controller: bound af5c000.displayport-controller (ops msm_dp_display_comp_ops [msm])
[    9.986192][  T188] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.997476][   T64] msm_dpu ae01000.display-controller: bound ae94000.dsi (ops dsi_ops [msm])
[   10.005718][   T43] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.014527][   T64] msm_dpu ae01000.display-controller: bound ae96000.dsi (ops dsi_ops [msm])
[   10.023936][   T43] cfg80211: failed to load regulatory.db
[   10.033621][   T64] [drm:dpu_kms_hw_init:1201] dpu hardware revision:0x80040000

🔵 FIRMWARE_FAIL (low)

[   11.062667][  T215] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22

Context

[   10.777075][  T124] msm_dpu 22001000.display-controller: [drm] Cannot find any crtc or sizes
[   11.009525][   T12] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x207 soc_id 0x400c0210
[   11.019382][   T12] 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.062667][  T215] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   11.084781][  T215] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   11.411260][  T186] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[   11.949593][  T215] hwmon hwmon51: temp1_input not attached to any thermal zone

🟡 ERROR (medium)

[   11.084781][  T215] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22

Context

[   11.009525][   T12] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x207 soc_id 0x400c0210
[   11.019382][   T12] 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.062667][  T215] Aquantia AQR115C stmmac-0:08: failed to read firmware-name: -22
[   11.084781][  T215] Aquantia AQR115C stmmac-0:08: probe with driver Aquantia AQR115C failed with error -22
[   11.411260][  T186] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[   11.949593][  T215] hwmon hwmon51: temp1_input not attached to any thermal zone
[   12.018450][  T188] qcom-ethqos 23000000.ethernet end1: renamed from eth0

🟡 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.702629][  T418] EXT4-fs (sda2): orphan cleanup on readonly fs
[   30.709518][  T418] EXT4-fs (sda2): mounted filesystem 57198697-7c20-47a4-944c-71a7b61d6a7e ro with ordered data mode. Quota mode: none.
done.

Target: `qcs6490-rb3gen2`

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

🟡 ERROR (medium)

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

Context

[    9.960137][   T73] arm-smmu 3da0000.iommu: probing hardware configuration...
[    9.967564][  T180] CSCFG registered etm1
[    9.967704][  T184] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    9.968463][   T69] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    9.968510][   T69] cfg80211: failed to load regulatory.db
[    9.974226][   T73] arm-smmu 3da0000.iommu: SMMUv2 with:
[    9.978219][  T180] coresight etm1: CPU1: etm v4.2 initialized

🟡 ERROR (medium)

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

Context

[   12.289391][  T159] EDAC DEVICE0: Giving out device to module qcom_llcc_edac controller llcc: DEV qcom_llcc_edac (INTERRUPT)
[   12.292143][  T105] Bluetooth: hci0: QCA ROM Version  :0x00000101
[   12.293691][   T12] msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
[   12.312805][  T173] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.317718][  T105] Bluetooth: hci0: QCA Patch Version:0x000024c7
[   12.327510][  T105] Bluetooth: hci0: QCA controller version 0x01100101
[   12.327628][  T173] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.312805][  T173] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.317718][  T105] Bluetooth: hci0: QCA Patch Version:0x000024c7
[   12.327510][  T105] Bluetooth: hci0: QCA controller version 0x01100101
[   12.327628][  T173] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.334416][  T105] Bluetooth: hci0: QCA Downloading qca/msbtfw11.mbn
[   12.374432][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.384535][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.327510][  T105] Bluetooth: hci0: QCA controller version 0x01100101
[   12.327628][  T173] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.334416][  T105] Bluetooth: hci0: QCA Downloading qca/msbtfw11.mbn
[   12.374432][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.384535][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.417647][  T160] CAN device driver interface
[   12.420865][   T75] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1

🟡 ERROR (medium)

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

Context

[   12.327628][  T173] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.334416][  T105] Bluetooth: hci0: QCA Downloading qca/msbtfw11.mbn
[   12.374432][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.384535][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.417647][  T160] CAN device driver interface
[   12.420865][   T75] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[   12.430369][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 16

🟡 ERROR (medium)

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

Context

[   12.417647][  T160] CAN device driver interface
[   12.420865][   T75] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[   12.430369][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 16
[   12.447681][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.450192][   T75] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[   12.457594][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.469451][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 17

🟡 ERROR (medium)

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

Context

[   12.430369][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 16
[   12.447681][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.450192][   T75] qcom,apr 3700000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[   12.457594][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.469451][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 17
[   12.469817][  T160] spi_master spi3: will run message pump with realtime priority
[   12.485857][  T154] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 1-001c for /pmic-glink/connector@0

🟡 ERROR (medium)

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

Context

[   12.509150][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 18
[   12.523604][  T160] mcp251xfd spi3.0 can0: MCP2518FD rev0.0 (-RX_INT -PLL -MAB_NO_WARN +CRC_REG +CRC_RX +CRC_TX +ECC -HD o:40.00MHz c:40.00MHz m:10.00MHz rs:10.00MHz es:0.00MHz rf:10.00MHz ef:0.00M
[   12.550694][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 19
[   12.565910][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.567078][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 20
[   12.587273][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.593791][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 21

🟡 ERROR (medium)

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

Context

[   12.550694][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 19
[   12.565910][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.567078][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 20
[   12.587273][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.593791][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 21
[   12.656544][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.666423][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   12.567078][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 20
[   12.587273][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.593791][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 21
[   12.656544][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.666423][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.698130][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 22
[   12.736769][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 23

🟡 ERROR (medium)

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

Context

[   12.587273][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.593791][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 21
[   12.656544][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.666423][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.698130][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 22
[   12.736769][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 23
[   12.753786][  T164] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2

🔵 FIRMWARE_FAIL (low)

[   12.753786][  T164] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2

Context

[   12.666423][   T12] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   12.698130][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 22
[   12.736769][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 23
[   12.753786][  T164] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2
[   12.763113][  T164] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2
[   12.764139][  T157] qcom-edp-phy aec2a00.phy: supply vdda-phy not found, using dummy regulator
[   12.818846][  T157] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator

🟡 ERROR (medium)

[   12.763113][  T164] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2

Context

[   12.698130][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 22
[   12.736769][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 23
[   12.753786][  T164] xhci-pci-renesas 0001:04:00.0: failed to load firmware renesas_usb_fw.mem: -2
[   12.763113][  T164] xhci-pci-renesas 0001:04:00.0: probe with driver xhci-pci-renesas failed with error -2
[   12.764139][  T157] qcom-edp-phy aec2a00.phy: supply vdda-phy not found, using dummy regulator
[   12.818846][  T157] qcom-edp-phy aec2a00.phy: supply vdda-pll not found, using dummy regulator
[   12.833056][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@11: Adding to iommu group 24

🟡 ERROR (medium)

[   12.932192][   T12] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

Context

[   12.856463][  T166] lt9611uxc 0-002b: LT9611 revision: 0x17.04.93
[   12.877579][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@12: Adding to iommu group 25
[   12.910339][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@13: Adding to iommu group 26
[   12.932192][   T12] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   12.940818][  T166] lt9611uxc 0-002b: LT9611 version: 0x50
[   12.941142][   T12] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   12.952050][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@14: Adding to iommu group 27

🟡 ERROR (medium)

[   12.941142][   T12] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)

Context

[   12.910339][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@13: Adding to iommu group 26
[   12.932192][   T12] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   12.940818][  T166] lt9611uxc 0-002b: LT9611 version: 0x50
[   12.941142][   T12] msm-dp-display aea0000.edp: error -EINVAL: invalid resource (null)
[   12.952050][  T170] platform a300000.remoteproc:glink-edge:fastrpc:compute-cb@14: Adding to iommu group 27
[   12.975059][  T170] platform 3700000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 28
[   12.986546][  T170] platform 3700000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 29

🟡 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
[   36.085042][  T330] EXT4-fs (sda2): orphan cleanup on readonly fs
[   36.093344][  T330] EXT4-fs (sda2): mounted filesystem 698d30c1-1e68-4325-852e-0d99efa1467f 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: 24 (0 critical, 1 high, 23 medium, 0 low)

🟡 WATCHDOG (medium)

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

Context

[    6.875655][    T1] usbcore: registered new interface driver uas
[    6.881863][    T1] usbcore: registered new interface driver usb-storage
[    6.906322][    T1] i2c_dev: i2c /dev entries driver
[    6.929339][    T1] sbsa-gwdt 1c840000.watchdog: Initialized with 10s timeout @ 19200000 Hz, action=0.
[    6.941259][    T1] sdhci: Secure Digital Host Controller Interface driver
[    6.948321][    T1] sdhci: Copyright(c) Pierre Ossman
[    6.953646][    T1] Synopsys Designware Multimedia Card Interface Driver

🟡 ERROR (medium)

[    6.987420][   T90] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16

Context

[    6.974411][    T1] pstore: Registered efi_pstore as persistent store backend
[    6.982042][   T90] efivars: efivars already registered
[    6.982084][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    6.987420][   T90] qcom_qseecom_uefisecapp qcom_qseecom.uefisecapp.0: probe with driver qcom_qseecom_uefisecapp failed with error -16
[    6.995021][    T1] clocksource: arch_mmio_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    7.019002][    T1] arch-timer-mmio 17800000.timer: mmio timer running at 19.20MHz (virt)
[    7.027735][    T1] usbcore: registered new interface driver usbhid

🟡 ERROR (medium)

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

Context

[   12.434946][  T209] platform 3d00000.gpu: Adding to iommu group 14
[   12.443199][  T209] platform 3d6a000.gmu: Adding to iommu group 15
[   12.451639][  T285] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: registered as rtc0
[   12.451690][  T287] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: error -EINVAL: invalid "reg" of multi-led
[   12.452451][  T256] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier 2-0008 for /pmic-glink/connector@1
[   12.452592][  T256] /soc@0/phy@fda000: Fixed dependency cycle(s) with /soc@0/geniqup@bc0000/i2c@b9c000/typec-mux@8
[   12.453133][  T256] /soc@0/geniqup@bc0000/i2c@b9c000/typec-mux@8: Fixed dependency cycle(s) with /soc@0/phy@fda000

🟡 ERROR (medium)

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

Context

[   12.453399][  T260] videodev: Linux video capture interface: v2.00
[   12.453649][  T283] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier fd5000.phy for /pmic-glink/connector@0
[   12.459284][  T285] rtc-pm8xxx c42d000.spmi:pmic@0:rtc@6100: setting system clock to 1980-01-06T00:00:25 UTC (315964825)
[   12.468598][  T287] qcom-spmi-lpg c42d000.spmi:pmic@1:pwm: probe with driver qcom-spmi-lpg failed with error -22
[   12.482045][  T262] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with supplier usb-1-ss0-sbu-mux for /pmic-glink/connector@0
[   12.560521][  T246] remoteproc remoteproc0: adsp is available
[   12.570771][  T260] platform iris_non_pixel.0: Adding to iommu group 16

🟡 ERROR (medium)

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

Context

[   12.739007][  T267] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae90000
[   12.745413][  T197] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x3, rev-id 1)
[   12.755287][  T267] /soc@0/display-subsystem@ae00000/displayport-controller@ae90000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000
[   12.766099][  T197] tpm tpm0: A TPM error (256) occurred attempting the self test
[   12.775124][  T323] remoteproc remoteproc1: remote processor cdsp is now up
[   12.779411][  T267] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@ae98000
[   12.785806][  T197] tpm tpm0: starting up the TPM manually

🟡 ERROR (medium)

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

Context

[   13.158253][  T209] hub 1-0:1.0: 2 ports detected
[   13.172965][  T209] hub 2-0:1.0: USB hub found
[   13.177596][  T209] hub 2-0:1.0: 2 ports detected
[   13.190961][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.200875][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.215356][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.225219][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.172965][  T209] hub 2-0:1.0: USB hub found
[   13.177596][  T209] hub 2-0:1.0: 2 ports detected
[   13.190961][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.200875][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.215356][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.225219][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.237467][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.177596][  T209] hub 2-0:1.0: 2 ports detected
[   13.190961][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.200875][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.215356][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.225219][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.237467][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.247347][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.190961][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.200875][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.215356][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.225219][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.237467][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.247347][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.260667][  T209] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.200875][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.215356][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.225219][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.237467][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.247347][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.260667][  T209] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.270674][  T209] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)

🟡 ERROR (medium)

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

Context

[   13.215356][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.225219][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.237467][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.247347][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.260667][  T209] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.270674][  T209] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.281567][  T209] /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)

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

Context

[   13.225219][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.237467][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.247347][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.260667][  T209] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.270674][  T209] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.281567][  T209] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   13.299312][  T209] /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)

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

Context

[   13.237467][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.247347][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.260667][  T209] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.270674][  T209] msm-dp-display aea0000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.281567][  T209] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel
[   13.299312][  T209] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000
[   13.364837][  T358] qcom-pcie 1c08000.pci: PCIe Gen.3 x2 link up

🟡 ERROR (medium)

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

Context

[   13.449627][  T358] pci 0004:00:00.0:   bridge window [io  0x300000-0x300fff]
[   13.456461][  T209] hub 3-0:1.0: 1 port detected
[   13.460996][  T358] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[   13.472505][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.474416][  T358] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   13.479160][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.486892][  T358] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold

🟡 ERROR (medium)

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

Context

[   13.460996][  T358] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[   13.472505][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.474416][  T358] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   13.479160][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.486892][  T358] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold
[   13.499700][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.508225][  T358] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint

🟡 ERROR (medium)

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

Context

[   13.474416][  T358] pci 0004:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[   13.479160][  T209] msm-dp-display ae90000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.486892][  T358] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold
[   13.499700][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.508225][  T358] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint
[   13.515224][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.522331][  T358] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]

🟡 ERROR (medium)

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

Context

[   13.486892][  T358] pci 0004:00:00.0: PME# supported from D0 D3hot D3cold
[   13.499700][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.508225][  T358] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint
[   13.515224][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.522331][  T358] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]
[   13.535603][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.540530][  T358] pci 0004:01:00.0: PME# supported from D0 D3hot D3cold

🟡 ERROR (medium)

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

Context

[   13.508225][  T358] pci 0004:01:00.0: [17cb:1107] type 00 class 0x028000 PCIe Endpoint
[   13.515224][  T209] msm-dp-display ae98000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.522331][  T358] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]
[   13.535603][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.540530][  T358] pci 0004:01:00.0: PME# supported from D0 D3hot D3cold
[   13.549965][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.564614][  T358] pci 0004:01:00.0: ASPM: default states L1

🟡 ERROR (medium)

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

Context

[   13.522331][  T358] pci 0004:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]
[   13.535603][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.540530][  T358] pci 0004:01:00.0: PME# supported from D0 D3hot D3cold
[   13.549965][  T209] msm-dp-display ae9a000.displayport-controller: error -EINVAL: invalid resource (null)
[   13.564614][  T358] pci 0004:01:00.0: ASPM: default states L1
[   13.570950][  T255] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 23
[   13.574196][  T358] pci 0004:00:00.0: bridge window [mem 0x7c400000-0x7c5fffff]: assigned

🟡 ERROR (medium)

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

Context

[   13.808485][  T368] usb 3-1: new full-speed USB device number 2 using xhci-hcd
[   13.822285][  T268] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   13.830380][  T268] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   13.838796][  T336] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   13.848473][  T336] cfg80211: failed to load regulatory.db
[   13.878059][  T268] ath12k_wifi7_pci 0004:01:00.0: BAR 0 [mem 0x7c400000-0x7c5fffff 64bit]: assigned
[   13.887517][  T268] ath12k_wifi7_pci 0004:01:00.0: enabling device (0000 -> 0002)

🟡 WARNING (medium)

[   13.980597][  T253] WARNING: CPU: 1 PID: 253 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]

Context

[   13.970083][  T268] mhi mhi0: Requested to power ON
[   13.972800][  T253] ------------[ cut here ]------------
[   13.975141][  T268] mhi mhi0: Power on setup success
[   13.980597][  T253] WARNING: CPU: 1 PID: 253 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x240/0x278 [panel_edp]
[   13.998050][  T253] Modules linked in: ath12k_wifi7(+) ath12k mac80211 libarc4 snd_q6apm(+) panel_edp(+) cfg80211 rfkill mhi apr rpmsg_ctrl qrtr_smd fastrpc rpmsg_char tpm_tis_spi qcom_pd_mapper ph
[   13.998281][  T253]  videocc_sm8550 camcc_x1e80100 soundwire_qcom snd_soc_lpass_wsa_macro pinctrl_lpass_lpi phy_snps_eusb2 phy_qcom_qmp_usb snd_soc_lpass_macro_common lpasscc_sc8280xp slimbus gpucc
[   14.116615][  T378] mhi mhi0: Wait for device to enter SBL or Mission mode

🟠 CALL_TRACE (high)

[   14.290951][  T253] Call trace:

Context

[   14.266764][  T253] x8 : ffff8000851eb518 x7 : 0000000000000000 x6 : 0000000000000001
[   14.274825][  T253] x5 : ffff80008260b000 x4 : 0000000000000b21 x3 : 0000000000000000
[   14.282887][  T253] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[   14.290951][  T253] Call trace:
[   14.294203][  T253]  generic_edp_panel_probe+0x240/0x278 [panel_edp] (P)
[   14.301106][  T253]  panel_edp_probe+0x2c0/0x380 [panel_edp]
[   14.306948][  T253]  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
[   34.248115][  T479] EXT4-fs (sda2): orphan cleanup on readonly fs
[   34.254852][  T479] EXT4-fs (sda2): mounted filesystem 2afe7eee-2d67-4173-9b85-5b1918477db3 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: 15 (0 critical, 2 high, 12 medium, 1 low)

🔵 FIRMWARE_FAIL (low)

FmpDxe(Qualcomm System Firmware Update Driver): Failed to get the controller state.  Status = Not Found

Context

    ====================================
Selected FW GUID =: 78462415-6133-431C-9FAE-48F2BAFD5C71 
  Platform = 20 
FmpDxe(Qualcomm System Firmware Update Driver): Failed to get the controller state.  Status = Not Found
UsbEnumNewDevRootHub: HIGH on port 0
XHCI: Don't support multi-TT feature for Hub now. (force to disable MTT)
XHCI: Don't support multi-TT feature for Hub now. (force to disable MTT)

🟡 ERROR (medium)

XhcControlTransfer: error - Device Error, transfer - 2

Context

POST Time      [ 2332] OS Loader
UsbEnumNewDevRootHub: SUPER_PLUS on port 1
XhcCheckUrbResult: STALL_ERROR! Completecode = 6
XhcControlTransfer: error - Device Error, transfer - 2
UsbHubInit: failed to read HUB descriptor Device Error
UsbSelectConfig: failed to connect driver Device Error, ignored
Start EBS        [ 2974]

🟡 ERROR (medium)

UsbHubInit: failed to read HUB descriptor Device Error

Context

UsbEnumNewDevRootHub: SUPER_PLUS on port 1
XhcCheckUrbResult: STALL_ERROR! Completecode = 6
XhcControlTransfer: error - Device Error, transfer - 2
UsbHubInit: failed to read HUB descriptor Device Error
UsbSelectConfig: failed to connect driver Device Error, ignored
Start EBS        [ 2974] 
mailbox_uefi_exit: Deinit mutexs success

🟡 ERROR (medium)

UsbSelectConfig: failed to connect driver Device Error, ignored

Context

XhcCheckUrbResult: STALL_ERROR! Completecode = 6
XhcControlTransfer: error - Device Error, transfer - 2
UsbHubInit: failed to read HUB descriptor Device Error
UsbSelectConfig: failed to connect driver Device Error, ignored
Start EBS        [ 2974] 
mailbox_uefi_exit: Deinit mutexs success 
mailbox_uefi_exit: Deinit mutexs success

🟡 ERROR (medium)

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

Context

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

🟡 WARNING (medium)

[    4.275201][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.250524][    T1] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 (0,8000003f) counters available
[    4.269725][    T1] ------------[ cut here ]------------
[    4.275178][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.275201][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.291806][    T1] Modules linked in:
[    4.295670][    T1] CPU: 5 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.44-g9a727a423861 #1 PREEMPT 
[    4.305221][    T1] Hardware name: Qualcomm Technologies, Inc. Lemans EVK (DT)

🟠 CALL_TRACE (high)

[    4.416421][    T1] Call trace:

Context

[    4.392310][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002c1
[    4.400346][    T1] x5 : 00000000000002c2 x4 : 40000000fffff2c1 x3 : 0000000000000000
[    4.408382][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.416421][    T1] Call trace:
[    4.419656][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.425383][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.431018][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 WARNING (medium)

[    4.528063][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150

Context

[    4.515871][    T1] ---[ end trace 0000000000000000 ]---
[    4.522598][    T1] ------------[ cut here ]------------
[    4.528052][    T1] notifier callback aest_cpu_pm_notify already registered
[    4.528063][    T1] WARNING: CPU: 5 PID: 1 at kernel/notifier.c:23 notifier_chain_register+0x64/0x150
[    4.544661][    T1] Modules linked in:
[    4.548519][    T1] CPU: 5 UID: 0 PID: 1 Comm: swapper/0 Tainted: G        W           6.18.44-g9a727a423861 #1 PREEMPT 
[    4.559669][    T1] Tainted: [W]=WARN

🟠 CALL_TRACE (high)

[    4.674625][    T1] Call trace:

Context

[    4.650511][    T1] x8 : 00000000ffffefff x7 : ffff800082692860 x6 : 00000000000002eb
[    4.658551][    T1] x5 : 00000000000002ec x4 : 40000000fffff2eb x3 : 0000000000000000
[    4.666587][    T1] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000080888040
[    4.674625][    T1] Call trace:
[    4.677858][    T1]  notifier_chain_register+0x64/0x150 (P)
[    4.683580][    T1]  raw_notifier_chain_register+0x1c/0x30
[    4.689214][    T1]  cpu_pm_register_notifier+0x44/0x78

🟡 ERROR (medium)

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

Context

[    8.326545][   T64] hub 2-0:1.0: USB hub found
[    8.336177][  T197] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    8.336385][  T197] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    8.336635][  T195] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[    8.336650][  T195] cfg80211: failed to load regulatory.db
[    8.351796][  T199] geni_i2c a90000.i2c: Bus frequency not specified, default to 100kHz.
[    8.354064][  T206] /soc@0/display-subsystem@ae00000/display-controller@ae01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@af54000

🟡 ERROR (medium)

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

Context

[    8.509796][   T63] tpm_tis_spi spi0.0: 2.0 TPM (device-id 0x0, rev-id 78)
[    8.510544][  T136] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    8.512217][  T116] Bluetooth: hci0: QCA Downloading qca/wcnhpbtfw21.tlv
[    8.512466][  T116] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.512481][  T116] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.512484][  T116] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.512682][  T116] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2

🟡 ERROR (medium)

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

Context

[    8.512466][  T116] bluetooth hci0: Direct firmware load for qca/wcnhpbtfw21.tlv failed with error -2
[    8.512481][  T116] Bluetooth: hci0: QCA Failed to request file: qca/wcnhpbtfw21.tlv (-2)
[    8.512484][  T116] Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
[    8.512682][  T116] bluetooth hci0: Direct firmware load for qca/hpbtfw21.tlv failed with error -2
[    8.512692][  T116] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.512698][  T116] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.512701][  T116] Bluetooth: hci0: HFP non-HCI data transport is supported

🟡 ERROR (medium)

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

Context

[    8.512692][  T116] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.512698][  T116] Bluetooth: hci0: QCA Failed to request file: qca/hpbtfw21.tlv (-2)
[    8.512701][  T116] Bluetooth: hci0: HFP non-HCI data transport is supported
[    8.512752][   T63] tpm tpm0: A TPM error (256) occurred attempting the self test
[    8.512758][   T63] tpm tpm0: starting up the TPM manually
[    8.516924][  T199] /soc@0/geniqup@ac0000/i2c@a90000/usb-typec@47: Fixed dependency cycle(s) with /connector-1
[    8.649267][  T179] platform 21c00000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 32

🟡 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.125040][  T354] EXT4-fs (sda2): orphan cleanup on readonly fs
[   30.131943][  T354] EXT4-fs (sda2): mounted filesystem 7f081a84-7045-4209-949a-773694ad02be ro with ordered data mode. Quota mode: none.
done.

QCLINUX: arm64: configs: Enable GPU virtualization

ea0b4ad

Enable DRM VirtIO GPU configs to support GPU virtualization. Signed-off-by: Shivam Rawat <shivrawa@qti.qualcomm.com>

Shivam Rawat (shivrawa) requested review from a team, Nicolas Dechesne (ndechesne), Shivendra Pratap (quicAspratap) and Trilok Soni (trsoni) September 15, 2026 06:59

Komal Bajaj (Komal-Bajaj) approved these changes Sep 15, 2026

View reviewed changes

Shiraz Hashim (shashim-quic) approved these changes Sep 16, 2026

View reviewed changes

Shiraz Hashim (shashim-quic) added this to the qli-2.1 pull-request freeze milestone Sep 16, 2026

Salendarsingh Gaud (sgaud-quic) merged commit 99a9a69 into qualcomm-linux:qcom-6.18.y Sep 19, 2026
6 of 8 checks passed

Conversation

Shivam Rawat (shivrawa) commented Sep 15, 2026 • edited by sgaud-quic Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qswat-orbit-external Bot commented Sep 15, 2026

Uh oh!

qswat-orbit-external Bot commented Sep 15, 2026

Uh oh!

qswat-orbit-external Bot commented Sep 15, 2026

Uh oh!

Shivam Rawat (shivrawa) commented Sep 15, 2026

Uh oh!

qcomlnxci commented Sep 15, 2026

Test jobs on ea0b4ad

Uh oh!

qcomlnxci commented Sep 15, 2026

Test Matrix

Uh oh!

Shivam Rawat (shivrawa) commented Sep 15, 2026

Uh oh!

qlijarvis commented Sep 16, 2026

LAVA Failed Case Triage Summary

Uh oh!

qcomlnxci commented Sep 18, 2026

Test jobs on ea0b4ad

Uh oh!

qcomlnxci commented Sep 18, 2026

Test Matrix

Uh oh!

qlijarvis commented Sep 18, 2026

LAVA Failed Case Triage Summary

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

Target: lemans-evk

Target: qcs615-ride

Target: hamoa-evk

Target: purwa-evk

Target: qcs6490-rb3gen2

Target: qcs8300-ride

Target: shikra-iqs-evk

Target: qcs9100-ride

Target: monaco-evk

Uh oh!

qcomlnxci commented Sep 18, 2026

Test jobs on ea0b4ad

Uh oh!

qcomlnxci commented Sep 18, 2026

Test Matrix

Uh oh!

qcomlnxci commented Sep 18, 2026

Test jobs on ea0b4ad

Uh oh!

qcomlnxci commented Sep 18, 2026

Test Matrix

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented Sep 19, 2026

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented Sep 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Shivam Rawat (shivrawa) commented Sep 19, 2026

Uh oh!

Shivam Rawat (shivrawa) commented Sep 19, 2026

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented Sep 19, 2026

Uh oh!

Uh oh!

qcomlnxci commented Sep 19, 2026

Test Matrix

Uh oh!

qcomlnxci commented Sep 19, 2026

Test jobs on ea0b4ad

Uh oh!

qlijarvis commented Sep 19, 2026

LAVA Failed Case Triage Summary

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

Target: hamoa-evk

Target: qcs8300-ride

Target: qcs9100-ride

Target: shikra-iqs-evk

Target: qcs6490-rb3gen2

Shivam Rawat (shivrawa) commented Sep 15, 2026 •

edited by sgaud-quic

Loading

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

Target: `lemans-evk`

Target: `qcs615-ride`

Target: `hamoa-evk`

Target: `purwa-evk`

Target: `qcs6490-rb3gen2`

Target: `qcs8300-ride`

Target: `shikra-iqs-evk`

Target: `qcs9100-ride`

Target: `monaco-evk`

Salendarsingh Gaud (sgaud-quic) commented Sep 19, 2026 •

edited

Loading

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

Target: `hamoa-evk`

Target: `qcs8300-ride`

Target: `qcs9100-ride`

Target: `shikra-iqs-evk`

Target: `qcs6490-rb3gen2`

Target: `qcs615-ride`

Target: `purwa-evk`

Target: `monaco-evk`

Target: `lemans-evk`

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

Target: `qcs8300-ride`

Target: `purwa-evk`

Target: `qcs615-ride`

Target: `monaco-evk`

Target: `shikra-iqs-evk`

Target: `qcs9100-ride`

Target: `qcs6490-rb3gen2`

Target: `hamoa-evk`

Target: `lemans-evk`