Re: Transport problem

The results:

music@devuan:~$ uname -a
Linux devuan 6.1.0-3-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.8-1 (2023-01-29)
x86_64 GNU/Linux
music@devuan:~$ grep -i preempt_voluntary /boot/config-$(uname -r)
# CONFIG_PREEMPT_VOLUNTARY is not set
music@devuan:~$ grep -i preempt_dynamic /boot/config-$(uname -r)
CONFIG_HAVE_PREEMPT_DYNAMIC=y
CONFIG_HAVE_PREEMPT_DYNAMIC_CALL=y
music@devuan:~$ grep -i preempt /etc/default/grub
music@devuan:~$

I see exactly the same on the Intel machine.
Everything software-wise is identical as far as I can tell.

I'm rather thinking now that Rosegarden may be an innocent victim of something
going right back to the machine firmware, although I don't have anything else
ALSA based as a double-check. Things like qtractor take their timing from the
audio backend.

The situation isn't fatal, as the non-preempt kernel seems to behave perfectly.


On Mon, 20 Feb 2023 05:20:50 -0500
Ted Felix <ted-Ll1PANez7xxWk0Htik3J/[email protected]> wrote:

>   Thanks, Will.  Here's a slightly newer set of steps based on what 
>I've learned this morning...
>
>----------------
>Boot into your real-time kernel.
>
>Confirm that it is a preemptible kernel.
>
>     $ grep -i config_preempt= /boot/config-$(uname -r)
>     CONFIG_PREEMPT=y
>
>If you don't see "CONFIG_PREEMPT=y" then you need to install a 
>preemptible kernel.
>
>Check for voluntary preemption.  Ideally this should be "y".  However, 
>I've had no problems with it "not set", so "y" might be the default. 
>Some more digging into the kernel code is in order here.
>
>     $ grep -i preempt_voluntary /boot/config-$(uname -r)
>     # CONFIG_PREEMPT_VOLUNTARY is not set
>
>Check for dynamic preemption.  This allows the preemption mode to be 
>specified on the kernel command line.
>
>     $ grep -i preempt_dynamic /boot/config-$(uname -r)
>     CONFIG_PREEMPT_DYNAMIC=y
>     CONFIG_HAVE_PREEMPT_DYNAMIC=y
>
>If both of those are set to "y", then we need to check the grub 
>configuration to make sure the kernel command line is asking for full 
>preemption (or nothing at all).
>
>     $ grep -i preempt /etc/default/grub
>
>You should either see nothing or "preempt=full" along with possibly 
>other options.  Anything else might mean trouble and requires a change 
>to your grub config.
>----------------
>
>Ted.
>
>On 2/20/23 4:10 AM, Will Godfrey wrote:
>> 
>> I'll try this today.
>> 
>> On Sun, 19 Feb 2023 12:19:53 -0500
>> Ted Felix <ted-Ll1PANez7xxWk0Htik3J/[email protected]> wrote:
>>   
>>>    Will, can you go through this first draft series of steps on the
>>> problematic box and let me know if it finds the issue?  Thanks.
>>>
>>> Boot into the problematic kernel.
>>>
>>> Confirm that it is a preemptible kernel.
>>>
>>>      $ grep -i config_preempt= /boot/config-$(uname -r)
>>>      CONFIG_PREEMPT=y
>>>
>>> If you don't see "CONFIG_PREEMPT=y" then you need to install a
>>> preemptible kernel.
>>>
>>> Check the grub configuration to make sure nothing is specified on the
>>> kernel command line related to preemption.
>>>
>>>      $ grep -i preempt /etc/default/grub
>>>
>>> You should either see nothing or "preempt=full" along with possibly
>>> other options.  Anything else might mean trouble and requires a change
>>> to your grub config.
>>>
>>> Check for voluntary preemption.  (Not sure how this fits into
>>> everything, but it might cause problems and need some further
>>> investigation.)
>>>
>>>      $ grep -i preempt_voluntary /boot/config-$(uname -r)
>>>      # CONFIG_PREEMPT_VOLUNTARY is not set
>>>
>>> Ted.  
>>   
>
>
>_______________________________________________
>Rosegarden-user mailing list
>Rosegarden-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org - use the link below to unsubscribe
>https://lists.sourceforge.net/lists/listinfo/rosegarden-user


-- 
Will J Godfrey {apparently now an 'elderly'}
https://willgodfrey.bandcamp.com/
http://yoshimi.github.io
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.