From: Andrew Morton <akpm@linux-foundation.org>
To: cam@neo-zeon.de
Cc: bugzilla-daemon@bugzilla.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [Bug 204789] New: Boot failure with more than 256G of memory
Date: Wed, 11 Sep 2019 07:31:53 -0700 [thread overview]
Message-ID: <20190911073153.9df4d4618d7f99752cd18edd@linux-foundation.org> (raw)
In-Reply-To: <bug-204789-27@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sun, 08 Sep 2019 00:04:26 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=204789
>
> Bug ID: 204789
> Summary: Boot failure with more than 256G of memory
> Product: Memory Management
> Version: 2.5
> Kernel Version: 5.2.x
> Hardware: PPC-64
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Other
> Assignee: akpm@linux-foundation.org
> Reporter: cam@neo-zeon.de
> Regression: No
"Yes" :)
> Kernel series 5.2.x will not boot on my Talos II workstation with dual POWER9
> 18 core processors and 512G of physical memory with disable_radix=yes and 4k
> pages.
>
> 5.3-rc6 did not work either.
>
> 5.1 and earlier boot fine.
Thanks. It's probably best to report this on the powerpc list, cc'ed here.
> I can get the system to boot IF I leave the Radix MMU enabled or if I boot a
> kernel with 64k pages. I haven't yet tested enabling the Radix MMU with 64k
> pages at the same time, but I suspect this would work. This is a system I
> cannot take down TOO frequently.
>
> The system will also boot with the Radix MMU disabled and 4k pages with 256G or
> less memory. Setting mem on the kernel CLI to 256G or less results in a
> successful boot. Setting mem=257G or higher no Radix MMU and 4k pages and the
> kernel will not boot.
>
> Petitboot comes up, but the system fails VERY early in boot in the serial
> console with:
> SIGTERM received, booting...
> [ 23.838858] kexec_core: Starting new kernel
>
> Early printk is enabled, and it never progresses any further.
>
> 5.1 boots just fine with the Radix MMU disabled and 4k pages.
>
> Unfortunately, I currently need 4k pages for bcache to work, and Radix MMU
> disabled in order for FreeBSD 12.x to work under KVM so I'm sticking with
> 5.1.21 for now.
>
> I have been unable to reproduce this issue in KVM.
>
> Here are my PCIe peripherals:
> 1. Microsemi/Adaptec HBA 1100-4i SAS controller
> 2. Megaraid 9316-16i SAS RAID controller.
>
> I've only tried little endian as this is a little endian install.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
next parent reply other threads:[~2019-09-11 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204789-27@https.bugzilla.kernel.org/>
2019-09-11 14:31 ` Andrew Morton [this message]
2019-09-11 15:34 ` [Bug 204789] New: Boot failure with more than 256G of memory Cameron Berkenpas
2019-09-13 4:53 ` Aneesh Kumar K.V
2019-09-13 14:21 ` Aneesh Kumar K.V
2019-09-13 15:05 ` Cameron Berkenpas
2019-09-13 16:13 ` Aneesh Kumar K.V
2019-09-13 17:28 ` Cameron Berkenpas
2019-09-18 3:15 ` Aneesh Kumar K.V
2019-09-18 15:38 ` Cameron Berkenpas
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=20190911073153.9df4d4618d7f99752cd18edd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=cam@neo-zeon.de \
--cc=linuxppc-dev@lists.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 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).