From: Marc Zyngier <maz@misterjones.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: v2.6.13.4 : Bad page state at prep_new_page when booting with quik
Date: Sat, 22 Oct 2005 10:44:03 +0200 [thread overview]
Message-ID: <wrpoe5ij60c.fsf@wild-wind.fr.eu.org> (raw)
In-Reply-To: <1129934528.7919.15.camel@gaston> (Benjamin Herrenschmidt's message of "Sat, 22 Oct 2005 08:42:08 +1000")
>>>>> "BenH" == Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
BenH> Hrm... another thing you can do is have a look at the
BenH> init_bandit() routine. It does:
[...]
BenH> What is the value of "magic" in both cases ?
It says 0x17 in both case...
BenH> As for the rest, well, printing out the various addresses where
BenH> the kernel is copied and/or decompresses itself may help...
Will try that next. I also started diving into quik sources...
One more data point : kernel loaded with quik works just fine on a
7500 with a 604e@200 CPU. So it looks like it is some particular
firmware/hardware combinaison that triggers this failure mode.
BenH> Have you tried also netbooting directly vmlinux.coff ? (boot
BenH> enet: might work on OldWorld OF, you'll need a bootp server)
BenH> That works with some oldworlds, not all, depends if they have a
BenH> working ethernet driver in OF.
Nope. The poor thing doesn't even have an integrated ethernet to start
with (nor its official Apple counterpart)...
Stay tuned ;-)
M.
--
And if you don't know where you're going, any road will take you there...
prev parent reply other threads:[~2005-10-22 8:44 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
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 [this message]
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=wrpoe5ij60c.fsf@wild-wind.fr.eu.org \
--to=maz@misterjones.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).