[Openvortex-dev] address@hidden: Re: [Alsa-devel] Unexpected hw_pointer value]

[Ryan Underwood]

Manuel,

Do you think this information might help solve the hw_pointer spam
somehow?

Ryan

----- Forwarded message from Takashi Iwai <address@hidden> -----

From: Takashi Iwai <address@hidden>
Date: Mon, 06 Oct 2003 13:07:52 +0200
Subject: Re: [Alsa-devel] Unexpected hw_pointer value
To: Ryan Underwood <address@hidden>
Cc: address@hidden
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) 
FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 13) (Rational 
FORTRAN) (i386-suse-linux)

At Sat, 4 Oct 2003 16:58:12 -0500,
Ryan Underwood wrote:
> 
> 
> Hi,
> 
> On Sat, Oct 04, 2003 at 11:12:00PM +0200, Jon wrote:
> > hello,
> > 
> > i have an ES1983S Maestro-3i on a c600 dell laptop
> > i got this message in syslog :
> > 
> > ALSA sound/core/pcm_lib.c:214: Unexpected hw_pointer value (stream = 0,
> > delta: -944, max jitter = 1024): wrong interrupt acknowledge?
> 
> I get a lot of these as well with the in-development Aureal driver.  I'm
> also curious as to what they mean.  (I seem to be the only person having
> the problem).  They mostly occur while playing music in xmms with xmms
> alsa plugin.  They fill up syslog with hundreds of megabytes. :)

in alsa pcm, there are two routes to update the hwptr, namely,
snd_pcm_update_hw_ptr_interrupt() and snd_pcm_update_hw_ptr().
the former is called through snd_pcm_period_elapsed(), which is
originally called from the device's interrupt handler.
meanwhile, the latter is called from timer tick and some ioctl
handlers (reset, read, write).

these routines are quite similar, and we can clean up them more...


Takashi


----- End forwarded message -----

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253