9 Dec
2004
9 Dec
'04
10:36 p.m.
Hello all,
Im hoping that you can help me with a problem Im having
with jack and PD.
I am running jackd from qjackctl in realtime with a 64
frame buffer (Hammerfall HDSP multiface: 2.67 ms delay).
I am using PD, and after both have been running fro about
20 min I get a ton of xruns. (and as an xrun has
negligable weight, that is a lot of xruns)
I got through my logs and can find no reason for this
when cross-referencing by time of occurance. Here are some
possible unrelated errors, or perhaps they are leading to
my problem...
From System Logs:
Failure registering Root Plug
module with the kernel
Failure registering Root Plug module with primary security module.
From Kernel Startup Log:
PCI: Using ACPI for IRQ
routing
** PCI interrupts are no longer routed automatically. If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device(). As a temporary
** workaround, the \"pci=routeirq\" argument restores the old
** behavior. If this argument makes the device work again,
** please email the output of \"lspci\" to bjorn.helgaas(a)hp.com
** so I can fix the driver.
My system is:
(http://www.aproximation.org/application/AMD64laptop.html (old))
AMD64 laptop
Hammerfall HDSP multiface and cardbus
Fedora Core 3 test 1
linux-2.6.10-rc2-mm1 kernel
What does the priority selector mean in qjackctl setup? I just
leave it at 0.
Any help would be greatly appreciated! I would LOVE to get
this machine running jackd flawlessly.
Thank you for your time!
-thewade
11:06 p.m.
thewade wrote:
Hello all,
Im hoping that you can help me with a problem Im having
with jack and PD.
I am running jackd from qjackctl in realtime with a 64
frame buffer (Hammerfall HDSP multiface: 2.67 ms delay).
I am using PD, and after both have been running fro about
20 min I get a ton of xruns. (and as an xrun has
negligable weight, that is a lot of xruns)
I got through my logs and can find no reason for this
when cross-referencing by time of occurance. Here are some
possible unrelated errors, or perhaps they are leading to
my problem...
Does that kernel have a "laptop_mode" in /proc/sys/vm ? If it does, is
it enabled? I'm just thinking maybe the machine is in laptop mode and to
save the battery it spins down the harddrive and then after a certain
amount of time it spins it back up to flush some stuff to disk and that
could cause your xruns.
Rick B
From System Logs:
Failure registering Root
Plug module with the kernel
Failure registering Root Plug module with primary security module.
From Kernel Startup Log:
PCI: Using ACPI for
IRQ routing
** PCI interrupts are no longer routed automatically. If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device(). As a temporary
** workaround, the \"pci=routeirq\" argument restores the old
** behavior. If this argument makes the device work again,
** please email the output of \"lspci\" to bjorn.helgaas(a)hp.com
** so I can fix the driver.
My system is:
(http://www.aproximation.org/application/AMD64laptop.html (old))
AMD64 laptop
Hammerfall HDSP multiface and cardbus
Fedora Core 3 test 1
linux-2.6.10-rc2-mm1 kernel
What does the priority selector mean in qjackctl setup? I just
leave it at 0.
Any help would be greatly appreciated! I would LOVE to get
this machine running jackd flawlessly.
Thank you for your time!
-thewade
11:16 p.m.
thewade,
Hi. I've had a few problems using ACPI at different times. When I
first built my 2.6.9-mm4-VPS7 kernel I had ACPI turned on and had
weird things happening. (Although not the exact one you are dealing
with.) That said I am using the PlanetEdge kernel
2.6.8.1-1.520.2vS7.ll.rhfc2.ccrma at 128/2 with the HDSP 9652 and
getting good results so far. Please remember to make your HDSP 9652
interrupt non-threaded.
You might try booting and trying one or more of these options
apm=off
acpi=off
pci=noacpi
No promises but it's a cheap experiment.
Good luck,
Mark
On Thu, 9 Dec 2004 19:36:37 -0700, thewade <pdman(a)aproximation.org> wrote:
Hello all,
Im hoping that you can help me with a problem Im having
with jack and PD.
I am running jackd from qjackctl in realtime with a 64
frame buffer (Hammerfall HDSP multiface: 2.67 ms delay).
I am using PD, and after both have been running fro about
20 min I get a ton of xruns. (and as an xrun has
negligable weight, that is a lot of xruns)
I got through my logs and can find no reason for this
when cross-referencing by time of occurance. Here are some
possible unrelated errors, or perhaps they are leading to
my problem...
From System Logs:
Failure registering Root
Plug module with the kernel
Failure registering Root Plug module with primary security module.
From Kernel Startup Log:
PCI: Using ACPI
for IRQ routing
** PCI interrupts are no longer routed automatically. If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device(). As a temporary
** workaround, the \"pci=routeirq\" argument restores the old
** behavior. If this argument makes the device work again,
** please email the output of \"lspci\" to bjorn.helgaas(a)hp.com
** so I can fix the driver.
My system is:
(http://www.aproximation.org/application/AMD64laptop.html (old))
AMD64 laptop
Hammerfall HDSP multiface and cardbus
Fedora Core 3 test 1
linux-2.6.10-rc2-mm1 kernel
What does the priority selector mean in qjackctl setup? I just
leave it at 0.
Any help would be greatly appreciated! I would LOVE to get
this machine running jackd flawlessly.
Thank you for your time!
-thewade
11:40 p.m.
On Thu, 2004-12-09 at 19:16 -0800, Mark Knecht wrote:
thewade,
Hi. I've had a few problems using ACPI at different times.
Ingo found and fixed a pretty bad ACPI bug recently that would cause up
to 1ms latencies at random. If you want to be able to use ACPI you need
a very recent kernel with Ingo's latest patches and
CONFIG_PREEMPT_DESKTOP.
Lee
7318
days inactive
7318
days old
linux-audio-user@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Lee Revell -
Mark Knecht -
Rick B -
thewade