public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: 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: 2.6.15-rt20, "bad page state", jackd
Date: Fri, 10 Mar 2006 16:08:12 +1100	[thread overview]
Message-ID: <441109BC.9070705@yahoo.com.au> (raw)
In-Reply-To: <1141958866.22708.69.camel@cmn3.stanford.edu>

Fernando Lopez-Lezcano wrote:
> On Fri, 2006-03-10 at 09:57 +1100, Nick Piggin wrote:
> 
>>Fernando Lopez-Lezcano wrote:

>>Can you test with the latest mainline -git snapshot, or is it only
>>the -rt tree that causes the warnings?
> 
> 
> I found something strange although I don't know why it happens yet:
> 
>   Fedora Core 4 kernel (2.6.15 + patches) works fine.
>   Fedora Core 4 kernel + -rt21, [ahem... sorry], works fine.
>   Fedora Core 4 kernel + -rt21 + alsa kernel modules from 1.0.10 or
>      1.0.11rc3, fails[*]
>   Plain vanilla 2.6.15 + -rt21, works fine
>   Plain vanilla 2.6.15 + -rt21 + alsa kernel modules from 1.0.10 or
>      1.0.11rc3, fails[*]
> 
> So, it looks like it is some weird interaction between kernel modules
> that were not compiled as part of the kernel and the kernel itself. The
> "updated" modules are installed in a separate location (not on top of
> the built in kernel modules) and are found before the ones in the kernel
> tree.
> 
> I have been building this combination for a long long time with no
> problems, I don't know what might have happened that changed things.
> 
> Could be:
> - configuration problems?

No. It shouldn't do this even if there is a configuration problem.

> - the alsa tree is somehow incompatible with the kernel alsa tree, is
>   that even possible?
> 

Yes. Most likely this. It should be fixed before the new ALSA code is
pushed upstream.

It is probably not so much a matter of somebody breaking the ALSA code
as that it hasn't been updated for the new kernel refcounting rules.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-03-10  5:08 UTC|newest]

Thread overview: 23+ 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  5:08         ` Nick Piggin [this message]
2006-03-10 18:50           ` [Alsa-devel] " Fernando Lopez-Lezcano
2006-03-10 23:10             ` Fernando Lopez-Lezcano
2006-03-11  0:01             ` Nick Piggin
2006-03-13  0:49               ` [Alsa-devel] 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
2006-03-13  3:39                       ` Fernando Lopez-Lezcano
2006-03-13  3:53                         ` 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

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=441109BC.9070705@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=alsa-devel@lists.sourceforge.net \
    --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 \
    /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