From: Jan Niehusmann <jan@gondor.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Ken Moffat <zarniwhoop@ntlworld.com>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [Alsa-devel] Slab corruptions & Re: 2.6.17-rc1: Oops in sound applications
Date: Wed, 5 Apr 2006 14:15:38 +0200 [thread overview]
Message-ID: <20060405121537.GA4807@knautsch.gondor.com> (raw)
In-Reply-To: <s5h1wwcp93l.wl%tiwai@suse.de>
On Wed, Apr 05, 2006 at 01:14:54PM +0200, Takashi Iwai wrote:
> Try the patch below. The change in pcm_native.c may be unnecessary,
> but it's better so.
> If it works, I'll submit the patches with a proper log.
The patch (applied to 2.6.17-rc1) does fix the oops, but sound is still
garbled with twinkle using /dev/dsp.
About this garbled sound: I call an echo service on my asterisk server,
which just echoes back everything I say. Works well using /dev/dsp with
2.6.16, but with 2.6.17-rc1, even with the patch applied, I hear no echo
at all for ~1s. After that, I hear a strongly distorted echo.
If I change the twinkle settings to use the ALSA native devices instead
of /dev/dsp, everything is fine.
Pure playback, eg. with xmms, is fine with 2.6.17-rc1 using /dev/dsp.
Jan
next prev parent reply other threads:[~2006-04-05 12:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 21:01 2.6.17-rc1: Oops in sound applications Ken Moffat
2006-04-04 13:38 ` Slab corruptions & " Jan Niehusmann
2006-04-04 15:56 ` [Alsa-devel] " Takashi Iwai
2006-04-04 17:23 ` Jan Niehusmann
2006-04-04 17:32 ` Ken Moffat
2006-04-04 19:06 ` Jan Niehusmann
2006-04-04 19:12 ` Takashi Iwai
2006-04-04 20:00 ` Ken Moffat
2006-04-04 20:31 ` Ken Moffat
2006-04-04 23:19 ` Jan Niehusmann
2006-04-05 0:28 ` Jan Niehusmann
2006-04-05 9:01 ` Jan Niehusmann
2006-04-05 11:14 ` Takashi Iwai
2006-04-05 12:15 ` Jan Niehusmann [this message]
2006-04-05 12:39 ` Takashi Iwai
2006-04-05 12:56 ` Takashi Iwai
2006-04-05 21:19 ` Ken Moffat
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=20060405121537.GA4807@knautsch.gondor.com \
--to=jan@gondor.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=zarniwhoop@ntlworld.com \
/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