[LAU] RME HDSP 9652 priority issue

[Michael Jarosch]

Sorry for the delay.

Am Mittwoch, den 30.11.2016, 21:17 +0100 schrieb Ralf Mardorf:

> Len wrote:
> "If you think it is a problem with systemd, try
> sudo /etc/init.d/rtirq restart"

Works:
:/home/mitsch# /etc/init.d/rtirq status

  PID CLS RTPRIO  NI PRI %CPU STAT COMMAND	
  321 FF      90   - 130  0.0 S    irq/19-snd_hda_	
  149 FF      85   - 125  0.0 S    irq/17-ehci_hcd	
  171 FF      85   - 125  0.0 S    irq/16-ohci_hcd	
  165 FF      84   - 124  0.0 S    irq/19-ehci_hcd	
  172 FF      84   - 124  0.0 S    irq/16-ohci_hcd	
  173 FF      84   - 124  0.0 S    irq/18-ohci_hcd	
  175 FF      83   - 123  0.0 S    irq/18-ohci_hcd	
  176 FF      82   - 122  0.0 S    irq/18-ohci_hcd	
   77 FF      80   - 120  0.0 S    irq/1-i8042	
   76 FF      79   - 119  0.0 S    irq/12-i8042	
   55 FF      50   -  90  0.0 S    irq/9-acpi	
   78 FF      50   -  90  0.0 S    irq/8-rtc0	
  133 FF      50   -  90  0.0 S    irq/6-floppy	
  139 FF      50   -  90  0.0 S    irq/22-firewire	
  140 FF      50   -  90  0.0 S    irq/14-pata_ati	
  141 FF      50   -  90  0.0 S    irq/15-pata_ati	
  150 FF      50   -  90  0.4 S    irq/22-ahci[000	
  328 FF      50   -  90  0.0 S    irq/18-radeon	
  336 FF      50   -  90  2.7 S    irq/21-snd_hdsp	
  810 FF      50   -  90  0.0 S    irq/25-eth0	
    3 TS       -   0  19  0.1 S    ksoftirqd/0	
   22 TS       -   0  19  0.1 S    ksoftirqd/1	
   31 TS       -   0  19  0.1 S    ksoftirqd/2	
   40 TS       -   0  19  0.1 S    ksoftirqd/3

As one can see: The HDSP is recognised, but the card with highest
priority is the hda-intel, followed by USB- and Firewire-Devices. The
hdsp is relatively low on priority (50).

>   systemctl status rtirq

Also works (if you autocomplete rtirq ro rtirq.service), but it doesn't
print that nice output of /etc/init.d/rtirq status:

:/home/mitsch# systemctl status rtirq.service 
● rtirq.service - LSB: Realtime IRQ thread tunning.
   Loaded: loaded (/etc/init.d/rtirq; generated; vendor preset:
enabled)
   Active: active (exited) since Sat 2016-12-03 00:50:51 CET; 15min ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/rtirq.service


When using journalctl one can see that snd_hdsp isn't set - only the
first ten devices listed in /etc/init.d/rtirq status (which differ from
priority 50) are.

That's strange. I remember that using "snd" as an item in
RTIRQ_NAME_LIST of /etc/default/rtirq usually made every sound-device
at least priority 80.

I should try to set the priority of snd_hdsp manually - how do I do
this, again?

> It's idiotic to mix systemd with init scripts.

Yes, maybe. But you'll remember how heatened the discussion about
systemd was and you know, they had to handle the situation. The mix-
systemd-with-sysv-init-sollution works for vast majority of scripts
which hasn't been ported, yet. So, it's a good compromise and maybe
when the next debian stable is ready, all sysv-init-related stuff is
already history... No need to get angry, they've done a good job in my
opinion.

Greets!
Mitsch