Jack logging on resume from hibernate (tuxonice)

[Ng Oon-Ee]

Hi all,

I'm using 1.9.3 (jackdmp), and if I forget to jack_control stop before
hibernating on my tuxonice enabled machine, when I resume from the
hibernate the jackdbus process is consuming 100% CPU (both cores), and
the file ~/.log/jack/jackdbus.log is growing at about 20 MB per second
as best I can figure.

The file ~/.log/jack/jackdbus.log is just being endlessly filled with
these lines (the formatting issues probably come from my bash shell's
colourizing script?):-

Sat Oct 10 10:27:59 2009: ERROR: alsa_driver_xrun_recovery
Sat Oct 10 10:27:59 2009: ERROR: ALSA: channel flush for
playback failed (File descriptor in bad state)
Sat Oct 10 10:27:59 2009: ERROR: JackAudioDriver::ProcessAsync:
read error, skip cycle

Is this a known issue, or is jack just not supposed to play nice with
hibernate?

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Stéphane Letz]

Le 10 oct. 2009 à 04:49, Ng Oon-Ee a écrit :

> Hi all,
>
> I'm using 1.9.3 (jackdmp), and if I forget to jack_control stop before
> hibernating on my tuxonice enabled machine, when I resume from the
> hibernate the jackdbus process is consuming 100% CPU (both cores), and
> the file ~/.log/jack/jackdbus.log is growing at about 20 MB per second
> as best I can figure.
>
> The file ~/.log/jack/jackdbus.log is just being endlessly filled with
> these lines (the formatting issues probably come from my bash shell's
> colourizing script?):-
>
> Sat Oct 10 10:27:59 2009: ERROR: alsa_driver_xrun_recovery
> [0m
> Sat Oct 10 10:27:59 2009: ERROR: ALSA: channel flush for
> playback failed (File descriptor in bad state)
> Sat Oct 10 10:27:59 2009: ERROR:  
> JackAudioDriver::ProcessAsync:
> read error, skip cycle
>
> Is this a known issue, or is jack just not supposed to play nice with
> hibernate?
>

It is a known problem. JACK does not handle hibernate/resume. (see http://trac.jackaudio.org/ticket/129 
)

Stéphane
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Ng Oon-Ee]

On Sat, 2009-10-10 at 07:19 +0200, Stéphane Letz wrote:

> Le 10 oct. 2009 à 04:49, Ng Oon-Ee a écrit :
>
> > Hi all,
> >
> > I'm using 1.9.3 (jackdmp), and if I forget to jack_control stop before
> > hibernating on my tuxonice enabled machine, when I resume from the
> > hibernate the jackdbus process is consuming 100% CPU (both cores), and
> > the file ~/.log/jack/jackdbus.log is growing at about 20 MB per second
> > as best I can figure.
> >
> > The file ~/.log/jack/jackdbus.log is just being endlessly filled with
> > these lines (the formatting issues probably come from my bash shell's
> > colourizing script?):-
> >
> > Sat Oct 10 10:27:59 2009: ERROR: alsa_driver_xrun_recovery
> > [0m
> > Sat Oct 10 10:27:59 2009: ERROR: ALSA: channel flush for
> > playback failed (File descriptor in bad state)
> > Sat Oct 10 10:27:59 2009: ERROR:  
> > JackAudioDriver::ProcessAsync:
> > read error, skip cycle
> >
> > Is this a known issue, or is jack just not supposed to play nice with
> > hibernate?
> >
>
>
> It is a known problem. JACK does not handle hibernate/resume. (see http://trac.jackaudio.org/ticket/129 
> )
>
> Stéphane

Okay, that's pretty clear. Is there any way to change the location of
jack's logs? I don't think any other application I know off logs to the
user's home directory...

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Stéphane Letz]

Le 10 oct. 2009 à 07:43, Ng Oon-Ee a écrit :

