On 2024/3/22 15:18, Dave Young wrote:
> On Thu, 21 Mar 2024 at 20:37, Li Huafei wrote:
>>
>>
>>
>> On 2024/3/21 18:06, Dave Young wrote:
>>> Hi,
>>>
>>> On Thu, 21 Mar 2024 at 17:49, Li Huafei wrote:
Hi Baoquan，
On 2024/3/21 17:17, chenhaixiang (A) wrote:
>
>>> I'm s
Hi,
On Fri, 22 Mar 2024 at 09:16, Baoquan He wrote:
>
> On 03/21/24 at 08:37pm, Li Huafei wrote:
> >
> >
> > On 2024/3/21 18:06, Dave Young wrote:
> > > Hi,
> > >
> > > On Thu, 21 Mar 2024 at 17:49, Li Huafei wrote:
> > >>
> > >> Hi Baoquan，
> > >>
> > >> On 2024/3/21 17:17, chenhaixiang (A) wro
On Thu, 21 Mar 2024 at 20:37, Li Huafei wrote:
>
>
>
> On 2024/3/21 18:06, Dave Young wrote:
> > Hi,
> >
> > On Thu, 21 Mar 2024 at 17:49, Li Huafei wrote:
> >>
> >> Hi Baoquan，
> >>
> >> On 2024/3/21 17:17, chenhaixiang (A) wrote:
> >>>
> > I'm sorry for the delay. Here are some details from
On 03/21/24 at 08:37pm, Li Huafei wrote:
>
>
> On 2024/3/21 18:06, Dave Young wrote:
> > Hi,
> >
> > On Thu, 21 Mar 2024 at 17:49, Li Huafei wrote:
> >>
> >> Hi Baoquan，
> >>
> >> On 2024/3/21 17:17, chenhaixiang (A) wrote:
> >>>
> > I'm sorry for the delay. Here are some details from the b
On 2024/3/21 18:06, Dave Young wrote:
> Hi,
>
> On Thu, 21 Mar 2024 at 17:49, Li Huafei wrote:
>>
>> Hi Baoquan，
>>
>> On 2024/3/21 17:17, chenhaixiang (A) wrote:
>>>
> I'm sorry for the delay. Here are some details from the boot log and
/proc/iomem:
> The Boot log:
> [0.00
Hi,
On Thu, 21 Mar 2024 at 17:49, Li Huafei wrote:
>
> Hi Baoquan，
>
> On 2024/3/21 17:17, chenhaixiang (A) wrote:
> >
> >>> 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.localdom
Hi Baoquan，
On 2024/3/21 17:17, chenhaixiang (A) wrote:
>
>>> 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
> > 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
On 03/21/24 at 03:22am, chenhaixiang (A) wrote:
> 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 2
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,
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 memo
On 03/19/24 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 segment in /proc/
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 segment in /proc/iomem. However, for some reason, within the
address range
Hi,
On 03/18/24 at 12:00pm, chenhaixiang (A) wrote:
> 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 a
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 :
15 matches
Mail list logo
