From: Jakub Kicinski <kubakici@wp.pl>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Cc: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Ganesh GR <ganeshgr@chelsio.com>,
Nirranjan Kirubaharan <nirranjan@chelsio.com>,
Indranil Choudhury <indranil@chelsio.com>
Subject: Re: [PATCH net-next] cxgb4: append firmware dump to vmcore in kernel panic
Date: Tue, 20 Feb 2018 16:43:04 -0800 [thread overview]
Message-ID: <20180220164304.2a38c962@cakuba.netronome.com> (raw)
In-Reply-To: <20180219123416.GA7737@chelsio.com>
On Mon, 19 Feb 2018 18:04:17 +0530, Rahul Lakkireddy wrote:
> Our requirement is to analyze the state of firmware/hardware at the
> time of kernel panic.
I was wondering about this since you posted the patch and I can't come
up with any specific scenario where kernel crash would correlate
clearly with device state in non-trivial way.
Perhaps there is something about cxgb4 HW/FW that makes this useful.
Could you explain? Could you give a real life example of a bug?
Is it related to the TOE-looking TLS offload Atul is posting?
Is the panic you're targeting here real or manually triggered from user
space to get a full dump of kernel and FW?
That's me trying to guess what you're doing.. :)
next prev parent reply other threads:[~2018-02-21 0:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 13:54 [PATCH net-next] cxgb4: append firmware dump to vmcore in kernel panic Rahul Lakkireddy
2018-02-16 20:41 ` David Miller
2018-02-19 12:34 ` Rahul Lakkireddy
2018-02-19 15:01 ` David Miller
2018-02-21 0:43 ` Jakub Kicinski [this message]
2018-02-21 0:51 ` Florian Fainelli
2018-02-21 1:04 ` Jakub Kicinski
2018-02-21 15:25 ` Rahul Lakkireddy
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=20180220164304.2a38c962@cakuba.netronome.com \
--to=kubakici@wp.pl \
--cc=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=indranil@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.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.