mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Ingo Molnar <mingo@elte.hu>, Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: nando@ccrma.Stanford.EDU, 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: Thu, 09 Mar 2006 13:08:08 -0800	[thread overview]
Message-ID: <1141938488.22708.28.camel@cmn3.stanford.edu> (raw)
In-Reply-To: <20060309084746.GB9408@osiris.boeblingen.de.ibm.com>

On Thu, 2006-03-09 at 09:47 +0100, Heiko Carstens wrote:
> On Wed, Mar 08, 2006 at 11:36:04AM -0800, Fernando Lopez-Lezcano wrote:
> > Hi all, I reported this in mid January (I thought I had sent to the list
> > but the report went to Ingo and Steven off list)
> > 
> > I'm seeing the same problem in 2.6.15-rt21 in some of my machines. After
> > a reboot into the kernel I just login as root in a terminal, start the
> > jackd sound server ("jackd -d alsa -d hw") and when stopping it (just
> > doing a <ctrl>c) I get a bunch of messages of this form:
> > 
> > > Trying to fix it up, but a reboot is needed
> > > Bad page state at __free_pages_ok (in process 'jackd', page c10012fc)
> > 
> > Has anyone else seen this?
> 
> Actually I have a bug report that looks quite the same. Happens on s390x
> with lots of I/O stress. But that is against vanilla 2.6.16-rc4 + additional
> patches. I need to ask to reproduce that with a plain vanilla kernel, so
> that a git bisect search might help to figure out what is wrong.
> Unfortunately it seems to take hours before we hit the bug.

In my case it is completely repeatable. 
Boot, start jackd, stop jackd -> problem appears. 

This does not happen on all computers so it would seem to me it is
related to the sound drivers. I'll try to see if there is a correlation
with the sound card being used. 

Is there anything else I could do to try to help resolve this?
-- Fernando



  parent reply	other threads:[~2006-03-09 21:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 19:36 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 [this message]
2006-03-09 22:57     ` Nick Piggin
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-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=1141938488.22708.28.camel@cmn3.stanford.edu \
    --to=nando@ccrma.stanford.edu \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®