On 10/11/2012 08:33 AM, Kevin Cosgrove wrote:
I've added this comment after having asked the exact same question at my
LAC2011 workshop. Nobody in the audience could acknowledge that changing
the inotify setting helped anything.
> 2. chrt: failed to set pid 0's policy: Operation not permitted
No it's not, unless it also outputs CONFIG_PREEMPT=y. if it doesn't than
your kernel isn't preemtible and in that case I doubt if threadirqs or
even chrt works (no expert on this).
> I altered my /boot/grub2/grub.cfg file to include
Slightly OT, but wow, that's a whole lot of kernel options ;) I only use
two or three.
> "uname -r" reports "3.5.5-2.fc17.x86_64" but I don't have
Check if your kernel is preemtible (at least, I think that might be a
probable cause) or install a kernel that is preemtible (there's no
real-time kernel available for FC17?). But like I said, I'm no expert on
the different preemption models so I could be completely wrong.
Hopefully someone with more knowledge on this matter chimes in.
Linux-audio-user mailing list