From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] i40e MDD events
Date: Mon, 2 Oct 2017 10:50:35 -0700 [thread overview]
Message-ID: <20171002105035.000047d6@intel.com> (raw)
In-Reply-To: <CAOZ2QJPHqPftMdWYfAM01grFehCyrySXy6VwhP2pCE+98rmkkg@mail.gmail.com>
On Mon, 2 Oct 2017 09:31:46 -0400
Dan Streetman <dan.streetman@canonical.com> wrote:
> unfortunately the updated firmware did not help; an MDD event happened
> again after upgrading to 6.01.
Hi Dan, sorry that didn't help.
> > Can you answer my questions about specifically what events in the NIC
> > will cause it to generate a MDD, and specifically what does MDD event
> > "2" indicate?
>
> It there any possibility to get more info about the MDD event details?
> Like what specifically the NIC didn't like?
Unfortunately the MDD mechanism didn't work for reporting as we had
hoped. I'll send you the troubleshooting instructions off-list.
Jesse
prev parent reply other threads:[~2017-10-02 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 20:53 [Intel-wired-lan] i40e MDD events Dan Streetman
2017-09-28 23:27 ` Wyborny, Carolyn
2017-09-29 12:17 ` Dan Streetman
2017-10-02 13:31 ` Dan Streetman
2017-10-02 17:50 ` Jesse Brandeburg [this message]
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=20171002105035.000047d6@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@osuosl.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