On Wed, 2014-05-07 at 14:57 +0200, Kaj Ailomaa wrote: > > On Wed, May 7, 2014, at 08:11 AM, Ralf Mardorf wrote: > > > > On Wed, 2014-05-07 at 06:44 +0100, Alex Armani wrote: > > > alex@armani:~$ grep vmlinuz /boot/grub/grub.cfg > > > linux /boot/vmlinuz-3.13.0-24-lowlatency > > > root=UUID=1039a024-0461-406e-844c-8fa86f89eb46 ro quiet splash > > > $vt_handoff > > > linux /boot/vmlinuz-3.13.0-24-lowlatency > > > root=UUID=1039a024-0461-406e-844c-8fa86f89eb46 ro quiet splash > > > $vt_handoff > > > linux /boot/vmlinuz-3.13.0-24-lowlatency > > > root=UUID=1039a024-0461-406e-844c-8fa86f89eb46 ro quiet splash > > > $vt_handoff > > > linux /boot/vmlinuz-3.13.0-24-lowlatency > > > root=UUID=1039a024-0461-406e-844c-8fa86f89eb46 ro recovery nomodeset > > > > JFTR, isn't there the need to add threadirqs anymore, when booting a > > "full" preempted kernel? > > > > The threadirqs option has always been hardcoded into linux-lowlatency. > Previously with a patch. Now, there is a config option for it, which is > enabled. I forget the name of the config - check your config in /boot/, > and grep for THREAD.
Or else I will check the status of rtirq after adding a new lowlatency kernel manually to my grub.cfg, without the option "threadirqs" ;D. I guess I understand your message ;), there's no need to add "threadirqs", when using a lowlatency kernel from the official *buntu repositories :). I marked the subject line with "OT", however my apologise. -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
