Ralf I have noticed the same thing with one of the things I tried to prioritize. I am wondering if it is a timing issue. That is, if rtirq is being run too soon before the irq driver is fully operating. It was obvious to me because the PID for mine is so much higher than any of the others. Try a sudo /etc/init.d/rtirq restart after boot and things have settled. Does that make a difference?
With sys v init everything is run in order, that is not the case with systemd which parallel processes things. It may be that some small delay in the script would fix things. Mine: after boot: 517 FF 90 - 130 0.1 S irq/17-snd_ice1 512 FF 85 - 125 0.0 S irq/19-snd_ens1 47 FF 50 - 90 0.0 S irq/9-acpi 77 FF 50 - 90 0.0 S irq/20-ehci_hcd 78 FF 50 - 90 0.0 S irq/23-ehci_hcd 79 FF 50 - 90 0.0 S irq/41-xhci_hcd 81 FF 50 - 90 0.0 S irq/12-i8042 82 FF 50 - 90 0.0 S irq/1-i8042 83 FF 50 - 90 0.0 S irq/8-rtc0 153 FF 50 - 90 0.0 S irq/16-pata_jmi 160 FF 50 - 90 0.0 S irq/43-ahci 408 FF 50 - 90 0.0 S irq/44-mei_me 446 FF 50 - 90 0.0 S irq/45-i915 1315 FF 50 - 90 0.0 S irq/42-eth0 Mine after rtirq restart: 517 FF 90 - 130 0.1 S irq/17-snd_ice1 512 FF 85 - 125 0.0 S irq/19-snd_ens1 1315 FF 80 - 120 0.0 S irq/42-eth0 47 FF 50 - 90 0.0 S irq/9-acpi In your case the PID is sooner than the two cards that did get grabbed, but it may still take some time to get fully initialized. I use RTIRQ_NAME_LIST="snd_ice1712 snd eth0" because: a) I am too lazy to switch the two sound cards in their physical slots and the ensoniq interferes with the ice if higher. b) I want to play with AoIP as I have time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482347 Title: [rtirq-init] Broken RTPRIO order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1482347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
