From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753201AbcGYSN5 (ORCPT ); Mon, 25 Jul 2016 14:13:57 -0400 Received: from forward3m.cmail.yandex.net ([5.255.216.21]:48936 "EHLO forward3m.cmail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752176AbcGYSN4 (ORCPT ); Mon, 25 Jul 2016 14:13:56 -0400 X-Greylist: delayed 427 seconds by postgrey-1.27 at vger.kernel.org; Mon, 25 Jul 2016 14:13:55 EDT Authentication-Results: smtp12.mail.yandex.net; dkim=pass header.i=@forstwoof.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0,1 0 Subject: Re: PROBLEM: Intel I210AT NIC resets while using PCI passthrough on ESXi (regression) To: Thomas Gleixner References: Cc: LKML , Matthias Prager , Jason Taylor , Marc Zyngier From: Foster Snowhill Organization: ForstWoof Message-ID: Date: Mon, 25 Jul 2016 21:06:45 +0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:49.0) Gecko/20100101 Thunderbird/49.0a2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25.07.16 13:56, Thomas Gleixner wrote: > On Sat, 23 Jul 2016, Foster Snowhill wrote: >> [1.] One line summary of the problem: >> >> Intel I210AT NIC resets while using PCI passthrough on ESXi (regression) > > That has been reported before and so far this has been believed to be a vmware > issue. Native hardware and KVM do not expose that. See: > > http://marc.info/?l=linux-kernel&m=145280623530135&w=2 > http://marc.info/?l=linux-kernel&m=145879968005421&w=2 This is indeed the same symptoms I encountered in my case. More than that, I have an LSI 2008 adapter which is also being passed through in the same manner as the NIC, absolutely the same problem there too. Before doing the bisect I considered it a separate issue and planned to work on it later. > Could you please give the patch below a try? It might be related, but I'm not > sure whether it will cure that particular vmware oddity. Patch fixed the issue for me. Did 4-5 reboots just to be sure, all working properly, no adapter resets. Just for the sake of experiment built a clean 4.7 kernel without the patch, issue still present there as expected.