7 Apr
2006
7 Apr
'06
11:59 a.m.
Hi,
On my laptop, I'm running ubuntu dapper. Using the 2.15.18 kernel, all my audio
applications work great OOTB. Very few xruns. With the latest two kernels (2.15.19 and
2.15.20), when I start jack using qjackctl, it immediately starts reporting xruns at the
rate of about 10 per second - and this is with no applications running at all. I'm not
sure about how to go about debugging this.
Any ideas?
Regards,
Bill
7 Apr
7 Apr
1:21 p.m.
On Fri, 2006-04-07 at 09:59 -0400, Bill Allen wrote:
On my laptop, I'm running ubuntu dapper. Using the
2.15.18 kernel, all
my audio applications work great OOTB. Very few xruns. With the latest
two kernels (2.15.19 and 2.15.20),
Those are not kernel version numbers.
I think you mean 2.6.something...
Lee
3:15 p.m.
On 4/7/06, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Fri, 2006-04-07 at 09:59 -0400, Bill Allen wrote:
Just installed Ubuntu Dapper, myself.
I think he means 2.6.15-18, ... 2.6.15-20.
Those are different package versions of the same kernel.
--
joq
On my laptop, I'm running ubuntu dapper.
Using the 2.15.18 kernel, all
my audio applications work great OOTB. Very few xruns. With the latest
two kernels (2.15.19 and 2.15.20),
Those are not kernel version numbers.
I think you mean 2.6.something... 
2 p.m.
On Fri, 07 Apr 2006 09:59:10 -0400
"Bill Allen" <lau(a)ballen.fastmail.fm> wrote:
Hi,
On my laptop, I'm running ubuntu dapper. Using the 2.15.18 kernel, all my audio
applications work great OOTB. Very few xruns. With the latest two kernels (2.15.19 and
2.15.20), when I start jack using qjackctl, it immediately starts reporting xruns at the
rate of about 10 per second - and this is with no applications running at all. I'm not
sure about how to go about debugging this.
Maybe you did use the realtime lsm and it misses for the new kernels.
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
5:12 p.m.
On Fri, 2006-07-04 at 09:59 -0400, Bill Allen wrote:
Hi,
On my laptop, I'm running ubuntu dapper. Using the 2.15.18 kernel, all my audio
applications work great OOTB. Very few xruns. With the latest two kernels (2.15.19 and
2.15.20), when I start jack using qjackctl, it immediately starts reporting xruns at the
rate of about 10 per second - and this is with no applications running at all. I'm not
sure about how to go about debugging this.
Can you send me these kernel sources from the future? Might as well
save the kernel devs back here in 2005 the work of having to write it
all.. uh, again? :)
-DR-
5:22 p.m.
On Fri, 2006-04-07 at 09:59 -0400, Bill Allen wrote:
Hi,
On my laptop, I'm running ubuntu dapper. Using the 2.15.18 kernel, all my audio
applications work great OOTB. Very few xruns. With the latest two kernels (2.15.19 and
2.15.20), when I start jack using qjackctl, it immediately starts reporting xruns at the
rate of about 10 per second - and this is with no applications running at all. I'm not
sure about how to go about debugging this.
Any ideas?
It's possible that they used to use realtime-lsm and recently switched
to the rlimit approach (although, shouldn't JACK bomb out if started
with -R and realtime scheduling is unavailable, rather than failing
silently?).
Try adding this to the end of /etc/security/limits.conf:
* rtprio hard 99
* nice hard -20
Then reboot and try it again.
If it still fails please post the JACK output
Lee
6:58 p.m.
On Fri, 07 Apr 2006 15:22:05 -0400, "Lee Revell" <rlrevell(a)joe-job.com>
said:
On Fri, 2006-04-07 at 09:59 -0400, Bill Allen wrote:
I'll try to do as you suggest. As I understand it (which could be not at all) Dapper
doesn't support realtime-lsm in any of those kernel builds. It uses Rlimits-Aware PAM.
I've added myself to the audio group and as I mentioned, jack works great in
2.6.15-18, but in *-19, and *-20 it's miserable.
Bill
Hi,
On my laptop, I'm running ubuntu dapper. Using the 2.15.18 kernel, all my audio
applications work great OOTB. Very few xruns. With the latest two kernels (2.15.19 and
2.15.20), when I start jack using qjackctl, it immediately starts reporting xruns at the
rate of about 10 per second - and this is with no applications running at all. I'm not
sure about how to go about debugging this.
Any ideas?
It's possible that they used to use realtime-lsm and recently switched
to the rlimit approach (although, shouldn't JACK bomb out if started
with -R and realtime scheduling is unavailable, rather than failing
silently?).
Try adding this to the end of /etc/security/limits.conf:
* rtprio hard 99
* nice hard -20
Then reboot and try it again.
If it still fails please post the JACK output
Lee
7:16 p.m.
On Fri, 2006-04-07 at 16:58 -0400, Bill Allen wrote:
I'll try to do as you suggest. As I understand it (which could be not
at all) Dapper doesn't support realtime-lsm in any of those kernel
builds. It uses Rlimits-Aware PAM. I've added myself to the audio
group and as I mentioned, jack works great in 2.6.15-18, but in *-19,
and *-20 it's miserable.
OK that's a kernel bug of some kind - can you please report it to
Ubuntu? There should not be too many changes between those point
releases.
Lee
8 Apr
8 Apr
3:22 p.m.
Lee Revell wrote:
On Fri, 2006-04-07 at 16:58 -0400, Bill Allen wrote:
I found that if I increase the number of periods to 3 that the xruns on
startup don't happen. Thus, using:
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p512 -n3
I was able to bring up qsynth and attach vkeybd and play some notes no
problem. But, when I launched jack rack and loaded a rack with a couple
of the CAPS amp/cabinet simulation plugins, all hell broke loose. Even
with a buffersize of 2048 and 4 periods (-p2048 -n4), loading the rack
caused way too many hard xruns.
On 2.6.15-18-686, I'm running jack with:
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p512 -n2
with no problems at all.
I'm trying to think of what could have regressed in the newer kernel
builds that would explain this behaviour?
Bill
I'll try to do as you suggest. As I
understand it (which could be not
at all) Dapper doesn't support realtime-lsm in any of those kernel
builds. It uses Rlimits-Aware PAM. I've added myself to the audio
group and as I mentioned, jack works great in 2.6.15-18, but in *-19,
and *-20 it's miserable.
OK that's a kernel bug of some kind - can you please report it to
Ubuntu? There should not be too many changes between those point
releases.
Lee
3:30 p.m.
On Sat, 2006-04-08 at 13:22 -0400, Bill Allen wrote:
On 2.6.15-18-686, I'm running jack with:
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p512 -n2
with no problems at all.
I'm trying to think of what could have regressed in the newer kernel
builds that would explain this behaviour?
No idea, only Ubuntu (or someone who reads their changelog) knows what
they changed between those versions. Please file a bug report with
them.
https://launchpad.net/distros/ubuntu/+filebug
Lee
3:32 p.m.
On Sat, 2006-04-08 at 13:22 -0400, Bill Allen wrote:
I'm trying to think of what could have regressed in the newer kernel
builds that would explain this behaviour?
Can you diff the kernel configs (should be /proc/config.gz or if they
don't enable that than /boot/config-whatever or something)
Lee
6807
days inactive
6808
days old
linux-audio-user@lists.linuxaudio.org
10 comments
5 participants
participants (5)
-
Bill Allen -
Dave Robillard -
Florian Schmidt -
Jack O'Quin -
Lee Revell