From: bugzilla-daemon@bugzilla•kernel.org
To: linuxppc-dev@lists•ozlabs.org
Subject: [Bug 204789] Boot failure with more than 256G of memory on Power9 with 4K pages & Hash MMU
Date: Tue, 01 Oct 2019 16:01:53 +0000 [thread overview]
Message-ID: <bug-204789-206035-UlJhpNtvRb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204789-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204789
--- Comment #11 from Cameron (cam@neo-zeon•de) ---
grep RAM /proc/iomem
00000000-3fffffffff : System RAM
The system has 16 dimm slots, all are populated. Unfortunately, I will
not have physical to access to the box in the foreseeable future.
Aneesh appears to be correct in that this issue started with 0034d395f89d.
On 10/1/19 3:04 AM, bugzilla-daemon@bugzilla•kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=204789
>
> --- Comment #10 from Michael Ellerman (michael@ellerman•id.au) ---
> Can you boot a good kernel and do:
>
> $ sudo grep RAM /proc/iomem
>
> And paste the output. Just to confirm what your memory layout is.
>
> What arrangement of DIMMs do you have? It's possible you could work around
> the
> bug by changing that, depending on how many DIMMs and slots you have.
>
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-10-01 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204789-206035@https.bugzilla.kernel.org/>
2019-10-01 9:56 ` [Bug 204789] Boot failure with more than 256G of memory on POWER/ppc64 bugzilla-daemon
2019-10-01 9:57 ` bugzilla-daemon
2019-10-01 10:04 ` [Bug 204789] Boot failure with more than 256G of memory on Power9 with 4K pages & Hash MMU bugzilla-daemon
2019-10-01 16:01 ` bugzilla-daemon [this message]
2019-10-05 20:07 ` bugzilla-daemon
2020-11-28 16:48 ` bugzilla-daemon
2020-11-30 1:49 ` bugzilla-daemon
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=bug-204789-206035-UlJhpNtvRb@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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