From: Andy Lutomirski <luto@amacapital.net>
To: Network Development <netdev@vger.kernel.org>,
Solarflare linux maintainers <linux-net-drivers@solarflare.com>,
Shradha Shah <sshah@solarflare.com>
Subject: sfc MC errors when using accelerated RFS
Date: Thu, 19 May 2016 09:01:53 -0700 [thread overview]
Message-ID: <CALCETrXHQr5K_ttGaF2N5Og0vcDcpsM-2uu8h6mRbgryBfAyHA@mail.gmail.com> (raw)
After a couple weeks of uptime under moderate accelerated RFS load
(mostly long-lived flows), I start getting errors like this:
sfc 0000:05:00.1 p3p2: MC command 0x8a inlen 108 failed rc=-28 (raw=28) arg=2
I've seem problems like this for a long time, and they're currently
happening on a stock 4.5.2 kernel using the in-tree sfc driver. My
best guess is that something's wrong with the RFS state machine or
flow tracking and that the core or the driver's idea of the loaded
filters gets out of sync with the NIC.
If this isn't fixed, at some point we'll give up on Solarflare devices
and switch to something else.
I think that SolarFlare is internally tracking this as issue 42806.
--Andy
reply other threads:[~2016-05-19 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CALCETrXHQr5K_ttGaF2N5Og0vcDcpsM-2uu8h6mRbgryBfAyHA@mail.gmail.com \
--to=luto@amacapital.net \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=sshah@solarflare.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).