mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Björn Töpel" <bjorn@kernel.org>
To: Pnina Feder <pnina.feder@mobileye.com>
Cc: alex@ghiti.fr, bjorn@rivosinc.com, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org, mick@ics.forth.gr,
	palmer@dabbelt.com, paul.walmsley@sifive.com,
	Pnina Feder <pnina.feder@mobileye.com>
Subject: Re: [PATCH 0/1] Fix for riscv vmcore issue
Date: Mon, 30 Jun 2025 15:33:38 +0200	[thread overview]
Message-ID: <87jz4txsjx.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20250630112309.97162-2-pnina.feder@mobileye.com>

Pnina!

Pnina Feder <pnina.feder@mobileye.com> writes:

> We are creating a vmcore using kexec on a Linux 6.15 RISC-V system and
> analyzing it with the crash tool on the host. This workflow used to
> work on Linux 6.14 but is now broken in 6.15.

Thanks for reporting this!

> The issue is caused by a change in the kernel:
> In Linux 6.15, certain memblock sections are now marked as Reserved in
> /proc/iomem. The kexec tool excludes all Reserved regions when
> generating the vmcore, so these sections are missing from the dump.

How are you collecting the /proc/vmcore file? A full set of commands
would be helpful.

> However, the kernel still uses addresses in these regions—for example,
> for IRQ pointers. Since the crash tool needs access to these memory
> areas to function correctly, their exclusion breaks the analysis.

Wdym with "IRQ pointers"? Also, what version (sha1) of crash are you
using?


Thanks!
Björn

  reply	other threads:[~2025-06-30 13:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 18:21 [PATCH fixes] riscv: Properly export reserved regions in /proc/iomem Björn Töpel
2025-04-11 10:28 ` Alexandre Ghiti
2025-04-16 18:42 ` patchwork-bot+linux-riscv
2025-06-30 11:21 ` [PATCH 0/1] Fix for riscv vmcore issue Pnina Feder
2025-06-30 13:33   ` Björn Töpel [this message]
2025-07-03 12:06     ` Pnina Feder
2025-07-04 12:25       ` Alexandre Ghiti
2025-07-06 13:57         ` Pnina Feder
2025-07-14 12:00           ` Pnina Feder
2025-07-16  6:58             ` Alexandre Ghiti
2025-07-16 11:05               ` Pnina Feder
2025-07-16 11:47                 ` Alexandre Ghiti
2025-07-16 18:16                   ` Nick Kossifidis
2025-06-30 11:21 ` [PATCH 1/1] riscv: Change memblock reserved name to be recognized on kexec Pnina Feder

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=87jz4txsjx.fsf@all.your.base.are.belong.to.us \
    --to=bjorn@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=bjorn@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mick@ics.forth.gr \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pnina.feder@mobileye.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

all inboxes | Powered by JetHome®