7 Jun
2020
7 Jun
'20
2:03 p.m.
$ grep -e "CONFIG_IRQ_FORCED_THREADING=y" -e "CONFIG_PREEMPT=y"
/boot/config-`uname -r`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash threadirqs"
sudo update-grub
reboot
Still gives me only|CONFIG_IRQ_FORCED_THREADING=y, running a rt kernel
https://wiki.linuxaudio.org/wiki/system_configuration#the_kernel \r |
7 Jun
7 Jun
2:21 p.m.
Am Sonntag, 7. Juni 2020, 12:03:26 CEST schrieb rosea.grammostola:
$ grep -e "CONFIG_IRQ_FORCED_THREADING=y" -e
"CONFIG_PREEMPT=y" /boot/config-`uname -r`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash threadirqs"
sudo update-grub
reboot
Still gives me only|CONFIG_IRQ_FORCED_THREADING=y, running a rt kernel
https://wiki.linuxaudio.org/wiki/system_configuration#the_kernel \r |
Well, the grep line checks for your current kernel configuration, and you don't show
what output it prints.
The remainer above deals with grub config only, I think it's logical that this
can't alter your kernel in any way.
I think the wiki page is pretty clear and correct about this; you don't run a RT
kernel, thus using the threadirqs kernel commandline option via grub is the best you can
do, and the steps above should have put that in place correctly. If you want
CONFIG_PREEMPT, you'll have to compile or install AND run a RT patched kernel.
2:31 p.m.
Well, the grep line checks for your current kernel
configuration, and you don't show what output it prints.
The remainer above deals with grub config only, I think it's logical that this
can't alter your kernel in any way.
I think the wiki page is pretty clear and correct about this; you don't run a RT
kernel, thus using the threadirqs kernel commandline option via grub is the best you can
do, and the steps above should have put that in place correctly. If you want
CONFIG_PREEMPT, you'll have to compile or install AND run a RT patched kernel.
Sorry for answering my own post.
I saw too late that you think you're actually running a RT kernel... can you confirm
that indeed, it doesn't look like the running kernel is a RT patched one.
CONFIG_PREEMPT would be printed by grep otherwise, I believe.
2:39 p.m.
Am Sonntag, 7. Juni 2020, 12:31:45 CEST schrieb Edgar Aichinger:
I saw too late that you think you're actually
running a RT kernel... can you confirm that indeed, it doesn't look like the running
kernel is a RT patched one. CONFIG_PREEMPT would be printed by grep otherwise, I believe.
*blush* (after reading Jeremy's answer)
I apologize for the noise ...
2:41 p.m.
On 6/7/20 12:39 PM, Edgar Aichinger wrote:
Am Sonntag, 7. Juni 2020, 12:31:45 CEST schrieb Edgar
Aichinger:
No, thanks for your help. Works now. Another Linuxaudio mystery solved ;)
I saw too late that you think you're actually
running a RT kernel... can you confirm that indeed, it doesn't look like the running
kernel is a RT patched one. CONFIG_PREEMPT would be printed by grep otherwise, I believe.
*blush* (after reading Jeremy's answer)
I apologize for the noise ...
2:28 p.m.
Hello,
On 07/06/2020 12:03, rosea.grammostola wrote:
$ grep -e "CONFIG_IRQ_FORCED_THREADING=y" -e
"CONFIG_PREEMPT=y"
/boot/config-`uname -r`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash threadirqs"
sudo update-grub
reboot
Still gives me only|CONFIG_IRQ_FORCED_THREADING=y, running a rt kernel
https://wiki.linuxaudio.org/wiki/system_configuration#the_kernel \r |
That's because CONFIG_PREEMPT should be CONFIG_PREEMPT_RT. Feel free to
change it on the wiki!
Best,
Jeremy
1585
days inactive
1585
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Edgar Aichinger -
Jeremy Jongepier -
rosea.grammostola