From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Unexpected hw_pointer value Date: Mon, 06 Oct 2003 13:07:52 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <20031004211200.GA13137@zeus.homenet> <20031004215812.GI2972@dbz.icequake.net> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20031004215812.GI2972@dbz.icequake.net> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Ryan Underwood Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org 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 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf