From: Doug Ledford <dledford@redhat.com>
To: Naren Devaiah <naren@cs.pdx.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i810_audio.c: Clicks while playing audio
Date: Sat, 07 Apr 2001 16:48:30 -0400 [thread overview]
Message-ID: <3ACF7D1E.6EAB0149@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0104071130340.7196-100000@spica.cs.pdx.edu>
Naren Devaiah wrote:
>
> Hi,
>
> On a HP Vectra VL 400 with a i815 motherboard playing a .wav file (haven't
> tried anything else) causes the sound to be played with a lot of periodic
> clicks.
> The kernel is 2.4.3
> dmesg shows:
> Intel 810 + AC97 Audio, version 0.01, 17:25:00 Apr 6 2001
> PCI: Enabling device 00:1f.5 (0000 -> 0001)
> PCI: Found IRQ 9 for device 00:1f.5
> PCI: The same IRQ used for device 00:1f.3
> PCI: Setting latency timer of device 00:1f.5 to 64
> i810: Intel ICH 82801AA found at IO 0x1300 and 0x1200, IRQ 9
> ac97_codec: AC97 Audio codec, id: 0x4352:0x5934 (Cirrus Logic CS4299)
> i810_audio: 9568 bytes in 50 milliseconds
> i810_audio: DMA overrun on send
> i810_audio: DMA overrun on send
>
> lsmod show:
> root@darkstar:~# lsmod
> Module Size Used by
> i810_audio 14084 0
> ac97_codec 7908 0 [i810_audio]
>
> My question is: What does "DMA overrun on send" mean?
It means it sounds like you have an older version of the driver (older here
means "not my latest patch"). I sent my stuff to Alan, and it was in the ac
series kernels, but I don't know what happened to make it into 2.4.3. I'm
fixing one last known bug in the driver tonight, and when I'm done I'll put a
patch against 2.4.3 on my web site and drop a note here.
--
Doug Ledford <dledford@redhat.com> http://people.redhat.com/dledford
Please check my web site for aic7xxx updates/answers before
e-mailing me about problems
prev parent reply other threads:[~2001-04-07 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-07 18:45 i810_audio.c: Clicks while playing audio Naren Devaiah
2001-04-07 20:48 ` Doug Ledford [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=3ACF7D1E.6EAB0149@redhat.com \
--to=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naren@cs.pdx.edu \
/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