drm/msm/dp: fix NULL pointer deref in msm_dp_snapshot() for unmapped MST streams - #1050

Open

YongxingMou wants to merge 4 commits into

qualcomm-linux:qcom-6.18.yfrom

YongxingMou:for-dp-snap-fix

YongxingMou commented Sep 7, 2026 •

edited

Loading

msm_dp_snapshot() unconditionally dumped pixel_base[0..3]/mst2link_base/
mst3link_base. On single-stream platforms, or when DT doesn't declare
the optional p1/p2/p3 pixel or mst2link/mst3link regions, these stay
NULL, so triggering a snapshot (e.g. DP hang/devcoredump) caused a NULL
pointer dereference.

Fix by explicitly setting pixel_base[i]/mst2link_base/mst3link_base to
NULL when the DT resource is legitimately absent (-EINVAL), and skip
dumping a block in msm_dp_snapshot() when its base is NULL or the
stream's pixel clock isn't enabled (via new msm_dp_ctrl_stream_clks_on()).

CRs-Fixed: 4589764

YongxingMou requested review from a team, jingyiwang42, Nicolas Dechesne (ndechesne) and Trilok Soni (trsoni)

September 7, 2026 10:43

qswat-orbit-external Bot commented Sep 7, 2026

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.

YongxingMou force-pushed the for-dp-snap-fix branch from 49ba46f to da47e70 Compare

September 7, 2026 10:52

qswat-orbit-external Bot commented Sep 7, 2026

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 Bot commented Sep 8, 2026

Merge Check Failed: CR Not Eligible for Merge

CR 4589764 is not eligible for merge.

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

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

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

YongxingMou force-pushed the for-dp-snap-fix branch from da47e70 to b9707e8 Compare

September 8, 2026 08:59

qswat-orbit-external Bot commented Sep 8, 2026

Merge Check Failed: CR Not Eligible for Merge

CR 4589764 is not eligible for merge.

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

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

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

qswat-orbit-external Bot commented Sep 8, 2026

Merge Check Failed: CR Not Eligible for Merge

CR 4670463 is not eligible for merge.

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

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

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

YongxingMou force-pushed the for-dp-snap-fix branch from b9707e8 to 5ebdf2b Compare

September 8, 2026 09:58

qswat-orbit-external Bot commented Sep 8, 2026

Merge Check Failed: CR Not Eligible for Merge

CR 4670463 is not eligible for merge.

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

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

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

YongxingMou force-pushed the for-dp-snap-fix branch from 5ebdf2b to 5ac8bcf Compare

September 8, 2026 09:59

qswat-orbit-external Bot commented Sep 8, 2026

Merge Check Failed: CR Not Eligible for Merge

CR 4670463 is not eligible for merge.

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

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

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

YongxingMou force-pushed the for-dp-snap-fix branch from 5ac8bcf to 60e276b Compare

September 8, 2026 10:01

qswat-orbit-external Bot commented Sep 8, 2026

Merge Check Failed: CR Not Eligible for Merge

CR 4670463 is not eligible for merge.

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

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

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

YongxingMou force-pushed the for-dp-snap-fix branch from 60e276b to 2cf09ad Compare

September 8, 2026 10:01

qswat-orbit-external Bot commented Sep 8, 2026

Merge Check Failed: CR Not Eligible for Merge

CR 4670463 is not eligible for merge.

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

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

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

Shiraz Hashim (shashim-quic) approved these changes

View reviewed changes

qcomlnxci commented Sep 8, 2026

Test jobs on 2cf09ad

qcomlnxci commented Sep 8, 2026

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	✅ Pass
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
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	❌ Fail	❌ 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	✅ Pass
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	❌ Fail	❌ Fail	❌ Fail	❌ 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

Salendarsingh Gaud (sgaud-quic) commented Sep 8, 2026

Contributor

Sign-off missing for reverted changes :

