Skip to content

ALSA XRUN happen when playback or capture on each platform #231

Closed

Description

@ZhendanYang

ALSA XRUN will random happen when playback or capture on APL, BYT, CNL.
This issue will be reproduce with high possibility with BUFFER_SIZE/PERIOD_SIZE=2
But audio functions are not affected by this issue.
This issue need developer to comment.
@xiulipan

Activity

  1. lgirdwood commented on Aug 17, 2018

    @lgirdwood
    Member

    @SinianYang we are missing a whole lot of details here. Logs, commit IDs, command line used in test etc.

  2. xiulipan commented on Aug 17, 2018

    @xiulipan
    Contributor

    @lgirdwood
    This is a normal case not specific to a simple commit.
    This ALSA XRUN may not be our firmware bug or driver BUG,
    Just a tracker for later dig in in ALSA.

  3. lgirdwood commented on Aug 17, 2018

    @lgirdwood
    Member

    @xiulipan I need to rule out if this is FS related as eMMC has high latency. i.e. does playing /dev/zero work ? or capturing to /dev/null ?

  4. xiulipan commented on Aug 17, 2018

    @xiulipan
    Contributor

    @lgirdwood
    This issue is here to track later findings.
    I think we did not do this test now. Will update the result here later.

  5. added
    bugSomething isn't working as expected
    APLApplies to Apollolake platform
    BYTApplies to Baytrail platform
    CNLApplies to Cannonlake platform
    on Aug 17, 2018
  6. ZhendanYang commented on Aug 21, 2018

    @ZhendanYang
    Author

    @lgirdwood
    There is no xrun when playing /dev/zero or capturing to /dev/null. But if I play /dev/zero and capture /dev/null at the same time, both overrun and underrun occur.

  7. added this to the TBD milestone on Aug 31, 2018
  8. mengdonglin commented on Sep 17, 2018

    @mengdonglin
    Collaborator

    Remove branch label br-glk because all generic fixes on glk-003 branch have been merged by master. So testing with master branch will be okay for mature platforms. glk release branch does not focus on compatibility across platforms.

  9. added
    P3Low-impact bugs or features
    and removed on Sep 28, 2018
  10. mengdonglin commented on Sep 30, 2018

    @mengdonglin
    Collaborator

    @ZhendanYang @bardliao Let's also check this issue after APL RVP or WHL RVP is set up

  11. lgirdwood commented on Oct 1, 2018

    @lgirdwood
    Member

    @ZhendanYang this is a test of the Linux scheduler, we have 2 ping pong buffers and we race to fill/empty them. Can you try mmap mode. 2 periods is rare in read()/write() io mode for this very reason.

  12. added
    won't fixThis will not be worked on atm (e.g. a bug closed for lack of user request, hardware etc)
    on Oct 1, 2018
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 platformBYTApplies to Baytrail platformCNLApplies to Cannonlake platformP3Low-impact bugs or featuresbugSomething isn't working as expectedwon't fixThis will not be worked on atm (e.g. a bug closed for lack of user request, hardware etc)

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions