1 Oct
2004
1 Oct
'04
1:21 p.m.
Hi all.
Does anyone have any ideas on what this message means:
Unexpected hw_pointer value [1] (stream = 0, delta: -106, max jitter = 128): wrong
interrupt acknowledge?
It seems to accompany the xruns I get with the 2.6.9-rc2-mm4-VP-S7 kernel.
Otherwise, this gives the best results I've yet got with jack.
Incidentally, has anyone ever had an xrun-free system with
jackd -R -d alsa -p64 ?
Cheers,
John
1 Oct
1 Oct
1:33 p.m.
On Sat, 2 Oct 2004 00:16:59 +0930
John Hedditch <jhedditc(a)physics.adelaide.edu.au> wrote:
Hi all.
Does anyone have any ideas on what this message means:
Unexpected hw_pointer value [1] (stream = 0, delta: -106, max jitter =
128): wrong interrupt acknowledge?
It seems to accompany the xruns I get with the 2.6.9-rc2-mm4-VP-S7
kernel. Otherwise, this gives the best results I've yet got with jack.
Incidentally, has anyone ever had an xrun-free system with
jackd -R -d alsa -p64 ?
Hi
i saw these errors when my jack tmpdir was not mounted on a tmpfs mount.
The delays which this caused in the jack client caused errors like the
above.
http://www.affenbande.org/~tapas/wiki/index.php?Jackd%20and%20tmpfs%20%28or…
flo
2 Oct
2 Oct
5:11 a.m.
OK. The 'Unexpected pointer ...' messages seem to be related to IRQ threading,
so turning them off fixed that. I still get xruns when opening or closing
hydrogen or ardour. Also, ZynAddSubFX generates huge amounts of them.
Any ideas?
dmesg gives me this:
XRUN: pcmC0D0p
[<c0302c7c>] snd_pcm_period_elapsed+0x2a5/0x408
[<c0118ffa>] effective_prio+0x8/0x53
[<c0330fff>] snd_ice1712_interrupt+0xe/0x229
[<c0114c18>] mcount+0x14/0x18
[<c0331194>] snd_ice1712_interrupt+0x1a3/0x229
[<c0131eb2>] handle_IRQ_event+0x35/0x68
[<c0107a23>] do_IRQ+0xec/0x1bd
[<c0105b24>] common_interrupt+0x18/0x20
[<c0119db6>] __wake_up+0x52/0x8a
[<c039e425>] unix_write_space+0xa0/0xa2
[<c033eefb>] sock_wfree+0x0/0x4d
[<c033ef46>] sock_wfree+0x4b/0x4d
[<c034034d>] __kfree_skb+0x70/0xe7
[<c03a0b82>] unix_stream_recvmsg+0x1f5/0x411
[<c0114c18>] mcount+0x14/0x18
[<c033c797>] sock_aio_read+0xf2/0x106
[<c0159c05>] do_sync_read+0x11/0xd9
[<c0114c18>] mcount+0x14/0x18
[<c0159ca1>] do_sync_read+0xad/0xd9
[<c015abee>] fput+0x8/0x1e
[<c0114c18>] mcount+0x14/0x18
[<c0131a4d>] autoremove_wake_function+0x0/0x57
[<c0159ce1>] vfs_read+0x14/0x111
[<c0114c18>] mcount+0x14/0x18
[<c0159daa>] vfs_read+0xdd/0x111
[<c015a018>] sys_read+0x50/0x7a
[<c01051b7>] syscall_call+0x7/0xb
XRUN: pcmC0D0p
[<c0302c7c>] snd_pcm_period_elapsed+0x2a5/0x408
[<c0118ffa>] effective_prio+0x8/0x53
[<c0330fff>] snd_ice1712_interrupt+0xe/0x229
[<c0114c18>] mcount+0x14/0x18
[<c0331194>] snd_ice1712_interrupt+0x1a3/0x229
[<c0131eb2>] handle_IRQ_event+0x35/0x68
[<c0107a23>] do_IRQ+0xec/0x1bd
[<c0105b24>] common_interrupt+0x18/0x20
On Fri, Oct 01, 2004 at 05:30:45PM +0200, Florian Schmidt wrote:
On Sat, 2 Oct 2004 00:16:59 +0930
John Hedditch <jhedditc(a)physics.adelaide.edu.au> wrote:
Hi all.
Does anyone have any ideas on what this message means:
Unexpected hw_pointer value [1] (stream = 0, delta: -106, max jitter =
128): wrong interrupt acknowledge?
It seems to accompany the xruns I get with the 2.6.9-rc2-mm4-VP-S7
kernel. Otherwise, this gives the best results I've yet got with jack.
Incidentally, has anyone ever had an xrun-free system with
jackd -R -d alsa -p64 ?
Hi
i saw these errors when my jack tmpdir was not mounted on a tmpfs mount.
The delays which this caused in the jack client caused errors like the
above.
http://www.affenbande.org/~tapas/wiki/index.php?Jackd%20and%20tmpfs%20%28or…
flo 
6:47 a.m.
On Sat, 2004-10-02 at 02:36, John Hedditch wrote:
OK. The 'Unexpected pointer ...' messages seem
to be related to IRQ threading,
so turning them off fixed that. I still get xruns when opening or closing
hydrogen or ardour. Also, ZynAddSubFX generates huge amounts of them.
Disable XRUN debugging. It is not reliable. The wiki needs to be
updated. Does jackd still report xruns?
Also did you read the WIKI regarding the NPTL problem?
Lee
7:01 a.m.
Sure, but I'm not using NTPL. I will disable xrun debugging and check to
see what that does.
Incidentally, running realfeel2 gives cycle times of up to 7.5 ms. How
can I figure out where they're coming from?
Cheers,
John
On Sat, Oct 02, 2004 at 04:29:50AM -0400, Lee Revell wrote:
On Sat, 2004-10-02 at 02:36, John Hedditch wrote:
OK. The 'Unexpected pointer ...' messages
seem to be related to IRQ threading,
so turning them off fixed that. I still get xruns when opening or closing
hydrogen or ardour. Also, ZynAddSubFX generates huge amounts of them.
Disable XRUN debugging. It is not reliable. The wiki needs to be
updated. Does jackd still report xruns?
Also did you read the WIKI regarding the NPTL problem?
Lee
7:25 a.m.
OK. I've figured some stuff out. Attached is the latency_trace output.
Any ideas?
Cheers,
John
On Sat, Oct 02, 2004 at 04:29:50AM -0400, Lee Revell wrote:
On Sat, 2004-10-02 at 02:36, John Hedditch wrote:
OK. The 'Unexpected pointer ...' messages
seem to be related to IRQ threading,
so turning them off fixed that. I still get xruns when opening or closing
hydrogen or ardour. Also, ZynAddSubFX generates huge amounts of them.
Disable XRUN debugging. It is not reliable. The wiki needs to be
updated. Does jackd still report xruns?
Also did you read the WIKI regarding the NPTL problem?
Lee
9:46 a.m.
On Sat, 02 Oct 2004 04:29:50 -0400
Lee Revell <rlrevell(a)joe-job.com> wrote:
On Sat, 2004-10-02 at 02:36, John Hedditch wrote:
Hmm, why do you think it's not reliable? It might not be too precise but
it still is a useful tool for debugging the alsa drivers themselfes i
can imagine. I for example still experience sporadic xruns independent
of the period size. Sometimes none for 12hs, then 2 per h for a while.
Since the longest non preemptible critical section reported is only
250us, the preempt timing code is not useful in debugging these. But the
xrun traces might give the driver dev some clue about what's going on.
But independent of that, the Wiki really needs to be updated. The xrun
diagnosis needs to be clearly seperated from the preempt timing stuff.
I will get to this tomorrow.
OK. The 'Unexpected pointer ...' messages
seem to be related to IRQ
threading, so turning them off fixed that. I still get xruns when
opening or closing hydrogen or ardour. Also, ZynAddSubFX generates
huge amounts of them.
Disable XRUN debugging. It is not reliable. The wiki needs to be
updated. Does jackd still report xruns?
Also did you read the WIKI regarding the NPTL problem?
Good point.
flo
7391
days inactive
7392
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
3 participants
participants (3)
-
Florian Schmidt -
John Hedditch -
Lee Revell