22 Nov
2014
22 Nov
'14
1:53 p.m.
On Sat, 22 Nov 2014 13:37:20 +0100
Frank Neumann <beachnase(a)web.de> wrote:
Hi Will,
[..]
Thank you both for such a quick response. This solved the problem completely :)
Xruns completely disappeared and qjackctl reading dropped from over 40% to less
than 10%
P.S.
I was running some quite complex yoshi/zyn patches - they can be quite
demanding!
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Eventually I found the cause. Going from linux
kernel 3.2 to 3.16 :(
This, apparently, does very aggressive CPU frequency scaling. Drop back to 3.2
and all is sweetness and light again.
The question is whether there is a reasonably straightforward way to stop this
behaviour. Doing the usual searches doesn't seem to turn up anything useful.
Any help gratefully appreciated.
I would add that I've double checked that the bios is set for 'performance'.
Just a shot in the dark here, but did you try using the "cpufreq-set" tool (in
Debian-based distributions: in package "cpufrequtils) to set the CPU governor?
(As root), do:
# cpufreq-set -g performance
On an older machine, I had Xrun issues sometimes, and this tool helped overcome
it at that time. However, I have never seen the CPU load spikes you mention.
Greetings,
Frank