From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: maz@misterjones.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: v2.6.13.4 : Bad page state at prep_new_page when booting with quik
Date: Fri, 21 Oct 2005 14:38:29 +1000 [thread overview]
Message-ID: <1129869509.6265.32.camel@gaston> (raw)
In-Reply-To: <wrpll0of535.fsf@wild-wind.fr.eu.org>
On Thu, 2005-10-20 at 19:53 +0200, Marc Zyngier wrote:
> List,
>
> I finally managed to bring back to life an old Apus 3000/200 (PowerMac
> 6400 clone, 603e@200, no L2 cache, 144MB RAM). Kernel is vanilla
> 2.6.13.4, userland is Debian Sarge.
>
> The strange thing is : while the machine boots perfectly with BootX,
> it fills the console with messages like this when booted from quik :
Well, it definitely looks like something is wrong :) Not sure what's up
at this point. Could be cache coherency not properly enabled on PSX
memory controller by Open Firmware maybe ...
It would be useful if you could dump the memory controller registers
between an OF boot and a BootX boot.
Look at this bit in pmac_setup.c:
sysctrl_regs = (volatile u32 *) ioremap(0xf8000000, 0x1000);
ohare_init();
The first line maps those registers, the second line enables the L2
cache on PSX memory controller. (The name "ohare_init() is actually a
bit bogus here, since that has nothing to do with ohare, but we do it in
ohare based machines only... go figure, that's pre-historical code,
certainly predates my involvement here :).
I'd suggest dumping to 8 or so first words of sysctrl_regs and checking
what difference is there.
Then, there is another blob that enables cache coherency on the PCI side
of Bandit/PSX in pmac_pci.c in init_bandit(). But this code seems to be
called for you ...
It could be something else tho ... like some problem with quik...
Ben.
next prev parent reply other threads:[~2005-10-21 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 17:53 v2.6.13.4 : Bad page state at prep_new_page when booting with quik Marc Zyngier
2005-10-21 4:38 ` Benjamin Herrenschmidt [this message]
2005-10-21 18:08 ` Marc Zyngier
2005-10-21 18:36 ` Mark Guertin
2005-10-21 18:52 ` Marc Zyngier
2005-10-21 22:42 ` Benjamin Herrenschmidt
2005-10-22 8:44 ` Marc Zyngier
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=1129869509.6265.32.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=maz@misterjones.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).