All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Cc: indranil@chelsio.com, netdev@vger.kernel.org,
	nirranjan@chelsio.com, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, stephen@networkplumber.org,
	ganeshgr@chelsio.com, viro@zeniv.linux.org.uk,
	linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, davem@davemloft.net,
	ebiederm@xmission.com
Subject: Re: [PATCH net-next v2 2/2] cxgb4: collect hardware dump in second kernel
Date: Sat, 24 Mar 2018 16:18:52 +0100	[thread overview]
Message-ID: <20180324151852.GE31941@lunn.ch> (raw)
In-Reply-To: <f06cca21650affa10d83a28dbd7fb577792e35a9.1521888444.git.rahul.lakkireddy@chelsio.com>

On Sat, Mar 24, 2018 at 04:26:34PM +0530, Rahul Lakkireddy wrote:
> Register callback to collect hardware/firmware dumps in second kernel
> before hardware/firmware is initialized.  The dumps for each device
> will be available under /sys/kernel/crashdd/cxgb4/ directory in second
> kernel.
> 
> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
> Signed-off-by: Ganesh Goudar <ganeshgr@chelsio.com>

Thanks for adding generic documentation about the files in sysfs.

However, you don't add any specific documentation here about the cxgb4
crash dump. How am i supposed to interpret it? Does it follow any of
the standard core dump formats? How do i use gdb with it? Are there
some specific tools i should use to analyse it?

Thanks
	Andrew

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

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Cc: netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, viro@zeniv.linux.org.uk,
	ebiederm@xmission.com, stephen@networkplumber.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	ganeshgr@chelsio.com, nirranjan@chelsio.com,
	indranil@chelsio.com
Subject: Re: [PATCH net-next v2 2/2] cxgb4: collect hardware dump in second kernel
Date: Sat, 24 Mar 2018 16:18:52 +0100	[thread overview]
Message-ID: <20180324151852.GE31941@lunn.ch> (raw)
In-Reply-To: <f06cca21650affa10d83a28dbd7fb577792e35a9.1521888444.git.rahul.lakkireddy@chelsio.com>

On Sat, Mar 24, 2018 at 04:26:34PM +0530, Rahul Lakkireddy wrote:
> Register callback to collect hardware/firmware dumps in second kernel
> before hardware/firmware is initialized.  The dumps for each device
> will be available under /sys/kernel/crashdd/cxgb4/ directory in second
> kernel.
> 
> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
> Signed-off-by: Ganesh Goudar <ganeshgr@chelsio.com>

Thanks for adding generic documentation about the files in sysfs.

However, you don't add any specific documentation here about the cxgb4
crash dump. How am i supposed to interpret it? Does it follow any of
the standard core dump formats? How do i use gdb with it? Are there
some specific tools i should use to analyse it?

Thanks
	Andrew

  reply	other threads:[~2018-03-24 15:19 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-24 10:56 [PATCH net-next v2 0/2] kernel: add support to collect hardware logs in crash recovery kernel Rahul Lakkireddy
2018-03-24 10:56 ` Rahul Lakkireddy
2018-03-24 10:56 ` [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel Rahul Lakkireddy
2018-03-24 10:56   ` Rahul Lakkireddy
2018-03-25 12:43   ` kbuild test robot
2018-03-25 12:43     ` kbuild test robot
2018-03-30 10:39   ` Jiri Pirko
2018-03-30 10:39     ` Jiri Pirko
2018-03-30 10:51     ` Rahul Lakkireddy
2018-03-30 10:51       ` Rahul Lakkireddy
2018-03-30 18:42       ` Eric W. Biederman
2018-03-30 18:42         ` Eric W. Biederman
2018-04-02  9:11         ` Jiri Pirko
2018-04-02  9:11           ` Jiri Pirko
2018-04-02 12:21           ` Andrew Lunn
2018-04-02 12:21             ` Andrew Lunn
2018-04-02 12:30           ` Rahul Lakkireddy
2018-04-02 12:30             ` Rahul Lakkireddy
2018-04-03  7:04             ` Jiri Pirko
2018-04-03  7:04               ` Jiri Pirko
2018-03-30 15:11     ` Andrew Lunn
2018-03-30 15:11       ` Andrew Lunn
2018-04-02  9:12       ` Jiri Pirko
2018-04-02  9:12         ` Jiri Pirko
2018-04-03  5:43         ` Alex Vesker
2018-04-03  5:43           ` Alex Vesker
2018-04-03 12:35           ` Andrew Lunn
2018-04-03 12:35             ` Andrew Lunn
2018-03-24 10:56 ` [PATCH net-next v2 2/2] cxgb4: " Rahul Lakkireddy
2018-03-24 10:56   ` Rahul Lakkireddy
2018-03-24 15:18   ` Andrew Lunn [this message]
2018-03-24 15:18     ` Andrew Lunn
2018-03-24 22:18   ` Thadeu Lima de Souza Cascardo
2018-03-24 22:18     ` Thadeu Lima de Souza Cascardo
2018-03-25  0:17     ` Eric W. Biederman
2018-03-25  0:17       ` Eric W. Biederman
2018-03-24 15:20 ` [PATCH net-next v2 0/2] kernel: add support to collect hardware logs in crash recovery kernel Eric W. Biederman
2018-03-24 15:20   ` Eric W. Biederman
2018-03-26 13:45   ` Rahul Lakkireddy
2018-03-26 13:45     ` Rahul Lakkireddy
2018-03-27 13:17     ` Eric W. Biederman
2018-03-27 13:17       ` Eric W. Biederman
2018-03-27 15:27       ` Rahul Lakkireddy
2018-03-27 15:27         ` Rahul Lakkireddy
2018-03-27 15:59         ` Eric W. Biederman
2018-03-27 15:59           ` Eric W. Biederman

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=20180324151852.GE31941@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=ganeshgr@chelsio.com \
    --cc=indranil@chelsio.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nirranjan@chelsio.com \
    --cc=rahul.lakkireddy@chelsio.com \
    --cc=stephen@networkplumber.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.