From: David Woodhouse <dwmw2@infradead.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: john stultz <johnstul@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org,
Paul TBBle Hampson <Paul.Hampson@Pobox.com>,
torvalds@linux-foundation.org
Subject: Re: Make sure we populate the initroot filesystem late enough
Date: Wed, 28 Feb 2007 10:13:04 +0000 [thread overview]
Message-ID: <1172657584.3452.51.camel@pmac.infradead.org> (raw)
In-Reply-To: <1172644987.11949.90.camel@localhost.localdomain>
On Wed, 2007-02-28 at 07:43 +0100, Benjamin Herrenschmidt wrote:
> I wouldn't be that sure ... I've had problems in the past with PMU based
> cpufreq... looks like flushing all caches and hard-resetting the
> processor on the fly when there can be pending DMAs might be a source of
> trouble... especially on CPUs that don't have working cache flush HW
> assist.
I've seen it on a PowerMac3,1 (400MHz G4) where we don't have cpufreq.
I've also seen it on the latest 1.5GHz Mac Mini, and on my shinybook.
They all fall over with the latest kernel, although the shinybook only
does so immediately when booted with mem=512M. The shinybook does crash
later with new kernels though; I don't yet know why. It could be the
same thing, or it could be something different. That one seemed to
appear between Fedora's 2.6.19-1.2913 and 2.6.19-1.2914 kernels, where
we did nothing but turned CONFIG_SYSFS_DEPRECATED on.
I don't blame cpufreq. At various times I've been equally convinced that
it was due to CONFIG_KPROBES, and Linus' initrd-moving patch.
--
dwmw2
next prev parent reply other threads:[~2007-02-28 10:13 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
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 [this message]
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=1172657584.3452.51.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=Paul.Hampson@Pobox.com \
--cc=benh@kernel.crashing.org \
--cc=johnstul@us.ibm.com \
--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).