From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: kexec@lists.infradead.org
Subject: 64-bit kernels and 32-bit user-space
Date: Tue, 2 May 2023 14:55:48 +0200 [thread overview]
Message-ID: <b4ada33d-f6a7-ad32-9de2-51968ea29af9@broadcom.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 425 bytes --]
I am trying to get a kernel crashdump on an embedded router, but it has
32-bit user-space while the kernel is 64-bit. I tried something simple
and got following:
# kexec -S
Unsupported machine type: aarch64
Looking in the build directory I only see arch/arm/ folder, but no
arch/arm64. Is this due to 32-bit user-space? Has someone tried kexec in
such an environment? Any pointers would be appreciated.
Regards,
Arend
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2023-05-03 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 12:55 Arend van Spriel [this message]
2023-05-03 11:43 ` 64-bit kernels and 32-bit user-space Arend van Spriel
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=b4ada33d-f6a7-ad32-9de2-51968ea29af9@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=kexec@lists.infradead.org \
/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