Re: [Jack-Devel] Fwd: [jack2] jackd provides too verbose output (#19)

On Sat, 22 Sep 2012 21:09:24 +0200
Stéphane Letz <[hidden]> wrote:

> Any solution for that?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=827748
> 
> Stéphane
> 
> Début du message réexpédié :
> 
> > De : Fryderyk Dziarmagowski <[hidden]>
> > Date : 22 septembre 2012 20:44:20 HAEC
> > À : jackaudio/jack2 <[hidden]>
> > Objet : [jack2] jackd provides too verbose output (#19)
> > Répondre à : jackaudio/jack2
> > <[hidden]>
> > 
> > jackd provides much too verbose by default (despite --verbose not
> > used or --silent passed as comand line parameter), example:
> > 
> > % jackd -P70 -p128 -t5000 -s -dfirewire -dhw:0 -r48000 -p64 -n3
> > -I127 -O127 jackdmp 1.9.9.4
> > Copyright 2001-2005 Paul Davis and others.
> > Copyright 2004-2012 Grame.
> > jackdmp comes with ABSOLUTELY NO WARRANTY
> > This is free software, and you are welcome to redistribute it
> > under certain conditions; see the file COPYING for details
> > no message buffer overruns
> > no message buffer overruns
> > no message buffer overruns
> > JACK server starting in realtime mode with priority 70
> > Jack: JackPosixThread::StartImp : create non RT thread
> > Jack: JackPosixThread::ThreadHandler : start
> > Jack: JackDriver::Open capture_driver_name = 
> > Jack: JackDriver::Open playback_driver_name = 
> > Jack: Check protocol client = 8 server = 8
> > Jack: JackEngine::ClientInternalOpen: name = system
> > Jack: JackEngine::AllocateRefNum ref = 0
> > Jack: JackPosixSemaphore::Allocate name =
> > jack_sem.1000_default_system val = 0 Jack:
> > JackEngine::NotifyAddClient: name = system Jack:
> > JackGraphManager::SetBufferSize size = 64 Jack:
> > JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 Jack:
> > JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
> > Jack: JackDriver::SetupDriverSync driver sem in flush mode Jack:
> > JackSocketServerChannel::Open Jack: JackServerSocket::Bind :
> > addr.sun_path /dev/shm/jack_default_1000_0 Jack:
> > JackSocketServerChannel::BuildPoolTable size = 1 Jack:
> > JackEngine::Open Jack: JackClientSocket::Connect :
> > addr.sun_path /dev/shm/jack_default_1000_0 Jack:
> > JackEngine::ClientInternalOpen: name = freewheel Jack:
> > JackEngine::AllocateRefNum ref = 1 Jack:
> > JackPosixSemaphore::Allocate name = jack_sem.1000_default_freewheel
> > val = 0 Jack: JackEngine::NotifyAddClient: name = freewheel Jack:
> > JackDriver::ClientNotify ref = 1 driver = system name = freewheel
> > notify = 0 using jack2 1.9.9 7c6d111
> > 
> > I found this bug describing same problem.
> > 
> > —
> > Reply to this email directly or view it on GitHub.
> > 
> > 
> 

We found a similar/same problem in archlinux with jack2 being extremely
verbose.  We think the problem comes from gcc 4.7.1 optimization.  At
the moment we build jack2 with -O0 which seems to have fixed the
problem.

-- 

   Joakim

1348344632.20247_0.ltw:2,a <20120922221019.4e18c842 at tor dot valhalla dot alchemy dot lu>