> On Sat, 2009-10-10 at 07:19 +0200, Stéphane Letz wrote:
>> Le 10 oct. 2009 à 04:49, Ng Oon-Ee a écrit :
>>
>>> Hi all,
>>>
>>> I'm using 1.9.3 (jackdmp), and if I forget to jack_control stop  
>>> before
>>> hibernating on my tuxonice enabled machine, when I resume from the
>>> hibernate the jackdbus process is consuming 100% CPU (both cores),  
>>> and
>>> the file ~/.log/jack/jackdbus.log is growing at about 20 MB per  
>>> second
>>> as best I can figure.
>>>
>>> The file ~/.log/jack/jackdbus.log is just being endlessly filled  
>>> with
>>> these lines (the formatting issues probably come from my bash  
>>> shell's
>>> colourizing script?):-
>>>
>>> Sat Oct 10 10:27:59 2009: ERROR: alsa_driver_xrun_recovery
>>> [0m
>>> Sat Oct 10 10:27:59 2009: ERROR: ALSA: channel flush for
>>> playback failed (File descriptor in bad state)
>>> Sat Oct 10 10:27:59 2009: ERROR:
>>> JackAudioDriver::ProcessAsync:
>>> read error, skip cycle
>>>
>>> Is this a known issue, or is jack just not supposed to play nice  
>>> with
>>> hibernate?
>>>
>>
>>
>> It is a known problem. JACK does not handle hibernate/resume. (see http://trac.jackaudio.org/ticket/129
>> )
>>
>> Stéphane
>
> Okay, that's pretty clear. Is there any way to change the location of
> jack's logs? I don't think any other application I know off logs to  
> the
> user's home directory...
>

jackdbus stuff is Nedko Arnaudov work. Please ask him.

Stéphane
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Nedko Arnaudov]

Ng Oon-Ee <ngoonee@...> writes:

> Okay, that's pretty clear. Is there any way to change the location of
> jack's logs? I don't think any other application I know off logs to the
> user's home directory...

Where you want it to log? jack is user daemon, not system one, and as
suck it looks natural to log somewhere in users's home directory. jack
tries to follow XDG guidelines but XDG has no guidleline for log files
and the spirit is beleived to be followed. I.e. ~/.config/jack/ so
~/.log/jack/.

ATM the only way to change location of jack log file is by changing the
source code.

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>


_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Ng Oon-Ee]

On Sat, 2009-10-10 at 10:36 +0300, Nedko Arnaudov wrote:

> Ng Oon-Ee <ngoonee@...> writes:
>
> > Okay, that's pretty clear. Is there any way to change the location of
> > jack's logs? I don't think any other application I know off logs to the
> > user's home directory...
>
> Where you want it to log? jack is user daemon, not system one, and as
> suck it looks natural to log somewhere in users's home directory. jack
> tries to follow XDG guidelines but XDG has no guidleline for log files
> and the spirit is beleived to be followed. I.e. ~/.config/jack/ so
> ~/.log/jack/.
>
> ATM the only way to change location of jack log file is by changing the
> source code.
>

Ah okay. Since there's no XDG guidelines then anything should be fine,
except that its weird to create an entire directory structure ~/.log if
noone else ever uses it. Not a big issue though, honestly.

What about verbosity of logging, is this something which can be set? Or
is the default already at the minimum level. The current level of
logging that I see is well and good, but will result in quite a lot of
buildup over time, and I doubt any log clean-up is done by Jack itself,
in contrast with the compression which occurs to /var/log stuff.

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Nedko Arnaudov]

Ng Oon-Ee <ngoonee@...> writes:

> Ah okay. Since there's no XDG guidelines then anything should be fine,
> except that its weird to create an entire directory structure ~/.log if
> noone else ever uses it. Not a big issue though, honestly.

a2jmidid, lash and ladish use it. On my system, I also redirect output
of mpdscribble and msmtp there.

> What about verbosity of logging, is this something which can be set? Or
> is the default already at the minimum level. The current level of
> logging that I see is well and good, but will result in quite a lot of
> buildup over time, and I doubt any log clean-up is done by Jack itself,
> in contrast with the compression which occurs to /var/log stuff.

Logging is same as with jackd output to stdout/stderr. Yes, verbosity
control, line duplication shrinking and log rotation could be useful.
Unfortunately for xruns the line duplication detection will not work
because they are multiline (something that I find annoying).

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>


_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org