All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Eran Ben Elisha <eranbe@mellanox.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
	Chris Preimesberger <chrisp@transition.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bug: 'ethtool -m' reports spurious alarm & warning threshold values for QSFP28 transceivers
Date: Thu, 27 Sep 2018 17:32:04 +0200	[thread overview]
Message-ID: <20180927153204.GE12979@lunn.ch> (raw)
In-Reply-To: <06e89e21-41b2-0711-4ff7-0af5fd7ef53e@mellanox.com>

> Driver return 256 bytes (reading it correctly, I verified it, no overruns),
> however the extra bytes are presented due to this bug (expecting to parse
> 640 bytes).
> 
> Do you see another bug here? Am I missing something?

Hi Erin

Please could you try ethtool -m raw on so you get a binary dump.  The
file which Chris provided had more bytes in it than 256.

Thanks
	Andrew

  reply	other threads:[~2018-09-27 21:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 19:29 bug: 'ethtool -m' reports spurious alarm & warning threshold values for QSFP28 transceivers Chris Preimesberger
2018-09-26 19:44 ` Andrew Lunn
2018-09-26 20:47   ` Chris Preimesberger
2018-09-26 21:46     ` Andrew Lunn
2018-09-26 21:34 ` Neil Horman
2018-09-26 21:58   ` Andrew Lunn
2018-09-27 13:23     ` Neil Horman
2018-09-27 13:25   ` Eran Ben Elisha
2018-09-27 14:52     ` Andrew Lunn
2018-09-27 15:20       ` Eran Ben Elisha
2018-09-27 15:32         ` Andrew Lunn [this message]
2018-09-27 16:08           ` Chris Preimesberger
2018-09-27 16:38             ` Andrew Lunn
2018-09-27 18:56               ` Chris Preimesberger
2018-09-27 20:17                 ` Chris Preimesberger
2018-10-02  7:10           ` Eran Ben Elisha

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=20180927153204.GE12979@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=chrisp@transition.com \
    --cc=eranbe@mellanox.com \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.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.