The attachment soft RLIMIT_RTTIME lower than hard limit of this bug
report has been identified as being a patch. The ubuntu-reviewers team
has been subscribed to the bug report so that they can review the patch.
In the event that this is in fact not a patch you can resolve this
situation by
@Dan Muresan (#37), may I know how to know whether I am or not using an
RT Kernel, as I do not currently know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367671
Title:
PulseAudio gets killed
Run
uname -a
on the command line and post the results. You're probably not running a
real-time kernel, because those stopped at around 2.6.33. But log the
results here anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
uname -a
Linux DavidPC 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367671
Title:
PulseAudio gets
I have the exact same problem, pulseaudio starts when I login, but
crashes after 5 minutes.
If I run it through a console, pulseaudio, I get:
W: pid.c: Stale PID file, overwriting.
#After a few minutes or sometimes even less than a minute
Killed
I have already made what was suggested in #22,
@David (#36): are you running a RT kernel though? PA tends to get killed
for many other reasons, being the stable piece of software that it is...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367671
I have the same problem on ubuntu 11.04 with 2.6.38-8-lowlatency , logs
are almost useless , no trace of crash , it just says Killed on
console after about 5 mins
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Strangely, the kernel sends SIGXCPU (due to real-time CPU usage
reaching the soft RLIMIT_RTTIME) in a write() call. The setrlimit(2) man
page says that blocking calls reset the RTTIME count.
Ok, thanks for the investigation - perhaps that write call is not
considered a blocking call, or not so
It's an interrupted syscall -- there is no result... And the for loop
only repeats on EINTR.
I take it that no support, or at least help, will be forthcoming from
the Ubuntu side?
Even though the lead PA developer seems like a smart guy who understands
real-time quite well, I'm sorry to say that
I take it that no support, or at least help, will be forthcoming from
the Ubuntu side?
Of course, I cannot speak for the entire Ubuntu community. Ubuntu relies
on volunteers such as yourself to help out with all parts of making the
distribution. For my own part, I'm following this with great
@Dan, since an improved version is in Natty it might make sense to see
if upgrading to that version of PulseAudio and/or GStreamer helps to
resolve the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, did not read comment #25 good enough, however, the comment about
upgrading GStreamer still applies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367671
Title:
PulseAudio gets killed
Thanks David. I am streaming from qmmp, and I have completely removed
gstreamer0.10-pulseaudio (and, yes, as per comment #25, I have a
backported natty pulseaudio).
I have performed the steps I planned in #28 and have obtained several
backtraces. They all look the same. Strangely, the kernel
From setrlimit(2): setrlimit allows the user to specify two limits -- a
soft one and a hard one. For RLIMIT_RTTIME, upon exceeding the soft
limit, the kernel sends a SIGXCPU every second, then a SIGKILL.
Unfortunately, pulseaudio sets the soft limit equal to the hard limit,
so no warning is
Bug #496616 is marked as a duplicate of bug #644644...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367671
Title:
PulseAudio gets killed mysteriously on RT kernels
--
ubuntu-bugs mailing list
This is hard to diagnose. I built 0.9.22 packages from natty, then
installed pulseaudio-dbg_0.9.22+stable-queue-24-g67d18-0ubuntu3_i386.deb
In ~/.pulse/daemon.conf, I enabled
log-level = debug
log-meta = yes
log-time = yes
log-backtrace = 1
then ran pulseaudio under gdb with
$ killall
pulseaudio -vvv
See also https://wiki.ubuntu.com/PulseAudio/Log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/367671
Title:
PulseAudio gets killed mysteriously on RT kernels
--
ubuntu-bugs
Doesn't the log-level = debug take care of that, Daniel?
I didn't attach a full log because minutes pass between the last printed
message and the SIGKILL.
Is there a way to see how much rttime a task has been using (with ps
or something else)?
And (less likely) is there a way to configure the
i tried bojo42's workaround while running the rt kernel found on his ppa
with lucid - no joy. the problem is indeed more scarce but still mp3
playback is not acceptable. i also compiled pulseaudio 0.9.22 from
source, still no joy. would installing the maverick package make any
difference?
@delete: I tried backported PA and rtkit, but it doesn't make a
difference for me. But as i said before PA get killed very rarely since
using the rlimit-rttime config stuff. Could you describe how often PA
gets killed on your hardware? What you can also do is to try the latest
PA config tweaking
I have edited /etc/pulse/daemon.conf but the problem still remains
With Ubuntu Lucid + Kernel 2.6.33-29-realtime
--
PulseAudio gets killed mysteriously on RT kernels
https://bugs.launchpad.net/bugs/367671
You received this bug notification because you are a member of Ubuntu
Bugs, which is
as i said before it doesn't stop completely, but at least it's really
less often. please check if you got some different settings in
~/.pulse/daemon.conf.
i am also testing maverick's pulseaudio backported to lucid and it seems
that i at least can't remember a killed PA for the last week.
--
@Bernard: good point, but on multi user machines you have to do that for
every user and pulse must not be started system wide. i like /etc
because to me such basic system administration belongs there ;)
@all: could you please report if it completely stops the killing on your
side, as i noticed
bojo42's solution seems to work. But may I suggest you copy
/etc/pulse/daemon.conf to ~/.pulse/daemon.conf and then edit that file, which
will then take precedence over the system wide file.
--
PulseAudio gets killed mysteriously on RT kernels
https://bugs.launchpad.net/bugs/367671
You
just like i said in comment #12 edit /etc/pulse/daemon.conf and change for
example
; rlimit-rttime = 100
to
rlimit-rttime = 1000
--
PulseAudio gets killed mysteriously on RT kernels
https://bugs.launchpad.net/bugs/367671
You received this bug notification because you are a member of
Bump. What is the workaround?
--
PulseAudio gets killed mysteriously on RT kernels
https://bugs.launchpad.net/bugs/367671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
So what is the bug that won't be fixed and what is the easy to perform
workaround?
--
PulseAudio gets killed mysteriously on RT kernels
https://bugs.launchpad.net/bugs/367671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This is affecting me in Lucid Lynx with RT kernel. It is very
frustrating because if I am trying to watch a film it cuts out every now
and then and I have to restart the movie player.
--
PulseAudio gets killed mysteriously on RT kernels
https://bugs.launchpad.net/bugs/367671
You received this
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
PulseAudio gets killed mysteriously on RT kernels
https://bugs.launchpad.net/bugs/367671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
i have good news: i managed to prevent the killing of PA on lucid with
an RT kernel. i did it by playing around with the
/etc/pulse/daemon.conf:
cpu-limit = no - PA won't kill itself
rlimit-rttime = 1000 - increased the value by adding a zero (x10)
- prevents the kernel from killing PA
i'm
bojo42, cpu-limit is already disabled by default in Lucid. The rttime
rlimit won't be changed; that's a pretty nasty thing to unleash on users
for an LTS, and there's a fairly easy to perform workaround.
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Won't Fix
--
PulseAudio gets
** Summary changed:
- PulseAudio gets killed mysteriously
+ PulseAudio gets killed mysteriously on RT kernels
** Package changed: linux (Ubuntu) = linux-rt (Ubuntu)
** Changed in: linux-rt (Ubuntu)
Status: Incomplete = Confirmed
--
PulseAudio gets killed mysteriously on RT kernels
yep still present on lucid. i also did packages some packages for a
2.6.33 based rt kernel (https://launchpad.net/~bojo42/+archive/rt) to
have support for rtkit ( bug #406702 ) but that doesn't help, even with
the latest rt19 patchset. rest of the system is at stock configuration.
--
PulseAudio
33 matches
Mail list logo
