From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
Date: Mon, 2 Oct 2017 10:50:35 -0700
Subject: [Intel-wired-lan] i40e MDD events
In-Reply-To: <CAOZ2QJPHqPftMdWYfAM01grFehCyrySXy6VwhP2pCE+98rmkkg@mail.gmail.com>
References: <CAOZ2QJPbOrGLoZWnZUY268owFsFxFq-UcdYLbUn1Kf7tzE9oHg@mail.gmail.com>
 <9BBC4E0CF881AA4299206E2E1412B6265A15909B@ORSMSX102.amr.corp.intel.com>
 <CAOZ2QJOQLyUzQa=E6QYjmGKcn7P9BL3N8OhUrJicRjTpr5Dp6g@mail.gmail.com>
 <CAOZ2QJPHqPftMdWYfAM01grFehCyrySXy6VwhP2pCE+98rmkkg@mail.gmail.com>
Message-ID: <20171002105035.000047d6@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: intel-wired-lan@osuosl.org
List-ID: <intel-wired-lan.osuosl.org>

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