|
Bugzilla – Full Text Bug Listing |
| Summary: | pulseaudio logging out of control. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Bart Whiteley <bwhiteley> |
| Component: | Sound | Assignee: | Scott Reeves <sreeves> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P3 - Medium | CC: | aj, forgotten_ny8t7SHjD_, jgreen, ke, mge, sreeves, tiwai |
| Version: | RC 1 | Flags: | coolo:
SHIP_STOPPER-
|
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | pulseaudio maint:released:sle11:24435 maint:released:sle11:24612 | ||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
strace output
more strace output another strace log |
||
|
Description
Bart Whiteley
2008-12-05 16:11:47 UTC
Can you replicate this? If so, please get a strace of pulseaudio: $ strace -f -ttt -o /tmp/strace-log -s 4096 -p <pid_of_pulseaudio_daemon> and attach /tmp/strace-log to this bug please Created attachment 261532 [details]
strace output
I can't reproduce it at will, but it did happen again with 11.1 GM. I attached the strace log. This time it stopped on its own after a while.
Both times that I've experienced this it was right after resuming from s2ram. Syslog indicates that the problem started immediately after resuming, and occurred for just under 5 minutes before stopping on its own. Created attachment 262172 [details]
more strace output
It's happening again. I had to kill it this time to get it to stop.
Created attachment 262416 [details]
another strace log
Still happening. Please fix it.
This happens nearly every time I resume from s2ram. Any workarounds? I'm building a package with some upstream fixes in http://download.opensuse.org/repositories/home:/rodrigomoya:/branches:/GNOME:/Factory/ As soon as it's built, I'll poke you to test it Packages ready at http://download.opensuse.org/repositories/home:/rodrigomoya:/branches:/GNOME:/Factory/openSUSE_11.1/ please test Which of these packages are necessary for testing? the *pulse* ones, that is pulseaudio-* and libpulse* *** Bug 466923 has been marked as a duplicate of this bug. *** They do not solve the problem: Jan 19 13:56:21 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLERR from ALSA Jan 19 13:56:21 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLOUT from ALSA Jan 19 13:56:21 vanamonde pulseaudio[4414]: alsa-util.c: PCM state is RUNNING Jan 19 13:56:21 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLERR from ALSA Jan 19 13:56:21 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLOUT from ALSA Jan 19 13:56:21 vanamonde pulseaudio[4414]: alsa-util.c: PCM state is RUNNING Jan 19 13:56:21 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLERR from ALSA Jan 19 13:56:22 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLOUT from ALSA Jan 19 13:56:22 vanamonde pulseaudio[4414]: alsa-util.c: PCM state is RUNNING Jan 19 13:56:22 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLERR from ALSA Jan 19 13:56:22 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLOUT from ALSA Jan 19 13:56:22 vanamonde pulseaudio[4414]: alsa-util.c: PCM state is RUNNING Jan 19 13:56:22 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLERR from ALSA Jan 19 13:56:23 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLOUT from ALSA Jan 19 13:56:23 vanamonde pulseaudio[4414]: alsa-util.c: PCM state is RUNNING Jan 19 13:56:23 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLERR from ALSA Jan 19 13:56:23 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLOUT from ALSA Jan 19 13:56:23 vanamonde pulseaudio[4414]: alsa-util.c: PCM state is RUNNING Jan 19 13:56:23 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLERR from ALSA Jan 19 13:56:24 vanamonde pulseaudio[4414]: alsa-util.c: Got POLLOUT from ALSA Jan 19 13:56:24 vanamonde pulseaudio[4414]: alsa-util.c: PCM state is RUNNING I also can confirm that the packages from comment #8 do not fix the problem. A closer look reveals that the problem starts during suspension. It merely continues after resumption. Jan 22 09:40:14 vanamonde kernel: PM: Syncing filesystems ... done. Jan 22 09:40:24 vanamonde pulseaudio[4406]: alsa-util.c: Got POLLERR from ALSA Jan 22 09:40:24 vanamonde pulseaudio[4406]: alsa-util.c: Got POLLOUT from ALSA Jan 22 09:40:24 vanamonde pulseaudio[4406]: alsa-util.c: PCM state is SUSPENDED Jan 22 09:40:24 vanamonde kernel: Freezing user space processes ... (elapsed 0.03 seconds) done. Jan 22 09:40:24 vanamonde kernel: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. It looks like this may happen if you are playing something via alsa when you suspend. This is: http://pulseaudio.org/ticket/265 Takeshi, maybe you can decipher Lennart for us? The messages in comment #14 is pretty normal and it's no error. The poll returns with an error because it's suspended. PA spews simply too many chats. The problem is rather the endless messages even in the "RUNNING" state like in comment #12. Any reliable way to reproduce this? Of course, it might be tied with the hardware... Looking at the git commit history for that file there have been multiple improvements in handling errors or better logging if not handled. I have an upgraded pulseaudio 0.9.14 (plus some selective patches). Could you try updating to this version and then testing to see if the problem still occurs. There are 2 different 0.9.14 options available, the stock mode and a glitch_free_disabled mode (glitch_free is a pulseaudio feature we are currently shipping but that causes problems with some sound drivers). Could you try the stock mode first and if you still see the problem then try the glitch_free_disabled mode. The rpms are at stock mode - http://www.gnome.org/~sreeves/openSUSE_11.1/pulse/ GF_disabled - http://www.gnome.org/~sreeves/openSUSE_11.1/pulse_GF_disabled/ You can easily upgrade from 0.9.12 to 0.9.14 with the following steps 1. sudo zypper addrepo http://www.gnome.org/~sreeves/openSUSE_11.1/pulse/ pulse_repo 2. sudo zypper refresh -f pulse_repo 3. sudo zypper up --force-resolution -r pulse_repo pulseaudio libpulse0 You can switch between the stock and GF_disabled mode by installing the respective rpms or the only difference between the stock and GF_disabled rpms is the change of the line load-module module-hal-detect to load-module module-hal-detect tsched=0 in the /etc/pulse/default.pa and /etc/pulse/system.pa files Make sure after any changes you stop any playing sound to free the devices, and kill the pulseaudio daemon (pulseaudio –kill) so it will reload with the new settings. When you report any results make sure and specify what version and mode you were running. Thanks. I can't get sound to work with the new packages. Everything seems like it should work. For example, in the volume control, I see the various apps that should be emitting sound. However, no sound comes from the speakers. I try the new packages in both the stock and GF_disabled mode, nothing can be heard when play a mp3 file with banshee. I was able to get the test packages to work with Scott's help. Try killing pulseaudio, and then moving or removing ~/.pulse. Then restart pulseaudio. Alternatively, run 'pavucontrol' (or double-click the volume applet in the panel). Go to Output Devices. If two are listed, try switching which one is set to default. I haven't seen the logging problem since switching to the new packages. The SWAMPID for this issue is 24401. Please submit the patch and patchinfo file using this ID. (https://swamp.suse.de/webswamp/wf/24401) package has been submitted. Matthias, please update release notes for SLE(S/D). yes. The patch seems to be incomplete: On my openSUSE 11.1/x86-64 system I just noticed: > zypper patch > Loading repository data... > Reading installed packages... > Resolving package dependencies... > > Problem: nothing provides pulseaudio-lang = 0.9.14 needed by > pulseaudio-0.9.14-2.1.1.x86_64 > Solution 1: Following actions will be done: > deinstallation of pulseaudio-esound-compat-0.9.12-9.5.x86_64 > deinstallation of pulseaudio-module-zeroconf-0.9.12-9.5.x86_64 > deinstallation of pulseaudio-module-x11-0.9.12-9.5.x86_64 > deinstallation of pulseaudio-module-lirc-0.9.12-9.5.x86_64 > deinstallation of pulseaudio-module-jack-0.9.12-9.5.x86_64 > deinstallation of pulseaudio-module-bluetooth-0.9.12-9.5.x86_64 > deinstallation of pulseaudio-0.9.12-9.5.x86_64 > Solution 2: do not install patch:libpulse-browse0-915.noarch > > Choose from above solutions by number or cancel [1/2/C]: Update released for: gdbm, gdbm-debuginfo, gdbm-debugsource, gdbm-devel, libpulse-browse0, libpulse-devel, libpulse-mainloop-glib0, libpulse0, libpulsecore4, pulseaudio, pulseaudio-debuginfo, pulseaudio-debugsource, pulseaudio-esound-compat, pulseaudio-lang, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-jack, pulseaudio-module-lirc, pulseaudio-module-x11, pulseaudio-module-zeroconf, pulseaudio-utils Products: openSUSE 11.1 (debug, i586, ppc, ppc64, x86_64) The SWAMPID for this issue is 24401. Please submit the patch and patchinfo file using this ID. (https://swamp.suse.de/webswamp/wf/24401) Update was released. Update released for: libpulse-browse0, libpulse-devel, libpulse-mainloop-glib0, libpulse0, libpulse0-32bit, libpulse0-x86, libpulsecore7, pulseaudio, pulseaudio-debuginfo, pulseaudio-debugsource, pulseaudio-esound-compat, pulseaudio-lang, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-jack, pulseaudio-module-lirc, pulseaudio-module-x11, pulseaudio-module-zeroconf, pulseaudio-utils Products: SLE-DEBUGINFO 11 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11 (i386, x86_64) SLE-SDK 11 (i386, ia64, ppc64, s390x, x86_64) SLE-SERVER 11 (i386, ia64, ppc64, s390x, x86_64) Update released for: release-notes-sled Products: SLE-DESKTOP 11 (i386, x86_64) Update released for: release-notes-sled Products: SLE-DESKTOP 11 (i386, x86_64) |