Issue with Soundwire on Up Squared 6000 Board
Affected images versions
Type | Arch | v2021 | v2022 | v2023dev2 |
---|---|---|---|---|
minimal/fixedfunction | amd64 | 20220808.0216 | ||
minimal/fixedfunction | armhf | |||
minimal/fixedfunction | arm64 | |||
target/hmi | amd64 | 20220808.0216 | ||
target/hmi | armhf | |||
target/hmi | arm64 | |||
basesdk | amd64 | |||
sdk | amd64 | |||
nfs | amd64 | |||
nfs | armhf | |||
nfs | arm64 | |||
lxc | amd64 | |||
lxc | armhf | |||
lxc | arm64 | |||
image-builder | ||||
package-source-builder |
Unaffected images versions
-
v2022
: newer kernel than v2021 (linux v5.10.113) -
v2023dev3
: newer kernel than v2021 (linux v5.10.113)
Testcase
The link to the testcase on https://qa.apertis.org/ if the bug was found during a testing round
Not related to a test case.
Steps to reproduce
- Download Apertis v2021 image.
- Flash it to a USB drive.
- Insert the USB drive on the Up Squared 6000 board USB port. Power on.
- Boot log should show error messages periodically reporting:
[ 83.038419] intel-sdw intel-sdw.0: Parity error
[ 83.042030] sdw_cdns_irq: 133519 callbacks suppressed
[ 83.042031] intel-sdw intel-sdw.0: Bus clash for control word
Expected result
- Kernel should report no error messages.
Actual result
- Boot log should show error messages periodically reporting:
[ 83.038419] intel-sdw intel-sdw.0: Parity error
[ 83.042030] sdw_cdns_irq: 133519 callbacks suppressed
[ 83.042031] intel-sdw intel-sdw.0: Bus clash for control word
Reproducibility
How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?
Put the
-
✅ always - often, but not always
- rarely
Impact of bug
- Kernel constantly logs error messages to the debug console. This makes LAVA tests impossible to get parsed properly.
- Audio may not work properly on v2021 (need to be checked).
Attachments
Add further information about the environment in the form of attachments here. Attach plain text files from log output (from
journalctl
,systemctl
, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.
Screenshots and videos are usually useful for graphic issues.
Root cause
describe in one line what caused the issue to give a hint to product teams whether they may be impacted or not
Outcomes
TBD
Management data
This section is for management only, it should be the last one in the description.
/cc @andrunko @em @sagar @sudarshan @wlozano
Phabricator link: https://phabricator.apertis.org/T9136