From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org, darren@stevens-zone.net,
Michael Ellerman <michaele@au1.ibm.com>,
Julian Margetson <runaway@candw.ms>,
Adrian Cox <adrian@humboldt.co.uk>,
rtd@a-eon.com, rtd2@xtra.co.nz, pjwall@mac.com, pjwall@me.com,
matthew@a-eon.biz, intermediadc@hotmail.com, contact@a-eon.com,
info@xenosoft.de
Subject: Kernel 4.7: PAGE_GUARDED and _PAGE_NO_CACHE
Date: Sun, 5 Jun 2016 18:09:05 +0200 [thread overview]
Message-ID: <053dd416-a9ab-5b06-5c3b-1acefb53fd3b@xenosoft.de> (raw)
In-Reply-To: <2FB13B5B-42F0-4396-AD29-70924D2710CC@xenosoft.de>
All,
I need an answer because I think Darren's guess is correct. It isn't a
problem in the pci code. I replaced the file head_64.S that Darren
mentioned with the one from the kernel 4.6 and it compiled but
unfortunately it doesn't boot. We know "head_64.S" is one file for the
early boot phase but I think there are some other files.
I am not a fan of reverting the PowerPC commits but there are some other
new things in the new kernel e.g. DRM 2.45.0 which are very interesting
for the Nemo board.
@Julian
What about the issues with the Sam460ex? Have you solved the problem
with the commit powerpc-4.7-1?
Cheers,
Christian
On 04 June 2016 at 5:25 PM, Christian Zigotzky wrote:
> Which files are responsible for the early boot phase in the commit powerpc-4.7-1? Perhaps the problem is there.
>
> - Christian
>
> Sent from my iPhone
>
On 28 May 2016 at 8:51 PM, Darren Stevens wrote:
> Hello Adrian
>
> On 28/05/2016, Adrian Cox wrote:
>>> From: Christian Zigotzky [mailto:chzigotzky@xenosoft.de]
>>> Sent: 28 May 2016 07:06
>>> Adrian, what is the expected WIMG bit mapping for the Nemo board?
>>>
>> I'm not able to help much here, I'm afraid. I don't have a Nemo board at
>> the moment, and it's been a few years. From memory all the peripherals
>> required standard uncached and guarded mappings on Nemo.
> Before everybody gets too involved, from what I've seen with my tests today
> the kernel is crashing long before it gets to the pci-common code.
>
> I've attached 2 boot logs, one from a 4.4 kernel I've been working on, and
> from a build of the latest git.
>
> You can see from this that the 4.7 kernel hangs right after the booting linux
> via __start(), whereas in the 4.4 there's about 29 lines of output before it
> gets to the Initialised io_base_virt printk in our patch.
>
> The last time we had a hang this early in the boot it turned out to be a
> problem in head_64.S, I think there is something else wrong in the commit
> Christian has identified
>
> I will see if this is something I can fix, but it may need better low level
> knowledge of PPC hardware than I have.
>
> Regards
> Darren
next prev parent reply other threads:[~2016-06-05 16:09 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 4:38 PAGE_GUARDED Christian Zigotzky
2016-05-23 8:01 ` PAGE_GUARDED Benjamin Herrenschmidt
2016-05-24 10:48 ` PAGE_GUARDED Christian Zigotzky
2016-05-24 11:16 ` PAGE_GUARDED Benjamin Herrenschmidt
2016-05-24 13:37 ` PAGE_GUARDED Christian Zigotzky
2016-05-24 15:37 ` PAGE_GUARDED Aneesh Kumar K.V
2016-05-25 6:58 ` PAGE_GUARDED Christian Zigotzky
2016-05-25 11:44 ` PAGE_GUARDED Christian Zigotzky
2016-06-04 7:19 ` Kernel 4.7: PAGE_GUARDED and _PAGE_NO_CACHE Christian Zigotzky
2016-06-04 7:40 ` Christian Zigotzky
2016-06-04 11:08 ` Christian Zigotzky
2016-06-04 14:46 ` Aneesh Kumar K.V
2016-06-04 15:13 ` Christian Zigotzky
2016-06-04 15:25 ` Christian Zigotzky
2016-06-05 16:09 ` Christian Zigotzky [this message]
2016-06-06 0:57 ` Michael Ellerman
2016-06-06 1:23 ` Julian Margetson
2016-06-06 2:00 ` Michael Ellerman
2016-06-06 8:59 ` Julian Margetson
2016-06-06 0:54 ` Michael Ellerman
2016-06-04 14:42 ` Aneesh Kumar K.V
2016-06-04 15:07 ` Christian Zigotzky
2016-06-06 0:51 ` Michael Ellerman
2016-06-06 5:21 ` Christian Zigotzky
2016-06-07 20:17 ` Christian Zigotzky
2016-06-07 22:14 ` Christian Zigotzky
2016-06-08 1:51 ` Michael Ellerman
2016-06-08 2:52 ` Michael Ellerman
2016-06-08 10:58 ` Christian Zigotzky
2016-06-08 11:30 ` Michael Ellerman
2016-06-08 12:50 ` Christian Zigotzky
2016-06-08 11:33 ` Darren Stevens
2016-06-08 13:24 ` Christian Zigotzky
2016-06-08 13:51 ` Christian Zigotzky
2016-06-08 13:52 ` Michael Ellerman
2016-06-08 15:11 ` Aneesh Kumar K.V
2016-06-08 15:47 ` Christian Zigotzky
2016-06-09 8:48 ` Christian Zigotzky
2016-06-09 11:15 ` Michael Ellerman
2016-06-09 13:13 ` Christian Zigotzky
2016-06-13 8:14 ` Christian Zigotzky
2016-06-13 8:19 ` Benjamin Herrenschmidt
2016-06-13 18:09 ` Christian Zigotzky
2016-06-22 19:07 ` Christian Zigotzky
2016-06-22 19:58 ` luigi burdo
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=053dd416-a9ab-5b06-5c3b-1acefb53fd3b@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=adrian@humboldt.co.uk \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=contact@a-eon.com \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=intermediadc@hotmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew@a-eon.biz \
--cc=michaele@au1.ibm.com \
--cc=pjwall@mac.com \
--cc=pjwall@me.com \
--cc=rtd2@xtra.co.nz \
--cc=rtd@a-eon.com \
--cc=runaway@candw.ms \
/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).