From: David Ahern <dsa@cumulusnetworks.com>
To: Arkadi Sharshevsky <arkadis@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: devlink dump of mlxsw_adj table triggers a panic
Date: Wed, 4 Oct 2017 16:57:35 -0700 [thread overview]
Message-ID: <78e0bce8-e122-ab92-2f48-e9d278f4d2b4@cumulusnetworks.com> (raw)
The following devlink command on a 2700 triggers a panic every time.
Kernel is net-next at 26873308b21654b6e0785b9f9e2c5414d37a4c4c
$ devlink dpipe table dump pci/0000:03:00.0 name mlxsw_adj
devlink answers: No buffer space available
<hang>
I have seen several different stack traces and varying amounts of EMAD
errors on console:
[ 77.453364] mlxsw_spectrum 0000:03:00.0: EMAD reg access failed
(tid=64c24a400003688,reg_id=200b(sfn),type=query,status=0(operation
performed))
[ 77.466568] mlxsw_spectrum 0000:03:00.0: Failed to get FDB notifications
If it does not reproduce for you let me know and I'll grab a trace.
David
next reply other threads:[~2017-10-04 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 23:57 David Ahern [this message]
2017-10-08 7:43 ` devlink dump of mlxsw_adj table triggers a panic Arkadi Sharshevsky
2017-10-08 15:04 ` David Ahern
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=78e0bce8-e122-ab92-2f48-e9d278f4d2b4@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=arkadis@mellanox.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox