public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "bhe@redhat.com" <bhe@redhat.com>
To: "Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>, piliu@redhat.com
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kexec reports "Cannot get kernel _text symbol address" on arm64 platform
Date: Wed, 9 Aug 2023 10:11:46 +0800	[thread overview]
Message-ID: <ZNL14lnrHvzbpRQu@MiWiFi-R3L-srv> (raw)
In-Reply-To: <MN0PR12MB59538822AA264031D0CAE468B70DA@MN0PR12MB5953.namprd12.prod.outlook.com>

On 08/08/23 at 07:17pm, Pandey, Radhey Shyam wrote:
> Hi,
> 
> I am trying to bring up kdump on arm64 platform[1]. But I get "Cannot get kernel _text symbol address".
> 
> Is there some Dump-capture kernel config options that I am missing?
> 
> FYI, copied below complete kexec debug log.
> 
> [1]: https://www.xilinx.com/products/boards-and-kits/vck190.html

Your description isn't clear. You saw the printing, then your kdump
kernel loading succeeded or not?

If no, have you tried applying Pingfan's patchset and still saw the issue?

[PATCHv7 0/5] arm64: zboot support
https://lore.kernel.org/all/20230803024152.11663-1-piliu@redhat.com/T/#u

Thanks
Baoquan


       reply	other threads:[~2023-08-09  2:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MN0PR12MB59538822AA264031D0CAE468B70DA@MN0PR12MB5953.namprd12.prod.outlook.com>
2023-08-09  2:11 ` bhe [this message]
2023-08-11 13:27   ` kexec reports "Cannot get kernel _text symbol address" on arm64 platform Pandey, Radhey Shyam
2023-08-11 23:11     ` bhe
2023-08-12  3:41       ` bhe
2023-08-14 12:38     ` bhe
2023-08-21 12:22       ` Pandey, Radhey Shyam
2023-08-22  3:54         ` Alexander Kamensky
2023-08-23 19:09           ` Pandey, Radhey Shyam
2023-08-24 15:05             ` Alexander Kamensky
2023-08-28 17:39               ` Pandey, Radhey Shyam

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=ZNL14lnrHvzbpRQu@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piliu@redhat.com \
    --cc=radhey.shyam.pandey@amd.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