[LAU] Issue with the priority of the sound cards using rtirq

[Ralf Mardorf]

> Looks good to me, except for the two ohci_hcd and the nvidia threads.
I 
> don't see those when you start rtirq but they are there when you
query 
> rtirq's status. Weird. Same issue after a reboot? And this hdspm
device, 
> is that an extension card (PCI, PCIe)? If so you might want to try 
> another slot because having it to share the same IRQ as your GPU
isn't 
> ideal. And maybe you could post or pastebin your complete 
> /etc/default/rtirq file.
> 
> Best,
> 
> Jeremy

Jeremy, the bad is, that I don't have another PCIe x1 slot :(.

> In my experience, restarting the script tries to raise the priorities
> of the threads in RTIRQ_NAME_LIST, but the ones which are already
> raised aren't lowered even if you leave them out of the list.
> 
> Try rebooting the computer.
> 
> Cheers, Pablo

*reboot*

The reboot doesn't improve anything :(.

I'll build my own kernel within the next days.

Is there anything missing to work with boot option threadirqs?
Usually I use self build kernel-rt and the nv driver. Since the nv
driver is dropped, I'm using the proprietary and I have given up to edit
the nvidia drivers header or to fake the license, since both never
worked on my machine.

spinymouse at precise:~$ cat /boot/config-* | grep PREEMPT
CONFIG_TREE_PREEMPT_RCU=y
CONFIG_PREEMPT_RCU=y
CONFIG_PREEMPT_NOTIFIERS=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_COUNT=y
# CONFIG_PREEMPT_TRACER is not set
spinymouse at precise:~$ cat /boot/config-* | grep
CONFIG_IRQ_FORCED_THREADING
CONFIG_IRQ_FORCED_THREADING=y
spinymouse at precise:~$ uname -a
Linux precise 3.2.0-23-lowlatency #31-Ubuntu SMP PREEMPT Wed Apr 11
02:24:03 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

There's another issue, I've got 4GB RAM, but only 3.8GB are accessible,
resp. shown. 256MB are missing. I've got this for another install too,
while a PAE 32-bit kernel has no issue with the 4GB. No framebuffer, the
graphics has got it's own RAM.

CONFIG_PREEMPT_COUNT ???

Thanks and regards,
Ralf