From: Jan Niehusmann <jan@gondor.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Alsa-devel] Slab corruptions & Re: 2.6.17-rc1: Oops in sound applications
Date: Tue, 4 Apr 2006 19:23:47 +0200 [thread overview]
Message-ID: <20060404172347.GA5968@knautsch.gondor.com> (raw)
In-Reply-To: <s5hlkul72rv.wl%tiwai@suse.de>
On Tue, Apr 04, 2006 at 05:56:36PM +0200, Takashi Iwai wrote:
> At Tue, 4 Apr 2006 15:38:14 +0200,
> Jan Niehusmann wrote:
> >
> > On Mon, Apr 03, 2006 at 10:01:08PM +0100, Ken Moffat wrote:
> > > 1. One line summary:
> > >
> > > On x86, sound applications oops when I refresh the browser.
> >
> > I also see Oopses which seem to be sound related, although I did
> > not notice a correllation with the browser. The oopses below are from
> > 2.6.17-rc1 with additional ipw2200 patches (first one), and from a clean
> > 2.6.17 (second one). The -dirty suffix in the version numbers comes from
> > compiling with make-kpkg, not from actual changes to the source.
>
> Could you try the patch below by OGAWA Hirofumi
> <hirofumi@mail.parknet.co.jp>?
That could be it - I remember having problems to access /dev/dsp prior
to the oops, and (without having read the code) it looks like the patch
is related to some error condition on open(). I'll try the patch.
Jan
next prev parent reply other threads:[~2006-04-04 17:23 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 [this message]
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
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=20060404172347.GA5968@knautsch.gondor.com \
--to=jan@gondor.com \
--cc=linux-kernel@vger.kernel.org \
--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