[BUG][TGL][SDW][CI] Volteer: Parity error detected

In daily test report 594 on TGL SDW Chromebook, below message shows in suspend-resume test case:

[   38.453229] max98373 sdw:1:19f:8373:0:7: Parity error detected
[   38.454043] max98373 sdw:1:19f:8373:0:3: Parity error detected

Recipe:
Kernel: topic/sof-dev d0a335d
SOF : master e04610b
TPLG: sof-tgl-sdw-max98373-rt5682-4ch.tplg
Platform: TGL Chrome book

@naveen-manohar

@naveen-manohar FYI.

Will monitor this issue for a week, if not reproduced, will close.

@aiChaoSONG

@aiChaoSONG I often get this parity error. According to @bardliao we need to add a prop to 98373

@aiChaoSONG

@aiChaoSONG @RanderWang Is there any impact on audio functionality when you observe this parity error? Need this info to decide the proper priority

@aiChaoSONG

@aiChaoSONG @RanderWang Is there any impact on audio functionality when you observe this parity error? Need this info to decide the proper priority

Nothing but notify you command parity error

Not reproduced on: 2020/11/23 UTC+8

@fredoh9

Reproduced w/ topic/sof-dev + timeout fixes:

kernel: [ 9630.149535] intel-sdw intel-sdw.0: intel_link_power_up: powering up all links
kernel: [ 9630.149536] intel-sdw intel-sdw.0: intel_link_power_up: first link up, programming SYNCPRD
kernel: [ 9630.149880] rt5682 sdw:0:25d:5682:0: sdw_modify_slave_status: initializing completion for Slave 1
kernel: [ 9630.150315] sof-audio-pci 0000:00:1f.3: ipc rx: 0x90020000: GLB_TRACE_MSG
kernel: [ 9630.150325] sof-audio-pci 0000:00:1f.3: ipc rx done: 0x90020000: GLB_TRACE_MSG
kernel: [ 9630.150742] intel-sdw intel-sdw.0: Slave status change: 0x2
kernel: [ 9630.150747] soundwire sdw-master-0: Slave attached, programming device number
kernel: [ 9630.150937] soundwire sdw-master-0: SDW Slave Addr: 20025d568200
kernel: [ 9630.150939] soundwire sdw-master-0: SDW Slave class_id 0x00, mfg_id 0x025d, part_id 0x5682, unique_id 0x0, version 0x2
kernel: [ 9630.150940] soundwire sdw-master-0: Slave already registered, reusing dev_num:1
kernel: [ 9630.151178] intel-sdw intel-sdw.0: Msg ignored for Slave 0
kernel: [ 9630.151179] soundwire sdw-master-0: No more devices to enumerate
kernel: [ 9630.151203] intel-sdw intel-sdw.0: Slave status change: 0x21
kernel: [ 9630.151206] rt5682 sdw:0:25d:5682:0: sdw_modify_slave_status: signaling completion for Slave 1
kernel: [ 9630.162317] max98373 sdw:1:19f:8373:0:7: sdw_modify_slave_status: initializing completion for Slave 1
kernel: [ 9630.162319] max98373 sdw:1:19f:8373:0:3: sdw_modify_slave_status: initializing completion for Slave 2
kernel: [ 9630.163071] intel-sdw intel-sdw.1: Slave status change: 0x2
kernel: [ 9630.163075] soundwire sdw-master-1: Slave attached, programming device number
kernel: [ 9630.163241] soundwire sdw-master-1: SDW Slave Addr: 27019f837300
kernel: [ 9630.163241] soundwire sdw-master-1: SDW Slave class_id 0x00, mfg_id 0x019f, part_id 0x8373, unique_id 0x7, version 0x2
kernel: [ 9630.163242] soundwire sdw-master-1: Slave already registered, reusing dev_num:1
kernel: [ 9630.163470] soundwire sdw-master-1: SDW Slave Addr: 23019f837300
kernel: [ 9630.163470] soundwire sdw-master-1: SDW Slave class_id 0x00, mfg_id 0x019f, part_id 0x8373, unique_id 0x3, version 0x2
kernel: [ 9630.163471] soundwire sdw-master-1: Slave already registered, reusing dev_num:2
kernel: [ 9630.163704] intel-sdw intel-sdw.1: Msg ignored for Slave 0
kernel: [ 9630.163705] soundwire sdw-master-1: No more devices to enumerate
kernel: [ 9630.163731] intel-sdw intel-sdw.1: Slave status change: 0x221
kernel: [ 9630.163734] max98373 sdw:1:19f:8373:0:7: sdw_modify_slave_status: signaling completion for Slave 1
kernel: [ 9630.163927] max98373 sdw:1:19f:8373:0:3: sdw_modify_slave_status: signaling completion for Slave 2
kernel: [ 9630.164145] intel-sdw intel-sdw.1: Slave status change: 0x440
kernel: [ 9630.164427] max98373 sdw:1:19f:8373:0:7: Parity error detected
kernel: [ 9630.165301] max98373 sdw:1:19f:8373:0:3: Parity error detected
kernel: [ 9630.165704] intel-sdw intel-sdw.1: Slave status change: 0x220

A parity check will typically miss 50% of the cases. Here we have two separate devices who report the parity issue at the same time, this is statistically strongly correlated and does not appear random.

The problem did not appear in a test repetition, so it's not 100% reproducible. Will add more traces and keep checking.

@fredoh9 @RanderWang I would need your help to inspect the cases where this error appeared to see if this was with a specific test case:

If I look at the initial bug report above, I see that in Test 594 the parity error happened with
check-suspend-resume-with-audio.sh -l 15 -m capture

When I reproduced the test, it was with
check-suspend-resume-with-audio.sh -l 15 -m playback

Maybe it's a red-herring, but it's worth checking if we need to have audio streaming to see the issue, or if this happened also in the past with regular plain vanilla suspend-resume.

soundwire: bus: clear parity interrupt before the mask is enabled

soundwire: add master quirks for bus clash and parity

soundwire: bus: clear parity interrupt before the mask is enabled

soundwire: add master quirks for bus clash and parity

Navigation Menu

Repository navigation

[BUG][TGL][SDW][CI] Volteer: Parity error detected #2533

21 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[BUG][TGL][SDW][CI] Volteer: Parity error detected #2533

Description

Activity

keyonjie commented on Nov 2, 2020

aiChaoSONG commented on Nov 13, 2020

RanderWang commented on Nov 17, 2020

mengdonglin commented on Nov 18, 2020

RanderWang commented on Nov 19, 2020

aiChaoSONG commented on Nov 23, 2020

plbossart commented on Dec 11, 2020

21 remaining items

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions