From: Baoquan He <bhe@redhat.com>
To: palmer@rivosinc.com, Chen Jiahao <chenjiahao16@huawei.com>,
patchwork-bot+linux-riscv@kernel.org
Cc: robh@kernel.org, aou@eecs.berkeley.edu, zephray@outlook.com,
alexghiti@rivosinc.com, thunder.leizhen@huawei.com,
bjorn@rivosinc.com, linux-kernel@vger.kernel.org,
conor.dooley@microchip.com, palmer@dabbelt.com,
jszhang@kernel.org, paul.walmsley@sifive.com,
linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
ajones@ventanamicro.com
Subject: Re: [PATCH -next v2] riscv: kdump: fix crashkernel reserving problem on RISC-V
Date: Fri, 13 Oct 2023 08:33:08 +0800 [thread overview]
Message-ID: <ZSiQRDGLZk7lpakE@MiWiFi-R3L-srv> (raw)
In-Reply-To: <169714322507.23371.6628705957236576989.git-patchwork-notify@kernel.org>
Hi,
On 10/12/23 at 08:40pm, patchwork-bot+linux-riscv@kernel.org wrote:
> Hello:
>
> This patch was applied to riscv/linux.git (fixes)
> by Palmer Dabbelt <palmer@rivosinc.com>:
This patches fixes a regression of one risc-v patch which Andrew picked
into his akpm tree. Later, Andrew merged those two into one patch, now
it shows up in next/master as:
39365395046f riscv: kdump: use generic interface to simplify crashkernel reservation
Maybe it can be droppped in risv-v git tree so as not to cause conflict
when merging.
Thanks
Baoquan
>
> On Mon, 25 Sep 2023 10:43:33 +0800 you wrote:
> > When testing on risc-v QEMU environment with "crashkernel="
> > parameter enabled, a problem occurred with the following
> > message:
> >
> > [ 0.000000] crashkernel low memory reserved: 0xf8000000 - 0x100000000 (128 MB)
> > [ 0.000000] crashkernel reserved: 0x0000000177e00000 - 0x0000000277e00000 (4096 MB)
> > [ 0.000000] ------------[ cut here ]------------
> > [ 0.000000] WARNING: CPU: 0 PID: 0 at kernel/resource.c:779 __insert_resource+0x8e/0xd0
> > [ 0.000000] Modules linked in:
> > [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.0-rc2-next-20230920 #1
> > [ 0.000000] Hardware name: riscv-virtio,qemu (DT)
> > [ 0.000000] epc : __insert_resource+0x8e/0xd0
> > [ 0.000000] ra : insert_resource+0x28/0x4e
> > [ 0.000000] epc : ffffffff80017344 ra : ffffffff8001742e sp : ffffffff81203db0
> > [ 0.000000] gp : ffffffff812ece98 tp : ffffffff8120dac0 t0 : ff600001f7ff2b00
> > [ 0.000000] t1 : 0000000000000000 t2 : 3428203030303030 s0 : ffffffff81203dc0
> > [ 0.000000] s1 : ffffffff81211e18 a0 : ffffffff81211e18 a1 : ffffffff81289380
> > [ 0.000000] a2 : 0000000277dfffff a3 : 0000000177e00000 a4 : 0000000177e00000
> > [ 0.000000] a5 : ffffffff81289380 a6 : 0000000277dfffff a7 : 0000000000000078
> > [ 0.000000] s2 : ffffffff81289380 s3 : ffffffff80a0bac8 s4 : ff600001f7ff2880
> > [ 0.000000] s5 : 0000000000000280 s6 : 8000000a00006800 s7 : 000000000000007f
> > [ 0.000000] s8 : 0000000080017038 s9 : 0000000080038ea0 s10: 0000000000000000
> > [ 0.000000] s11: 0000000000000000 t3 : ffffffff80a0bc00 t4 : ffffffff80a0bc00
> > [ 0.000000] t5 : ffffffff80a0bbd0 t6 : ffffffff80a0bc00
> > [ 0.000000] status: 0000000200000100 badaddr: 0000000000000000 cause: 0000000000000003
> > [ 0.000000] [<ffffffff80017344>] __insert_resource+0x8e/0xd0
> > [ 0.000000] ---[ end trace 0000000000000000 ]---
> > [ 0.000000] Failed to add a Crash kernel resource at 177e00000
> >
> > [...]
>
> Here is the summary with links:
> - [-next,v2] riscv: kdump: fix crashkernel reserving problem on RISC-V
> https://git.kernel.org/riscv/c/1d6cd2146c2b
>
> You are awesome, thank you!
> --
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
>
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
>
next prev parent reply other threads:[~2023-10-13 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 2:43 [PATCH -next v2] riscv: kdump: fix crashkernel reserving problem on RISC-V Chen Jiahao
2023-10-12 20:40 ` patchwork-bot+linux-riscv
2023-10-13 0:33 ` Baoquan He [this message]
2024-04-21 16:13 ` Mingzheng Xing
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=ZSiQRDGLZk7lpakE@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=ajones@ventanamicro.com \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=chenjiahao16@huawei.com \
--cc=conor.dooley@microchip.com \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=patchwork-bot+linux-riscv@kernel.org \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=thunder.leizhen@huawei.com \
--cc=zephray@outlook.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox