Baoquan,
On 21/03/2024 14:17, Baoquan He wrote:
> On 03/21/24 at 05:40am, Zhijian Li (Fujitsu) wrote:
>> ping
>>
>>
>> Any comment is welcome.
>
> I will have a look at this from kdump side. How do you test your code?
Thanks for your support.
- nothing change is required for makedumpfile and
On 03/21/24 at 05:40am, Zhijian Li (Fujitsu) wrote:
> ping
>
>
> Any comment is welcome.
I will have a look at this from kdump side. How do you test your code?
By the way, there's issue reported by test robot.
Thanks
Baoquan
>
>
> On 06/03/2024 18:28, Li Zhijian wrote:
> > Hello folks,
> >
ping
Any comment is welcome.
On 06/03/2024 18:28, Li Zhijian wrote:
> Hello folks,
>
> Compared with the V2[1] I posted a long time ago, this time it is a
> completely new proposal design.
>
> ### Background and motivate overview ###
> ---
> Crash dump is an important feature for troubleshoot
Hi,
On Thu, 21 Mar 2024 at 05:56, Huang, Kai wrote:
>
> Hi Dave,
>
> Some nitpicking in changelog:
Will fix the grammar issues. Thanks for your review!
>
> On 5/03/2024 2:32 pm, Dave Young wrote:
> > crashkernel reservation failed on a Thinkpad t440s laptop recently,
>
> ',' -> '.' to make it
Hi Dave,
Some nitpicking in changelog:
On 5/03/2024 2:32 pm, Dave Young wrote:
crashkernel reservation failed on a Thinkpad t440s laptop recently,
',' -> '.' to make it as a standalone sentence.
Actually the memblock reservation succeeded, but later insert_resource()
failed.
Test step:
kex
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,
On 03/20/24 at 05:06pm, Changhui Zhong wrote:
> On Tue, Mar 19, 2024 at 10:43 PM Baoquan He wrote:
> >
> > On 03/19/24 at 01:59pm, Ilpo Järvinen wrote:
> > > On Tue, 19 Mar 2024, Changhui Zhong wrote:
> > >
> > > > Hello,
> > > >
> > > > found a kernel warning issue at "kernel/resource.c:834
> > >
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 Tue, Mar 19, 2024 at 10:43 PM Baoquan He wrote:
>
> On 03/19/24 at 01:59pm, Ilpo Järvinen wrote:
> > On Tue, 19 Mar 2024, Changhui Zhong wrote:
> >
> > > Hello,
> > >
> > > found a kernel warning issue at "kernel/resource.c:834
> > > __insert_resource+0x84/0x110" ,please help check,
> > >
> > >