Summary
Commit sha: [a67ecae](https://github.com/qualcomm-linux/kernel/pull/1050/commits/a67ecaef79ee22b3ab70c5f130eb0d4a39f2dc0f), Author: Yongxing Mou, Committer: Yongxing Mou; The sign-off is missing.
Commit sha: [1d881cc](https://github.com/qualcomm-linux/kernel/pull/1050/commits/1d881cc0889847da74235c40d58f3b4f56b5ad80), Author: Yongxing Mou, Committer: Yongxing Mou; The sign-off is missing.

Yongxing Mou added 4 commits

September 9, 2026 11:14


          Revert "FROMLIST: drm/msm/dp: Add catalog support for 3rd/4th stream …

65443eb

…MST"

This reverts commit cd58926.

This is reverted because a newer version of this patch is being introduced.

Signed-off-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>


          Revert "FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 re…

a601e2c

…gister blocks"

This reverts commit c8a9835.

This is reverted because a newer version of this patch is being introduced.

Signed-off-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>


          FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 register b…

1147ec0

…locks

Add support for additional pixel register blocks (p1, p2, p3) to enable
4-stream MST pixel clocks. Introduce the helper functions msm_dp_read_pn
and msm_dp_write_pn for pixel register programming. All pixel clocks
share the same register layout but use different base addresses.

Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
Signed-off-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20260831-msm-dp-mst-v6-5-c91d35d6fb9e@oss.qualcomm.com/


          FROMLIST: drm/msm/dp: Add stream-aware link register accessors

9d49f1b

DisplayPort MST uses multiple stream-specific register spaces. Streams
0 and 1 share the primary link register block with different register
offsets, while streams 2 and 3 use dedicated MST link register blocks.

Add stream-aware register access helpers that translate stream-specific
register offsets and route accesses to the appropriate register space
based on the stream id.

Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
Signed-off-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>
Link: https://lore.kernel.org/all/20260831-msm-dp-mst-v6-7-c91d35d6fb9e@oss.qualcomm.com/

YongxingMou force-pushed the for-dp-snap-fix branch from 2cf09ad to 9d49f1b Compare

September 9, 2026 03:14

YongxingMou commented Sep 9, 2026

Author

Sign-off missing for reverted changes :

Summary
Commit sha: [a67ecae](https://github.com/qualcomm-linux/kernel/pull/1050/commits/a67ecaef79ee22b3ab70c5f130eb0d4a39f2dc0f), Author: Yongxing Mou, Committer: Yongxing Mou; The sign-off is missing.
Commit sha: [1d881cc](https://github.com/qualcomm-linux/kernel/pull/1050/commits/1d881cc0889847da74235c40d58f3b4f56b5ad80), Author: Yongxing Mou, Committer: Yongxing Mou; The sign-off is missing.

Done

qcomlnxci requested a review from a team

September 9, 2026 03:19

qlijarvis commented Sep 9, 2026

PR #1050 — validate-patch

PR: #1050

Verdict	Issues	Detailed Report
❌	3	Full report

Final Summary

Lore link present:
- Commits 1/4, 2/4: ❌ No — revert commits lack lore links for original patches
- Commits 3/4, 4/4: ✅ Yes — valid lore links provided
Lore link matches PR commits:
- Commits 1/4, 2/4: N/A — no lore links to compare
- Commits 3/4, 4/4: ⚠️ Partial — core functionality matches but subject capitalization differs, baseline context differs due to reverts
Upstream patch status:
- Commits 1/4, 2/4: N/A — revert commits
- Commits 3/4, 4/4: ⏳ Decision Pending — v6 series posted August 31, 2026, under active review, not yet merged to mainline
PR present in qcom-next/topics: Partial - 4/4 commit(s) only have partial integration evidence
- ⚠️ Partial — 4/4 commits show partial integration evidence per integration_presence_report.md; full changes not verified in qcom-next or topics branches

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1050 - drm/msm/dp: MST v6 patch series update
Verdict: ❌ FAIL

Summary

This PR contains 4 commits:

Commit 1/4: Revert of FROMLIST patch (cd58926) - no lore link

Commit 2/4: Revert of FROMLIST patch (c8a9835) - no lore link

Commit 3/4: FROMLIST patch with lore link to v6 05/29

Commit 4/4: FROMLIST patch with lore link to v6 07/29

Commit 1/4: Revert "FROMLIST: drm/msm/dp: Add catalog support for 3rd/4th stream MST"

Upstream: N/A (revert commit)
Verdict: ❌ FAIL

Commit Message

Check Status Note

Subject matches upstream N/A Revert commit

Body preserves rationale ⚠️ Minimal rationale: "newer version of this patch is being introduced"

Fixes tag present/correct N/A Not applicable for revert

Authorship preserved ✅ Yongxing Mou as submitter

Backport note N/A Not applicable

Issues

Missing lore link for reverted commit: The commit being reverted (cd58926) should have had a lore link in its original commit message. Without it, we cannot verify what upstream patch is being reverted.

Insufficient revert rationale: The commit message states "a newer version of this patch is being introduced" but doesn't explain why the revert is necessary or what changed between versions.

Revert prefix missing: Subject should be Revert "FROMLIST: ..." which it is, but the original FROMLIST commit should have included the lore link that's now lost.

Commit 2/4: Revert "FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 register blocks"

Upstream: N/A (revert commit)
Verdict: ❌ FAIL

Commit Message

Check Status Note

Subject matches upstream N/A Revert commit

Body preserves rationale ⚠️ Minimal rationale: "newer version of this patch is being introduced"

Fixes tag present/correct N/A Not applicable for revert

Authorship preserved ✅ Yongxing Mou as submitter

Backport note N/A Not applicable

Issues

Missing lore link for reverted commit: The commit being reverted (c8a9835) should have had a lore link. Cannot verify the upstream source.

Insufficient revert rationale: Same issue as commit 1/4 - doesn't explain what necessitated the revert.

Commit 3/4: FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 register blocks

Upstream: https://lore.kernel.org/all/20260831-msm-dp-mst-v6-5-c91d35d6fb9e@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note

Subject matches upstream ⚠️ PR: "Add support for programming p1/p2/p3 register blocks"
Lore: "add support for programming p1/p2/p3 register blocks" (capitalization differs)

Body preserves rationale ✅ Key rationale preserved

Fixes tag present/correct N/A No Fixes tag in upstream

Authorship preserved ⚠️ FROMLIST authorship issue (see below)

Backport note N/A Not a backport

Authorship Analysis (FROMLIST-specific)

Lore patch author: Abhinav Kumar quic_abhinavk@quicinc.com
PR commit author: Yongxing Mou yongxing.mou@oss.qualcomm.com

Signed-off-by chain in PR:
Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
Signed-off-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>
Status: ✅ CORRECT - For FROMLIST commits, the submitter (Yongxing Mou) is legitimately in the From: field, and the original lore author (Abhinav Kumar) is correctly preserved in the Signed-off-by: chain. This follows the FROMLIST authorship convention.

Diff Comparison

Comparing PR commit 3/4 against lore patch v6 05/29:

File Status Notes

drivers/gpu/drm/msm/dp/dp_ctrl.c ⚠️ Function signature differs

drivers/gpu/drm/msm/dp/dp_ctrl.h ✅ Matches

drivers/gpu/drm/msm/dp/dp_display.c ⚠️ Context differences

drivers/gpu/drm/msm/dp/dp_panel.c ⚠️ Context differences

drivers/gpu/drm/msm/dp/dp_panel.h ✅ Matches

Key differences identified:

dp_ctrl.c line count: PR shows +10 lines, lore shows similar additions for msm_dp_ctrl_stream_clks_on() function

dp_display.c context: PR applies to different baseline (after revert) vs lore v6 which applies to v6-04/29 state

Function placement: The msm_dp_ctrl_stream_clks_on() function appears at different line numbers due to baseline differences

Assessment: The diff content appears functionally equivalent to the lore patch, but applies to a different baseline (post-revert state). This is expected given commits 1-2 reverted previous versions.

Upstream Patch Status

Community verdict: ⏳ Decision Pending

Evidence from lore thread analysis:

Posted: August 31, 2026 as part of v6 29-patch series

Maintainer feedback: Thread shows review activity (Re: [PATCH v6 05/29] visible in mbox at line 8934)

Merge status: Not found in torvalds/linux mainline (cannot verify without network access, but no merge confirmation in thread)

Series status: This is v6 of the series, indicating active iteration and review

Recommendation: Patch is under active review upstream. FROMLIST prefix is appropriate.

Commit 4/4: FROMLIST: drm/msm/dp: Add stream-aware link register accessors

Upstream: https://lore.kernel.org/all/20260831-msm-dp-mst-v6-7-c91d35d6fb9e@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note

Subject matches upstream ⚠️ PR: "Add stream-aware link register accessors"
Lore: "add stream-aware link register accessors" (capitalization differs)

Body preserves rationale ✅ Key rationale preserved

Fixes tag present/correct N/A No Fixes tag in upstream

Authorship preserved ⚠️ FROMLIST authorship issue (see below)

Backport note N/A Not a backport

Authorship Analysis (FROMLIST-specific)

Lore patch author: Abhinav Kumar quic_abhinavk@quicinc.com
PR commit author: Yongxing Mou yongxing.mou@oss.qualcomm.com

Signed-off-by chain in PR:
Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
Signed-off-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>
Status: ✅ CORRECT - Same as commit 3/4, follows FROMLIST authorship convention correctly.

Diff Comparison

Comparing PR commit 4/4 against lore patch v6 07/29:

File Status Notes

drivers/gpu/drm/msm/dp/dp_ctrl.c ⚠️ Large refactor, context-dependent

drivers/gpu/drm/msm/dp/dp_ctrl.h ✅ Matches

drivers/gpu/drm/msm/dp/dp_display.c ⚠️ Context differences

drivers/gpu/drm/msm/dp/dp_panel.c ⚠️ Context differences

drivers/gpu/drm/msm/dp/dp_panel.h ✅ Matches

drivers/gpu/drm/msm/dp/dp_reg.h ⚠️ Context differences

Key differences identified:

Function naming: Lore uses msm_dp_read_stream_link() while PR uses msm_dp_read_link() with stream_id parameter

Line counts: PR shows +242/-132 for dp_ctrl.c, lore shows different counts due to baseline

Context: PR applies after commits 1-3, lore applies after v6-06/29

Assessment: The core logic (stream-aware register accessors with switch statements for stream 0/1/2/3) appears present in both, but function naming and structure may differ due to baseline differences.

Upstream Patch Status

Community verdict: ⏳ Decision Pending

Evidence from lore thread analysis:

Posted: August 31, 2026 as part of v6 29-patch series (patch 07/29)

Series status: v6 iteration indicates active development

Merge status: Not found in mainline (based on integration report showing "partial" evidence)

Recommendation: Patch is under active review upstream. FROMLIST prefix is appropriate.

Integration Presence Check

From integration_presence_report.md:

Commit qcom-next topics Final Status

1/4 (Revert) partial partial partial

2/4 (Revert) partial partial partial

3/4 (FROMLIST) partial partial partial

4/4 (FROMLIST) partial partial partial

Overall: PARTIAL - 4/4 commits show only partial integration evidence

Analysis: All commits show "partial" status, meaning subject or partial tree evidence was found but full changes were not verified. This is concerning because:

The revert commits (1/4, 2/4) should cleanly remove previous commits if those commits exist

The FROMLIST commits (3/4, 4/4) should not yet be in qcom-next if they're still under upstream review

Critical Issues Found

❌ Revert commits lack lore links: Commits 1/4 and 2/4 revert previous FROMLIST commits, but those original commits apparently lacked lore links. This breaks traceability.

❌ Insufficient revert rationale: Both revert commits provide minimal explanation ("newer version being introduced") without detailing what changed or why the revert is necessary.

⚠️ Subject capitalization inconsistency: PR commits use title case ("Add support...") while lore uses sentence case ("add support..."). While minor, this creates unnecessary diff noise.

⚠️ Baseline confusion: The PR applies patches 3/4 and 4/4 after reverting 1/4 and 2/4, but it's unclear if the net result matches the lore v6 series state or introduces additional changes.

⚠️ Integration presence unclear: All commits show "partial" integration status, which doesn't clearly indicate whether these changes are already present, partially present, or missing from qcom-next/topics.

❌ Patch ordering concern: The PR reverts patches then re-applies similar functionality. This suggests the original commits (cd58926, c8a9835) were from an older lore version (v5 or earlier?), but without lore links on those commits, we cannot verify.

Recommendation

DO NOT MERGE without addressing the following:

Add lore links to commit messages for reverted commits: Update the revert commit messages to include the lore links for the original patches being reverted (cd58926 and c8a9835). If those commits never had lore links, add them retroactively in the revert message.

Enhance revert rationale: Explain specifically what changed between the old version (being reverted) and the new version (v6 05/29 and 07/29). For example:

"This reverts commit cd58926 which was based on v5 of the upstream series. The v6 series refactored the register accessor naming and added additional stream validation."

Fix subject capitalization: Match the upstream lore subject line capitalization exactly:

Change "Add support for programming" → "add support for programming"

Change "Add stream-aware link register" → "add stream-aware link register"

Verify net diff: Confirm that after applying all 4 commits, the net result matches the lore v6 series state for patches 05/29 and 07/29. If there are intentional deviations, document them.

Clarify integration status: Investigate why all commits show "partial" integration evidence. Are these commits already partially present in qcom-next? If so, this PR may create conflicts or duplicates.

Final Summary

Lore link present:

Commits 1/4, 2/4: ❌ No — revert commits lack lore links for original patches

Commits 3/4, 4/4: ✅ Yes — valid lore links provided

Lore link matches PR commits:

Commits 1/4, 2/4: N/A — no lore links to compare

Commits 3/4, 4/4: ⚠️ Partial — core functionality matches but subject capitalization differs, baseline context differs due to reverts

Upstream patch status:

Commits 1/4, 2/4: N/A — revert commits

Commits 3/4, 4/4: ⏳ Decision Pending — v6 series posted August 31, 2026, under active review, not yet merged to mainline

PR present in qcom-next/topics:

⚠️ Partial — 4/4 commits show partial integration evidence per integration_presence_report.md; full changes not verified in qcom-next or topics branches

Deterministic Integration Presence

Integration Presence Report

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

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

Commit Subject qcom-next topics Final

1/4 [PATCH 1/4] Revert "FROMLIST: drm/msm/dp: Add catalog support for partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

2/4 [PATCH 2/4] Revert "FROMLIST: drm/msm/dp: Add support for programming partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

3/4 [PATCH 3/4] FROMLIST: drm/msm/dp: Add support for programming partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

4/4 [PATCH 4/4] FROMLIST: drm/msm/dp: Add stream-aware link register partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

Final Status

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

qlijarvis commented Sep 9, 2026

PR #1050 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	2 commits with style issues (alignment checks)
dt-binding-check	⏭️	No DT binding changes
dtb-check	⏭️	No DTS changes
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	4 issues: 2 missing prefix, 2 content mismatch, 1 author mismatch
tag-check	❌	2 commits missing required prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1050 - drm/msm/dp: MST stream register accessor updates
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/34306644298
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ❌ 2 commits with style issues (alignment checks)

dt-binding-check ⏭️ No DT binding changes

dtb-check ⏭️ No DTS changes

sparse-check ✅ Passed

check-uapi-headers ✅ Passed

check-patch-compliance ❌ 4 issues: 2 missing prefix, 2 content mismatch, 1 author mismatch

tag-check ❌ 2 commits missing required prefix

❌ checkpatch

Root cause: Two revert commits contain alignment style issues inherited from the original code being reverted.

Failure details:

Commit 1: 65443ebd3b64 - Revert "FROMLIST: drm/msm/dp: Add catalog support for 3rd/4th stream MST"
total: 0 errors, 0 warnings, 17 checks, 922 lines checked
17 CHECK warnings (alignment issues in reverted code)

Commit 2: a601e2cdea53 - Revert "FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 register blocks"
CHECK: Alignment should match open parenthesis
#141: FILE: drivers/gpu/drm/msm/dp/dp_panel.c:48:
+static inline void msm_dp_write_p0(struct msm_dp_panel_private *panel,
+			       u32 offset, u32 data)

CHECK: Alignment should match open parenthesis
#154: FILE: drivers/gpu/drm/msm/dp/dp_panel.c:58:
+static inline u32 msm_dp_read_p0(struct msm_dp_panel_private *panel,
+			       u32 offset)

[... 4 more alignment checks ...]
total: 0 errors, 0 warnings, 6 checks, 266 lines checked
Fix: These are CHECK-level warnings (not ERROR or WARNING), and they appear in revert commits. The alignment issues exist in the code being reverted. Since these are reverts preparing for newer versions of the patches, the style issues will be resolved when the new patches (commits 3 and 4) are applied. No action required — the new patches (commits 3 and 4) passed checkpatch cleanly.

Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git b5d890825bc2826f24b1b12e992fe14cdafe0cea..b3f6e3fdb68532420d80dcb717106fb19fc95842
❌ check-patch-compliance

Root cause: Four distinct compliance failures across all four commits.

Failure details:

Issue 1 & 2: Missing prefix on Revert commits
Checking commit: Revert "FROMLIST: drm/msm/dp: Add catalog support for 3rd/4th stream MST"
Commit summary does not start with a required prefix

Checking commit: Revert "FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 register blocks"
Commit summary does not start with a required prefix
The two revert commits (commits 1 and 2) have subjects starting with Revert "FROMLIST: ... but lack a prefix before the word Revert. The checker requires revert commits to carry their own prefix.

Issue 3: Content mismatch + Author mismatch
Checking commit: FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 register blocks
Change is different from the one mentioned in Link
Author mismatch:
  Original author: Abhinav Kumar <quic_abhinavk@quicinc.com>
  Commit author : Yongxing Mou <yongxing.mou@oss.qualcomm.com>
Commit 3 (1147ec0b5574) has:

Content mismatch: The patch differs from the upstream lore link.

Author mismatch: The commit author is Yongxing Mou but the upstream author is Abhinav Kumar.

Issue 4: Content mismatch
Checking commit: FROMLIST: drm/msm/dp: Add stream-aware link register accessors
Change is different from the one mentioned in Link
Commit 4 (9d49f1b7e221) has content that differs from the upstream lore link.

Fix:

For Issues 1 & 2 (Revert prefix):
git rebase -i b5d890825bc2826f24b1b12e992fe14cdafe0cea
# Mark commits 65443ebd3b64 and a601e2cdea53 as 'edit'

# For commit 1:
git commit --amend -m "FROMLIST: Revert \"FROMLIST: drm/msm/dp: Add catalog support for 3rd/4th stream MST\"

This reverts commit cd58926a62d45b9964f8cb6241e18a95e1067757.

This is reverted because a newer version of this patch is being introduced.

Signed-off-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>"

# For commit 2:
git commit --amend -m "FROMLIST: Revert \"FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 register blocks\"

This reverts commit [original-sha].

This is reverted because a newer version of this patch is being introduced.

Signed-off-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>"

git rebase --continue
For Issue 3 (Content + Author mismatch):

First, verify the content difference:
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260831-msm-dp-mst-v6-5-c91d35d6fb9e@oss.qualcomm.com/ -o /tmp/out
diff <(git format-patch -1 1147ec0b5574 --stdout | awk '/^diff/,/^--$/' | grep -E '^[+-][^+-]') \
     <(awk '/^diff/,/^--$/' /tmp/out/*.mbx | grep -E '^[+-][^+-]')
If the content difference is legitimate (e.g., adaptation for the target tree), document it in the commit message. Otherwise, align the patch with upstream.

Fix the author:
git rebase -i b5d890825bc2826f24b1b12e992fe14cdafe0cea
# Mark commit 1147ec0b5574 as 'edit'
git commit --amend --author="Abhinav Kumar <quic_abhinavk@quicinc.com>"
git rebase --continue
For Issue 4 (Content mismatch):

Verify and align with upstream:
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260831-msm-dp-mst-v6-7-c91d35d6fb9e@oss.qualcomm.com/ -o /tmp/out
# Compare and fix any unintended differences
Reproduce locally:
cd /path/to/kernel
bash /path/to/kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base b5d890825bc2826f24b1b12e992fe14cdafe0cea \
  --head b3f6e3fdb68532420d80dcb717106fb19fc95842
❌ tag-check

Root cause: Two commits (the revert commits) do not start with a required subject-line prefix tag.

Failure details:

The target branch is qcom-6.18.y, which is not qcom-next or qcom-next-staging. Therefore, every commit must start with a valid prefix tag.

Commits with missing prefix:

Commit 65443ebd3b64:
Subject: Revert "FROMLIST: drm/msm/dp: Add catalog support for 3rd/4th stream MST"
❌ Missing prefix before Revert

Commit a601e2cdea53:
Subject: Revert "FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 register blocks"
❌ Missing prefix before Revert

Commits with valid prefix:

Commit 1147ec0b5574:
Subject: FROMLIST: drm/msm/dp: Add support for programming p1/p2/p3 register blocks
✅ Valid prefix: FROMLIST:

Commit 9d49f1b7e221:
Subject: FROMLIST: drm/msm/dp: Add stream-aware link register accessors
✅ Valid prefix: FROMLIST:

Fix:

Add FROMLIST: prefix before Revert for both revert commits:
git rebase -i b5d890825bc2826f24b1b12e992fe14cdafe0cea
# Mark commits 65443ebd3b64 and a601e2cdea53 as 'edit'

# For each commit:
git commit --amend -m "FROMLIST: Revert \"FROMLIST: drm/msm/dp: ...\""
git rebase --continue
This is the same fix as required for check-patch-compliance Issues 1 & 2.

Verdict

4 blockers must be fixed before merge:

Revert commits missing prefix (affects both check-patch-compliance and tag-check): Add FROMLIST: prefix before Revert in commits 1 and 2.

Author mismatch in commit 3: Change author from Yongxing Mou to Abhinav Kumar.

Content mismatch in commit 3: Verify and align with upstream lore patch, or document the adaptation reason.

Content mismatch in commit 4: Verify and align with upstream lore patch.

The checkpatch style issues are CHECK-level warnings in revert commits and do not block merge, as the new patches (commits 3 and 4) passed checkpatch cleanly.

qcomlnxci commented Sep 9, 2026

Test jobs on 9d49f1b

qcomlnxci commented Sep 9, 2026

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	✅ Pass
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
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	◻️	◻️	⚠️ skip	⚠️ skip	❌ Fail	❌ 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	✅ Pass
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	❌ Fail	❌ Fail	❌ Fail	❌ 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	◻️	❌ Fail	✅ 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) commented Sep 9, 2026

Contributor

Crash on Purwa device :
https://lava-oss.qualcomm.com/scheduler/job/220623

[   38.671995][ T1221] CPU: 1 UID: 0 PID: 1221 Comm: v4l_id Tainted: G        W           6.18.44-g564a1ba1e231 #1 PREEMPT 
[   38.672006][ T1221] Tainted: [W]=WARN
[   38.672011][ T1221] Hardware name: Qualcomm Technologies, Inc. Purwa IoT EVK (DT)
[   38.672017][ T1221] pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
[   38.672019][ T1221] pc : __iommu_unmap+0x38/0x258
[   38.707303][ T1221] lr : iommu_unmap+0x50/0xa8
[   38.711869][ T1221] sp : ffff80009b83b890
[   38.715993][ T1221] x29: ffff80009b83b8a0 x28: ffff0008291ed240 x27: 0000000000000000
[   38.724035][ T1221] x26: 0000000000000000 x25: ffff00080d160ac0 x24: 0000000087700000
[   38.732075][ T1221] x23: ffff00080c77c840 x22: ffff00081c3aecc0 x21: 0000000000000000
[   38.740116][ T1221] x20: ffff000810e00080 x19: 0000000000000000 x18: ffffffffffffffff
[   38.748153][ T1221] x17: ffff80007b4ddbf0 x16: ffff80007b4e1430 x15: ffff80007b4e1374
[   38.756193][ T1221] x14: ffff800080f60cb0 x13: ffff8000804d4e08 x12: 0000000000000000
[   38.764232][ T1221] x11: 0000000000000000 x10: 0000000000000000 x9 : ffff800080ae9ba0
[   38.772272][ T1221] x8 : ffff80009b83b740 x7 : 0000000000000000 x6 : 0000000000000000
[   38.780313][ T1221] x5 : ffffffffffffffff x4 : ffff0008291ed240 x3 : ffff80009b83b908
[   38.788354][ T1221] x2 : 0000000000700000 x1 : 0000000000000000 x0 : 0000000000000000
[   38.796394][ T1221] Call trace:
[   38.799633][ T1221]  __iommu_unmap+0x38/0x258 (P)
[   38.804471][ T1221]  iommu_unmap+0x50/0xa8
[   38.808685][ T1221]  iris_load_fw_to_memory+0x1b0/0x1d8 [qcom_iris]
[   38.815135][ T1221]  iris_fw_load+0x20/0x118 [qcom_iris]
[   38.820601][ T1221]  iris_core_init+0xc8/0x190 [qcom_iris]
[   38.826241][ T1221]  iris_open+0x88/0x460 [qcom_iris]
[   38.831441][ T1221]  v4l2_open+0x80/0x1b8 [videodev]
[   38.836551][ T1221]  chrdev_open+0xb8/0x240
[   38.840856][ T1221]  do_dentry_open+0x23c/0x4d0
[   38.845519][ T1221]  vfs_open+0x34/0xf8
[   38.849461][ T1221]  do_open+0x288/0x350
[   38.853498][ T1221]  path_openat+0x110/0x260
[   38.857886][ T1221]  do_filp_open+0xb0/0x178
[   38.862272][ T1221]  do_sys_openat2+0x94/0x108
[   38.866839][ T1221]  __arm64_sys_openat+0x6c/0xc0
[   38.871670][ T1221]  invoke_syscall+0x4c/0xf8
[   38.876146][ T1221]  el0_svc_common.constprop.0+0xc8/0xf0
[   38.881695][ T1221]  do_el0_svc+0x24/0x38
[   38.885821][ T1221]  el0_svc+0x3c/0x110
[   38.889774][ T1221]  el0t_64_sync_handler+0xa0/0xe8
[   38.894785][ T1221]  el0t_64_sync+0x19c/0x1a0
[   38.899268][ T1221] Code: a90673fb f9432c80 f90007e0 d2800000 (b94002a0) 
[   38.906245][ T1221] ---[ end trace 0000000000000000 ]---
[   38.946005][ T1221] Kernel panic - not syncing: Oops: Fatal exception

YongxingMou commented Sep 9, 2026

Author

Crash on Purwa device : https://lava-oss.qualcomm.com/scheduler/job/220623

[   38.671995][ T1221] CPU: 1 UID: 0 PID: 1221 Comm: v4l_id Tainted: G        W           6.18.44-g564a1ba1e231 #1 PREEMPT 
[   38.672006][ T1221] Tainted: [W]=WARN
[   38.672011][ T1221] Hardware name: Qualcomm Technologies, Inc. Purwa IoT EVK (DT)
[   38.672017][ T1221] pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
[   38.672019][ T1221] pc : __iommu_unmap+0x38/0x258
[   38.707303][ T1221] lr : iommu_unmap+0x50/0xa8
[   38.711869][ T1221] sp : ffff80009b83b890
[   38.715993][ T1221] x29: ffff80009b83b8a0 x28: ffff0008291ed240 x27: 0000000000000000
[   38.724035][ T1221] x26: 0000000000000000 x25: ffff00080d160ac0 x24: 0000000087700000
[   38.732075][ T1221] x23: ffff00080c77c840 x22: ffff00081c3aecc0 x21: 0000000000000000
[   38.740116][ T1221] x20: ffff000810e00080 x19: 0000000000000000 x18: ffffffffffffffff
[   38.748153][ T1221] x17: ffff80007b4ddbf0 x16: ffff80007b4e1430 x15: ffff80007b4e1374
[   38.756193][ T1221] x14: ffff800080f60cb0 x13: ffff8000804d4e08 x12: 0000000000000000
[   38.764232][ T1221] x11: 0000000000000000 x10: 0000000000000000 x9 : ffff800080ae9ba0
[   38.772272][ T1221] x8 : ffff80009b83b740 x7 : 0000000000000000 x6 : 0000000000000000
[   38.780313][ T1221] x5 : ffffffffffffffff x4 : ffff0008291ed240 x3 : ffff80009b83b908
[   38.788354][ T1221] x2 : 0000000000700000 x1 : 0000000000000000 x0 : 0000000000000000
[   38.796394][ T1221] Call trace:
[   38.799633][ T1221]  __iommu_unmap+0x38/0x258 (P)
[   38.804471][ T1221]  iommu_unmap+0x50/0xa8
[   38.808685][ T1221]  iris_load_fw_to_memory+0x1b0/0x1d8 [qcom_iris]
[   38.815135][ T1221]  iris_fw_load+0x20/0x118 [qcom_iris]
[   38.820601][ T1221]  iris_core_init+0xc8/0x190 [qcom_iris]
[   38.826241][ T1221]  iris_open+0x88/0x460 [qcom_iris]
[   38.831441][ T1221]  v4l2_open+0x80/0x1b8 [videodev]
[   38.836551][ T1221]  chrdev_open+0xb8/0x240
[   38.840856][ T1221]  do_dentry_open+0x23c/0x4d0
[   38.845519][ T1221]  vfs_open+0x34/0xf8
[   38.849461][ T1221]  do_open+0x288/0x350
[   38.853498][ T1221]  path_openat+0x110/0x260
[   38.857886][ T1221]  do_filp_open+0xb0/0x178
[   38.862272][ T1221]  do_sys_openat2+0x94/0x108
[   38.866839][ T1221]  __arm64_sys_openat+0x6c/0xc0
[   38.871670][ T1221]  invoke_syscall+0x4c/0xf8
[   38.876146][ T1221]  el0_svc_common.constprop.0+0xc8/0xf0
[   38.881695][ T1221]  do_el0_svc+0x24/0x38
[   38.885821][ T1221]  el0_svc+0x3c/0x110
[   38.889774][ T1221]  el0t_64_sync_handler+0xa0/0xe8
[   38.894785][ T1221]  el0t_64_sync+0x19c/0x1a0
[   38.899268][ T1221] Code: a90673fb f9432c80 f90007e0 d2800000 (b94002a0) 
[   38.906245][ T1221] ---[ end trace 0000000000000000 ]---
[   38.946005][ T1221] Kernel panic - not syncing: Oops: Fatal exception

This error is not coming from the display subsystem and is unrelated to my changes. Was this error already present before this change was merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Labels

None yet