http://bugzilla.opensuse.org/show_bug.cgi?id=930015 Martin Jakl changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.jakl@qbicon.cz -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 --- Comment #2 from Roberto Tolin Sommer --- jackd -v exits this message: jackdmp 1.9.10 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 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 Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user I use a Behringer FCA202 firewire audio card on a MacPro 3.1 (64bits). It worked in every Linux distribution i tested (Ubuntu Studio 13.04 to 14.10, KaOS, Ubuntu Mate 15.04, Linux Mint and Ubuntu 14.04. More information here: https://forums.opensuse.org/showthread.php/506613-after-update-Tumbleweed-I-... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 --- Comment #4 from Takashi Iwai --- BTW, if it's about the firewire device, is ALSA firewire driver loaded with the newer kernel while it's not with the older kernel? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 --- Comment #6 from Takashi Iwai --- If you run jackd as root user, it works? Also, if you use 3.19 kernel on the current system, it still works as is, right? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 --- Comment #8 from Takashi Iwai --- If you still have 3.19 kernel on your machine, just boot with it and confirm that it's really a regression by kernel. If you don't have it, at least you can install openSUSE 13.2 kernel in addition (e.g. via zypper in --oldpackage option) and confirm that the current jack works with the older kernel. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 --- Comment #10 from Takashi Iwai --- Installing another kernel in addition is really little risk. Don't need to fear too much about it. Just install a kernel package via zypper in --oldpackage kernel-XXX.rpm and you'll be able to choose the old kernel from GRUB menu. Downgrading the whole system doesn't help for analysis. We need to figure out what causes the problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 Steffen Klein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |steffen@klein-network.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 --- Comment #13 from Takashi Iwai --- OK, thanks for checking. So it's unlikely a kernel regression but other things got broken. Maybe something related with the permission or capability. Which setup do you have to make jack working as RT? You should have some ulimit.conf or whatever fiddling with the RT setup. Also, could you run jackd manually via strace, -f -ostrace.log, e.g. strace -f -ostrace.log jackd -t2000 -dfirewire -r48000 -p1024 -n5 ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 --- Comment #15 from Steffen Klein --- What you have found is the alsa firewire support by takashi Sakamoto. While I'm not sure, Idon't think it's permissions related. In my case I see the same beahviour with firewire (Edirol FA-101) as well as with ALSA, with RT or with RT disabled, as a normal user as well as root. I'm not even able to show the help info:

/usr/bin/jackd -v -P70 -dalsa -dhw:0 -r96000 -p256 -n3 -m -H -M -Xseq jackdmp 1.9.10 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 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 ^C /usr/bin/jackd -r jackdmp 1.9.10 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 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 ^C /usr/bin/jackd jackdmp 1.9.10 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 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 ^C

/usr/bin/jackd -h jackdmp 1.9.10 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 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 ^C

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(robertotolin@gmai |needinfo?(schwab@suse.com) |l.com) | --- Comment #17 from Takashi Iwai --- Hm, there seems a problem in thread handling. I could see the hang of manual "jackd --help" invocation on my machine even without firewire. This actually stuck with jack_firewire.so, according to gdb. #0 0x00007ffff6e2265d in pthread_join () from /lib64/libpthread.so.0 #1 0x00007ffff5f09362 in DebugModuleManager::~DebugModuleManager() () from /usr/lib64/libffado.so.2 #2 0x00007ffff5efab66 in ?? () from /usr/lib64/libffado.so.2 #3 0x00007ffff7def78a in _dl_close_worker () from /lib64/ld-linux-x86-64.so.2 #4 0x00007ffff7df026c in _dl_close () from /lib64/ld-linux-x86-64.so.2 #5 0x00007ffff7dea8b4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2 #6 0x00007ffff67f856d in _dlerror_run () from /lib64/libdl.so.2 #7 0x00007ffff67f809f in dlclose () from /lib64/libdl.so.2 #8 0x00007ffff7b9ab20 in ?? () from /usr/lib64/libjackserver.so.0 #9 0x00007ffff7b9bba0 in ?? () from /usr/lib64/libjackserver.so.0 #10 0x00007ffff7b9ff80 in jackctl_server_create () from /usr/lib64/libjackserver.so.0 #11 0x0000000000402b5a in ?? () #12 0x00007ffff70578c5 in __libc_start_main () from /lib64/libc.so.6 #13 0x0000000000403607 in ?? () And, more interestingly, the problem could be seen on openSUSE 13.2 just by upgrading from glibc-2.19 to glibc-2.21 while keeping the rest as is. So, this looks more like a regression (or some ill side-effect) of newer glibc. Andreas, does this ring a bell? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=930015 --- Comment #32 from Takashi Iwai --- As the upstream patch seems working, I submitted the fixed package now via SRID 311128. -- You are receiving this mail because: You are on the CC list for the bug.