public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Udo van den Heuvel <udovdh@xs4all.nl>
To: RT <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.33.1-rt11 BUG: sleeping function called from invalid context at kernel/rtmutex.c:684
Date: Tue, 06 Apr 2010 16:01:48 +0200	[thread overview]
Message-ID: <4BBB3ECC.107@xs4all.nl> (raw)
In-Reply-To: <20100406134318.GR4234@uudg.org>

On 2010-04-06 15:43, Luis Claudio R. Goncalves wrote:
> | After applying, compilign and rebooting the BUG-messages appear to be
> | gone (after a quick test).
> | Thanks!
> | 
> | Only issue remaining is this message:
> | 
> | Apr  6 15:25:02 nawdew rtkit-daemon[3484]: Failed to make ourselves RT:
> | Operation not permitted
> | (repeated a number of times)
> | 
> | Is this also -rt related?
> 
> here's the description of rtkit:
> 
> 	Summary     : Realtime Policy and Watchdog Daemon
(...)

> One famous user of rtkit is pulseaudio. In fact, it is the only user of
> rtkit on my system. And the message reflects that either your pulseaudio
> config is forbidding usage of RT prios or the user running pulseaudio has
> no rights to use higher priorities (check with ulimit)

At the time rtkit-daemon is/was running as the gdm user since no user
was logged in using the gui.
So perhaps I can fix this in /etc/security/limits.conf?
Hmm.
Putting gdm user in pulse-rt group does fix the rtkit-daemon messages
but not the pulseaudio error.

I will seek help for this elsewhere as it is not so on topic here.

Thanks for the patch!

Udo

  reply	other threads:[~2010-04-06 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04  9:14 2.6.33.1-rt11 BUG: sleeping function called from invalid context at kernel/rtmutex.c:684 Udo van den Heuvel
2010-04-04  9:17 ` Udo van den Heuvel
2010-04-06  8:07 ` Thomas Gleixner
2010-04-06 13:34   ` Udo van den Heuvel
2010-04-06 13:43     ` Luis Claudio R. Goncalves
2010-04-06 14:01       ` Udo van den Heuvel [this message]
2010-04-06 14:39     ` Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BBB3ECC.107@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --cc=linux-rt-users@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox