linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org, torvalds@linux-foundation.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Make sure we populate the initroot filesystem late enough
Date: Mon, 26 Feb 2007 11:27:47 -0800	[thread overview]
Message-ID: <1172518068.15970.6.camel@localhost> (raw)
In-Reply-To: <1172448057.3971.9.camel@shinybook.infradead.org>

On Sun, 2007-02-25 at 19:00 -0500, David Woodhouse wrote:
> On Mon, 2006-12-11 at 20:59 +0000, Linux Kernel Mailing List wrote:
> > 
> >     Make sure we populate the initroot filesystem late enough
>
> This seems to be what's triggering the apparent memory corruption we've
> been seeing recently -- in the case of the Fedora kernel it manifests
> itself as a BUG() in cache_alloc_refill() when the pmac ide driver
> initialises.
> 
> Another report was at http://lkml.org/lkml/2006/12/17/4
> 
> We've been seeing it on a Mac Mini too, and I managed to reproduce it on
> my shinybook this evening by booting with 'mem=512M'.

Just for reference (as its not in the thread linked above), this issue
disappeared for me after some config changes (I somehow changed my
selection when I backtracked and then moved forward w/ git bisect).

I've not been able to reproduce it since, but I know others (BCC'ed on
this note) have seen it and might prod them to come forth with details
(and broken .config files)

thanks
-john

  parent reply	other threads:[~2007-02-26 19:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200612112059.kBBKx1j7022473@hera.kernel.org>
2007-02-26  0:00 ` Make sure we populate the initroot filesystem late enough David Woodhouse
2007-02-26  0:24   ` Linus Torvalds
2007-02-26  0:45     ` David Woodhouse
2007-02-26  1:17     ` David Woodhouse
2007-02-26  3:45       ` Linus Torvalds
2007-02-26  4:01         ` David Woodhouse
2007-02-26  4:13           ` Linus Torvalds
2007-02-26 16:24             ` David Woodhouse
2007-02-26  6:59           ` William Lee Irwin III
2007-02-26 15:53           ` Benjamin Herrenschmidt
2007-02-26 16:00             ` Segher Boessenkool
2007-02-26 16:44           ` Milton Miller
2007-02-26 20:57             ` David Woodhouse
2007-02-26 21:17               ` Linus Torvalds
2007-02-27  6:46                 ` Benjamin Herrenschmidt
2007-02-26 15:51       ` Benjamin Herrenschmidt
2007-02-26 20:51         ` Kumar Gala
2007-02-26 19:27   ` john stultz [this message]
2007-02-26 22:27     ` Paul TBBle Hampson
2007-02-27  6:48       ` Benjamin Herrenschmidt
2007-02-27 11:58         ` Segher Boessenkool
2007-02-28  6:43           ` Benjamin Herrenschmidt
2007-02-28 10:13             ` David Woodhouse
2007-03-01  0:30               ` Michael Ellerman
2007-03-12 23:01                 ` Paul TBBle Hampson
2007-03-13  3:03                   ` Kumar Gala
2007-03-13  7:03                   ` Benjamin Herrenschmidt
2007-03-16  7:20                     ` Paul TBBle Hampson

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=1172518068.15970.6.camel@localhost \
    --to=johnstul@us.ibm.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).