Skip to content

The sof does not work on UP2 with pcm512x. #609

Closed
Closed
The sof does not work on UP2 with pcm512x.#609
Assignees
tlaudamichalgrodzicki
Labels
APLApplies to Apollolake platformP1Blocker bugs or important featuresblockedprogress blocked by something else, applies to either feature or bugbugSomething isn't working as expectedverifiedQA/Bug reporter verifies solution worked.

Description

@markyang
markyang
opened on Nov 22, 2018

Summary:
The sof does not work on UP2 with pcm512x.
sof-logger is empty. sof-logger -t log is attached below.
dmesg:

[    4.361126] random: crng init done
[    4.361130] random: 7 urandom warning(s) missed due to ratelimiting
[    4.492483] sof-audio sof-audio: ipc tx: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    4.492617] sof-audio sof-audio: ipc tx succeeded: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    4.492683] sof-audio sof-audio: ipc tx: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    4.492800] sof-audio sof-audio: ipc tx succeeded: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    4.492862] sof-audio sof-audio: ipc tx: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    4.492980] sof-audio sof-audio: ipc tx succeeded: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    4.493028] sof-audio sof-audio: ipc tx: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    4.493150] sof-audio sof-audio: ipc tx succeeded: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    4.493267] sof-audio sof-audio: ipc rx: 0x90020000: GLB_TRACE_MSG
[    4.493284] sof-audio sof-audio: ipc rx done: 0x90020000: GLB_TRACE_MSG
[    4.951842] systemd-udevd (1441) used greatest stack depth: 11368 bytes left
[    4.993285] sof-audio sof-audio: ipc rx: 0x90020000: GLB_TRACE_MSG
[    4.993301] sof-audio sof-audio: ipc rx done: 0x90020000: GLB_TRACE_MSG
[    5.160103] sof-audio sof-audio: ipc tx: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    5.160251] sof-audio sof-audio: ipc tx succeeded: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    5.160315] sof-audio sof-audio: ipc tx: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    5.160435] sof-audio sof-audio: ipc tx succeeded: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    5.160808] sof-audio sof-audio: ipc tx: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    5.160937] sof-audio sof-audio: ipc tx succeeded: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    5.160998] sof-audio sof-audio: ipc tx: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    5.161121] sof-audio sof-audio: ipc tx succeeded: 0x50010000: GLB_COMP_MSG: SET_VALUE
[    5.579899] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[    5.583319] Generic PHY r8169-200:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
[    5.696134] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[    5.706674] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[    5.708733] Generic PHY r8169-300:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
[    5.820665] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[    5.820728] r8169 0000:03:00.0 enp3s0: Link is Down
[    5.993379] sof-audio sof-audio: ipc rx: 0x90020000: GLB_TRACE_MSG
[    5.993401] sof-audio sof-audio: ipc rx done: 0x90020000: GLB_TRACE_MSG
[    7.282210] sof-audio sof-audio: ipc tx: 0x40010000: GLB_PM_MSG: CTX_SAVE
[    7.282471] sof-audio sof-audio: error: reply expected 0x40 got 0xc bytes
[    7.282516] sof-audio sof-audio: error: ipc error for 0x40010000 size 0x40
[    7.282528] sof-audio sof-audio: error: ctx_save ipc error during suspend -22
[    7.282542] sof-audio-pci 0000:00:0e.0: can't suspend (snd_sof_runtime_suspend [snd_sof] returned -22)
[    7.418897] pcm512x i2c-104C5122:00: No SCLK, using BCLK: -2

