From: Carlos s. <csa...@gm...> - 2012-05-08 15:47:21
|
Hi rakarrakers. I keep on testing Musix on various portable and not so powerful devices. I get this error (on a txt file using "2>some-error-file.txt") sometimes when enabling the FX processing on a UMPC[1]: " rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas McClendon - Arnout Engelen Try 'rakarrack --help' for command-line options. cannot use real-time scheduling (FIFO at priority -4) [for thread -1267381392, from thread -1267381392] (22: Invalid argument) " I would like to know why and when this happens to see if I can stabilized the environment. I'm using it as an FX processor and live-looping system instead of a pedalboard. Thanks in advance, as always. [1] Ultra Mobile PC with this specs for the purpose CPU type: Intel Atom (Silverthorne) CPU speed: Z520, 1.33Ghz -- Carlos sanchiavedraz * Musix GNU+Linux http://www.musix.es |
From: Ryan B. <ry...@gm...> - 2012-05-09 01:35:53
|
Probably a first question to ask is, Does it happen for every preset? For example, I think the first preset "Rodent Airlines" uses a lot of CPU (40% on my 3Ghz Pentium 4). So, try some different presets, for example, start rakarrack with a preset that you know is low cpu. This might help to narrow it down. Another question, does it always happen on this machine? Do you have jack started first, or do you start rakarrack without jack and let rakarrack start jack? Does this happen with other jack programs, or only rakarrack? Perhaps answering those questions will bring us closer. Of course, using gdb may help to narrow the problem to something specific. Ryan On 05/08/2012 08:46 AM, Carlos sanchiavedraz wrote: > Hi rakarrakers. > > I keep on testing Musix on various portable and not so powerful > devices. I get this error (on a txt file using > "2>some-error-file.txt") sometimes when enabling the FX processing on > a UMPC[1]: > > " > rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas > McClendon - Arnout Engelen > Try 'rakarrack --help' for command-line options. > cannot use real-time scheduling (FIFO at priority -4) [for thread > -1267381392, from thread -1267381392] (22: Invalid argument) > " > I would like to know why and when this happens to see if I can > stabilized the environment. I'm using it as an FX processor and > live-looping system instead of a pedalboard. > > Thanks in advance, as always. > > > [1] Ultra Mobile PC with this specs for the purpose > > CPU type: Intel Atom (Silverthorne) > CPU speed: Z520, 1.33Ghz > > -- > Carlos sanchiavedraz > * Musix GNU+Linux > http://www.musix.es > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > Rakarrack-users mailing list > Rak...@li... > https://lists.sourceforge.net/lists/listinfo/rakarrack-users > |
From: Carlos s. <csa...@gm...> - 2012-05-09 09:53:03
|
You're totally right, Ryan. I wrote my email in a hurry and forget about writing some necessary context info that is mandatory (I should remembered it by now for my own experience ;) ). This is kind of a regular workflow when I run Rakarrack on that device: * I switch on the device and Musix starts (I'm running now Musix beta 3 (Debian Squeeze) with some 3.0 and 3.2 RT kernels, but I think this is not relevant for the matter) * I or some script runs Qjackctl that starts Jack with RT configuration - usually with my external Edirol UA25 audio interface that performs great * I or some script runs Rakarrack(RK) - it's configured optimed for the UMPC capabilities: low values for Upsampling and Harm. Quality, and Recognize Note Optimization set to Guitar - my scripts run now RK adding "2>some-error-file.txt" to log info for debugging purposes - given my latelly crashes I run RK with processing unabled at the start and then I use presets that the device can stand. * Then, maybe I or some script runs additional "light" programs (Freewheeling most of the times) that don't overload CPU and leave room for RK processing So now: * Does it happen for every preset? No. As you mention, I know the limitations of the device and, on this kind of devices, I don't use presets as Rodent Airlines or others CPU intense. I try to select/filter the stock presets that it can handles with RT. I have some presets of my own and several presets used as pedalboards (10 discrete pedals to switch on and off) as well. * Does it always happen on this machine? No. It doesn't happen all the time and it doesn't crash always with the same preset. i.e. sometimes I enable processing and the Harmonizer or Sustainer and it keeps on, and others don't and it shuts down itself. * Does this happen with other jack programs, or only rakarrack? Just yesterday I run Freewheeling with "2>some-error-file.txt" and, surprise!, the error was: *" cannot use real-time scheduling (FIFO at priority -4) [for thread -1261438096, from thread -1261438096] (22: Invalid argument) zombified - calling shutdown handler "* So it seems that is a general and localized cause, but now I doubt if the problem is related to jack configuration or something else, but the thing is that I've jammed with no problems for some time with the same jack configuration for RT with the external audio interface (relevant parameters: RT enabled, Tolerant mode enabled, 256 frames, 2 periods) Please tell me if you need anything else. Thanks. 2012/5/9 Ryan Billing <ry...@gm...> > ** > Probably a first question to ask is, > Does it happen for every preset? > > For example, I think the first preset "Rodent Airlines" uses a lot of CPU > (40% on my 3Ghz Pentium 4). So, try some different presets, for example, > start rakarrack with a preset that you know is low cpu. This might help to > narrow it down. > > Another question, does it always happen on this machine? Do you have jack > started first, or do you start rakarrack without jack and let rakarrack > start jack? > > > Does this happen with other jack programs, or only rakarrack? > > Perhaps answering those questions will bring us closer. Of course, using > gdb may help to narrow the problem to something specific. > > Ryan > > > > On 05/08/2012 08:46 AM, Carlos sanchiavedraz wrote: > > Hi rakarrakers. > > I keep on testing Musix on various portable and not so powerful devices. I > get this error (on a txt file using "2>some-error-file.txt") sometimes when > enabling the FX processing on a UMPC[1]: > > " > rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas > McClendon - Arnout Engelen > Try 'rakarrack --help' for command-line options. > cannot use real-time scheduling (FIFO at priority -4) [for thread > -1267381392, from thread -1267381392] (22: Invalid argument) > " > I would like to know why and when this happens to see if I can stabilized > the environment. I'm using it as an FX processor and live-looping system > instead of a pedalboard. > > Thanks in advance, as always. > > > [1] Ultra Mobile PC with this specs for the purpose > > CPU type: Intel Atom (Silverthorne) > CPU speed: Z520, 1.33Ghz > > -- > Carlos sanchiavedraz > * Musix GNU+Linux > http://www.musix.es > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > Rakarrack-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/rakarrack-users > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rakarrack-users mailing list > Rak...@li... > https://lists.sourceforge.net/lists/listinfo/rakarrack-users > > -- Carlos sanchiavedraz * Musix GNU+Linux http://www.musix.es |
From: Josep A. <ho...@te...> - 2012-05-09 11:29:41
|
Hi > cannot use real-time scheduling (FIFO at priority -4) [for thread > -1261438096, from thread -1261438096] (22: Invalid argument) > zombified - calling shutdown handler First .. what version of rakarrack are you using? older version of rakarrack put the real time schedule for some threads but not the newest IIRC. anyway .... check your Realtime prioritys in /etc/security/limits.conf ( newest versions of jackd put the correct values on /etc/security/limits.d/audio.conf ( Google for the correct values) Josep |
From: Josep A. <ho...@te...> - 2012-05-09 11:33:02
|
Hi Also be sure that the user that launch rakarrack is on the "audio" group Josep |
From: Ryan B. <ry...@gm...> - 2012-05-10 05:39:47
|
Josep, It looks like he uses the last release: " rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas McClendon - Arnout Engelen Try 'rakarrack --help' for command-line options. cannot use real-time scheduling (FIFO at priority -4) [for thread -1267381392, from thread -1267381392] (22: Invalid argument) " Carlos, maybe try building current development from git and see if you still have the problem. I don't remember what version where this changed, but Josep knows, so I will let him say. On 05/09/2012 04:29 AM, Josep Andreu wrote: > Hi > > >> cannot use real-time scheduling (FIFO at priority -4) [for thread >> -1261438096, from thread -1261438096] (22: Invalid argument) >> zombified - calling shutdown handler >> > > First .. what version of rakarrack are you using? older version of rakarrack put the real time schedule for some threads but not the newest IIRC. > anyway .... check your Realtime prioritys in /etc/security/limits.conf ( newest versions of jackd put the correct values on /etc/security/limits.d/audio.conf ( Google for the correct values) > > Josep > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rakarrack-users mailing list > Rak...@li... > https://lists.sourceforge.net/lists/listinfo/rakarrack-users > > |
From: Ryan B. <ry...@gm...> - 2012-05-15 04:20:30
|
Thanks for the information. I use Debian Squeeze, and I have no problems on the stock kernel 2.6.32-5-686. I have not attempted to compile a kernel with the RT patch (are you using kernel w/ RT patch?). This makes me think there is something specific about hardware we need to identify. "Last, but not least, I'm afraid I can't compile the newest version of Rakarrack, at least not by now." In git I added the dependency for FFTW3. Let me know if the configure script fails to inform you of the need to install FFTW3 dev package (it seemed good on my system here). You should not be able to finish "./configure" without a failure ... unless maybe you did not run "./autogen.sh". I have not yet updated the README, so it does not mention this dependency (it reminds me I need to do that). If using git repo, make sure you do this ./autogen.sh ./configure make #make install Let us know if you have the same problem once you get the most recent code to compile. I am sorry at the moment I can't think of anything that causes this, so we need to keep the emails going and maybe I will think of something. Thanks again for reporting the problem, and thanks for maintaining Musix... it is a good distribution :) Ryan Hi again. I'm using Musix as my distribution. We at Musix try to configure everything needed for the user to have kernel RT and Jack with an appropriate config, at least. I remember that some years ago there it was a little more complicated things to do to achieve all that, but the latest versions of Debian and the kernel are great and it's easier now. The Musix version we're debugging is based on Debian Squeeze. So now, answering to the things you asked before: * /etc/security/limits.conf (attached) It seems this file is correct and I think it is untouched from the Debian original. * /etc/security/limits.d/audio.conf (attached) This is generated by Jack, according with what says on its content, so it should be right. It says that you can run "dpkg-reconfigure -p high jackd", I should check if this was already done; I suppose there is another command option for this. BTW, there is a file called "audio.conf.disabled" that is exactly the same as this "audio.conf" and is in the same directory. * user in "audio" group This is done by default in Musix, so my user is in this group. Last, but not least, I'm afraid I can't compile the newest version of Rakarrack, at least not by now. Please, let me know if there's something else I can add. Thanks 2012/5/10 Ryan Billing <ry...@gm... <mailto:ry...@gm...>> Josep, It looks like he uses the last release: " rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas McClendon - Arnout Engelen Try 'rakarrack --help' for command-line options. cannot use real-time scheduling (FIFO at priority -4) [for thread -1267381392, from thread -1267381392] (22: Invalid argument) " Carlos, maybe try building current development from git and see if you still have the problem. I don't remember what version where this changed, but Josep knows, so I will let him say. On 05/09/2012 04:29 AM, Josep Andreu wrote: > Hi > > >> cannot use real-time scheduling (FIFO at priority -4) [for thread >> -1261438096, from thread -1261438096] (22: Invalid argument) >> zombified - calling shutdown handler >> > > First .. what version of rakarrack are you using? older version of rakarrack put the real time schedule for some threads but not the newest IIRC. > anyway .... check your Realtime prioritys in /etc/security/limits.conf ( newest versions of jackd put the correct values on /etc/security/limits.d/audio.conf ( Google for the correct values) > > Josep > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rakarrack-users mailing list > Rak...@li... <mailto:Rak...@li...> > https://lists.sourceforge.net/lists/listinfo/rakarrack-users > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Rakarrack-users mailing list Rak...@li... <mailto:Rak...@li...> https://lists.sourceforge.net/lists/listinfo/rakarrack-users -- Carlos sanchiavedraz * Musix GNU+Linux http://www.musix.es On 05/14/2012 07:27 AM, Carlos sanchiavedraz wrote: > d o |
From: Carlos s. <csa...@gm...> - 2012-05-15 07:34:09
|
I'm glad you like Musix, I'm CCing to the list, they would love to know that because we love Rakarrack ;). Without the whole team and users Musix would not be possible. Some weeks ago I was using kernel RT 3.0.x and lately linux-image-3.2.12-gnu-rt22 compiled by the team. I should have some time to test some older kernels to see if problems are because of the 3.x branch. Maybe I'll have some time to compile Rakarrack, it seems you don't have to "fight" with errors and dependencies. We'll see. 2012/5/15 Ryan Billing <ry...@gm...> > ** > Thanks for the information. I use Debian Squeeze, and I have no problems > on the stock kernel 2.6.32-5-686. I have not attempted to compile a kernel > with the RT patch (are you using kernel w/ RT patch?). This makes me think > there is something specific about hardware we need to identify. > > > "Last, but not least, I'm afraid I can't compile the newest version of > Rakarrack, at least not by now." > > In git I added the dependency for FFTW3. Let me know if the configure > script fails to inform you of the need to install FFTW3 dev package (it > seemed good on my system here). You should not be able to finish > "./configure" without a failure ... unless maybe you did not run > "./autogen.sh". I have not yet updated the README, so it does not mention > this dependency (it reminds me I need to do that). > > If using git repo, make sure you do this > ./autogen.sh > ./configure > make > #make install > > Let us know if you have the same problem once you get the most recent code > to compile. I am sorry at the moment I can't think of anything that causes > this, so we need to keep the emails going and maybe I will think of > something. > > Thanks again for reporting the problem, and thanks for maintaining > Musix... it is a good distribution :) > > Ryan > > > > > > > Hi again. > > I'm using Musix as my distribution. We at Musix try to configure > everything needed for the user to have kernel RT and Jack with an > appropriate config, at least. I remember that some years ago there it was a > little more complicated things to do to achieve all that, but the latest > versions of Debian and the kernel are great and it's easier now. > > The Musix version we're debugging is based on Debian Squeeze. > > So now, answering to the things you asked before: > > * /etc/security/limits.conf (attached) > It seems this file is correct and I think it is untouched from the Debian > original. > > * /etc/security/limits.d/audio.conf (attached) > This is generated by Jack, according with what says on its content, so it > should be right. It says that you can run "dpkg-reconfigure -p high jackd", > I should check if this was already done; I suppose there is another command > option for this. > BTW, there is a file called "audio.conf.disabled" that is exactly the same > as this "audio.conf" and is in the same directory. > > * user in "audio" group > This is done by default in Musix, so my user is in this group. > > Last, but not least, I'm afraid I can't compile the newest version of > Rakarrack, at least not by now. > > Please, let me know if there's something else I can add. > > Thanks > > > 2012/5/10 Ryan Billing <ry...@gm...> > >> Josep, >> It looks like he uses the last release: >> >> " >> rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas >> McClendon - Arnout Engelen >> Try 'rakarrack --help' for command-line options. >> cannot use real-time scheduling (FIFO at priority -4) [for thread >> -1267381392, from thread -1267381392] (22: Invalid argument) >> " >> >> Carlos, maybe try building current development from git and see if you >> still have the problem. I don't remember what version where this >> changed, but Josep knows, so I will let him say. >> >> >> >> >> On 05/09/2012 04:29 AM, Josep Andreu wrote: >> > Hi >> > >> > >> >> cannot use real-time scheduling (FIFO at priority -4) [for thread >> >> -1261438096, from thread -1261438096] (22: Invalid argument) >> >> zombified - calling shutdown handler >> >> >> > >> > First .. what version of rakarrack are you using? older version of >> rakarrack put the real time schedule for some threads but not the newest >> IIRC. >> > anyway .... check your Realtime prioritys in /etc/security/limits.conf >> ( newest versions of jackd put the correct values on >> /etc/security/limits.d/audio.conf ( Google for the correct values) >> > >> > Josep >> > >> > >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Live Security Virtual Conference >> > Exclusive live event will cover all the ways today's security and >> > threat landscape has changed and how IT managers can respond. >> Discussions >> > will include endpoint security, mobile security and the latest in >> malware >> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> > _______________________________________________ >> > Rakarrack-users mailing list >> > Rak...@li... >> > https://lists.sourceforge.net/lists/listinfo/rakarrack-users >> > >> > >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Rakarrack-users mailing list >> Rak...@li... >> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >> > > > > -- > Carlos sanchiavedraz > * Musix GNU+Linux > http://www.musix.es > > > > On 05/14/2012 07:27 AM, Carlos sanchiavedraz wrote: > > d o > > > -- Carlos sanchiavedraz * Musix GNU+Linux http://www.musix.es |
From: Ryan B. <ry...@gm...> - 2012-05-15 14:59:51
|
Good to know the kernels you are using. Is there a way I can get a copy of the kernel you are using, linux-image-3.2.12-gnu-rt22? This might help me reproduce the error (source or pre-build binary ok). Thanks On 05/15/2012 12:33 AM, Carlos sanchiavedraz wrote: > I'm glad you like Musix, I'm CCing to the list, they would love to > know that because we love Rakarrack ;). Without the whole team and > users Musix would not be possible. > > Some weeks ago I was using kernel RT 3.0.x and lately > linux-image-3.2.12-gnu-rt22 compiled by the team. I should have some > time to test some older kernels to see if problems are because of the > 3.x branch. > > Maybe I'll have some time to compile Rakarrack, it seems you don't > have to "fight" with errors and dependencies. We'll see. > > > 2012/5/15 Ryan Billing <ry...@gm... <mailto:ry...@gm...>> > > Thanks for the information. I use Debian Squeeze, and I have no > problems on the stock kernel 2.6.32-5-686. I have not attempted > to compile a kernel with the RT patch (are you using kernel w/ RT > patch?). This makes me think there is something specific about > hardware we need to identify. > > > "Last, but not least, I'm afraid I can't compile the newest > version of Rakarrack, at least not by now." > > In git I added the dependency for FFTW3. Let me know if the > configure script fails to inform you of the need to install FFTW3 > dev package (it seemed good on my system here). You should not be > able to finish "./configure" without a failure ... unless maybe > you did not run "./autogen.sh". I have not yet updated the > README, so it does not mention this dependency (it reminds me I > need to do that). > > If using git repo, make sure you do this > ./autogen.sh > ./configure > make > #make install > > Let us know if you have the same problem once you get the most > recent code to compile. I am sorry at the moment I can't think of > anything that causes this, so we need to keep the emails going and > maybe I will think of something. > > Thanks again for reporting the problem, and thanks for maintaining > Musix... it is a good distribution :) > > Ryan > > > > > > > Hi again. > > I'm using Musix as my distribution. We at Musix try to configure > everything needed for the user to have kernel RT and Jack with an > appropriate config, at least. I remember that some years ago there > it was a little more complicated things to do to achieve all that, > but the latest versions of Debian and the kernel are great and > it's easier now. > > The Musix version we're debugging is based on Debian Squeeze. > > So now, answering to the things you asked before: > > * /etc/security/limits.conf (attached) > It seems this file is correct and I think it is untouched from the > Debian original. > > * /etc/security/limits.d/audio.conf (attached) > This is generated by Jack, according with what says on its > content, so it should be right. It says that you can run > "dpkg-reconfigure -p high jackd", I should check if this was > already done; I suppose there is another command option for this. > BTW, there is a file called "audio.conf.disabled" that is exactly > the same as this "audio.conf" and is in the same directory. > > * user in "audio" group > This is done by default in Musix, so my user is in this group. > > Last, but not least, I'm afraid I can't compile the newest version > of Rakarrack, at least not by now. > > Please, let me know if there's something else I can add. > > Thanks > > > 2012/5/10 Ryan Billing <ry...@gm... <mailto:ry...@gm...>> > > Josep, > It looks like he uses the last release: > > " > rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - > Douglas > McClendon - Arnout Engelen > Try 'rakarrack --help' for command-line options. > cannot use real-time scheduling (FIFO at priority -4) [for thread > -1267381392, from thread -1267381392] (22: Invalid argument) > " > > Carlos, maybe try building current development from git and > see if you > still have the problem. I don't remember what version where this > changed, but Josep knows, so I will let him say. > > > > > On 05/09/2012 04:29 AM, Josep Andreu wrote: > > Hi > > > > > >> cannot use real-time scheduling (FIFO at priority -4) [for > thread > >> -1261438096, from thread -1261438096] (22: Invalid argument) > >> zombified - calling shutdown handler > >> > > > > First .. what version of rakarrack are you using? older > version of rakarrack put the real time schedule for some > threads but not the newest IIRC. > > anyway .... check your Realtime prioritys in > /etc/security/limits.conf ( newest versions of jackd put the > correct values on /etc/security/limits.d/audio.conf ( Google > for the correct values) > > > > Josep > > > > > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's > security and > > threat landscape has changed and how IT managers can > respond. Discussions > > will include endpoint security, mobile security and the > latest in malware > > threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Rakarrack-users mailing list > > Rak...@li... > <mailto:Rak...@li...> > > https://lists.sourceforge.net/lists/listinfo/rakarrack-users > > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest > in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rakarrack-users mailing list > Rak...@li... > <mailto:Rak...@li...> > https://lists.sourceforge.net/lists/listinfo/rakarrack-users > > > > > -- > Carlos sanchiavedraz > * Musix GNU+Linux > http://www.musix.es > > > > On 05/14/2012 07:27 AM, Carlos sanchiavedraz wrote: >> d o > > > > > -- > Carlos sanchiavedraz > * Musix GNU+Linux > http://www.musix.es |
From: Carlos s. <csa...@gm...> - 2012-06-04 13:20:14
|
Hi again, I can't send any of two kernels due to mail file size restrictions, maybe I could send them later by other means. In advance I tell you that kernels are: * linux-image-3.2.12-gnu-rt22-686-musix-3_3.2.12-gnu-rt22-686-musix-3-10.00.Custom_i386.deb * and another one prepared for Wheezy: linux-image-3.2.12-gnu-rt22-prueba_3.2.12-gnu-rt22-prueba-10.00.Custom_i386.deb I did some test with 2.6.x and it seems Rakarrack doesn't have this problems I mentioned. I'm not 100% sure but it seems the problems is any kernel 3.x, maybe. Anyway, with other programs, like Freewheeling, I still get (what it seems to be) same error: " cannot use real-time scheduling (FIFO at priority -4) [for thread -1260520592, from thread -1260520592] (22: Invalid argument) " ... and I can also see this on the info ( >1 parameter) output: " MIDI: HiPri Thread 99 MIDI: Can't set realtime thread, will use nonRT! " 2012/5/15 Ryan Billing <ry...@gm...>: > Good to know the kernels you are using. Is there a way I can get a copy of > the kernel you are using, linux-image-3.2.12-gnu-rt22? This might help me > reproduce the error (source or pre-build binary ok). > > Thanks > > > On 05/15/2012 12:33 AM, Carlos sanchiavedraz wrote: > > I'm glad you like Musix, I'm CCing to the list, they would love to know that > because we love Rakarrack ;). Without the whole team and users Musix would > not be possible. > > Some weeks ago I was using kernel RT 3.0.x and lately > linux-image-3.2.12-gnu-rt22 compiled by the team. I should have some time to > test some older kernels to see if problems are because of the 3.x branch. > > Maybe I'll have some time to compile Rakarrack, it seems you don't have to > "fight" with errors and dependencies. We'll see. > > > 2012/5/15 Ryan Billing <ry...@gm...> >> >> Thanks for the information. I use Debian Squeeze, and I have no problems >> on the stock kernel 2.6.32-5-686. I have not attempted to compile a kernel >> with the RT patch (are you using kernel w/ RT patch?). This makes me think >> there is something specific about hardware we need to identify. >> >> >> "Last, but not least, I'm afraid I can't compile the newest version of >> Rakarrack, at least not by now." >> >> In git I added the dependency for FFTW3. Let me know if the configure >> script fails to inform you of the need to install FFTW3 dev package (it >> seemed good on my system here). You should not be able to finish >> "./configure" without a failure ... unless maybe you did not run >> "./autogen.sh". I have not yet updated the README, so it does not mention >> this dependency (it reminds me I need to do that). >> >> If using git repo, make sure you do this >> ./autogen.sh >> ./configure >> make >> #make install >> >> Let us know if you have the same problem once you get the most recent code >> to compile. I am sorry at the moment I can't think of anything that causes >> this, so we need to keep the emails going and maybe I will think of >> something. >> >> Thanks again for reporting the problem, and thanks for maintaining >> Musix... it is a good distribution :) >> >> Ryan >> >> >> >> >> >> >> Hi again. >> >> I'm using Musix as my distribution. We at Musix try to configure >> everything needed for the user to have kernel RT and Jack with an >> appropriate config, at least. I remember that some years ago there it was a >> little more complicated things to do to achieve all that, but the latest >> versions of Debian and the kernel are great and it's easier now. >> >> The Musix version we're debugging is based on Debian Squeeze. >> >> So now, answering to the things you asked before: >> >> * /etc/security/limits.conf (attached) >> It seems this file is correct and I think it is untouched from the Debian >> original. >> >> * /etc/security/limits.d/audio.conf (attached) >> This is generated by Jack, according with what says on its content, so it >> should be right. It says that you can run "dpkg-reconfigure -p high jackd", >> I should check if this was already done; I suppose there is another command >> option for this. >> BTW, there is a file called "audio.conf.disabled" that is exactly the same >> as this "audio.conf" and is in the same directory. >> >> * user in "audio" group >> This is done by default in Musix, so my user is in this group. >> >> Last, but not least, I'm afraid I can't compile the newest version of >> Rakarrack, at least not by now. >> >> Please, let me know if there's something else I can add. >> >> Thanks >> >> >> 2012/5/10 Ryan Billing <ry...@gm...> >>> >>> Josep, >>> It looks like he uses the last release: >>> >>> " >>> rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas >>> McClendon - Arnout Engelen >>> Try 'rakarrack --help' for command-line options. >>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>> -1267381392, from thread -1267381392] (22: Invalid argument) >>> " >>> >>> Carlos, maybe try building current development from git and see if you >>> still have the problem. I don't remember what version where this >>> changed, but Josep knows, so I will let him say. >>> >>> >>> >>> >>> On 05/09/2012 04:29 AM, Josep Andreu wrote: >>> > Hi >>> > >>> > >>> >> cannot use real-time scheduling (FIFO at priority -4) [for thread >>> >> -1261438096, from thread -1261438096] (22: Invalid argument) >>> >> zombified - calling shutdown handler >>> >> >>> > >>> > First .. what version of rakarrack are you using? older version of >>> > rakarrack put the real time schedule for some threads but not the newest >>> > IIRC. >>> > anyway .... check your Realtime prioritys in /etc/security/limits.conf >>> > ( newest versions of jackd put the correct values on >>> > /etc/security/limits.d/audio.conf ( Google for the correct values) >>> > >>> > Josep >>> > >>> > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ >>> > Live Security Virtual Conference >>> > Exclusive live event will cover all the ways today's security and >>> > threat landscape has changed and how IT managers can respond. >>> > Discussions >>> > will include endpoint security, mobile security and the latest in >>> > malware >>> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> > _______________________________________________ >>> > Rakarrack-users mailing list >>> > Rak...@li... >>> > https://lists.sourceforge.net/lists/listinfo/rakarrack-users >>> > >>> > >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Rakarrack-users mailing list >>> Rak...@li... >>> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >> >> >> >> >> -- >> Carlos sanchiavedraz >> * Musix GNU+Linux >> http://www.musix.es >> >> >> >> On 05/14/2012 07:27 AM, Carlos sanchiavedraz wrote: >> >> d o >> >> > > > > -- > Carlos sanchiavedraz > * Musix GNU+Linux > http://www.musix.es > > -- Carlos sanchiavedraz * Musix GNU+Linux http://www.musix.es |
From: Ryan B. <ry...@gm...> - 2012-06-04 16:59:41
|
Maybe you have already tried this: http://trac.jackaudio.org/wiki/Cgroups If not, let me know if it helps. The section for "for packagers" might be the most relevant. Also, what version of JACK are you using? Maybe a certain version of jack is needed to work with newer kernels? Certainly it seems the kernel is not allowing the user to request RT privilege. Have you tried to run JACK and rakarrack as root? Does that work. Finding out if it runs as root will let us know whether we are having a problem with user configuration (in which case the link above might help), or whether there are deeper problems. Just some more ideas. Thanks, Ryan On 06/04/2012 06:19 AM, Carlos sanchiavedraz wrote: > Hi again, > > I can't send any of two kernels due to mail file size restrictions, > maybe I could send them later by other means. > In advance I tell you that kernels are: > * linux-image-3.2.12-gnu-rt22-686-musix-3_3.2.12-gnu-rt22-686-musix-3-10.00.Custom_i386.deb > * and another one prepared for Wheezy: > linux-image-3.2.12-gnu-rt22-prueba_3.2.12-gnu-rt22-prueba-10.00.Custom_i386.deb > > I did some test with 2.6.x and it seems Rakarrack doesn't have this > problems I mentioned. I'm not 100% sure but it seems the problems is > any kernel 3.x, maybe. Anyway, with other programs, like Freewheeling, > I still get (what it seems to be) same error: > " > cannot use real-time scheduling (FIFO at priority -4) [for thread > -1260520592, from thread -1260520592] (22: Invalid argument) > " > ... and I can also see this on the info (>1 parameter) output: > " > MIDI: HiPri Thread 99 > MIDI: Can't set realtime thread, will use nonRT! > " > > > 2012/5/15 Ryan Billing<ry...@gm...>: > >> Good to know the kernels you are using. Is there a way I can get a copy of >> the kernel you are using, linux-image-3.2.12-gnu-rt22? This might help me >> reproduce the error (source or pre-build binary ok). >> >> Thanks >> >> >> On 05/15/2012 12:33 AM, Carlos sanchiavedraz wrote: >> >> I'm glad you like Musix, I'm CCing to the list, they would love to know that >> because we love Rakarrack ;). Without the whole team and users Musix would >> not be possible. >> >> Some weeks ago I was using kernel RT 3.0.x and lately >> linux-image-3.2.12-gnu-rt22 compiled by the team. I should have some time to >> test some older kernels to see if problems are because of the 3.x branch. >> >> Maybe I'll have some time to compile Rakarrack, it seems you don't have to >> "fight" with errors and dependencies. We'll see. >> >> >> 2012/5/15 Ryan Billing<ry...@gm...> >> >>> Thanks for the information. I use Debian Squeeze, and I have no problems >>> on the stock kernel 2.6.32-5-686. I have not attempted to compile a kernel >>> with the RT patch (are you using kernel w/ RT patch?). This makes me think >>> there is something specific about hardware we need to identify. >>> >>> >>> "Last, but not least, I'm afraid I can't compile the newest version of >>> Rakarrack, at least not by now." >>> >>> In git I added the dependency for FFTW3. Let me know if the configure >>> script fails to inform you of the need to install FFTW3 dev package (it >>> seemed good on my system here). You should not be able to finish >>> "./configure" without a failure ... unless maybe you did not run >>> "./autogen.sh". I have not yet updated the README, so it does not mention >>> this dependency (it reminds me I need to do that). >>> >>> If using git repo, make sure you do this >>> ./autogen.sh >>> ./configure >>> make >>> #make install >>> >>> Let us know if you have the same problem once you get the most recent code >>> to compile. I am sorry at the moment I can't think of anything that causes >>> this, so we need to keep the emails going and maybe I will think of >>> something. >>> >>> Thanks again for reporting the problem, and thanks for maintaining >>> Musix... it is a good distribution :) >>> >>> Ryan >>> >>> >>> >>> >>> >>> >>> Hi again. >>> >>> I'm using Musix as my distribution. We at Musix try to configure >>> everything needed for the user to have kernel RT and Jack with an >>> appropriate config, at least. I remember that some years ago there it was a >>> little more complicated things to do to achieve all that, but the latest >>> versions of Debian and the kernel are great and it's easier now. >>> >>> The Musix version we're debugging is based on Debian Squeeze. >>> >>> So now, answering to the things you asked before: >>> >>> * /etc/security/limits.conf (attached) >>> It seems this file is correct and I think it is untouched from the Debian >>> original. >>> >>> * /etc/security/limits.d/audio.conf (attached) >>> This is generated by Jack, according with what says on its content, so it >>> should be right. It says that you can run "dpkg-reconfigure -p high jackd", >>> I should check if this was already done; I suppose there is another command >>> option for this. >>> BTW, there is a file called "audio.conf.disabled" that is exactly the same >>> as this "audio.conf" and is in the same directory. >>> >>> * user in "audio" group >>> This is done by default in Musix, so my user is in this group. >>> >>> Last, but not least, I'm afraid I can't compile the newest version of >>> Rakarrack, at least not by now. >>> >>> Please, let me know if there's something else I can add. >>> >>> Thanks >>> >>> >>> 2012/5/10 Ryan Billing<ry...@gm...> >>> >>>> Josep, >>>> It looks like he uses the last release: >>>> >>>> " >>>> rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas >>>> McClendon - Arnout Engelen >>>> Try 'rakarrack --help' for command-line options. >>>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>>> -1267381392, from thread -1267381392] (22: Invalid argument) >>>> " >>>> >>>> Carlos, maybe try building current development from git and see if you >>>> still have the problem. I don't remember what version where this >>>> changed, but Josep knows, so I will let him say. >>>> >>>> >>>> >>>> >>>> On 05/09/2012 04:29 AM, Josep Andreu wrote: >>>> >>>>> Hi >>>>> >>>>> >>>>> >>>>>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>>>>> -1261438096, from thread -1261438096] (22: Invalid argument) >>>>>> zombified - calling shutdown handler >>>>>> >>>>>> >>>>> First .. what version of rakarrack are you using? older version of >>>>> rakarrack put the real time schedule for some threads but not the newest >>>>> IIRC. >>>>> anyway .... check your Realtime prioritys in /etc/security/limits.conf >>>>> ( newest versions of jackd put the correct values on >>>>> /etc/security/limits.d/audio.conf ( Google for the correct values) >>>>> >>>>> Josep >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Live Security Virtual Conference >>>>> Exclusive live event will cover all the ways today's security and >>>>> threat landscape has changed and how IT managers can respond. >>>>> Discussions >>>>> will include endpoint security, mobile security and the latest in >>>>> malware >>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>> _______________________________________________ >>>>> Rakarrack-users mailing list >>>>> Rak...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >>>>> >>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Live Security Virtual Conference >>>> Exclusive live event will cover all the ways today's security and >>>> threat landscape has changed and how IT managers can respond. Discussions >>>> will include endpoint security, mobile security and the latest in malware >>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>> _______________________________________________ >>>> Rakarrack-users mailing list >>>> Rak...@li... >>>> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >>>> >>> >>> >>> >>> -- >>> Carlos sanchiavedraz >>> * Musix GNU+Linux >>> http://www.musix.es >>> >>> >>> >>> On 05/14/2012 07:27 AM, Carlos sanchiavedraz wrote: >>> >>> d o >>> >>> >>> >> >> >> -- >> Carlos sanchiavedraz >> * Musix GNU+Linux >> http://www.musix.es >> >> >> > > > |
From: Carlos s. <csa...@gm...> - 2012-06-05 13:40:30
|
Hi, 1) cgroups: I didn't check that about cgroups, I'll check 2) $jackd --version jackd version 0.118.0 3) sudo: I'll check that also Thanks so much for your kind help. I'll reply with more information. 2012/6/4 Ryan Billing <ry...@gm...>: > Maybe you have already tried this: > http://trac.jackaudio.org/wiki/Cgroups > > If not, let me know if it helps. The section for "for packagers" might be > the most relevant. > > Also, what version of JACK are you using? Maybe a certain version of jack > is needed to work with newer kernels? Certainly it seems the kernel is not > allowing the user to request RT privilege. > > Have you tried to run JACK and rakarrack as root? Does that work. Finding > out if it runs as root will let us know whether we are having a problem with > user configuration (in which case the link above might help), or whether > there are deeper problems. > > Just some more ideas. > Thanks, > Ryan > > > On 06/04/2012 06:19 AM, Carlos sanchiavedraz wrote: >> >> Hi again, >> >> I can't send any of two kernels due to mail file size restrictions, >> maybe I could send them later by other means. >> In advance I tell you that kernels are: >> * >> linux-image-3.2.12-gnu-rt22-686-musix-3_3.2.12-gnu-rt22-686-musix-3-10.00.Custom_i386.deb >> * and another one prepared for Wheezy: >> >> linux-image-3.2.12-gnu-rt22-prueba_3.2.12-gnu-rt22-prueba-10.00.Custom_i386.deb >> >> I did some test with 2.6.x and it seems Rakarrack doesn't have this >> problems I mentioned. I'm not 100% sure but it seems the problems is >> any kernel 3.x, maybe. Anyway, with other programs, like Freewheeling, >> I still get (what it seems to be) same error: >> " >> cannot use real-time scheduling (FIFO at priority -4) [for thread >> -1260520592, from thread -1260520592] (22: Invalid argument) >> " >> ... and I can also see this on the info (>1 parameter) output: >> " >> MIDI: HiPri Thread 99 >> MIDI: Can't set realtime thread, will use nonRT! >> " >> >> >> 2012/5/15 Ryan Billing<ry...@gm...>: >> >>> >>> Good to know the kernels you are using. Is there a way I can get a copy >>> of >>> the kernel you are using, linux-image-3.2.12-gnu-rt22? This might help >>> me >>> reproduce the error (source or pre-build binary ok). >>> >>> Thanks >>> >>> >>> On 05/15/2012 12:33 AM, Carlos sanchiavedraz wrote: >>> >>> I'm glad you like Musix, I'm CCing to the list, they would love to know >>> that >>> because we love Rakarrack ;). Without the whole team and users Musix >>> would >>> not be possible. >>> >>> Some weeks ago I was using kernel RT 3.0.x and lately >>> linux-image-3.2.12-gnu-rt22 compiled by the team. I should have some time >>> to >>> test some older kernels to see if problems are because of the 3.x branch. >>> >>> Maybe I'll have some time to compile Rakarrack, it seems you don't have >>> to >>> "fight" with errors and dependencies. We'll see. >>> >>> >>> 2012/5/15 Ryan Billing<ry...@gm...> >>> >>>> >>>> Thanks for the information. I use Debian Squeeze, and I have no >>>> problems >>>> on the stock kernel 2.6.32-5-686. I have not attempted to compile a >>>> kernel >>>> with the RT patch (are you using kernel w/ RT patch?). This makes me >>>> think >>>> there is something specific about hardware we need to identify. >>>> >>>> >>>> "Last, but not least, I'm afraid I can't compile the newest version of >>>> Rakarrack, at least not by now." >>>> >>>> In git I added the dependency for FFTW3. Let me know if the configure >>>> script fails to inform you of the need to install FFTW3 dev package (it >>>> seemed good on my system here). You should not be able to finish >>>> "./configure" without a failure ... unless maybe you did not run >>>> "./autogen.sh". I have not yet updated the README, so it does not >>>> mention >>>> this dependency (it reminds me I need to do that). >>>> >>>> If using git repo, make sure you do this >>>> ./autogen.sh >>>> ./configure >>>> make >>>> #make install >>>> >>>> Let us know if you have the same problem once you get the most recent >>>> code >>>> to compile. I am sorry at the moment I can't think of anything that >>>> causes >>>> this, so we need to keep the emails going and maybe I will think of >>>> something. >>>> >>>> Thanks again for reporting the problem, and thanks for maintaining >>>> Musix... it is a good distribution :) >>>> >>>> Ryan >>>> >>>> >>>> >>>> >>>> >>>> >>>> Hi again. >>>> >>>> I'm using Musix as my distribution. We at Musix try to configure >>>> everything needed for the user to have kernel RT and Jack with an >>>> appropriate config, at least. I remember that some years ago there it >>>> was a >>>> little more complicated things to do to achieve all that, but the latest >>>> versions of Debian and the kernel are great and it's easier now. >>>> >>>> The Musix version we're debugging is based on Debian Squeeze. >>>> >>>> So now, answering to the things you asked before: >>>> >>>> * /etc/security/limits.conf (attached) >>>> It seems this file is correct and I think it is untouched from the >>>> Debian >>>> original. >>>> >>>> * /etc/security/limits.d/audio.conf (attached) >>>> This is generated by Jack, according with what says on its content, so >>>> it >>>> should be right. It says that you can run "dpkg-reconfigure -p high >>>> jackd", >>>> I should check if this was already done; I suppose there is another >>>> command >>>> option for this. >>>> BTW, there is a file called "audio.conf.disabled" that is exactly the >>>> same >>>> as this "audio.conf" and is in the same directory. >>>> >>>> * user in "audio" group >>>> This is done by default in Musix, so my user is in this group. >>>> >>>> Last, but not least, I'm afraid I can't compile the newest version of >>>> Rakarrack, at least not by now. >>>> >>>> Please, let me know if there's something else I can add. >>>> >>>> Thanks >>>> >>>> >>>> 2012/5/10 Ryan Billing<ry...@gm...> >>>> >>>>> >>>>> Josep, >>>>> It looks like he uses the last release: >>>>> >>>>> " >>>>> rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas >>>>> McClendon - Arnout Engelen >>>>> Try 'rakarrack --help' for command-line options. >>>>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>>>> -1267381392, from thread -1267381392] (22: Invalid argument) >>>>> " >>>>> >>>>> Carlos, maybe try building current development from git and see if you >>>>> still have the problem. I don't remember what version where this >>>>> changed, but Josep knows, so I will let him say. >>>>> >>>>> >>>>> >>>>> >>>>> On 05/09/2012 04:29 AM, Josep Andreu wrote: >>>>> >>>>>> >>>>>> Hi >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>>>>>> -1261438096, from thread -1261438096] (22: Invalid argument) >>>>>>> zombified - calling shutdown handler >>>>>>> >>>>>>> >>>>>> >>>>>> First .. what version of rakarrack are you using? older version of >>>>>> rakarrack put the real time schedule for some threads but not the >>>>>> newest >>>>>> IIRC. >>>>>> anyway .... check your Realtime prioritys in /etc/security/limits.conf >>>>>> ( newest versions of jackd put the correct values on >>>>>> /etc/security/limits.d/audio.conf ( Google for the correct values) >>>>>> >>>>>> Josep >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Live Security Virtual Conference >>>>>> Exclusive live event will cover all the ways today's security and >>>>>> threat landscape has changed and how IT managers can respond. >>>>>> Discussions >>>>>> will include endpoint security, mobile security and the latest in >>>>>> malware >>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>>> _______________________________________________ >>>>>> Rakarrack-users mailing list >>>>>> Rak...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Live Security Virtual Conference >>>>> Exclusive live event will cover all the ways today's security and >>>>> threat landscape has changed and how IT managers can respond. >>>>> Discussions >>>>> will include endpoint security, mobile security and the latest in >>>>> malware >>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>> _______________________________________________ >>>>> Rakarrack-users mailing list >>>>> Rak...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >>>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Carlos sanchiavedraz >>>> * Musix GNU+Linux >>>> http://www.musix.es >>>> >>>> >>>> >>>> On 05/14/2012 07:27 AM, Carlos sanchiavedraz wrote: >>>> >>>> d o >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Carlos sanchiavedraz >>> * Musix GNU+Linux >>> http://www.musix.es >>> >>> >>> >> >> >> >> > > -- Carlos sanchiavedraz * Musix GNU+Linux http://www.musix.es |
From: Ryan B. <ry...@gm...> - 2012-06-05 15:45:06
|
It looks like you are using a version of jack that ships with Squeeze. It may be a valid experiment to download jackd source and compile against your kernel. Is there a reason where a linux 3.x kernel is needed for Musix? For example, would it be a problem to compile a standard Debian Squeeze kernel with the appropriate RT patch? The reason I ask this is because a snapshot from Debian Sid might be a better choice if your goal is to include the most recent drivers from the newer kernels. I have used Sid on my dev laptop for years and it has treated me fine, but perhaps, that is because my Sid system is a very minimal WM environment. Just some more ideas. Either way I am curious to find out whether there is a Rakarrack problem we need to fix or if it is kernel/jackd/user configuration problem. Thanks, Ryan On 06/05/2012 06:39 AM, Carlos sanchiavedraz wrote: > Hi, > > 1) cgroups: I didn't check that about cgroups, I'll check > > 2) $jackd --version > jackd version 0.118.0 > > 3) sudo: I'll check that also > > Thanks so much for your kind help. > I'll reply with more information. > > > 2012/6/4 Ryan Billing<ry...@gm...>: > >> Maybe you have already tried this: >> http://trac.jackaudio.org/wiki/Cgroups >> >> If not, let me know if it helps. The section for "for packagers" might be >> the most relevant. >> >> Also, what version of JACK are you using? Maybe a certain version of jack >> is needed to work with newer kernels? Certainly it seems the kernel is not >> allowing the user to request RT privilege. >> >> Have you tried to run JACK and rakarrack as root? Does that work. Finding >> out if it runs as root will let us know whether we are having a problem with >> user configuration (in which case the link above might help), or whether >> there are deeper problems. >> >> Just some more ideas. >> Thanks, >> Ryan >> >> >> On 06/04/2012 06:19 AM, Carlos sanchiavedraz wrote: >> >>> Hi again, >>> >>> I can't send any of two kernels due to mail file size restrictions, >>> maybe I could send them later by other means. >>> In advance I tell you that kernels are: >>> * >>> linux-image-3.2.12-gnu-rt22-686-musix-3_3.2.12-gnu-rt22-686-musix-3-10.00.Custom_i386.deb >>> * and another one prepared for Wheezy: >>> >>> linux-image-3.2.12-gnu-rt22-prueba_3.2.12-gnu-rt22-prueba-10.00.Custom_i386.deb >>> >>> I did some test with 2.6.x and it seems Rakarrack doesn't have this >>> problems I mentioned. I'm not 100% sure but it seems the problems is >>> any kernel 3.x, maybe. Anyway, with other programs, like Freewheeling, >>> I still get (what it seems to be) same error: >>> " >>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>> -1260520592, from thread -1260520592] (22: Invalid argument) >>> " >>> ... and I can also see this on the info (>1 parameter) output: >>> " >>> MIDI: HiPri Thread 99 >>> MIDI: Can't set realtime thread, will use nonRT! >>> " >>> >>> >>> 2012/5/15 Ryan Billing<ry...@gm...>: >>> >>> >>>> Good to know the kernels you are using. Is there a way I can get a copy >>>> of >>>> the kernel you are using, linux-image-3.2.12-gnu-rt22? This might help >>>> me >>>> reproduce the error (source or pre-build binary ok). >>>> >>>> Thanks >>>> >>>> >>>> On 05/15/2012 12:33 AM, Carlos sanchiavedraz wrote: >>>> >>>> I'm glad you like Musix, I'm CCing to the list, they would love to know >>>> that >>>> because we love Rakarrack ;). Without the whole team and users Musix >>>> would >>>> not be possible. >>>> >>>> Some weeks ago I was using kernel RT 3.0.x and lately >>>> linux-image-3.2.12-gnu-rt22 compiled by the team. I should have some time >>>> to >>>> test some older kernels to see if problems are because of the 3.x branch. >>>> >>>> Maybe I'll have some time to compile Rakarrack, it seems you don't have >>>> to >>>> "fight" with errors and dependencies. We'll see. >>>> >>>> >>>> 2012/5/15 Ryan Billing<ry...@gm...> >>>> >>>> >>>>> Thanks for the information. I use Debian Squeeze, and I have no >>>>> problems >>>>> on the stock kernel 2.6.32-5-686. I have not attempted to compile a >>>>> kernel >>>>> with the RT patch (are you using kernel w/ RT patch?). This makes me >>>>> think >>>>> there is something specific about hardware we need to identify. >>>>> >>>>> >>>>> "Last, but not least, I'm afraid I can't compile the newest version of >>>>> Rakarrack, at least not by now." >>>>> >>>>> In git I added the dependency for FFTW3. Let me know if the configure >>>>> script fails to inform you of the need to install FFTW3 dev package (it >>>>> seemed good on my system here). You should not be able to finish >>>>> "./configure" without a failure ... unless maybe you did not run >>>>> "./autogen.sh". I have not yet updated the README, so it does not >>>>> mention >>>>> this dependency (it reminds me I need to do that). >>>>> >>>>> If using git repo, make sure you do this >>>>> ./autogen.sh >>>>> ./configure >>>>> make >>>>> #make install >>>>> >>>>> Let us know if you have the same problem once you get the most recent >>>>> code >>>>> to compile. I am sorry at the moment I can't think of anything that >>>>> causes >>>>> this, so we need to keep the emails going and maybe I will think of >>>>> something. >>>>> >>>>> Thanks again for reporting the problem, and thanks for maintaining >>>>> Musix... it is a good distribution :) >>>>> >>>>> Ryan >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Hi again. >>>>> >>>>> I'm using Musix as my distribution. We at Musix try to configure >>>>> everything needed for the user to have kernel RT and Jack with an >>>>> appropriate config, at least. I remember that some years ago there it >>>>> was a >>>>> little more complicated things to do to achieve all that, but the latest >>>>> versions of Debian and the kernel are great and it's easier now. >>>>> >>>>> The Musix version we're debugging is based on Debian Squeeze. >>>>> >>>>> So now, answering to the things you asked before: >>>>> >>>>> * /etc/security/limits.conf (attached) >>>>> It seems this file is correct and I think it is untouched from the >>>>> Debian >>>>> original. >>>>> >>>>> * /etc/security/limits.d/audio.conf (attached) >>>>> This is generated by Jack, according with what says on its content, so >>>>> it >>>>> should be right. It says that you can run "dpkg-reconfigure -p high >>>>> jackd", >>>>> I should check if this was already done; I suppose there is another >>>>> command >>>>> option for this. >>>>> BTW, there is a file called "audio.conf.disabled" that is exactly the >>>>> same >>>>> as this "audio.conf" and is in the same directory. >>>>> >>>>> * user in "audio" group >>>>> This is done by default in Musix, so my user is in this group. >>>>> >>>>> Last, but not least, I'm afraid I can't compile the newest version of >>>>> Rakarrack, at least not by now. >>>>> >>>>> Please, let me know if there's something else I can add. >>>>> >>>>> Thanks >>>>> >>>>> >>>>> 2012/5/10 Ryan Billing<ry...@gm...> >>>>> >>>>> >>>>>> Josep, >>>>>> It looks like he uses the last release: >>>>>> >>>>>> " >>>>>> rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas >>>>>> McClendon - Arnout Engelen >>>>>> Try 'rakarrack --help' for command-line options. >>>>>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>>>>> -1267381392, from thread -1267381392] (22: Invalid argument) >>>>>> " >>>>>> >>>>>> Carlos, maybe try building current development from git and see if you >>>>>> still have the problem. I don't remember what version where this >>>>>> changed, but Josep knows, so I will let him say. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 05/09/2012 04:29 AM, Josep Andreu wrote: >>>>>> >>>>>> >>>>>>> Hi >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>>>>>>> -1261438096, from thread -1261438096] (22: Invalid argument) >>>>>>>> zombified - calling shutdown handler >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> First .. what version of rakarrack are you using? older version of >>>>>>> rakarrack put the real time schedule for some threads but not the >>>>>>> newest >>>>>>> IIRC. >>>>>>> anyway .... check your Realtime prioritys in /etc/security/limits.conf >>>>>>> ( newest versions of jackd put the correct values on >>>>>>> /etc/security/limits.d/audio.conf ( Google for the correct values) >>>>>>> >>>>>>> Josep >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Live Security Virtual Conference >>>>>>> Exclusive live event will cover all the ways today's security and >>>>>>> threat landscape has changed and how IT managers can respond. >>>>>>> Discussions >>>>>>> will include endpoint security, mobile security and the latest in >>>>>>> malware >>>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>>>> _______________________________________________ >>>>>>> Rakarrack-users mailing list >>>>>>> Rak...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Live Security Virtual Conference >>>>>> Exclusive live event will cover all the ways today's security and >>>>>> threat landscape has changed and how IT managers can respond. >>>>>> Discussions >>>>>> will include endpoint security, mobile security and the latest in >>>>>> malware >>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>>> _______________________________________________ >>>>>> Rakarrack-users mailing list >>>>>> Rak...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Carlos sanchiavedraz >>>>> * Musix GNU+Linux >>>>> http://www.musix.es >>>>> >>>>> >>>>> >>>>> On 05/14/2012 07:27 AM, Carlos sanchiavedraz wrote: >>>>> >>>>> d o >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Carlos sanchiavedraz >>>> * Musix GNU+Linux >>>> http://www.musix.es >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> > > > |
From: Carlos s. <csa...@gm...> - 2012-06-11 07:48:32
|
Hi, Ryan. We began working on Musix 3 over Debian Squeeze. Given that next version of Debian is out now, we are considering the switch before even releasing version 3. Actually, the 3.x kernels we're testing are aimed for this Debian Wheezy, but what bugs me is that I have problems even with the kernel 2.x we put originally in Musix 3 beta 2 months ago. I'll continue testing ASAIC. Thanks, again. 2012/6/5 Ryan Billing <ry...@gm...>: > It looks like you are using a version of jack that ships with Squeeze. It > may be a valid experiment to download jackd source and compile against your > kernel. > > Is there a reason where a linux 3.x kernel is needed for Musix? For > example, would it be a problem to compile a standard Debian Squeeze kernel > with the appropriate RT patch? > > The reason I ask this is because a snapshot from Debian Sid might be a > better choice if your goal is to include the most recent drivers from the > newer kernels. I have used Sid on my dev laptop for years and it has > treated me fine, but perhaps, that is because my Sid system is a very > minimal WM environment. > > Just some more ideas. Either way I am curious to find out whether there is > a Rakarrack problem we need to fix or if it is kernel/jackd/user > configuration problem. > > Thanks, > Ryan > > > On 06/05/2012 06:39 AM, Carlos sanchiavedraz wrote: >> >> Hi, >> >> 1) cgroups: I didn't check that about cgroups, I'll check >> >> 2) $jackd --version >> jackd version 0.118.0 >> >> 3) sudo: I'll check that also >> >> Thanks so much for your kind help. >> I'll reply with more information. >> >> >> 2012/6/4 Ryan Billing<ry...@gm...>: >> >>> >>> Maybe you have already tried this: >>> http://trac.jackaudio.org/wiki/Cgroups >>> >>> If not, let me know if it helps. The section for "for packagers" might >>> be >>> the most relevant. >>> >>> Also, what version of JACK are you using? Maybe a certain version of >>> jack >>> is needed to work with newer kernels? Certainly it seems the kernel is >>> not >>> allowing the user to request RT privilege. >>> >>> Have you tried to run JACK and rakarrack as root? Does that work. >>> Finding >>> out if it runs as root will let us know whether we are having a problem >>> with >>> user configuration (in which case the link above might help), or whether >>> there are deeper problems. >>> >>> Just some more ideas. >>> Thanks, >>> Ryan >>> >>> >>> On 06/04/2012 06:19 AM, Carlos sanchiavedraz wrote: >>> >>>> >>>> Hi again, >>>> >>>> I can't send any of two kernels due to mail file size restrictions, >>>> maybe I could send them later by other means. >>>> In advance I tell you that kernels are: >>>> * >>>> >>>> linux-image-3.2.12-gnu-rt22-686-musix-3_3.2.12-gnu-rt22-686-musix-3-10.00.Custom_i386.deb >>>> * and another one prepared for Wheezy: >>>> >>>> >>>> linux-image-3.2.12-gnu-rt22-prueba_3.2.12-gnu-rt22-prueba-10.00.Custom_i386.deb >>>> >>>> I did some test with 2.6.x and it seems Rakarrack doesn't have this >>>> problems I mentioned. I'm not 100% sure but it seems the problems is >>>> any kernel 3.x, maybe. Anyway, with other programs, like Freewheeling, >>>> I still get (what it seems to be) same error: >>>> " >>>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>>> -1260520592, from thread -1260520592] (22: Invalid argument) >>>> " >>>> ... and I can also see this on the info (>1 parameter) output: >>>> " >>>> MIDI: HiPri Thread 99 >>>> MIDI: Can't set realtime thread, will use nonRT! >>>> " >>>> >>>> >>>> 2012/5/15 Ryan Billing<ry...@gm...>: >>>> >>>> >>>>> >>>>> Good to know the kernels you are using. Is there a way I can get a >>>>> copy >>>>> of >>>>> the kernel you are using, linux-image-3.2.12-gnu-rt22? This might help >>>>> me >>>>> reproduce the error (source or pre-build binary ok). >>>>> >>>>> Thanks >>>>> >>>>> >>>>> On 05/15/2012 12:33 AM, Carlos sanchiavedraz wrote: >>>>> >>>>> I'm glad you like Musix, I'm CCing to the list, they would love to know >>>>> that >>>>> because we love Rakarrack ;). Without the whole team and users Musix >>>>> would >>>>> not be possible. >>>>> >>>>> Some weeks ago I was using kernel RT 3.0.x and lately >>>>> linux-image-3.2.12-gnu-rt22 compiled by the team. I should have some >>>>> time >>>>> to >>>>> test some older kernels to see if problems are because of the 3.x >>>>> branch. >>>>> >>>>> Maybe I'll have some time to compile Rakarrack, it seems you don't have >>>>> to >>>>> "fight" with errors and dependencies. We'll see. >>>>> >>>>> >>>>> 2012/5/15 Ryan Billing<ry...@gm...> >>>>> >>>>> >>>>>> >>>>>> Thanks for the information. I use Debian Squeeze, and I have no >>>>>> problems >>>>>> on the stock kernel 2.6.32-5-686. I have not attempted to compile a >>>>>> kernel >>>>>> with the RT patch (are you using kernel w/ RT patch?). This makes me >>>>>> think >>>>>> there is something specific about hardware we need to identify. >>>>>> >>>>>> >>>>>> "Last, but not least, I'm afraid I can't compile the newest version of >>>>>> Rakarrack, at least not by now." >>>>>> >>>>>> In git I added the dependency for FFTW3. Let me know if the configure >>>>>> script fails to inform you of the need to install FFTW3 dev package >>>>>> (it >>>>>> seemed good on my system here). You should not be able to finish >>>>>> "./configure" without a failure ... unless maybe you did not run >>>>>> "./autogen.sh". I have not yet updated the README, so it does not >>>>>> mention >>>>>> this dependency (it reminds me I need to do that). >>>>>> >>>>>> If using git repo, make sure you do this >>>>>> ./autogen.sh >>>>>> ./configure >>>>>> make >>>>>> #make install >>>>>> >>>>>> Let us know if you have the same problem once you get the most recent >>>>>> code >>>>>> to compile. I am sorry at the moment I can't think of anything that >>>>>> causes >>>>>> this, so we need to keep the emails going and maybe I will think of >>>>>> something. >>>>>> >>>>>> Thanks again for reporting the problem, and thanks for maintaining >>>>>> Musix... it is a good distribution :) >>>>>> >>>>>> Ryan >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Hi again. >>>>>> >>>>>> I'm using Musix as my distribution. We at Musix try to configure >>>>>> everything needed for the user to have kernel RT and Jack with an >>>>>> appropriate config, at least. I remember that some years ago there it >>>>>> was a >>>>>> little more complicated things to do to achieve all that, but the >>>>>> latest >>>>>> versions of Debian and the kernel are great and it's easier now. >>>>>> >>>>>> The Musix version we're debugging is based on Debian Squeeze. >>>>>> >>>>>> So now, answering to the things you asked before: >>>>>> >>>>>> * /etc/security/limits.conf (attached) >>>>>> It seems this file is correct and I think it is untouched from the >>>>>> Debian >>>>>> original. >>>>>> >>>>>> * /etc/security/limits.d/audio.conf (attached) >>>>>> This is generated by Jack, according with what says on its content, so >>>>>> it >>>>>> should be right. It says that you can run "dpkg-reconfigure -p high >>>>>> jackd", >>>>>> I should check if this was already done; I suppose there is another >>>>>> command >>>>>> option for this. >>>>>> BTW, there is a file called "audio.conf.disabled" that is exactly the >>>>>> same >>>>>> as this "audio.conf" and is in the same directory. >>>>>> >>>>>> * user in "audio" group >>>>>> This is done by default in Musix, so my user is in this group. >>>>>> >>>>>> Last, but not least, I'm afraid I can't compile the newest version of >>>>>> Rakarrack, at least not by now. >>>>>> >>>>>> Please, let me know if there's something else I can add. >>>>>> >>>>>> Thanks >>>>>> >>>>>> >>>>>> 2012/5/10 Ryan Billing<ry...@gm...> >>>>>> >>>>>> >>>>>>> >>>>>>> Josep, >>>>>>> It looks like he uses the last release: >>>>>>> >>>>>>> " >>>>>>> rakarrack 0.6.1 - Copyright (c) Josep Andreu - Ryan Billing - Douglas >>>>>>> McClendon - Arnout Engelen >>>>>>> Try 'rakarrack --help' for command-line options. >>>>>>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>>>>>> -1267381392, from thread -1267381392] (22: Invalid argument) >>>>>>> " >>>>>>> >>>>>>> Carlos, maybe try building current development from git and see if >>>>>>> you >>>>>>> still have the problem. I don't remember what version where this >>>>>>> changed, but Josep knows, so I will let him say. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 05/09/2012 04:29 AM, Josep Andreu wrote: >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Hi >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> cannot use real-time scheduling (FIFO at priority -4) [for thread >>>>>>>>> -1261438096, from thread -1261438096] (22: Invalid argument) >>>>>>>>> zombified - calling shutdown handler >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> First .. what version of rakarrack are you using? older version of >>>>>>>> rakarrack put the real time schedule for some threads but not the >>>>>>>> newest >>>>>>>> IIRC. >>>>>>>> anyway .... check your Realtime prioritys in >>>>>>>> /etc/security/limits.conf >>>>>>>> ( newest versions of jackd put the correct values on >>>>>>>> /etc/security/limits.d/audio.conf ( Google for the correct values) >>>>>>>> >>>>>>>> Josep >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> Live Security Virtual Conference >>>>>>>> Exclusive live event will cover all the ways today's security and >>>>>>>> threat landscape has changed and how IT managers can respond. >>>>>>>> Discussions >>>>>>>> will include endpoint security, mobile security and the latest in >>>>>>>> malware >>>>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>>>>> _______________________________________________ >>>>>>>> Rakarrack-users mailing list >>>>>>>> Rak...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Live Security Virtual Conference >>>>>>> Exclusive live event will cover all the ways today's security and >>>>>>> threat landscape has changed and how IT managers can respond. >>>>>>> Discussions >>>>>>> will include endpoint security, mobile security and the latest in >>>>>>> malware >>>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>>>> _______________________________________________ >>>>>>> Rakarrack-users mailing list >>>>>>> Rak...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/rakarrack-users >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Carlos sanchiavedraz >>>>>> * Musix GNU+Linux >>>>>> http://www.musix.es >>>>>> >>>>>> >>>>>> >>>>>> On 05/14/2012 07:27 AM, Carlos sanchiavedraz wrote: >>>>>> >>>>>> d o >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Carlos sanchiavedraz >>>>> * Musix GNU+Linux >>>>> http://www.musix.es >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> > > -- Carlos sanchiavedraz * Musix GNU+Linux http://www.musix.es |