qlijarvis / pr_only_checker_log_detailed.md

Created November 6, 2026 07:25

PR #2176 checker-log-analyzer detailed analysis

PR #2176 — checker-log-analyzer Detailed Analysis

PR: qualcomm-linux/kernel-topics#2176 Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175823636

Report

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #2176 - QCLINUX: arm64: dts: qcom: add Nord CAMX EL2 overlay

qlijarvis / pr_only_validate_patch_detailed.md

Created November 6, 2026 07:25

PR #2176 validate-patch detailed analysis

PR #2176 — validate-patch Detailed Analysis

PR: qualcomm-linux/kernel-topics#2176

Report

🔍 Patch Validation

PR: #2176 - QCLINUX: arm64: dts: qcom: add Nord CAMX EL2 overlay
Upstream commit: N/A (vendor-only QCLINUX: commit)

qlijarvis / build_job_detailed.md

Created November 6, 2026 07:19

PR #2176 build failure detailed analysis

PR #2176 — Build Failure Detailed Analysis

PR: qualcomm-linux/kernel-topics#2176 Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175817102

Summary

🔨 Build Failure Analysis — PR #2176

PR: qualcomm-linux/kernel-topics#2176

qlijarvis / build_job_detailed.md

Created November 6, 2026 07:14

PR #2176 build failure detailed analysis

PR #2176 — Build Failure Detailed Analysis

PR: qualcomm-linux/kernel-topics#2176 Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175817102

Summary

🔨 Build Failure Analysis — PR #2176

PR: qualcomm-linux/kernel-topics#2176

qlijarvis / pr_only_checker_log_detailed.md

Created November 6, 2026 07:10

PR #2203 checker-log-analyzer detailed analysis

PR #2203 — checker-log-analyzer Detailed Analysis

PR: qualcomm-linux/kernel-topics#2203 Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42171485805

Report

🤖 CI Checker Analysis (checker-log-analyzer)

qlijarvis / pr_only_validate_patch_detailed.md

Created November 6, 2026 07:10

PR #2203 validate-patch detailed analysis

PR #2203 — validate-patch Detailed Analysis

PR: qualcomm-linux/kernel-topics#2203

Report

🔍 Patch Validation

PR: #2203 - PENDING: arm64: dts: qcom: purwa-evk: add QPS615 m.2 ethernet staging overlay
Upstream commit: N/A (PENDING: prefix — work-in-progress, not posted upstream)

qlijarvis / failed_case_job269736_1_detailed.md

Created November 6, 2026 07:06

PR #1208 LAVA job 269736 case 1 detailed analysis

PR 1208 | Job 269736 | SoC lemans-evk | Case 1

Failed case: Probe_Failure_Check
LAVA job: https://lava-oss.qualcomm.com/scheduler/job/269736
Skill hint: qlijarvis-triage

Detailed analysis

Summary: The Probe_Failure_Check test failed on lemans-evk because it detected a deferred probe for the nvmem-reboot-mode driver, which cannot find its required NVMEM cell named "reboot-mode" in the device tree. This is a pre-existing platform configuration gap unrelated to PR #1208, which only adds the PSCRR framework with a separate "reboot-reason-persist" cell. The system boots successfully and all functional tests pass, indicating this is a non-critical configuration issue rather than a kernel regression.

qlijarvis / failed_case_job269735_8_detailed.md

Created November 6, 2026 07:06

PR #1208 LAVA job 269735 case 8 detailed analysis

PR 1208 | Job 269735 | SoC shikra-iqs-evk | Case 8

Failed case: KVM_Infra
LAVA job: https://lava-oss.qualcomm.com/scheduler/job/269735
Skill hint: qlijarvis-triage

Detailed analysis

Summary: The KVM_Infra test failure on Shikra IQS EVK is not a kernel regression or bug introduced by PR #1208 (which only modifies power management headers and reboot reason handling). The failure occurs because the platform is configured to boot under the Gunyah hypervisor, which occupies EL2 (hypervisor privilege level). KVM requires direct EL2 access to create virtual machines, but when Linux runs as a guest under Gunyah, EL2 is unavailable. The kernel correctly detects this and disables KVM initialization, resulting in /dev/kvm not being created. This is expected architectural behavior on hypervisor-based platforms.

qlijarvis / failed_case_job269737_2_detailed.md

Created November 6, 2026 07:06

PR #1208 LAVA job 269737 case 2 detailed analysis

PR 1208 | Job 269737 | SoC qcs6490-rb3gen2 | Case 2

Failed case: 0_qcom-next-ci-premerge-tests
LAVA job: https://lava-oss.qualcomm.com/scheduler/job/269737
Skill hint: lava-issues

Detailed analysis

Summary: The LAVA job failed because the Probe_Failure_Check test detected a firmware load error for regulatory.db (wireless regulatory database) in the kernel dmesg log. This error is a pre-existing test environment issue unrelated to the PR changes, which introduce the PSCRR (Power State Change Reason Recorder) framework for tracking shutdown/reboot reasons. The kernel booted successfully, all functional tests passed, and the regulatory.db error does not indicate a regression introduced by this PR.

qlijarvis / failed_case_job269735_7_detailed.md

Created November 6, 2026 07:06

PR #1208 LAVA job 269735 case 7 detailed analysis

PR 1208 | Job 269735 | SoC shikra-iqs-evk | Case 7

Failed case: KVM_EL2_DTB
LAVA job: https://lava-oss.qualcomm.com/scheduler/job/269735
Skill hint: qlijarvis-triage

Detailed analysis

Summary: The KVM_EL2_DTB test failed because the /dev/kvm device node does not exist. This occurs because KVM initialization fails at boot when it detects that EL2 (hypervisor mode) is already occupied by the Gunyah hypervisor. The test correctly identifies that CONFIG_KVM is enabled but cannot proceed because the KVM subsystem failed to initialize. This is a platform configuration issue specific to the Shikra IQS EVK running Gunyah, not a kernel regression introduced by the PR.