[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180220164304.2a38c962@cakuba.netronome.com>
Date: Tue, 20 Feb 2018 16:43:04 -0800
From: Jakub Kicinski <kubakici@...pl>
To: Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>
Cc: David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Ganesh GR <ganeshgr@...lsio.com>,
Nirranjan Kirubaharan <nirranjan@...lsio.com>,
Indranil Choudhury <indranil@...lsio.com>
Subject: Re: [PATCH net-next] cxgb4: append firmware dump to vmcore in
kernel panic
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.. :)
Powered by blists - more mailing lists