linux-kernel - Re: PROBLEM: Intel I210AT NIC resets while using PCI passthrough on ESXi (regression)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Jul 2016 21:06:45 +0300
From:	Foster Snowhill <forst@...stwoof.ru>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Matthias Prager <linux@...thiasprager.de>,
	Jason Taylor <jason.taylor@...plivity.com>,
	Marc Zyngier <marc.zyngier@....com>
Subject: Re: PROBLEM: Intel I210AT NIC resets while using PCI passthrough on
 ESXi (regression)

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.