From: Birk Skyum <birk.skyum@pm.me>
To: Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Question about Iris SID override assertion on Yoga Slim 7x
Date: Sun, 13 Sep 2026 19:47:14 +0000 [thread overview]
Message-ID: <20260913194707.91885-1-birk.skyum@pm.me> (raw)
Hi Vikash and Dikshita,
I'm testing Iris video decoding on a Lenovo Yoga Slim 7x (83ED, X1E80100).
This is a request for guidance on a firmware assertion. It currently
reproduces on a modified test stack, and I'm working on reducing it to
an unmodified-driver reproduction.
After repeated runtime-suspend/resume cycles, VP9 startup intermittently
hits this firmware assertion before initial stream settings or CAPTURE START:
VenusCoreCtrl_InitSS(506): un-expected SID override configuration
WaitForHWidle(462): VENUS is idle, no HW is running
assert_loop(500): FW Assertion - venusCoreController.c:507
The first HFI error is 0x05000003. The SFR names the same source line.
Later venus_c2_parsing.c:1550 assertions follow automatic recovery; they
are not the original failure.
Could you clarify what the SID override check expects on X1E80100, and
whether there is a known firmware, secure-firmware, or resume-sequencing
requirement I should check? Which diagnostics would help distinguish a
driver sequencing problem from a firmware requirement? I can test a
targeted diagnostic or patch.
The firmware is qcom/x1e80100/LENOVO/83ED/qcvss8380.mbn from
linux-firmware-qcom 20260810-2:
video-firmware.3.1-e5aea20c64cb6df9a1c9be99e206053b36424939
PROD, build May 9 2024
SHA256 3456a15e01528c2ba2957ef2b78daefd875841b262dc02f0c3bb03c33cba657f
That hash matches the current linux-firmware main file. The BIOS is
NHCN62WW, dated 12/02/2025. The device tree lists qcom,x1e80100-iris with
the qcom,sm8550-iris fallback.
The test repeatedly decodes the same synthetic 1280x720 VP9 clip, 120
frames at normal speed, closes the decoder, verifies runtime_status is
suspended for 100 seconds, then starts again. FFmpeg is 9.0.1 with a local
fix to requeue empty non-LAST ERROR capture buffers. Successful runs
match every decoded frame against software decoding.
On one cold boot, three 100-second idle trials with power/control=on
passed. After restoring auto, two suspended-idle trials passed and the
third failed. On another boot with auto throughout, two passed and the
third failed. A separate codec guard removed an unnecessary AV1-only
partial buffer from VP9; its warning disappeared, but the fourth
suspended-idle trial still hit the same SID assertion. These comparisons
do not establish runtime PM as the cause or keeping power on as a fix.
This is a modified test stack, not a pristine-mainline reproduction. The
kernel is 7.2.0-1.1-aarch64-ARCH-camera1, with camera patches. The in-tree
Iris and video-clock sources were built as external modules. Iris also
has experimental initial-CAPTURE deferral and pre-start buffer ownership
changes, a bounded HFI/SFR diagnostic, and Renjiang Han's firmware-logging
patch with an early debug-queue drain to retain the pre-assertion messages.
The failing session receives OPEN acknowledgement and its first compressed
input before the fatal error. No looping or seek is reached.
Testing stops at the first failure and resumes only after a clean shutdown
and physical power-on. No clock-module reloads are involved. I can provide
the synthetic clip, exact source changes and filtered HFI trace if useful.
Thanks,
Birk
next reply other threads:[~2026-09-13 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 19:47 Birk Skyum [this message]
2026-09-17 11:20 ` Question about Iris SID override assertion on Yoga Slim 7x Vikash Garodia
2026-09-17 14:08 ` Birk Skyum
2026-09-17 14:21 ` Birk Skyum
2026-09-24 14:41 ` Vikash Garodia
2026-09-24 15:07 ` Birk Skyum
2026-09-24 15:25 ` Vikash Garodia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260913194707.91885-1-birk.skyum@pm.me \
--to=birk.skyum@pm.me \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=vikash.garodia@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox