linuxaudio.org

--0016e6469a0eb645910486c39c51

Content-Type: text/plain; charset=UTF-8
On Sun, May 16, 2010 at 7:12 PM, Fernando Lopez-Lezcano <

nando@ccrma.stanford.edu> wrote:
> > > Speaking of pulseaudio,

quoted text
> http://old.nabble.com/Re:-Fwd:-jack2-p28288652.html is

> > > a potential bad interaction between pulseaudio and jack (through

> > > /etc/security/limits.conf, potential priority escalation issue).

> ...

> Not that many "tweaks". The ability for all users to run jack with

> realtime scheduling is "added" when you install the Planet CCRMA jack

> package. That thread talks about some security problems that could arise

> with the use of realtime scheduling, that is definitely not the source

> of your problems.

I'm not so sure about that...  It might be a good idea to make sure it's not

the same problem described here:

http://old.nabble.com/Re:-Fwd:-jack2-p28296197.html
I experienced the similar lockup problems with jackd/qjackctl prior to my

change (

http://old.nabble.com/help-w--qjackctl-locks-up-X-GUI-(perhaps-caused-by-dbus-or-kernel-2.6.32.11-99.fc12.x86_64)-to28221239.html#a28224046

).

Note that these lockups DO NOT require a reboot. What's happened is that the

GUI/Xserver ends up getting locked up (via qjackctl) so if you SSH in to

your box and "killall qjackctl" you'll unlock ( Make sure to also do

"killall jackd" afterwards.).  Unfortunatelythe X server is so locked-up

that you can't Alt-F2 and login via console and kill it that way.
HOWEVER -- in testing out a new $5.00 soundcard, I also experienced

transient lock-ups again with jackd/qjackctl. The one thing that I could

point to consistently as causing problems: having the wrong settings in

'alsamixer', i.e. when one of these is set to "on" you can neither play

directly through ALSA, and jackd will hang:

 (

http://old.nabble.com/Re:-QXGEdit-(was-Re:-Suzuki-QC1-Qchord-Digital-Songcard-Guitar-)-p28541528.html

 )
> ** in alsamixer (F3-playback):
Item: "Multi Track Rate Locking" set to  [Off]
Item: "Multi Track Rate Reset" set to [Off]
Likewise, if the card is locked to the wrong sampling rate , jack may not be

able to reset it if the above settings are wrong.... To make things worse,

it seems like some of these settings are "sticky" and may require

loading/unloading the driver module or rebooting for the change to take

effect.
Similar badness may be going on w/ your soundcard, which has been a source

of longstanding problems in jack and alsa ... problems that often can be

remedied via alsamixer magic:

http://www.google.com/search?hl=en&q=SiS+SI7012+jackd&aq=f&aqi=&aql=&oq=...
-- Niels

http://nielsmayer.com
--0016e6469a0eb645910486c39c51

Content-Type: text/html; charset=UTF-8

Content-Transfer-Encoding: quoted-printable
On Sun, May 16, 2010 at 7:12 PM, Fernando Lopez-=

Lezcano <nando@ccrma.stanford.edu> wrote:
> > Speaking of pulseaudio, http://old.nabble.com/Re:-Fwd=

:-jack2-p28288652.html is

quoted text
> > a potential bad interaction between pulseaudio and jack (through<=

br>

quoted text
> > /etc/security/limits.conf, potential priority escalation issue).<=

br>...

Not that many "tweaks". The ability for all users to run ja=

ck with

realtime scheduling is "added" when you install the Planet CCRMA =

jack

package. That thread talks about some security problems that could arise

with the use of realtime scheduling, that is definitely not the source

of your problems.I'm not so sure about=

 that... =C2=A0It might be a good idea to make sure it's not the same p=

roblem described here:=C2=A0http://old.nabble.com/Re:-Fwd:-jack2-p28296197.html

I experienced the similar lockup problems with jackd/qj=

ackctl prior to my change (=C2=A0http://old.nabble.com/help-w--qjackctl-l=

ocks-up-X-GUI-(perhaps-caused-by-dbus-or-kernel-2.6.32.11-99.fc12.x86_64)-t=

o28221239.html#a28224046=C2=A0). Note that these lockups DO NOT require=

 a reboot. What's happened is that the GUI/Xserver ends up getting lock=

ed up (via qjackctl) so if you SSH in to your box and "killall qjackct=

l" you'll unlock (=C2=A0Make sure to also do "killall jackd&q=

uot; afterwards.).=C2=A0=C2=A0Unfortunatelythe X server is so locked-up tha=

t you can't Alt-F2 and login via console and kill it that way.

HOWEVER -- in testing out a new $5.00 soundcard, I also=

 experienced transient lock-ups again with jackd/qjackctl. The one thing th=

at I could point to consistently as causing problems: having the wrong sett=

ings in 'alsamixer', i.e. when one of these is set to "on&quot=

;=C2=A0you can neither play directly through ALSA, and jackd will hang:

=C2=A0(=C2=A0http://old.nabble.=

com/Re:-QXGEdit-(was-Re:-Suzuki-QC1-Qchord-Digital-Songcard-Guitar-)-p28541=

528.html=C2=A0)

** in alsamixer (F3-playback):

Item: "Multi Track Rate Locking" set to =C2=A0[Off]<=

blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0p=

x; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-l=

eft-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;=

 ">

Item: "Multi Track Rate Reset" set to [Off]=

Likewise, if the card is locked to the wrong sampling rate , jac=

k may not be able to reset it if the above settings are wrong.... To make t=

hings worse, it seems like some of these settings are "sticky" an=

d may require loading/unloading the driver module or rebooting for the chan=

ge to take effect.=C2=A0

Similar badness may be going on w/ your soundcard, whic=

h has been a source of longstanding problems in jack and alsa ... problems =

that often can be remedied via alsamixer magic:=C2=A0http://www.google.com/search?hl=3Den&amp=

;q=3DSiS+SI7012+jackd&aq=3Df&aqi=3D&aql=3D&oq=3D&gs_rfa=

i=3D=C2=A0=C2=A0

-- Nielsht=

tp://nielsmayer.com
--0016e6469a0eb645910486c39c51--