From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jan Niehusmann <jan@gondor.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: Tue, 4 Apr 2006 21:31:52 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.63.0604042129170.12127@deepthought.mydomain> (raw)
In-Reply-To: <Pine.LNX.4.63.0604042058560.11426@deepthought.mydomain>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 455 bytes --]
On Tue, 4 Apr 2006, Ken Moffat wrote:
> On Tue, 4 Apr 2006, Takashi Iwai wrote:
>
> > What happens if you copy the whole subtree linux/sound and
> > linux/include/sound from 2.6.16?
>
> also needs include/linux/sound.h (building at the moment)
>
I've been using it now to play sound for 15 or 20 minutes while
browsing heavily - looks as if the problem is in the sound subtree.
Sorry.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2006-04-04 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 21:01 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 [this message]
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=Pine.LNX.4.63.0604042129170.12127@deepthought.mydomain \
--to=zarniwhoop@ntlworld.com \
--cc=alsa-devel@alsa-project.org \
--cc=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
all inboxes | Powered by JetHome®