> > When kexec_iomem_for_each_line() reads from /proc/iomem, concurrent
> > modifications to /proc/iomem may lead to usablemem_rgns recording
> > duplicate Crash kernel segments.
> > This can result in the number of retrieved Crash kernel segments
> > exceeding CRASH_MAX_RESERVED_RANGES, triggeri
> > I'm sorry for the delay. Here are some details from the boot log and
> /proc/iomem:
> > The Boot log:
> > [0.00] Linux version 6.8.0 (root@localhost.localdomain) (gcc (GCC)
> 10.3.1, GNU ld (GNU Binutils) 2.37) #3 SMP PREEMPT_DYNAMIC Wed Mar 20
> 11:46:11 UTC 2024
> > [0.00] C
at 07:24am, chenhaixiang (A) wrote:
> > Thank you for your reply!
> > The kernel version on my machine is kernel-5.10, and the kexec-tools
> > version is
> kexec-tools-2.0.27.
> > However, my issue seems to be a bit different. On my machine, I can see the
> crashkernel memory
cbd000-53cc : Reserved
```
I'm not sure if the crashkernel memory segment should not include other
markings, and if not supported, whether kexec-tools should raise an error.
Thanks
Chen Haixiang
--
On 03/19/24 at 9:38qm, Baoquan He wrote:
> Hi,
>
> On 03/18/24 at 12:00pm, che
Dear kexec Community Members,
I encountered an issue while using kexec-tools on my x86_64 machine.
When there is a segment marked as 'reserved' within the memory range allocated
for the crash kernel in /proc/iomem,the output appears as follows:
2d4fd058-60efefff : System RAM
2d4fd058-58ff :
