sunrat wrote: ↑Mon Mar 13, 2023 9:40 pmI get "Sanity Check Failed!" with the backports 6.0 kernel on Debian. Will reboot to Liquorix and check that.
Back in the latest Liquorix 6.1.18-1-liquorix-amd64 now.
Sanity check passes "Sanity Check OK!" when using performance governor, but fails with ondemand governor. CPU governor seems to be the critical factor.
Interesting... My system fails Ardour's test even with performance governor:
Code: Select all
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
performance
performance
performance
performance
performance
performance
performance
performance
$ /opt/Ardour-7.3.0/bin/sanityCheck -a
Sanity Check Failed!
sunrat wrote: ↑Mon Mar 13, 2023 9:40 pmRebooted to the Debian kernel 6.0.0-0.deb11.6-amd64 and found the same result. Sanity check OK with performance governor and fails with powersave (this kernel doesn't have ondemand governor).
We must remember the sanity check is just a simple parameter check afaik; it doesn't check actual performance.
I was curious about that. If that is really the case, I need to do some more tests to see if there is any loss in performance with my new kernels.
sunrat wrote: ↑Mon Mar 13, 2023 9:40 pmThere's a simple GUI utility available in Debian to switch governors - cpupower-gui.
And it is well worth checking setup with rtcqs - https://codeberg.org/rtcqs/rtcqs . It would tell you to set performance governor.
I've just ran it:
Code: Select all
$ rtcqs
rtcqs - version 0.5.3
Root User
=========
[ OK ] Not running as root.
Audio Group
===========
[ OK ] User finotti is in the audio group.
CPU Frequency Scaling
=====================
[ OK ] The scaling governor of all CPU's is set at performance.
Kernel Configuration
====================
[ OK ] Valid kernel configuration found.
High Resolution Timers
======================
[ OK ] High resolution timers are enabled.
Tickless Kernel
===============
[ OK ] System is using a tickless kernel.
Preempt RT
==========
[ WARNING ] Kernel 6.2.0-5.slh.1-aptosid-amd64 without 'threadirqs' parameter or real-time capabilities found. See also https://wiki.linuxaudio.org/wiki/system_configuration#do_i_really_need_a_real-time_kernel
Spectre/Meltdown Mitigations
============================
[ WARNING ] Kernel with Spectre/Meltdown mitigations found. This could have a negative impact on the performance of your system. See also https://wiki.linuxaudio.org/wiki/system_configuration#disabling_spectre_and_meltdown_mitigations
RT Priorities
=============
[ WARNING ] Could not assign a 80 rtprio SCHED_FIFO value due to the following error: [Errno 1] Operation not permitted. Set up limits.conf. See also https://wiki.linuxaudio.org/wiki/system_configuration#limitsconfaudioconf
Swappiness
==========
[ OK ] Swappiness is set at 10.
Filesystems
===========
[ OK ] The following mounts can be used for audio purposes: /, /gnu/store, /media/music, /media/sd_data, /media/data3, /media/media, /media/data2, /media/sg4tb
[ WARNING ] The following mounts should be avoided for audio purposes: /run/user/1000/doc. See also https://wiki.linuxaudio.org/wiki/system_configuration#filesystems
IRQs
=====
[ OK ] USB port ehci_hcd:usb2 with IRQ 16 does not share its IRQ.
USB port ehci_hcd:usb1 with IRQ 23 does not share its IRQ.
USB port xhci_hcd with IRQ 29 does not share its IRQ.
Power Management
================
[ WARNING ] Power management can't be controlled from user space, the device node /dev/cpu_dma_latency can't be accessed by your user. This prohibits DAW's like Ardour and Reaper to set CPU DMA latency which could help prevent xruns. For enabling access see https://wiki.linuxaudio.org/wiki/system_configuration#quality_of_service_interface
I will investigate the results later. Thanks for pointing it out. (I had seen it before, but forgotten...)
sunrat wrote: ↑Mon Mar 13, 2023 9:40 pmI see @finotti also has an interesting thread going at https://discourse.ardour.org/t/system-d ... /108331/13
Yes, I meant to link it above, but it seems that I forgot.