From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: PS3 early lock-up
Date: Tue, 05 Aug 2008 07:52:57 +1000 [thread overview]
Message-ID: <1217886777.24157.91.camel@pasglop> (raw)
In-Reply-To: <1217886287.24157.87.camel@pasglop>
> > ps3_hpte_insert() seems to be called during system initialization with the
> > following values of rflags:
> > - first call: 0x190
> > - initial memory: 0x194 (455 times)
> > - hotplug memory:
> > o crash: 0x115
> > o OK: 0x117
> >
> > Do you have an idea of what's really going on?
>
> Weird... Both look incorrect. In fact, it's a bit scary...
>
> The one with the 7 at the end means that user space as RO access to
> the segment (oops !) and supervisor too. The one with the 5 means
> RO for user and RW for supervisor.
>
> That is unless your HV is munging them in strange ways... I don't
> know why LV1 is refusing a combination though.
>
> As for the flags, it depends what htab_bolt_mapping() is called
> with.
>
> Do you have a backtrace ? I'm a bit lots in the mem hotswap code
> trying to figure out where the mapping comes from..
Ah, found it... It should be ok... both the mapping of the RAM itself
and vmemmap_populate() should be passing
_PAGE_ACCESSED | _PAGE_DIRTY | _PAGE_COHERENT | PP_RWXX;
Which should be 0x194.
Can you find out where that stupid value comes from ?
Ben.
next prev parent reply other threads:[~2008-08-04 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 15:48 PS3 early lock-up Geert Uytterhoeven
2008-08-04 21:44 ` Benjamin Herrenschmidt
2008-08-04 21:52 ` Benjamin Herrenschmidt [this message]
2008-08-05 0:31 ` Geoff Levand
2008-08-05 1:40 ` Benjamin Herrenschmidt
2008-08-05 9:43 ` Geert Uytterhoeven
2008-08-05 10:28 ` Benjamin Herrenschmidt
2008-08-05 11:31 ` Benjamin Herrenschmidt
2008-08-05 23:24 ` Geoff Levand
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=1217886777.24157.91.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.