public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Martijn Uffing <mp3project@cam029208.student.utwente.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG/WARNING?] 2.5.57 ALSA sound/core/pcm_lib.c
Date: Wed, 15 Jan 2003 10:31:38 +0100	[thread overview]
Message-ID: <s5h7kd6yd1h.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301150122520.13717-100000@cam029208.student.utwente.nl>

At Wed, 15 Jan 2003 01:27:37 +0100 (CET),
Martijn Uffing wrote:
> 
> Ave people.
> 
> In 2.5.57 I get a bug/warning  when I'm using xmms. Xmms is configured for 
> OSS output,and the kernel is configured for ALSA sound including OSS emulation.
> 
> The following message is found in dmesg.
> "ALSA sound/core/pcm_lib.c:123: Unexpected hw_pointer value (stream = 0, 
> delta: -280, max jitter = 8192): wrong interrupt acknowledge? "
> I tried to reproduce the error and got another one. Only know the 
> delta 
> is -1008.
> 
> I didn't notice this messages until I looked in dmesg. So no hickup or 
> something from xmms. The song played fine.
> So the question is: Is this just a warning or a bug?

the message appears when the period (fragment) has not been processed
enough fast as expected.  a typical reason is the delay of hardware
interrupts, but this could be, of course, a bug of the driver, too.

this would be a bit problem if the application uses small numbers of
periods.  but in the case of xmms, it won't be serious.
if you don't see such a message not too often, you can ignore it...
(at least, i've never heard about this kind of bug on ens1371 driver.)

-- 
Takashi Iwai <tiwai@suse.de>		SuSE Linux AG - www.suse.de
ALSA Developer				ALSA Project - www.alsa-project.org

      parent reply	other threads:[~2003-01-15  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15  0:27 [BUG/WARNING?] 2.5.57 ALSA sound/core/pcm_lib.c Martijn Uffing
2003-01-15  0:52 ` Arador
2003-01-15  9:31 ` Takashi Iwai [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5h7kd6yd1h.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mp3project@cam029208.student.utwente.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox