From: Oscar Salvador <osalvador@suse.de>
To: "Qian Cai (QUIC)" <quic_qiancai@quicinc.com>
Cc: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Vlastimil Babka <vbabka@suse.cz>,
Michal Hocko <mhocko@kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Arm64 crash while online/offline memory sections
Date: Tue, 25 May 2021 20:00:22 +0200 [thread overview]
Message-ID: <YK07NhNOnKNB02RY@localhost.localdomain> (raw)
In-Reply-To: <DM5PR0201MB35576CEF62C53EF393E3D9768E259@DM5PR0201MB3557.namprd02.prod.outlook.com>
On Tue, May 25, 2021 at 05:57:34PM +0000, Qian Cai (QUIC) wrote:
> > Do we know which patch in particular is problematic?
>
> Okay, the winner is "mm,memory_hotplug: Allocate memmap from the added memory range".
>
> https://lore.kernel.org/linux-mm/20210421102701.25051-5-osalvador@suse.de/
Ok, which means that is irrelevant to having it enabled, as the latter
patch of that series actualy enables it for arm64.
Can you work out where exactly the crash happens?
I will have a look into it tomorrow.
Thanks for reporting.
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2021-05-25 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 15:36 Arm64 crash while online/offline memory sections Qian Cai (QUIC)
2021-05-25 15:40 ` David Hildenbrand
2021-05-25 16:40 ` Qian Cai (QUIC)
2021-05-25 17:57 ` Qian Cai (QUIC)
2021-05-25 18:00 ` Oscar Salvador [this message]
2021-05-25 18:12 ` David Hildenbrand
2021-05-25 19:56 ` Qian Cai (QUIC)
2021-05-26 7:20 ` Oscar Salvador
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=YK07NhNOnKNB02RY@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=quic_qiancai@quicinc.com \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.