Bug 102877

Summary: pulseaudio killed by SIGKILL
Product: PulseAudio Reporter: Carlo Caione <carlo>
Component: coreAssignee: pulseaudio-bugs
Status: RESOLVED DUPLICATE QA Contact: pulseaudio-bugs
Severity: normal    
Priority: medium CC: lennart
Version: unspecified   
Hardware: Other   
OS: All   
i915 platform: i915 features:
Attachments: pulsaudio log when killed with SIGKILL

Description Carlo Caione 2017-09-19 14:52:10 UTC
Created attachment 134338 [details]
pulsaudio log when killed with SIGKILL

Hardware is a Cherrytrail Z8350 with a RT5651 codec with a v4.13.1+ kernel. Pulseaudio is 11.0-30-g2693.

The UCM file for the codec is taken from https://github.com/plbossart/UCM/tree/master/bytcr-rt5651 and it is working fine when testing directly with:

speaker-test -D hw:1,0 -c 2 -t wav

The problem is that pulsaudio is being killed by SIGKILL when starting. The only way I can avoid it from being killed is to start it with:

pulseaudio --realtime=false

In attachment the log when it is being killed.

Strace-ing it is not an option since when trying with `strace -f` the problem is not reproducible anymore. And a simple strace is not that useful:

open("/dev/snd/controlC1", O_RDWR|O_CLOEXEC) = 22 
fcntl(22, F_SETFD, FD_CLOEXEC)          = 0 
ioctl(22, SNDRV_CTL_IOCTL_PVERSION or USBDEVFS_CONTROL, 0x7ffe752db234) = 0
ioctl(22, SNDRV_CTL_IOCTL_PCM_PREFER_SUBDEVICE, 0x7ffe752db29c) = 0
open("/dev/snd/pcmC1D0p", O_RDWR|O_NONBLOCK|O_CLOEXEC <unfinished ...>
+++ killed by SIGKILL +++
Comment 1 Arun Raghavan 2017-09-19 15:30:18 UTC
That kill is almost certainly from the kernel, because PA exceeded RT prio. If this is CherryTrail, might be related to the HDMI LPE issue in https://bugs.freedesktop.org/show_bug.cgi?id=100488
Comment 2 Arun Raghavan 2017-10-18 08:55:10 UTC
Marking as duplicate unless we have information to the contrary.

*** 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.