Re: Low timer resolution (but it shouldn't be!)

On 2025-02-05 14:52, Ted Felix wrote:
> On 1/31/25 6:18 AM, Jeronimo Pellegrini wrote:
>> So... It was already set to "auto". Then, I changed to "system timer", 
>> restarted Rosegarden, and now it shows the timer as "OK" (Thanks for 
>> pointing me to the right place in the config). So perhaps the "auto" 
>> setting is not working as expected?
> 
>   Actually, it looks like the "system timer" setting does not perform 
> the resolution checks.  Can you try the following on your system:
> 
>   $ grep ^CONFIG_HZ /boot/config-`uname -r`

Oh, I see. You mean this:

CONFIG_HZ_250=y
CONFIG_HZ=250

It seems then that Debian ships a kernel patched for real-time, that 
operates at 250Hz (?)

But shouldn't the "system timer" setting actually do check if the timer 
is good?

J.