From: "Guilherme G. Piccoli" <guilherme.piccoli@canonical.com>
To: Bruce Mitchell <Bruce.Mitchell@ibm.com>
Cc: kexec mailing list <kexec@lists.infradead.org>
Subject: Re: Issues with kdump/kexec on an ARM dual-core ARM Cortex-A7.
Date: Wed, 24 Feb 2021 11:51:27 -0300 [thread overview]
Message-ID: <CAHD1Q_z8zhpXFUybsPX6yOW2WPuYgpxsv-k90fwgqzyP1QqPVw@mail.gmail.com> (raw)
In-Reply-To: <OF267FCB7E.EA06E022-ON00258685.0074D9AA-00258685.0074D9AE@notes.na.collabserv.com>
On Tue, Feb 23, 2021 at 6:18 PM Bruce Mitchell <Bruce.Mitchell@ibm.com> wrote:
>
>
> I am having troubles getting kdump/kexec functioning on an
> ARM dual-core ARM Cortex-A7 (a BMC by ASPEED AST2600) and QEMU.
> I do have kexec -l loading the new kernel, but after kexec -e
> the new kernel starts booting and the I get a watchdog BUG as shown here:
> [240.343350] kexec_core: Starting new kernel
> [241.639076] IRQ36: set affinity failed(-22).
> [241.657868] Bye!
> [ 0.000000] Booting Linux on physical CPU 0xf00
>
Just our of curiosity, what happens when you try "kexec -p" and induce
a kernel panic, to jump to kdump kernel? Does it work, or it's the
same?
Also, worth to try irqpoll maybe as a parameter of the second kernel,
to see if it can progress.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2021-02-24 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 21:16 Issues with kdump/kexec on an ARM dual-core ARM Cortex-A7 Bruce Mitchell
2021-02-24 14:51 ` Guilherme G. Piccoli [this message]
2021-02-24 15:01 ` Bruce Mitchell
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=CAHD1Q_z8zhpXFUybsPX6yOW2WPuYgpxsv-k90fwgqzyP1QqPVw@mail.gmail.com \
--to=guilherme.piccoli@canonical.com \
--cc=Bruce.Mitchell@ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.