14 Sep
2012
14 Sep
'12
4:03 p.m.
ok.... so after all this:
1. there ARE folks successfully using a Mutiface on an ExpressCard adapter
with kernels more recent than 3.1.
2. there is a lot of discussion about pulseaudio -- i don't have
pulseaudio on this machine.
3. there is some discussion about dbus -- not sure if that applies or not,
but the jack failure happens the same way in qjackctl with "Enable D-Bus
interface" box UNchecked, so i think not.
to review, here's what happens when jack falls over for me with kernels
beyond 3.1-6 (note that this is in a boot in which i have not touched
hdspmixer, so let's forget about *that* issue for now!):
plutek@palnote:~$ jackd -p1024 -dalsa -r44100 -p256 -n2 -D -Chw:0,0
-Phw:0,0 &
[1] 3671
plutek@palnote:~$ jackdmp 1.9.9
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 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
JACK server starting in realtime mode with priority 10
control device hw:0
control device hw:0
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ...
hw:0,0|hw:0,0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
ALSA: poll time out, polled for 8706958 usecs
JackAudioDriver::ProcessAsync: read error, stopping...
should i try jack1, instead of jack2?
any other ideas, or troubleshooting bits i should post?
note also that, once jack has failed, hdspmixer won't start, AND vice
versa, so i think there may be some aspect of this that is "behind the
scenes" and common to both. when started on a clean boot, hdspmixer fails
thusly:
plutek@palnote:~$ hdspmixer
HDSPMixer 1.11 - Copyright (C) 2003 Thomas Charbonnel <thomas(a)undata.org>
This program comes with ABSOLUTELY NO WARRANTY
HDSPMixer is free software, see the file COPYING for details
Looking for RME cards:
Card 1: RME Hammerfall DSP + Multiface at 0xf1c00000, irq 19
Multiface found!
Card 29: ThinkPad Console Audio Control at EC reg 0x30, fw unknown
1 RME cards card found.
Initializing default presets
HwDep ioctl failed. Metering stopped
thanks so much for all your help, guys!
cheers!
.pltk.
14 Sep
14 Sep
9:50 p.m.
New subject: hdsp not happy with recent kernels
On Fri, 2012-09-14 at 10:03 -0400, peter(a)peterlutek.com wrote:
should i try jack1, instead of jack2?
If I were you I would test Jack2 1.9.8 and current version of Jack1, but
before doing this, I would follow Fernando's advice. His advice seems to
be the only thought to hold water.
HwDep ioctl failed. Metering stopped
On Thu, 2012-09-13 at 13:41 -0700, Fernando Lopez-Lezcano wrote:
It can be a bug in alsa-tools that shows up with new
kernels, that was a
problem a while back. Try getting the latest alsa-tools release
installed (1.0.26), I think I had to patch hdspmixer in previous
releases for it work fine with current kernels.
-- Fernando
On Thu, 2012-09-13 at 14:08 -0700, Fernando Lopez-Lezcano wrote:
[snip]
In my experience "HwDep ioctl failed. Metering stopped" has been caused
by broken versions of hdspmixer (that was the case until very recently).
-- Fernando
Good luck!
Ralf
9:58 p.m.
New subject: hdsp not happy with recent kernels
From: Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
Date: Fri, 14 Sep 2012 21:50:40 +0200
On Fri, 2012-09-14 at 10:03 -0400,
peter(a)peterlutek.com wrote:
well... that *might* be a solution for the hdspmixer issue, and i will test it for that.
however, note also that jack is still failing for me even if i don't use hdspmixer at
all, so there's definitely something else going on (as well).
thanks again for your help... it's frustrating to have audio hardware which has been
rock-solid for me for years suddenly begin to fall over like this! i can only hope a
solution will emerge...
cheers!
.pltk.
should i try jack1, instead of jack2?
If I were you I would test Jack2 1.9.8 and current version of Jack1, but
before doing this, I would follow Fernando's advice. His advice seems to
be the only thought to hold water.
HwDep ioctl failed. Metering stopped
On Thu, 2012-09-13 at 13:41 -0700, Fernando Lopez-Lezcano wrote:
It can be a bug in alsa-tools that shows up with
new kernels, that was a
problem a while back. Try getting the latest alsa-tools release
installed (1.0.26), I think I had to patch hdspmixer in previous
releases for it work fine with current kernels.
-- Fernando
On Thu, 2012-09-13 at 14:08 -0700, Fernando Lopez-Lezcano wrote:
[snip]
In my experience "HwDep ioctl failed. Metering stopped" has been caused
by broken versions of hdspmixer (that was the case until very recently).
-- Fernando
Good luck!
Ralf
15 Sep
15 Sep
4:48 p.m.
New subject: hdsp not happy with recent kernels
i've just switched over to jack1... it fails as well, with a different
error message (don't know if this sheds any more light on the situation!):
plutek@palnote:~$ jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0,0|hw:0,0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
ALSA: prepare error for playback on "hw:0,0" (Input/output error)
DRIVER NT: could not run driver cycle
**** alsa_pcm: xrun of at least 0.013 msecs
thanks again for any help on this!
.pltk.
5:04 p.m.
New subject: hdsp not happy with recent kernels
i've just switched over to jack1... it fails as
well, with a different
error message (don't know if this sheds any more light on the situation!):
plutek@palnote:~$ jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ...
hw:0,0|hw:0,0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
ALSA: prepare error for playback on "hw:0,0" (Input/output error)
DRIVER NT: could not run driver cycle
**** alsa_pcm: xrun of at least 0.013 msecs
thanks again for any help on this!
.pltk.
ooops... getting rid of the extra -p flag, and going with -p1024, i get this:
plutek@palnote:~$ jackd -dalsa -r44100 -p1024 -n2 -D -Chw:0,0 -Phw:0,0 &
[1] 3580
plutek@palnote:~$ jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0,0|hw:0,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
jackd watchdog: timeout - killing jackd
thanks... cheers!
.pltk.
7:53 p.m.
New subject: hdsp not happy with recent kernels
On 09/15/2012 08:04 AM, peter(a)peterlutek.com wrote:
All errors seem to point to a problem with interrupts. Somehow the
kernel is not handling interrupts from the soundcard, or the soundcard
is not generating them. Jack's driver waits for them and they never
arrive and as a result eventually the watchdog kills the whole thing in
the case of jack1.
Anything in /var/log/messages?
On 09/13/2012 11:24 AM, Peter Lutek wrote:
i've just
switched over to jack1... it fails as well, with a different
error message (don't know if this sheds any more light on the situation!):
plutek@palnote:~$ jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ...
hw:0,0|hw:0,0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
ALSA: prepare error for playback on "hw:0,0" (Input/output error)
DRIVER NT: could not run driver cycle
**** alsa_pcm: xrun of at least 0.013 msecs
thanks again for any help on this!
ooops... getting rid of the extra -p flag, and going with -p1024, i get this:
plutek@palnote:~$ jackd -dalsa -r44100 -p1024 -n2 -D -Chw:0,0 -Phw:0,0&
[1] 3580
plutek@palnote:~$ jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0,0|hw:0,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
jackd watchdog: timeout - killing jackd i suppose it's possible there's some weird
interaction between the more
recent kernels and my ThinkPad T520.
That would seem to be the case, something must have changed in the newer
kernel versions. I'm successfully running a pci express card and
multiface II under 3.2.18-1.rt29.1.fc14.ccrma.i686.rtPAE in a Lenovo
T510 (older than yours).
-- Fernando
8:32 p.m.
New subject: hdsp not happy with recent kernels
On 09/15/2012 08:04 AM, peter(a)peterlutek.com wrote:
All errors seem to point to a problem with interrupts. Somehow the
kernel is not handling interrupts from the soundcard, or the soundcard
is not generating them. Jack's driver waits for them and they never
arrive and as a result eventually the watchdog kills the whole thing in
the case of jack1.
Anything in /var/log/messages?
maybe, if i knew what to look for! ;-)
comparing a 3.2.0 (jack fails) boot with a 3.1-6 (jack is ok) boot, i
noticed two things:
3.2.0: NMI watchdog is active (disabling it via kernel params didn't fix
jack)
BOTH show this:
Sep 15 10:52:17 palnote kernel: [ 0.810792] pci 0000:00:1c.3: PCI INT D
-> GSI 19 (level, low) -> IRQ 19
Sep 15 10:52:17 palnote kernel: [ 1.391566] firewire_ohci 0000:0d:00.3:
PCI INT D -> GSI 19 (level, low) -> IRQ 19
Sep 15 10:52:17 palnote kernel: [ 1.567717] ahci 0000:00:1f.2: PCI INT
B -> GSI 19 (level, low) -> IRQ 19
Sep 15 10:52:17 palnote kernel: [ 11.827204] snd_hdsp 0000:05:00.0: PCI
INT A -> GSI 19 (level, low) -> IRQ 19
so, perhaps the hdsp sharing IRQ 19 with ohci and ahci is not a good
thing?? but that's the same in BOTH boots, so i dunno....
anything else i should look for, or any other info you might be interested
in seeing?
big thanks for any help on this, fernando!!
cheers!
.pltk.
i've
just switched over to jack1... it fails as well, with a different
error message (don't know if this sheds any more light on the
situation!):
plutek@palnote:~$ jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben
Hohn
and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ...
hw:0,0|hw:0,0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2
periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
ALSA: prepare error for playback on "hw:0,0" (Input/output error)
DRIVER NT: could not run driver cycle
**** alsa_pcm: xrun of at least 0.013 msecs
thanks again for any help on this!
ooops... getting rid of the extra -p flag, and going with -p1024, i get
this:
plutek@palnote:~$ jackd -dalsa -r44100 -p1024 -n2 -D -Chw:0,0 -Phw:0,0&
[1] 3580
plutek@palnote:~$ jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ...
hw:0,0|hw:0,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2
periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
jackd watchdog: timeout - killing jackd
9:22 p.m.
New subject: hdsp not happy with recent kernels
On 09/15/2012
08:04 AM, peter(a)peterlutek.com wrote:
All errors seem to point to a problem with interrupts. Somehow the
kernel is not handling interrupts from the soundcard, or the soundcard
is not generating them. Jack's driver waits for them and they never
arrive and as a result eventually the watchdog kills the whole thing in
the case of jack1.
Anything in /var/log/messages?
maybe, if i knew what to look for! ;-)
comparing a 3.2.0 (jack fails) boot with a 3.1-6 (jack is ok) boot, i
noticed two things:
3.2.0: NMI watchdog is active (disabling it via kernel params didn't fix
jack)
BOTH show this:
Sep 15 10:52:17 palnote kernel: [ 0.810792] pci 0000:00:1c.3: PCI INT D
-> GSI 19 (level, low) -> IRQ 19
Sep 15 10:52:17 palnote kernel: [ 1.391566] firewire_ohci 0000:0d:00.3:
PCI INT D -> GSI 19 (level, low) -> IRQ 19
Sep 15 10:52:17 palnote kernel: [ 1.567717] ahci 0000:00:1f.2: PCI INT
B -> GSI 19 (level, low) -> IRQ 19
Sep 15 10:52:17 palnote kernel: [ 11.827204] snd_hdsp 0000:05:00.0: PCI
INT A -> GSI 19 (level, low) -> IRQ 19
so, perhaps the hdsp sharing IRQ 19 with ohci and ahci is not a good
thing?? but that's the same in BOTH boots, so i dunno....
anything else i should look for, or any other info you might be interested
in seeing?
big thanks for any help on this, fernando!!
cheers!
.pltk.
i've
just switched over to jack1... it fails as well, with a different
error message (don't know if this sheds any more light on the
situation!):
plutek@palnote:~$ jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben
Hohn
and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ...
hw:0,0|hw:0,0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2
periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
ALSA: prepare error for playback on "hw:0,0" (Input/output error)
DRIVER NT: could not run driver cycle
**** alsa_pcm: xrun of at least 0.013 msecs
thanks again for any help on this!
ooops... getting rid of the extra -p flag, and going with -p1024, i get
this:
plutek@palnote:~$ jackd -dalsa -r44100 -p1024 -n2 -D -Chw:0,0 -Phw:0,0&
[1] 3580
plutek@palnote:~$ jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben
Hohn
and others.
jackd 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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ...
hw:0,0|hw:0,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2
periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
jackd watchdog: timeout - killing jackd
9:43 p.m.
New subject: hdsp not happy with recent kernels
did some observing...
when i put snd_hdsp in the RTIRQ_NAME_LIST in the rtirq config, neither
priorities nor IRQs change. however...
for ALL kernels under which jack fails:
/etc/init.d/rtirq status
shows irq/19-snd_hdsp AND irq/19-firewire
and for the one kernel under which jack works:
/etc/init.d/rtirq status
shows irq/19-snd_hdsp and a DIFFERENT irq for firewire
this seems significant.
and... how can i ensure firewire gets a different irq?
for now, i'll try killing the firewire module, since i don't use anything
firewire at the moment.
cheers!
.pltk.
4481
days inactive
4482
days old
linux-audio-user@lists.linuxaudio.org
8 comments
4 participants
participants (4)
-
Fernando Lopez-Lezcano -
Peter Lutek -
peter＠peterlutek.com
-
Ralf Mardorf