From: Rene Herman <rene.herman@keyaccess.nl>
To: Bob Tracy <rct@frus.com>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA devel <alsa-devel@alsa-project.org>,
Michael Cree <mcree@orcon.net.nz>,
linux-kernel@vger.kernel.org,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-alpha@vger.kernel.org, Krzysztof Helt <krzysztof.h1@wp.pl>
Subject: Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha
Date: Tue, 11 Mar 2008 16:17:32 +0100 [thread overview]
Message-ID: <47D6A28C.4060804@keyaccess.nl> (raw)
In-Reply-To: <20080311140718.8B3ABDBA2@gherkin.frus.com>
[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]
On 11-03-08 15:07, Bob Tracy wrote:
> Both native ALSA and emulated OSS playback are broken based on last
> night's testing. Just to rule out sound hardware issues, this morning I
> built a 2.6.25-rc4 kernel with OSS (sb driver), and that seems to be
> working fine.
Okay... From your testing report:
>> $ sox foo.wav -t alsa default
>
> Playback results in infinite loop over the first quarter second or so
> of audio. Using "aplay" results in same looping behavior over a longer
> segment of audio -- maybe a half second.
This is behaviour consistent with the IRQ being dead ...
>> > $ sox foo.wav -t ossdsp /dev/dsp
>
> Identical results to using "play" (as expected): for the 50K ".wav"
> file, I hear the entire file approx. 1.8 times.
... and this isn't. Worse yet, we have a conflicting report from Michael
where things are fine while using aplay and I'm seeing nothing particularly
suspicious recently. I suppose it used to work and I suppose the behaviour
you are describing above is 100% repeatable?
Given that you can use aplay -- probably no difference with "aplay -M" ?
To get to the bottom of this we might need to get a specific failed version
(for readers, it's not been verified that this is a regression since 2.6.24)
but we can try to get lucky first.
The most recent change to sound/isa/es18xx.c that's not utterly impossible
to have made a difference is 1bc9eed379399484d3f5d5a0834674983969bc1,
"es18xx: Enable wavetable input from ESS chips". I don't know if you're a
GIT user. If you are, you can revert it simply with
$ git revert 1bc9eed3
If you're not a GIT user, applying the attached should work. Unlikely, but
as said, we can try.
> I tried a few rmmod/insmod cycles with different values for dma2.
> Results as follows:
>
> (a) dma2=1 (== dma1): no change
> (b) dma2 option omitted : no change
> (c) dma2=-1 : probe failed
Okay. A and B seem to at least confirm it's not the 16-bit DMA.
Rene.
[-- Attachment #2: es18xx_revert_wavetable_input.diff --]
[-- Type: text/plain, Size: 762 bytes --]
commit 8fa1de6349913b63d8ebfb27003b7045eeb9f12a
Author: Rene Herman <rene.herman@gmail.com>
Date: Tue Mar 11 15:52:36 2008 +0100
Revert "[ALSA] es18xx: Enable wavetable input from ESS chips"
This reverts commit 1bc9eed379399484d3f5d5a0834674983969bc1e.
diff --git a/sound/isa/es18xx.c b/sound/isa/es18xx.c
index 90498e4..865ab1d 100644
--- a/sound/isa/es18xx.c
+++ b/sound/isa/es18xx.c
@@ -1441,8 +1441,6 @@ static int __devinit snd_es18xx_initialize(struct snd_es18xx *chip)
snd_es18xx_write(chip, 0xB2, 0x50);
/* Enable MPU and hardware volume interrupt */
snd_es18xx_mixer_write(chip, 0x64, 0x42);
- /* Enable ESS wavetable input */
- snd_es18xx_mixer_bits(chip, 0x48, 0x10, 0x10);
}
else {
int irqmask, dma1mask, dma2mask;
next prev parent reply other threads:[~2008-03-11 15:17 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 3:58 [regression] 2.6.25-rc4 snd-es18xx broken on Alpha Bob Tracy
2008-03-09 15:34 ` Ivan Kokshaysky
2008-03-09 23:57 ` Bob Tracy
2008-03-10 7:34 ` Michael Cree
2008-03-10 15:17 ` Rene Herman
2008-03-10 15:21 ` Rene Herman
2008-03-10 16:21 ` Bob Tracy
2008-03-10 16:56 ` Rene Herman
2008-03-10 17:14 ` Takashi Iwai
2008-03-10 19:29 ` [alsa-devel] " Rene Herman
2008-03-10 22:22 ` Bob Tracy
2008-03-10 22:33 ` Rene Herman
2008-03-11 14:07 ` [alsa-devel] " Bob Tracy
2008-03-11 15:17 ` Rene Herman [this message]
2008-03-11 18:08 ` Bob Tracy
2008-03-11 20:00 ` [alsa-devel] " Michael Cree
2008-03-11 20:34 ` Bob Tracy
2008-03-12 14:40 ` Bob Tracy
2008-03-12 19:34 ` Rene Herman
2008-03-12 20:31 ` [alsa-devel] " Bob Tracy
2008-03-12 21:12 ` Rene Herman
2008-03-13 4:24 ` Bob Tracy
2008-03-17 22:00 ` Rene Herman
2008-03-18 3:24 ` [alsa-devel] " Bob Tracy
2008-03-18 3:54 ` Michael Cree
2008-03-23 10:40 ` Michael Cree
2008-03-24 18:15 ` Rene Herman
2008-03-24 23:56 ` Michael Cree
2008-03-25 0:29 ` [alsa-devel] " Rene Herman
2008-03-25 1:22 ` Michael Cree
2008-03-25 2:22 ` Rene Herman
2008-03-30 5:18 ` Bob Tracy
2008-03-30 10:02 ` Michael Cree
2008-03-30 9:13 ` [alsa-devel] " Michael Cree
2008-03-25 2:46 ` Rene Herman
2008-03-30 21:07 ` Bob Tracy
2008-03-30 21:11 ` Michael Cree
2008-03-30 21:18 ` Bob Tracy
2008-03-30 4:24 ` Bob Tracy
2008-03-30 22:09 ` [alsa-devel] " Bob Tracy
2008-03-14 13:13 ` Bob Tracy
2008-03-15 1:18 ` Tyson Whitehead
2008-03-17 22:04 ` Rene Herman
2008-03-18 13:55 ` Tyson Whitehead
2008-03-18 22:57 ` Rene Herman
[not found] ` <s5hskypnwp8.wl%tiwai@suse.de>
2008-03-18 14:16 ` Tyson Whitehead
2008-03-29 6:42 ` Bob Tracy
2008-03-29 12:09 ` [alsa-devel] " Rene Herman
2008-03-30 16:14 ` Ivan Kokshaysky
2008-03-30 21:17 ` Michael Cree
2008-03-30 20:24 ` [alsa-devel] " Bob Tracy
2008-03-12 22:48 ` Rafael J. Wysocki
2008-03-23 9:48 ` Michael Cree
2008-03-11 5:36 ` Bob Tracy
2008-03-10 15:08 ` Rene Herman
-- strict thread matches above, loose matches on Subject: below --
2008-03-14 23:33 Bob Tracy
2008-04-01 18:07 ` [alsa-devel] " Tyson Whitehead
2008-04-01 18:29 ` Rene Herman
2008-04-01 18:31 ` Rene Herman
2008-04-01 18:34 ` Rene Herman
2008-04-01 19:07 ` Rene Herman
2008-04-01 20:26 ` Bob Tracy
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=47D6A28C.4060804@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=ink@jurassic.park.msu.ru \
--cc=krzysztof.h1@wp.pl \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcree@orcon.net.nz \
--cc=rct@frus.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).