Bug 106645

Summary: [krez ninja 1103] Audio is not working; pulseaudio consumes 100% of a single CPU core
Product: PulseAudio Reporter: sklochkov <sklochkov.mail>
Component: alsaAssignee: AL42925 <alade1518>
Status: RESOLVED DUPLICATE QA Contact: pulseaudio-bugs
Severity: major    
Priority: medium CC: alade1518, lennart
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Pulseaudio log

Description sklochkov 2018-05-25 02:26:00 UTC
Created attachment 139750 [details]
Pulseaudio log

On a krez ninja 1103 laptop audio is not working; pulseaudio consumes 100% of a single CPU core. Pulseaudio log atached.

According to perf, most CPU is consumed at __memset_erms.

Below is the GDB stacktrace of pulseaudio.

# gdb -p 1009 -batch -eval-command="thread apply all bt"
[New LWP 1028]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x56318e574a30) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
205 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
#0 0x00007fe2ab063339 in _IO_str_init_static_internal (sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
#1 0x00007fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", maxlen=<optimized out>, flags=1, slen=<optimized out>, format=0x7fe2ac698e8d "%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
#2 0x00007fe2ac6601ca in pa_vsnprintf () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#3 0x00007fe2ac660366 in pa_snprintf () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#4 0x00007fe2ac66bda8 in pa_log_levelv_meta () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#5 0x00007fe2ac66b655 in pa_log_level_meta () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#6 0x00007fe2a52b36ae in ?? () from /usr/lib/pulse-11.1/modules/libalsa-util.so
#7 0x00007fe2ac68c2a8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#8 0x00007fe2abb756db in start_thread (arg=0x7fe2a7458700) at pthread_create.c:463
#9 0x00007fe2ab0f488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
#0 0x00007fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x56318e574a30) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1 do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at sem_waitcommon.c:111
#2 0x00007fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, abstime=0x0) at sem_waitcommon.c:181
#3 0x00007fe2ac68c502 in pa_semaphore_wait () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#4 0x00007fe2ac8cca24 in pa_asyncmsgq_send () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
#5 0x00007fe2a6841119 in ?? () from /usr/lib/pulse-11.1/modules/libprotocol-native.so
#6 0x00007fe2ac675ee2 in pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#7 0x00007fe2a6844695 in ?? () from /usr/lib/pulse-11.1/modules/libprotocol-native.so
#8 0x00007fe2ac678bef in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#9 0x00007fe2ac67b6ab in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#10 0x00007fe2ac67ba49 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#11 0x00007fe2ac67c2cf in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#12 0x00007fe2ac40e0d8 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#13 0x00007fe2ac40e4ae in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#14 0x00007fe2ac40e530 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#15 0x000056318d445b82 in main ()

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic.
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: **** List of CAPTURE Hardware Devices ****
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: user 1009 F...m pulseaudio
 /dev/snd/controlC0: user 1009 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
   Mixer name : ''
   Components : ''
   Controls : 15
   Simple ctrls : 0
Card0.Amixer.values:

CurrentDesktop: LXDE
Date: Thu May 24 16:04:13 2018
InstallationDate: Installed on 2018-05-22 (1 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8.17
dmi.board.asset.tag: Default string
dmi.board.name: TY1103B
dmi.board.vendor: KREZ
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 30
dmi.chassis.vendor: KREZ
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd08/18/2017:svnKREZ:pnTY1103B:pvrDefaultstring:rvnKREZ:rnTY1103B:rvr1.0:cvnKREZ:ct30:cvrDefaultstring:
dmi.product.family: EMI30P3S6M12L25B310T4C00W1H2G0G3A1C2P0C0D0C1801M0N1X1WOS
dmi.product.name: TY1103B
dmi.product.version: Default string
dmi.sys.vendor: KREZ

Relevant ubuntu launchpad ticket: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773167
Comment 1 Daniel van Vugt 2018-05-25 02:49:35 UTC
It looks like this is what's filling the log (and probably consuming the CPU):

( 48.319| 0.000) I: [alsa-sink-HdmiLpeAudio] alsa-sink.c: Starting playback.
( 48.319| 0.000) D: [alsa-sink-HdmiLpeAudio] alsa-util.c: Got POLLERR from ALSA
( 48.319| 0.000) D: [alsa-sink-HdmiLpeAudio] alsa-util.c: Got POLLOUT from ALSA
( 48.319| 0.000) D: [alsa-sink-HdmiLpeAudio] alsa-util.c: PCM state is XRUN
Comment 2 sklochkov 2018-05-25 11:14:16 UTC
Excuse me, but why was the "hardware" field switched to powerpc? The problem happened on x86_64.
Comment 3 Tanu Kaskinen 2018-05-25 11:45:09 UTC

*** This bug has been marked as a duplicate of bug 100488 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.