All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yong Li" <yong.b.li@linux.intel.com>
To: "'Vijay Khemka'" <vijaykhemka@fb.com>,
	"'Kun Yi'" <kunyi@google.com>, "'Joel Stanley'" <joel@jms.id.au>,
	"'Andrew Jeffery'" <andrew@aj.id.au>,
	"'OpenBMC Maillist'" <openbmc@lists.ozlabs.org>
Subject: RE: Accessing kernel panic information without BMC console?
Date: Sun, 29 Sep 2019 15:47:38 +0800	[thread overview]
Message-ID: <000201d5769a$2b91bc30$82b53490$@linux.intel.com> (raw)
In-Reply-To: <E6FDE343-5FC6-4493-9D53-BE6317525DB7@fb.com>

I am working on this ramoops feature too, and it works on ast2500, just enable some kernel config and modify the dts.

I will send out a patch about this change later.

Thanks,
Yong
-----Original Message-----
From: openbmc <openbmc-bounces+yong.b.li=linux.intel.com@lists.ozlabs.org> On Behalf Of Vijay Khemka
Sent: Saturday, September 28, 2019 6:28 AM
To: Kun Yi <kunyi@google.com>; Joel Stanley <joel@jms.id.au>; Andrew Jeffery <andrew@aj.id.au>; OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Accessing kernel panic information without BMC console?



On 9/27/19, 3:05 PM, "openbmc on behalf of Kun Yi" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of kunyi@google.com> wrote:

    Hello there,
    
    Wonder whether anyone has had experience persisting kernel panic
    information or sending them through network? For a lot of our devices
    the console is either unconnected or served by obmc-console-client
    only, which wouldn't be able to capture kernel oops.
    
    We are starting to look into these tools:
    
    https://www.kernel.org/doc/html/v5.3/admin-guide/ramoops.html
    Ramoops says it requires persistent RAM.. Which may make it infeasible
    since we don't persist memory (or, we try not to).
    
    https://urldefense.proofpoint.com/v2/url?u=https-3A__linux.die.net_man_8_netdump&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=0H6Yf0igviHCOSHAbOPQxxM-_B0Lh1EyZm4dpdMqe2g&s=H3n57FRZwV0z_wOHqmaiRa-kQ6h3doWg712SV4ez-GU&e= 
    netdump seems promising.
    
    https://www.kernel.org/doc/html/v5.3/admin-guide/kdump/kdump.html
    It seems we need more pieces to get kdump working. Have anyone tried
    kexec/kdump on their platforms?

I have used kdump in past was very happy with it. Yes, it needs lot more pieces to make it work.
    
    
    
    Regards,
    Kun
    

  reply	other threads:[~2019-09-29  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 22:01 Accessing kernel panic information without BMC console? Kun Yi
2019-09-27 22:28 ` Vijay Khemka
2019-09-29  7:47   ` Yong Li [this message]
2019-09-30 18:08     ` Kun Yi
2019-09-30 20:21       ` Neeraj Ladkani
2019-09-30 18:06   ` Kun Yi

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='000201d5769a$2b91bc30$82b53490$@linux.intel.com' \
    --to=yong.b.li@linux.intel.com \
    --cc=andrew@aj.id.au \
    --cc=joel@jms.id.au \
    --cc=kunyi@google.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=vijaykhemka@fb.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.