From: Michael Ellerman <mpe@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Romain Dolbeau <romain@dolbeau.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
PowerPC List Debian <debian-powerpc@lists.debian.org>,
linuxppc-dev@lists.ozlabs.org,
jjhdiederen <jjhdiederen@zonnet.nl>,
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: Tue, 07 Jan 2020 11:39:26 +1100 [thread overview]
Message-ID: <8736cs2j7l.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <874kx81xxt.fsf@linux.ibm.com>
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
> Romain Dolbeau <romain@dolbeau.org> writes:
>
>> Le sam. 21 déc. 2019 à 05:31, Aneesh Kumar K.V
>> <aneesh.kumar@linux.ibm.com> a écrit :
>>> I don't have direct access to this system, I have asked if we can get a run
>>> with 64K.
>>
>> OK, thanks! Do you know which model it is? It seems to be working on
>> some systems,
>> but we don't have enough samples to figure out why at this time, I think.
>>
>>> 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.
>>
>> Sorry, no idea, completely out of my depth here. I can try some kernel
>> (build, runtime) options and/or patch, but someone will have to tell
>> me what to try,
>> as I have no ideas.
>
>
> Can you try this change.
>
> modified arch/powerpc/include/asm/book3s/64/mmu-hash.h
> @@ -580,7 +580,7 @@ extern void slb_set_size(u16 size);
> #if (MAX_PHYSMEM_BITS > MAX_EA_BITS_PER_CONTEXT)
> #define MAX_KERNEL_CTX_CNT (1UL << (MAX_PHYSMEM_BITS - MAX_EA_BITS_PER_CONTEXT))
> #else
> -#define MAX_KERNEL_CTX_CNT 1
> +#define MAX_KERNEL_CTX_CNT 4
> #endif
Didn't help.
Same crash, here's a previous one OCR'ed from a photo:
Oops: Machine check, sig: 7 [#1]
BE PAGE SIZE-64 MMU-Hash SMP NR_CPUS 4 NUMA PowerMac
Modules linked in:
CPU: PID: 1 Comn: init Tainted: G M 5.5.0-rc4-gcc-8.2.0-00919-g443b9413a05e #1465
NIP: c00000000026f528 LR: c000000000296138 CTR: 0000000000000000
REGS: ce0000000ffa3d70 TRAP: 0200 Tainted: G M (5.5.0-rc-gcc-8.2.0-00919-g443b9413a05e)
MSR: 9000000000109032 <SF, HV, EE, ME, IR, DR, RI> CR: 24282048 XER: 00000000
DAR: c00c000000612c80 DSISR: 00000400 IRQ MASK: 8
GPR00: c0000000002970d0 c0000001bc343a90 c000000001399600 c0000001bc01c800
GPR04: ce000001bc390000 ce000001bc3439d4 c0000001bc343a9c c0000001bb4b73b8
GPR08: c0000001bc320000 0000000000612c78 c000000001442a98 0000000000000fe0
GPR12: 7f7f7f7f7f7f7f7f c0000000016a0000 0000000000000000 00000000f7df38c8
GPR16: 0000000000000002 0000000000000000 00000000ffb14bac 00000000f7df5690
GPRZ0: 00000000f7df26c4 000000000000000d 0000000000008000 00000000f7ddfc0c
GPR24: ffffffffffffff9c 0000000000000010 0000000000000002 c0000001bc343db8
GPR28: c000000000296138 c00c000000612c78 c0000001bc390000 c0000001bc01c800
NIP [c0000000626f528] .kmem_cache_free+8x58/0x140
LR [c000000000296138] .putname.0x08/0xa
Call Trace:
c0000001bc343b40 [c000000000296138] .putname+0x88/0xa0
c0000001bc343bc0 [c0000000002970d0] .filename_lookup.part.76+0xb0/0x160
ce000001bc343d40 [c000008000279b20] .do_faccessat+0xe0/0x380
c0000001bc343e20 [c00000000000a40c] systen_call+0x5c/0x68
Instruction dump:
408201e8 2fa30000 419e0080 fb8100c0 fb4100080 fb610088 789d8502 3d22000b
39499498 1d3d0038 ebaa0000 7fbd4a14 <e93d0008> 712a0001 40820240 3422001e
cheers
prev parent reply other threads:[~2020-01-07 0:41 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 ` 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 ` 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 [this message]
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=8736cs2j7l.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=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=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).