On 26.07.16 17:06, Thomas Gleixner wrote:
> On Tue, 26 Jul 2016, Foster Snowhill wrote:
>> On 26.07.16 16:49, Thomas Gleixner wrote:
>>> On Mon, 25 Jul 2016, Foster Snowhill wrote:
>>>> On 25.07.16 13:56, Thomas Gleixner wrote:
>>>>> Could you please gi
On 26.07.16 16:49, Thomas Gleixner wrote:
> On Mon, 25 Jul 2016, Foster Snowhill wrote:
>> On 25.07.16 13:56, Thomas Gleixner wrote:
>>> Could you please give the patch below a try? It might be related, but I'm
>>> not
>>> sure whether it will cure that pa
On 26.07.16 14:46, Thomas Gleixner wrote:
> Can you please try whether the replacement patch below fixes your issue as
> well?
This one doesn't fix the issue, getting resets again. Patch applied to HEAD
(commit e65805251f2db69c9f67ed8062ab82526be5a374).
[4.377316] igb: Intel(R) Gigabit Ether
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 b
[1.] One line summary of the problem:
Intel I210AT NIC resets while using PCI passthrough on ESXi (regression)
[2.] Full description of the problem/report:
Intel I210AT NIC running on the latest (4.7-rc7) kernel revision suffers a
"transmit queue 0 timed out" issue, which makes the NIC unusabl
5 matches
Mail list logo
