From: Lee Revell <rlrevell@joe-job.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
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: Sun, 12 Mar 2006 22:31:55 -0500 [thread overview]
Message-ID: <1142220716.25358.273.camel@mindpipe> (raw)
In-Reply-To: <1142220385.7471.46.camel@cmn3.stanford.edu>
On Sun, 2006-03-12 at 19:26 -0800, Fernando Lopez-Lezcano wrote:
> On Mon, 2006-03-13 at 13:42 +1100, Nick Piggin wrote:
> > 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.
>
> It fixes 1.0.10 with recent kernels but I guess 1.0.10 is old so maybe
> it will not get patched (just a guess) - what would that be, 1.0.10a?.
> 1.0.11rc3 did not trigger the problem in a quick test but I could swear
> it did before, I'll have to retest again tomorrow (maybe it was
> happening with a different card).
Older ALSA with a newer kernel has never been supported. Why would you
want to replace the ALSA in the kernel with an old version?
Lee
-------------------------------------------------------
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
next prev parent reply other threads:[~2006-03-13 3:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1141846564.5262.20.camel@cmn3.stanford.edu>
[not found] ` <20060309084746.GB9408@osiris.boeblingen.de.ibm.com>
[not found] ` <1141938488.22708.28.camel@cmn3.stanford.edu>
[not found] ` <4410B2D7.4090806@yahoo.com.au>
2006-03-10 2:47 ` 2.6.15-rt20, "bad page state", jackd 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-11 0:01 ` [Alsa-devel] " 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 2:42 ` Nick Piggin
2006-03-13 3:26 ` Fernando Lopez-Lezcano
2006-03-13 3:31 ` Lee Revell [this message]
2006-03-13 3:39 ` [Alsa-devel] " Fernando Lopez-Lezcano
2006-03-13 3:53 ` Lee Revell
2006-03-13 11:05 ` [Alsa-devel] " Takashi Iwai
2006-03-13 17:33 ` Fernando Lopez-Lezcano
2006-03-13 17:41 ` Takashi Iwai
2006-03-13 9:25 ` 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=1142220716.25358.273.camel@mindpipe \
--to=rlrevell@joe-job.com \
--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=nickpiggin@yahoo.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox