From: Romain Dolbeau <romain@dolbeau.org>
To: Bertrand <bertrand.dekoninck@gmail.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Jeroen Diederen <jjhdiederen@zonnet.nl>,
PowerPC List Debian <debian-powerpc@lists.debian.org>,
Andreas Schwab <schwab@linux-m68k.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
linuxppc-dev@lists.ozlabs.org
Subject: Patch for '5.3.7 64-bits kernel doesn't boot on G5 Quad' found (was: Re: PPC64: G5 & 4k/64k page size)
Date: Tue, 7 Jan 2020 19:34:22 +0100 [thread overview]
Message-ID: <CADuzgboztYeRbruGmQDuTScaLAZp2ozoy-KARtNq1ViyTm86jw@mail.gmail.com> (raw)
In-Reply-To: <113ee36c-684f-9201-aea8-8cd437b6d009@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hello all,
Great news: Aneesh sent me a patch that solves the problem on my G5 Quad :-)
I don't know whether he considers it a 'workaround' or if it's the
'proper' patch for upstream, so beware. It's a one-liner so I attach
it to this message: those affected can test it as well to confirm if
that indeed solves the problem for them as well.
If it is the 'proper' patch, I expect it should get into upstream
pretty quickly. Then Debian should be able to trivially backport it to
their PPC64 kernel, and the G5 will still be a great machine in 2020!
Thanks everyone for your help in tracking down the bug & to Aneesh for
finding a fix :-)
Cordially,
--
Romain Dolbeau
[-- Attachment #2: g5.patch --]
[-- Type: text/x-patch, Size: 617 bytes --]
diff --git a/arch/powerpc/include/asm/book3s/64/mmu-hash.h b/arch/powerpc/include/asm/book3s/64/mmu-hash.h
index 15b75005bc34..516db8a2e6ca 100644
--- a/arch/powerpc/include/asm/book3s/64/mmu-hash.h
+++ b/arch/powerpc/include/asm/book3s/64/mmu-hash.h
@@ -601,7 +601,7 @@ extern void slb_set_size(u16 size);
*/
#define MAX_USER_CONTEXT ((ASM_CONST(1) << CONTEXT_BITS) - 2)
#define MIN_USER_CONTEXT (MAX_KERNEL_CTX_CNT + MAX_VMALLOC_CTX_CNT + \
- MAX_IO_CTX_CNT + MAX_VMEMMAP_CTX_CNT)
+ MAX_IO_CTX_CNT + MAX_VMEMMAP_CTX_CNT + 1)
/*
* For platforms that support on 65bit VA we limit the context bits
*/
next prev parent reply other threads:[~2020-01-07 18:36 UTC|newest]
Thread overview: 33+ 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 ` Romain Dolbeau [this message]
2019-12-21 4:31 ` PPC64: G5 & 4k/64k page size (was: Re: Call for report - G5/PPC970 status) Aneesh Kumar K.V
2020-01-05 13:03 ` 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
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=CADuzgboztYeRbruGmQDuTScaLAZp2ozoy-KARtNq1ViyTm86jw@mail.gmail.com \
--to=romain@dolbeau.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bertrand.dekoninck@gmail.com \
--cc=debian-powerpc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jjhdiederen@zonnet.nl \
--cc=linuxppc-dev@lists.ozlabs.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).