All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
To: dyoung@redhat.com, panand@redhat.com, vgoyal@redhat.com,
	maneesh@in.ibm.com, kexec@lists.infradead.org
Subject: Re: Regarding your presentation "CFP, #LinuxCon, Beijing, June 19-20,  2017"
Date: Thu, 1 Apr 2021 12:17:34 -0700	[thread overview]
Message-ID: <6a13d2c5-64f5-6543-c55e-d0191bd78755@linux.vnet.ibm.com> (raw)
In-Reply-To: <d0ea2ae4-211f-8bbc-1789-72e941f865f2@linux.vnet.ibm.com>

On 4/1/2021 12:04, Bruce Mitchell wrote:
> Hello David, Pratyush, Vivek, and Maneesh,
> 
> This did not seem to send properly from IBM Notes; trying an alternative 
> plain text style.
> 
> And I am also referencing:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/kdump/kdump.rst 
> 
> 
> I am Senior System Software / Firmware / Embedded Engineer do Linux 
> Kernel Developer for OpenBMC Firmware at @IBM, @ibm-openbmc, and @openbmc.
> 
> I am having troubles getting kdump functioning (fully implemented) on 
> our SoC is the ASPEED AST2600 which is an ARM Cortex A7 core.
> I need a crash dump on a kernel panic.  I need to get kdump working on 
> this platform.
> Our system has 512MB of RAM  and somewhere between 8GB and 32GB of eMMC 
> for mass storage; kernel panic mounts haven't always gone right,
> but that seem build dependent.
> 
> My Ubuntu 18.04 LTS Server it just worked first time, no issues.
> 
> My kernel is:
>      Bruce.Mitchell@fstone05p1:~/tmp/openbmc/build/rainier/tmp/work-shared/rainier/kernel-source$ git log | head
>      commit a3e4860badca60a766b53d169c1c9822cd65b344
>      Author: Zev Weiss <zev@bewilderbeest.net>
>      Date:   Mon Mar 29 19:23:38 2021 -0500
> 
> I have kexec -l functioning about like I would expect.
> I can get kexec -p to boot the "crash" kernel (my primary kernel and my 
> crash kernel are the same).
> 
> My kexec command line; I have tried with out 
> --initrd=/home/kexec_files/initrd as well.
>      kexec -d -p /home/kexec_files/kernel.zImage \
>                --initrd=/home/kexec_files/initrd \
>                --dtb=/home/kexec_files/dtb \
>                --append="earlycon crashkernel=24M console=ttyS4,115200n8 
> rootwait root=PARTLABEL=rofs-a 1 reset_devices"
> 
> I have no core files in /proc
>      sh-5.1# ls -l /proc/ | grep core
>      sh-5.1#
> So what or where should I copy from for kdump?
> 
> OpenBMC builds on OpenEmbedded and Yocto all part of The Linux 
> Foundation Projects.
> 
> I feel like I am just missing some simple clue or two.
> 
> 
> Any suggestions, pointers, critique would be highly appreciated!
> 
> Thank you!
> 
> -- 
> Bruce Mitchell


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

           reply	other threads:[~2021-04-01 19:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <d0ea2ae4-211f-8bbc-1789-72e941f865f2@linux.vnet.ibm.com>]

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=6a13d2c5-64f5-6543-c55e-d0191bd78755@linux.vnet.ibm.com \
    --to=bruce.mitchell@linux.vnet.ibm.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=maneesh@in.ibm.com \
    --cc=panand@redhat.com \
    --cc=vgoyal@redhat.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 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.