Skip to content

[TGL][SDW][RT711] Initialization not complete, timed out in suspend-resume test #2599

Closed

Description

@aiChaoSONG

Description
In daily report 962, several TGL device show below error message in suspend-resume test case, include TGL_RVP_SDW, TGLU_ANDR_SDCA and TGL_OLPMLK_RT715 and CML_OLP_RT711

[ 8611.896412] kernel: rt711 sdw:0:25d:711:0: Initialization not complete, timed out
[ 8611.896427] kernel: PM: dpm_run_callback(): rt711_dev_resume+0x0/0x90 [snd_soc_rt711] returns -110
[ 8611.896433] kernel: PM: Device sdw:0:25d:711:0 failed to resume: error -110

Recipe
Kernel Branch: topic/sof-dev
Kernel Commit: 25012df
SOF Branch: master
SOF Commit: cc1cd8a

dmesg.txt

Reproduced in:

Activity

  1. added
    TGLApplies to Tiger Lake platform
    SDWApplies to SoundWire bus for codec connection
    on Dec 4, 2020
  2. plbossart commented on Dec 4, 2020

    @plbossart
    Member

    That's not good... Do we know what has changed since the last case that worked? We haven't seen those issues for weeks, it's surprising that they pop-up again.

    @bardliao @RanderWang FYI.

  3. bardliao commented on Dec 7, 2020

    @bardliao
    Collaborator

    I think we should firstly find a easier way to reproduce it. I can only see this issue in run-all-tests.sh. I can't see it if I run ./check-suspend-resume.sh only.

  4. plbossart commented on Dec 7, 2020

    @plbossart
    Member

    @bardliao it's reproduced in other CI tests.
    I agree that it's not clear why that happens only when we run multiple tests, but the problem does exist :-)

  5. bardliao commented on Dec 8, 2020

    @bardliao
    Collaborator

    @plbossart Yep, my point is that if we want to figure out when did the issue start from, we need a easier way to reproduce it. But you have fixed it by #2603 :)

  6. plbossart commented on Dec 8, 2020

    @plbossart
    Member

    I am not happy though, I'd really want to know what causes this test to fail in the sequence - something must interfere. it's very very odd that the suspend-resume tests work if there is nothing done prior.

  7. added
    bugSomething isn't working
    P1Blocker bugs or important features
    on Dec 11, 2020
  8. added
    P2Critical bugs or normal features
    and removed
    P1Blocker bugs or important features
    on Dec 15, 2020
  9. keyonjie commented on Dec 15, 2020

    @keyonjie

    lower priority to P2 as it is not a usual end user scenario with kmod remove/install.

  10. bardliao commented on Dec 15, 2020

    @bardliao
    Collaborator

    This only happens after d5dcce0c414fcbfe4c2037b66ac69ea5f9b3f75cand 99aed92 and two iterations of kmod test.

  11. plbossart commented on Dec 15, 2020

    @plbossart
    Member

    lower priority to P2 as it is not a usual end user scenario with kmod remove/install.

    No. This breaks our CI and needs to be fixed as P1. no exceptions, sorry. You are sending a really bad message here.

  12. added
    P1Blocker bugs or important features
    and removed
    P2Critical bugs or normal features
    on Dec 15, 2020
  13. marc-hb commented on Dec 17, 2020

    @marc-hb
    Collaborator

    This only happens after d5dcce0 99aed92 and two iterations of kmod test.

    @bardliao can you submit to sof-test a test change or test parameter/configuration that reproduces more easily? It doesn't have to be in CI if it takes long but it should be at least in nightly tests.

    Yep, my point is that if we want to figure out when did the issue start from, we need a easier way to reproduce it. But you have fixed it by #2603 :)

    Reverting fixes locally is required to "test the test". If the reverts are too complicated then backtracking is another option.

  14. keyonjie commented on Dec 21, 2020

    @keyonjie

    lower priority to P2 as it is not a usual end user scenario with kmod remove/install.

    No. This breaks our CI and needs to be fixed as P1. no exceptions, sorry. You are sending a really bad message here.

    Thanks for your feedback @plbossart . That was the decision from the bug scrub meeting. FWIW, I have no objection to mark it P1 since Bard and you who actually works on it agree. :)

  15. keyonjie commented on Dec 21, 2020

    @keyonjie

    assign it to @bardliao who actually already work on it.

  16. keyonjie commented on Dec 21, 2020

    @keyonjie

    will PR fix this issue: #2635

  17. mengdonglin commented on Dec 22, 2020

    @mengdonglin

    Closing as PR #2635 was merged.

  18. marc-hb commented on Jan 4, 2021

    @marc-hb
    Collaborator

    Closing as PR #2635 was merged.

    I hope you meant "as #2635 was merged and the tests have been consistently passing" :-)

    Either way, re-opening based on the most recent comments in #2635, more specifically: "we don't need this" and "please prepare a revert".

  19. reopened this on Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1Blocker bugs or important featuresSDWApplies to SoundWire bus for codec connectionTGLApplies to Tiger Lake platformbugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions