Hi Chris,
Yes, I do recall the debacle. But, as you say, that should have been worked
around a long time ago already.
It would be interesting to know if anyone else has noticed anything similar?
For the moment I'm content running just one of the cores.. ;)
/Robert
2009/2/6 Chris Cannam <cannam(a)all-day-breakfast.com>
On Fri, Feb 6, 2009 at 8:18 PM, Robert Jonsson
<spamatica(a)gmail.com>
wrote:
Thinking back I realize that I stumbled on this
problem on the last
rebuild
some years ago but ended up running single core
without investigating why
this was.
The symptom sounds rather like the infamous old AMD64 non-monotonic
clock resulting from clocks not being properly synchronised across
cores. But I had thought that workarounds in the kernel, JACK, or
both had made this a non-issue for most systems installed in the last
couple of years. (I am quite sure that a workaround dedicated to
solving specifically this problem was merged to JACK trunk quite a
number of releases ago, and any contemporary JACK release will have
it.)
This page:
http://www.sound-man.co.uk/linuxaudio/kernel.html refers to
the problem.
I realise I'm not offering any solution here, just pointing out that
your problem sounds the same as this one.
Chris