From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: cc@ccrma.Stanford.EDU, Takashi Iwai <tiwai@suse.de>,
alsa-devel@lists.sourceforge.net, Ingo Molnar <mingo@elte.hu>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Re: 2.6.15-rt20, "bad page state", jackd (alsa 1.0.10 vs. recent kernels)
Date: Mon, 13 Mar 2006 13:42:06 +1100 [thread overview]
Message-ID: <4414DBFE.1050400@yahoo.com.au> (raw)
In-Reply-To: <1142210977.7471.27.camel@cmn3.stanford.edu>
Fernando Lopez-Lezcano wrote:
> Well, I found it. Finally. I diffed memalloc.c in the alsa kernel tree
> with alsa stable 1.0.10 and googled for the obvious two chunks that
> stood out :-)
>
Well, good work on tracking it down. I guess you should forward
forward your patch to the ALSA guys.
[snip]
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: cc@ccrma.Stanford.EDU, Takashi Iwai <tiwai@suse.de>,
alsa-devel@lists.sourceforge.net, Ingo Molnar <mingo@elte.hu>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Alsa-devel] Re: 2.6.15-rt20, "bad page state", jackd (alsa 1.0.10 vs. recent kernels)
Date: Mon, 13 Mar 2006 13:42:06 +1100 [thread overview]
Message-ID: <4414DBFE.1050400@yahoo.com.au> (raw)
In-Reply-To: <1142210977.7471.27.camel@cmn3.stanford.edu>
Fernando Lopez-Lezcano wrote:
> Well, I found it. Finally. I diffed memalloc.c in the alsa kernel tree
> with alsa stable 1.0.10 and googled for the obvious two chunks that
> stood out :-)
>
Well, good work on tracking it down. I guess you should forward
forward your patch to the ALSA guys.
[snip]
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-03-13 2:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 19:36 2.6.15-rt20, "bad page state", jackd Fernando Lopez-Lezcano
2006-03-08 21:48 ` Fernando Lopez-Lezcano
2006-03-09 0:30 ` Fernando Lopez-Lezcano
2006-03-09 2:19 ` Fernando Lopez-Lezcano
2006-03-09 8:47 ` Heiko Carstens
2006-03-09 9:05 ` Nick Piggin
2006-03-09 21:08 ` Fernando Lopez-Lezcano
2006-03-09 22:57 ` Nick Piggin
2006-03-10 2:47 ` Fernando Lopez-Lezcano
2006-03-10 2:47 ` Fernando Lopez-Lezcano
2006-03-10 5:08 ` Nick Piggin
2006-03-10 18:50 ` [Alsa-devel] " Fernando Lopez-Lezcano
2006-03-10 23:10 ` Fernando Lopez-Lezcano
2006-03-10 23:10 ` [Alsa-devel] " Fernando Lopez-Lezcano
2006-03-11 0:01 ` Nick Piggin
2006-03-13 0:49 ` Re: 2.6.15-rt20, "bad page state", jackd (alsa 1.0.10 vs. recent kernels) Fernando Lopez-Lezcano
2006-03-13 0:49 ` [Alsa-devel] " Fernando Lopez-Lezcano
2006-03-13 2:42 ` Nick Piggin [this message]
2006-03-13 2:42 ` Nick Piggin
2006-03-13 3:26 ` Fernando Lopez-Lezcano
2006-03-13 3:26 ` [Alsa-devel] " Fernando Lopez-Lezcano
2006-03-13 3:31 ` Lee Revell
2006-03-13 3:31 ` [Alsa-devel] " Lee Revell
2006-03-13 3:39 ` Fernando Lopez-Lezcano
2006-03-13 3:53 ` Lee Revell
2006-03-13 3:53 ` [Alsa-devel] " Lee Revell
2006-03-13 11:05 ` Takashi Iwai
2006-03-13 17:33 ` Fernando Lopez-Lezcano
2006-03-13 17:41 ` Takashi Iwai
2006-03-13 9:25 ` Ingo Molnar
2006-03-13 9:25 ` [Alsa-devel] " Ingo Molnar
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=4414DBFE.1050400@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=alsa-devel@lists.sourceforge.net \
--cc=cc@ccrma.Stanford.EDU \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nando@ccrma.Stanford.EDU \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.