Test steps:

  1. arecord -l
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofbxtpcm512x [sof-bxt-pcm512x], device 0: Port5 (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofbxtpcm512x [sof-bxt-pcm512x], device 1: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofbxtpcm512x [sof-bxt-pcm512x], device 2: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofbxtpcm512x [sof-bxt-pcm512x], device 3: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Test env:
sof master: 7a79343
sof tool: 6da07a9
kernel sof-dev: b846ee5
tplg: sof-apl-pcm512x.tplg-6da07a91

Log:
dmesg-apl.log
logger-apl-t.log

Activity

  1. markyang
    added
    bugSomething isn't working as expected
    APLApplies to Apollolake platform
    blockedprogress blocked by something else, applies to either feature or bug
    on Nov 22, 2018

  2. xiulipan commented on Nov 22, 2018

    @xiulipan
    xiulipan
    on Nov 22, 2018
    Contributor

    @tlauda @jajanusz @lgirdwood
    This bug is a regression caused by #603

  3. mengdonglin
    added
    P1Blocker bugs or important features
    on Nov 22, 2018
  4. mengdonglin
    assigned
    tlauda
    and
    michalgrodzicki
    on Nov 22, 2018

  5. tlauda commented on Nov 22, 2018

    @tlauda
    tlauda
    on Nov 22, 2018
    Contributor

    @xiulipan Then we also need to modify kernel. Let's not make any exceptions in terms of ipc replies. Every other ipc uses some kind of reply type message, even if it's the custom one.

  6. xiulipan commented on Nov 22, 2018

    @xiulipan
    xiulipan
    on Nov 22, 2018
    Contributor

    @tlauda
    What do you mean by exceptions
    @ranj063
    I think the reply here will be used to store some important info at the suspend?

  7. tlauda commented on Nov 22, 2018

    @tlauda
    tlauda
    on Nov 22, 2018
    Contributor

    @xiulipan I mean, that we shouldn't use the same struct as a reply. It's not done for any other ipc. And I know, that in the future it will be used to store some info, but let's not get ahead of ourselves. Either way, the struct for reply will need to be changed.

  8. xiulipan commented on Nov 22, 2018

    @xiulipan
    xiulipan
    on Nov 22, 2018
    Contributor

    @tlauda
    Ok, maybe we have some misuse here. @ranj063 Please give @tlauda some explanation about why the PM need use the same structure as reply.

    But I still did not know what is the purpose of #603

    Uses generic reply for pm_context ipc messages.
    Why do you need the use generic reply for this CTX_SAVE IPC?

    And if you need to change some IPC related stuff, please notify us ahead to have some buffer time to make the change work smoothly between Linux and FW.

  9. tlauda commented on Nov 22, 2018

    @tlauda
    tlauda
    on Nov 22, 2018
    Contributor

    @xiulipan Change in kernel is here: thesofproject/linux#310.

  10. xiulipan commented on Nov 22, 2018

    @xiulipan
    xiulipan
    on Nov 22, 2018
    Contributor

    @tlauda
    Thanks, wait for @ranj063 review.

  11. lgirdwood commented on Nov 22, 2018

    @lgirdwood
    lgirdwood
    on Nov 22, 2018
    Member

    @xiulipan merged.

  12. xiulipan commented on Nov 23, 2018

    @xiulipan
    xiulipan
    on Nov 23, 2018
    Contributor

    close via thesofproject/linux#310

  13. xiulipan
    closed this as completedon Nov 23, 2018

  14. mengdonglin commented on Nov 24, 2018

    @mengdonglin
    mengdonglin
    on Nov 24, 2018
    Collaborator

    @markyang Could you share latest verification result?

  15. mengdonglin
    reopened this on Nov 24, 2018

  16. markyang commented on Nov 26, 2018

    @markyang
    markyang
    on Nov 26, 2018
    Author

    Summary:
    This issue cannot be reproduced on UP2 w/ pcm512x any more.

  17. mengdonglin
    added
    verifiedQA/Bug reporter verifies solution worked.
    on Nov 26, 2018
  18. mengdonglin
    closed this as completedon Nov 26, 2018
  19. mengdonglin
    reopened this on Nov 27, 2018
  20. mengdonglin
    closed this as completedon Nov 27, 2018

  21. markyang commented on Jan 7, 2019

    @markyang
    markyang
    on Jan 7, 2019
    Author

    @stevyan

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

Metadata

Metadata

Assignees

Labels

APLApplies to Apollolake platformP1Blocker bugs or important featuresblockedprogress blocked by something else, applies to either feature or bugbugSomething isn't working as expectedverifiedQA/Bug reporter verifies solution worked.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions