Skip to contentSkip to conversation

Unexpected hw_pointer value

DISCUSSION Jon 5 participants 6 messages Oct 4, 2003 – Oct 6, 2003

lore
Share & tools
lore

Jon

author
#0 lore raw

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?

what does it mean ?

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

#1 lore raw

Hi,

Quoted 7 lines · Jon

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. :)

Thanks,

Signature · 7 lines
Ryan Underwood, <nemesis at icequake.net>, icq=10317253


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
#2 lore raw
Quoted 7 lines · On Sat, 4 Oct 2003 16:58:12 -0500 Ryan Underwood <[email protected]>…
Quoted 5 lines

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.

Me too, with the Echoaudio driver. I had quick look at the code that prints that warning and I couldn't see anything obviously wrong. btw I can't figure out why it happens. It seems harmless, so I left the question on hold.

Quoted 3 lines

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. :)

It happens with any program and it depends a lot on the period number and period size settings.

--
Giuliano.

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

#3 lore raw
Quoted 15 lines · Giuliano Pochini
Quoted 7 lines · On Sat, 4 Oct 2003 16:58:12 -0500 Ryan Underwood <[email protected]>…
Quoted 5 lines

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.

Me too, with the Echoaudio driver. I had quick look at the code that prints that warning and I couldn't see anything obviously wrong. btw I can't figure out why it happens. It seems harmless, so I left the question on hold.

Quoted 6 lines
Quoted 3 lines

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. :)

It happens with any program and it depends a lot on the period number and period size settings.

We added these sanity checks for debugging purposes, but if they occur too much, there's something bad with driver or hardware.

Basically, we have only information from last interrupt position and the actual position in the ring buffer. We need to determine the new "absolute" position. To detect the wrap point, we compute the delta value for the new and old position and if delta is greater than buffer_size / 2, we correct the new position by adding buffer_size. Otherwise we take value as error, because we ask driver to acknowledge interrupts after period_size not before. Note that some interrupt might be lost.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

author
#4 lore raw
Quoted 11 lines · Jaroslav Kysela

We added these sanity checks for debugging purposes, but if they occur too much, there's something bad with driver or hardware.

Basically, we have only information from last interrupt position and the actual position in the ring buffer. We need to determine the new "absolute" position. To detect the wrap point, we compute the delta value for the new and old position and if delta is greater than buffer_size / 2, we correct the new position by adding buffer_size. Otherwise we take value as error, because we ask driver to acknowledge interrupts after period_size not before. Note that some interrupt might be lost.

Quoted 1 line

Jaroslav

my hardware seems really bad : ES1983S Maestro-3i on a dell c600. i experience lots of hardware freeze (bios does not respond) caused the driver/card with oss or alsa.

i'm kind of desperate with my sound card :(

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

#5 lore raw
In reply to Ryan Underwood

At Sat, 4 Oct 2003 16:58:12 -0500,

Quoted 10 lines · Ryan Underwood

Hi,

Quoted 5 lines · Jon

hello,

i have an ES1983S Maestro-3i on a c600 dell laptop i got this message in syslog :

Quoted 7 lines
Quoted 2 lines

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