From: Andrew Lunn <andrew@lunn.ch>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Sunil Goutham <sgoutham@cavium.com>, netdev <netdev@vger.kernel.org>
Subject: Re: thunderx sgmii interface hang
Date: Fri, 22 Dec 2017 23:45:07 +0100 [thread overview]
Message-ID: <20171222224507.GD22041@lunn.ch> (raw)
In-Reply-To: <CAJ+vNU3Gn2YXwMegzh+D2mTcAfwauzKoXhTWBzZyROWG+UxKQA@mail.gmail.com>
> Currently I'm not using the DP83867_PHY driver (after verifying the
> issue occurs with or without that driver).
>
> It does not occur if I limit UDP (ie 950mbps). I disabled all offloads
> and the issue still occurs.
> I'm told that the particular Cavium reference board with an SGMII phy
> doesn't show this issue (I don't have that specific board to do my own
> testing or comparisons against our board) so I'm inclined to think it
> has something to do with an interaction with the DP83867 PHY. I would
> like to start poking at PHY registers to see if I can find anything
> unusual. The best way to do that from userspace is via
> SIOCGMIIREG/SIOCSMIIREG right? The thunderx nic doesn't currently
> support ioctl's so I guess I'll have to add that support unless
> there's a way to get at phy registers from userspace through a phy
> driver?
phy_mii_ioctl() does what you need, and is simple to use.
mii-tool will then give you access to the standard PHY registers.
Andre
next prev parent reply other threads:[~2017-12-22 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 23:05 thunderx sgmii interface hang Tim Harvey
2017-12-13 19:43 ` Andrew Lunn
2017-12-18 21:53 ` Tim Harvey
2017-12-19 9:47 ` Sunil Kovvuri
2017-12-19 20:52 ` Andrew Lunn
2017-12-22 22:19 ` Tim Harvey
2017-12-22 22:45 ` Andrew Lunn [this message]
2017-12-23 0:22 ` Tim Harvey
2017-12-22 23:00 ` David Daney
2017-12-23 0:22 ` Tim Harvey
2017-12-23 0:30 ` David Daney
2018-01-02 19:18 ` Tim Harvey
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=20171222224507.GD22041@lunn.ch \
--to=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=sgoutham@cavium.com \
--cc=tharvey@gateworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).