On Fri, Mar 06, 2009 at 01:01:01PM +0100, MarcO'Chapeau wrote:
> On Thu, 5 Mar 2009 09:07:10 -0500, Paul Davis <paul@email-addr-hidden>
> wrote:
> > On Thu, Mar 5, 2009 at 9:02 AM, nescivi <nescivi@email-addr-hidden> wrote:
> >
> >> Hiho,
> >>
> >> It seems that JACK (just tested with v0.116) does not survive when the
> >> computer is put to sleep, and woken up again.
> >>
> >> Is there any reason why this is so?
> >
> >
> > JACK will see this as a major system malfunction. If you are using JACK,
> do
> > not let your computer sleep, or suspend, or engage in CPU frequency
> > scaling.
> > These all appear to JACK as indistinguishable from your audio interface
> > ceasing to function in a way that leads it to quit or die. Remember that
> > JACK is watching the passing of absolute time.
>
> While cpu freq scaling *might* confuse JACK, it seems is not the case here.
> Sleep is a whole different story...
yup. i still using frequency scaling too, although it is going to fade
away, because, according to some kernel dev, you save more power with a
tickless kernel when cpu is running full speed
however my CPU is hotter then and the fan wouldnt stop, so i still
prefer frequency scaling ondemand governor.
i guess this is due to jack_get_microseconds using hpet timer default.
which shouldnt get hit by frequency changes.
-- torben Hohn http://galan.sourceforge.net -- The graphical Audio language _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@email-addr-hidden http://lists.linuxaudio.org/mailman/listinfo/linux-audio-devReceived on Sat Mar 7 00:15:02 2009
This archive was generated by hypermail 2.1.8 : Sat Mar 07 2009 - 00:15:02 EET