From: Baoquan He <bhe@redhat.com>
To: "chenhaixiang (A)" <chenhaixiang3@huawei.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Louhongxiang <louhongxiang@huawei.com>,
"wangbin (A)" <wangbin224@huawei.com>,
"Fangchuangchuang(Fcc,Euler)" <fangchuangchuang@huawei.com>,
lihuafei <lihuafei1@huawei.com>,
"wanghai (M)" <wanghai38@huawei.com>
Subject: Re: Question about Address Range Validation in Crash Kernel Allocation
Date: Wed, 20 Mar 2024 22:08:30 +0800 [thread overview]
Message-ID: <Zfrt3qdIWsbflBq0@MiWiFi-R3L-srv> (raw)
In-Reply-To: <b1c67ea9d8fe4f6f832d9272be177bec@huawei.com>
On 03/20/24 at 01:12pm, chenhaixiang (A) wrote:
> I tested the kernel-6.8 on my machine and found that the crashkernel memory reservation range is consistent with kernel-5.10. However, it's strange that when crashkernel=512M, the kernel still allocates two memory segments for crashkernel, as seen in the logs:
> [ 0.022640] crashkernel low memory reserved: 0x49000000 - 0x59000000 (256 MB)
> [ 0.022641] crashkernel reserved: 0x000000c01f000000 - 0x000000c03f000000 (512 MB)
> But only one segment is shown in /proc/iomem:
> c01f000000-c03effffff : Crash kernel
> Moreover, the conflicting address 53cbd000-53ccffff is still reserved by someone else:
> 53cbd000-53ccffff : Reserved
> [ 0.029843] e820: update [mem 0x53cbd000-0x53ccffff] usable ==> reserved
> It seems there is a kernel bug here.
> If you need the complete log, I can send it later.
Yeah, please attach the complete log. I will have a look.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2024-03-20 14:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 13:12 Question about Address Range Validation in Crash Kernel Allocation chenhaixiang (A)
2024-03-20 14:08 ` Baoquan He [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-21 9:17 chenhaixiang (A)
2024-03-21 9:48 ` Li Huafei
2024-03-21 10:06 ` Dave Young
2024-03-21 12:37 ` Li Huafei
2024-03-22 1:16 ` Baoquan He
2024-03-22 7:26 ` Dave Young
2024-03-22 7:18 ` Dave Young
2024-03-22 7:18 ` Dave Young
2024-03-22 7:58 ` Li Huafei
2024-03-22 7:58 ` Li Huafei
[not found] <45065451d7d343679e150313c1ee2b62@huawei.com>
2024-03-21 7:09 ` Baoquan He
2024-03-19 7:24 chenhaixiang (A)
2024-03-19 8:21 ` Baoquan He
2024-03-18 12:00 chenhaixiang (A)
2024-03-19 1:38 ` Baoquan He
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=Zfrt3qdIWsbflBq0@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=chenhaixiang3@huawei.com \
--cc=fangchuangchuang@huawei.com \
--cc=kexec@lists.infradead.org \
--cc=lihuafei1@huawei.com \
--cc=louhongxiang@huawei.com \
--cc=wangbin224@huawei.com \
--cc=wanghai38@huawei.com \
/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.