We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 2882 - summary
Summary: summary
Status: RESOLVED INVALID
Alias: None
Product: SDL
Classification: Unclassified
Component: audio (show other bugs)
Version: don't know
Hardware: ARM Linux
: P2 major
Assignee: Mahendran K
QA Contact: Mahendran K
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-16 11:01 UTC by Mahendran K
Modified: 2015-02-18 03:14 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mahendran K 2015-02-16 11:01:05 UTC
Hi,

Issue : CPU load is high (more than 95% @~06:59:26) for 4-6 seconds

Test setup:
Board name = imx6 Dual Lite
audio card name = card 0: imx6qsabreaics4 [imx6q-sabreai-cs42888], device 0: HiFi cs42888-0

asound.conf:
pcm.ratehw {              
        type rate           
        slave {     
                pcm output
                rate 48000  
        }
        converter linear
} 

pcm.output {     
        type hw       
        card imx6qsabreaics4
} 

I have used aplay util to execute the test.
aplay -D ratehw -r44100 -fS16_LE -c2 /dev/urandom -v --period-time=8000 --buffer-time=24000


I have monitored the aplay CPU load for every two seconds.
test_time  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
06:59:22   678 root      20   0  3436 1188 1036 S   10  0.1  41:02.28 aplay
06:59:25   678 root      20   0  3436 1188 1036 R   10  0.1  41:02.54 aplay
06:59:27   678 root      20   0  3436 1188 1036 R   99  0.1  41:05.00 aplay
06:59:30   678 root      20   0  3436 1188 1036 R   10  0.1  41:06.99 aplay
06:59:32   678 root      20   0  3436 1188 1036 S   10  0.1  41:07.24 aplay

Seems like https://bugzilla.libsdl.org/show_bug.cgi?id=2794 bug.

Someone could give a hint on CPU load high scenario and who is causing the problem.

Regards,
Mahendran K
Comment 1 Ryan C. Gordon 2015-02-18 03:14:12 UTC
This isn't an SDL bug, this sounds like a ALSA driver or libasound bug.

(I suspect Bug #2794 is also not an SDL bug, fwiw, but I'll mention this info there.)

Resolving this bug as INVALID because there's nothing we can do if aplay triggers the problem.

--ryan.