Bug 50518 - Pulseaudio Daemon crashing.
Summary: Pulseaudio Daemon crashing.
Status: RESOLVED DUPLICATE of bug 47830
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: daemon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-30 18:53 UTC by neltnerb@mit.edu
Modified: 2012-05-30 20:30 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
log file (27.09 KB, application/octet-stream)
2012-05-30 19:37 UTC, neltnerb@mit.edu
Details
log file of crashing (26.78 KB, application/octet-stream)
2012-05-30 19:40 UTC, neltnerb@mit.edu
Details

Description neltnerb@mit.edu 2012-05-30 18:53:14 UTC
I am running Mint 13 Debian Edition with the MATE desktop environment.

My pulseaudio version provided by Debian Testing is 2.0-3.

My alsa version provided by Debian Testing is 1.0.23+dfsg-4.

My audio device from lspci is
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
with which I am using the SPDIF outputs.

I previously had this working tolerably with Ubuntu 11.10, but recently switched to Mint 13 Debian Edition for unrelated reasons.

As to my problem, I can get everything to work while pulseaudio is running, but it crashes without any obvious cause periodically.

I ran pulseaudio manually from a terminal in verbose mode and it said this when it crashed:

---
I: [pulseaudio] protocol-native.c: Requested tlength=200.00 ms, minreq=10.00 ms
I: [pulseaudio] protocol-native.c: Final latency 210.00 ms = 180.00 ms + 2*10.00 ms + 10.00 ms
I: [pulseaudio] client.c: Freed 19 "ALSA plug-in [clementine]"
I: [pulseaudio] protocol-native.c: Connection died.
I: [pulseaudio] sink-input.c: Freeing input 5 "ALSA Playback"
I: [pulseaudio] client.c: Created 20 "Native client (UNIX socket client)"
I: [pulseaudio] protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: [pulseaudio] sink-input.c: Trying to change sample rate
I: [alsa-sink] alsa-sink.c: Device suspended...
I: [pulseaudio] alsa-sink.c: Updating rate for device front:0, new rate is 44100
I: [pulseaudio] sink.c: Changed sampling rate successfully
I: [pulseaudio] sink-input.c: Rate changed to 44100 Hz
I: [alsa-sink] alsa-sink.c: Trying resume...
I: [alsa-sink] alsa-util.c: Trying to disable ALSA period wakeups, using timers only
Killed
---

There is far more before it crashed, including some alsa-sink.c: Underrun! statements. I can send it all to a text file if that would help.

Does anyone have any ideas as to why this might be crashing? I am using it with Clementine if that means anything. But this looks to me to be a lower level problem than that.
Comment 1 neltnerb@mit.edu 2012-05-30 19:14:29 UTC
I have also determined that after pulseaudio crashed here I needed to stop pulseaudio, force-reload the alsa modules several times, and then restart pulseaudio in order to make it functional again.
Comment 2 neltnerb@mit.edu 2012-05-30 19:37:38 UTC
Created attachment 62306 [details]
log file

This time, audio simply stopped playing and the SPDIF output stopped working. I went into the sound control and attempted muting and unmuting all of the outputs and this did not change anything.

I subsequently attempted to restart the pulseaudio control, and unmuted all of the proper outputs, but there is still no sound. My receiver does not click to indicate that it is receiving inputs.
Comment 3 neltnerb@mit.edu 2012-05-30 19:40:40 UTC
Created attachment 62308 [details]
log file of crashing

After killing pulseaudio and force-reloading the ALSA driver modules, it appeared to reconnect to the receiver properly, but as soon as I attempted to play anything it immediately crashed. I have attached the log file of this crash here. The only message to the terminal after the log is "Killed".
Comment 4 Tanu Kaskinen 2012-05-30 20:30:19 UTC
Given the similar symptoms (getting killed while trying to resume an alsa device), I believe the root cause is the same as with bug 47830, so I'm resolving this as duplicate.

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


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.