From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Romain Dolbeau <romain@dolbeau.org>,
linuxppc-dev@lists.ozlabs.org,
PowerPC List Debian <debian-powerpc@lists.debian.org>,
Andreas Schwab <schwab@linux-m68k.org>,
jjhdiederen <jjhdiederen@zonnet.nl>,
mpe@ellerman.id.au
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: PPC64: G5 & 4k/64k page size (was: Re: Call for report - G5/PPC970 status)
Date: Sat, 21 Dec 2019 10:01:16 +0530 [thread overview]
Message-ID: <87lfr62tbf.fsf@linux.ibm.com> (raw)
In-Reply-To: <CADuzgbo=Yr09hxrkbkwj7Crg0aUfx+RQZOt0sCSNOeYUfR0SmA@mail.gmail.com>
Romain Dolbeau <romain@dolbeau.org> writes:
> Le jeu. 12 déc. 2019 à 22:40, Andreas Schwab <schwab@linux-m68k.org> a écrit :
>> I'm using 4K pages, in case that matters
>
> Yes it does matter, as it seems to be the difference between "working"
> and "not working" :-)
> Thank you for the config & pointing out the culprit!
>
> With your config, my machine boots (though it's missing some features
> as the config seems quite tuned).
>
> Moving from 64k pages to 4k pages on 'my' config (essentially,
> Debian's 5.3 with default values for changes since), my machine boots
> as well & everything seems to work fine.
>
> So question to Aneesh - did you try 64k pages on your G5, or only 4k?
> In the second case, could you try with 64k to see if you can reproduce
> the crash?
I don't have direct access to this system, I have asked if we can get a run
with 64K.
Meanwhile is there a way to find out what caused MachineCheck? more
details on this? I was checking the manual and I don't see any
restrictions w.r.t effective address. We now have very high EA with 64K
page size.
-aneesh
next prev parent reply other threads:[~2019-12-21 4:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADuzgbqYpv40NvAMGjo1cU2cNnij-2p4SYpWgM-Xn0v-8Qapsg@mail.gmail.com>
[not found] ` <e87e2397-a8d4-c928-d3d4-7ae700603770@physik.fu-berlin.de>
[not found] ` <CA+7wUsxBkmG-jW_UVBUuMriZbDkJko3kg0hzmMrVMoJLu2+rPw@mail.gmail.com>
2019-11-10 10:45 ` 5.3.7 64-bits kernel doesn't boot on G5 Quad Romain Dolbeau
2019-11-16 16:34 ` Found the commit for: " Romain Dolbeau
2019-11-16 16:41 ` John Paul Adrian Glaubitz
2019-12-10 8:35 ` Found the commit for: 5.3.7 64-bits kernel doesn't boot on G5 Quad [regression] Romain Dolbeau
2019-12-10 10:22 ` John Paul Adrian Glaubitz
2019-12-11 2:20 ` Aneesh Kumar K.V
2019-12-11 7:19 ` Call for report - G5/PPC970 status (was: Re: Found the commit for: 5.3.7 64-bits kernel doesn't boot on G5 Quad [regression]) Romain Dolbeau
2019-12-11 7:24 ` Call for report - G5/PPC970 status jjhdiederen
2019-12-12 7:32 ` jjhdiederen
2019-12-12 8:00 ` Romain Dolbeau
2019-12-12 8:07 ` John Paul Adrian Glaubitz
2019-12-12 18:12 ` Romain Dolbeau
2019-12-12 18:20 ` Andreas Schwab
2019-12-12 18:43 ` Romain Dolbeau
2019-12-12 21:40 ` Andreas Schwab
2019-12-13 7:47 ` PPC64: G5 & 4k/64k page size (was: Re: Call for report - G5/PPC970 status) Romain Dolbeau
2019-12-14 9:32 ` Jeroen Diederen
2020-01-05 15:06 ` Bertrand Dekoninck
2020-01-06 18:30 ` Romain Dolbeau
2020-01-07 15:27 ` PPC64: G5 & 4k/64k page size Bertrand
2020-01-07 15:54 ` Bertrand
2020-01-07 17:13 ` Romain Dolbeau
2020-01-07 17:51 ` Bertrand
2020-01-07 18:34 ` Patch for '5.3.7 64-bits kernel doesn't boot on G5 Quad' found (was: Re: PPC64: G5 & 4k/64k page size) Romain Dolbeau
2019-12-21 4:31 ` Aneesh Kumar K.V [this message]
2020-01-05 13:03 ` PPC64: G5 & 4k/64k page size (was: Re: Call for report - G5/PPC970 status) Romain Dolbeau
2020-01-06 14:06 ` Aneesh Kumar K.V
2020-01-06 18:18 ` Romain Dolbeau
2020-01-06 18:54 ` Lennart Sorensen
2020-01-06 19:11 ` Romain Dolbeau
2020-01-06 19:26 ` Lennart Sorensen
2020-01-07 9:40 ` Michel Dänzer
2020-01-07 0:39 ` Michael Ellerman
2024-08-06 20:56 ` John Paul Adrian Glaubitz
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=87lfr62tbf.fsf@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=debian-powerpc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jjhdiederen@zonnet.nl \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=romain@dolbeau.org \
--cc=schwab@linux-m68k.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).