linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 21 Oct 2005 20:08:55 +0200	[thread overview]
Message-ID: <wrpek6eeo94.fsf@wild-wind.fr.eu.org> (raw)
In-Reply-To: <1129869509.6265.32.camel@gaston> (Benjamin Herrenschmidt's message of "Fri, 21 Oct 2005 14:38:29 +1000")

>>>>> "BenH" == Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:

BenH> I'd suggest dumping to 8 or so first words of sysctrl_regs and checking
BenH> what difference is there.

Here you go :

BootX :

*fde69000 = 10000000
*fde69004 = 00000000
*fde69008 = 04000000
*fde6900c = 00000000
*fde69010 = 04101102
*fde69014 = 00000000
*fde69018 = 00000345
*fde6901c = 00000000

Quik:

*fdeff000 = 10000000
*fdeff004 = 00000000
*fdeff008 = 04000000
*fdeff00c = 00000000
*fdeff010 = 04101102
*fdeff014 = 00000000
*fdeff018 = 00000345
*fdeff01c = 00000000

Except for the ioremap address being different, not much to see
here...

BenH> It could be something else tho ... like some problem with
BenH> quik...

I fear that... But even in such a case ,understanding what confuses
the kernel would help a lot...

Thanks for your help,

	M.
-- 
And if you don't know where you're going, any road will take you there...

  reply	other threads:[~2005-10-21 18:16 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 [this message]
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=wrpek6eeo94.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).