public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jan Niehusmann <jan@gondor.com>
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, 05 Apr 2006 14:56:44 +0200	[thread overview]
Message-ID: <s5hodzgnptf.wl%tiwai@suse.de> (raw)
In-Reply-To: <s5hslosnqm6.wl%tiwai@suse.de>

At Wed, 05 Apr 2006 14:39:29 +0200,
I wrote:
> 
> At Wed, 5 Apr 2006 14:15:38 +0200,
> Jan Niehusmann wrote:
> > 
> > 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.
> 
> Did you have any special setting (e.g. oss proc file)?

How about the patch below?


Takashi


diff --git a/sound/core/oss/pcm_oss.c b/sound/core/oss/pcm_oss.c
index 91114c7..c951cf8 100644
--- a/sound/core/oss/pcm_oss.c
+++ b/sound/core/oss/pcm_oss.c
@@ -1682,7 +1682,7 @@ static void snd_pcm_oss_init_substream(s
 	substream->oss.setup = *setup;
 	if (setup->nonblock)
 		substream->ffile->f_flags |= O_NONBLOCK;
-	else
+	else if (setup->block)
 		substream->ffile->f_flags &= ~O_NONBLOCK;
 	runtime = substream->runtime;
 	runtime->oss.params = 1;

  reply	other threads:[~2006-04-05 12:56 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
2006-04-05 12:39                   ` Takashi Iwai
2006-04-05 12:56                     ` Takashi Iwai [this message]
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=s5hodzgnptf.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jan@gondor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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