Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #58124 > unrolled thread

Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes Patrick Matthäi <pmatthaei@debian.org> - 2017-06-22 15:10 +0200
    Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes Patrick Matthäi <pmatthaei@debian.org> - 2017-07-11 10:30 +0200
      Processed: Re: vmxnet3: Reports suspect GRO implementation on  vSphere hosts / one VM crashes owner@bugs.debian.org (Debian Bug Tracking System) - 2017-07-11 10:30 +0200
      Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes Patrick Matthäi <pmatthaei@debian.org> - 2017-07-13 14:20 +0200
        Processed: Re: vmxnet3: Reports suspect GRO implementation on  vSphere hosts / one VM crashes owner@bugs.debian.org (Debian Bug Tracking System) - 2017-07-13 14:20 +0200

#58124 — Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

found #864642 4.9.30-2+deb9u1
thanks


Am 12.06.2017 um 10:02 schrieb Patrick Matthäi:
> Package: src:linux
> Version: 4.9.30-1
> Severity: important
> File: linux
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where
> appropriate ***
>
> Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to
> linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the
> "primary" interface this:
>
> TCP: ens192: Driver has suspect GRO implementation, TCP performance may
> be compromised.
>
> I can't see any performance impact. This happens on all our vSphere 6.0
> and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML
> 350 G9 and so on).
>
> Why is this bug important? Because on one VM this also produces a kernel
> panic after some time (minutes or hours). I just could get the panic
> attached as screenshot. The only "big" difference between the crashing
> host and the others may be, that it is also running PM2, NPM, NodeJS and
> a NFS kernel server.
>
> If I boot the VM with 4.9.30-1 and deactivate gro and lro with:
> ethtool -K ens192 gro off
> ethtool -K ens192 lro off
> .. it does not crash.
>
> Booting 4.9.18-1 and everything is completly fine ;)
>

The VM keeps on crashing after a few hours

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatthaei@debian.org
        patrick@linux-dev.org
*/

[toc] | [next] | [standalone]

#58338

found #864642 4.9.30-2+deb9u2
thanks

And it still crashes..


Am 22.06.2017 um 14:58 schrieb Patrick Matthäi:
> found #864642 4.9.30-2+deb9u1
> thanks
>
>
> Am 12.06.2017 um 10:02 schrieb Patrick Matthäi:
>> Package: src:linux
>> Version: 4.9.30-1
>> Severity: important
>> File: linux
>>
>> Dear Maintainer,
>>
>> *** Reporter, please consider answering these questions, where
>> appropriate ***
>>
>> Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to
>> linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the
>> "primary" interface this:
>>
>> TCP: ens192: Driver has suspect GRO implementation, TCP performance may
>> be compromised.
>>
>> I can't see any performance impact. This happens on all our vSphere 6.0
>> and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML
>> 350 G9 and so on).
>>
>> Why is this bug important? Because on one VM this also produces a kernel
>> panic after some time (minutes or hours). I just could get the panic
>> attached as screenshot. The only "big" difference between the crashing
>> host and the others may be, that it is also running PM2, NPM, NodeJS and
>> a NFS kernel server.
>>
>> If I boot the VM with 4.9.30-1 and deactivate gro and lro with:
>> ethtool -K ens192 gro off
>> ethtool -K ens192 lro off
>> .. it does not crash.
>>
>> Booting 4.9.18-1 and everything is completly fine ;)
>>
> The VM keeps on crashing after a few hours
>

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatthaei@debian.org
        patrick@linux-dev.org
*/

[toc] | [prev] | [next] | [standalone]

#58339 — Processed: Re: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

Processing commands for control@bugs.debian.org:

> found #864642 4.9.30-2+deb9u2
Bug #864642 [src:linux] vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes
Marked as found in versions linux/4.9.30-2+deb9u2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
864642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864642
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#58358

forwarded #864642 https://bugzilla.kernel.org/show_bug.cgi?id=191201
thanks


Am 11.07.2017 um 10:24 schrieb Patrick Matthäi:
> found #864642 4.9.30-2+deb9u2
> thanks
>
> And it still crashes..
>
>
> Am 22.06.2017 um 14:58 schrieb Patrick Matthäi:
>> found #864642 4.9.30-2+deb9u1
>> thanks
>>
>>
>> Am 12.06.2017 um 10:02 schrieb Patrick Matthäi:
>>> Package: src:linux
>>> Version: 4.9.30-1
>>> Severity: important
>>> File: linux
>>>
>>> Dear Maintainer,
>>>
>>> *** Reporter, please consider answering these questions, where
>>> appropriate ***
>>>
>>> Since updating the kernel from linux-image-4.9.0-2-amd64 (4.9.18-1) to
>>> linux-image-4.9.0-3-amd64 (4.9.30-1) all VMs report - just for the
>>> "primary" interface this:
>>>
>>> TCP: ens192: Driver has suspect GRO implementation, TCP performance may
>>> be compromised.
>>>
>>> I can't see any performance impact. This happens on all our vSphere 6.0
>>> and 6.5 hosts (running on HPE ProLiant DL 360 G8 - G9 HW / ProLiant ML
>>> 350 G9 and so on).
>>>
>>> Why is this bug important? Because on one VM this also produces a kernel
>>> panic after some time (minutes or hours). I just could get the panic
>>> attached as screenshot. The only "big" difference between the crashing
>>> host and the others may be, that it is also running PM2, NPM, NodeJS and
>>> a NFS kernel server.
>>>
>>> If I boot the VM with 4.9.30-1 and deactivate gro and lro with:
>>> ethtool -K ens192 gro off
>>> ethtool -K ens192 lro off
>>> .. it does not crash.
>>>
>>> Booting 4.9.18-1 and everything is completly fine ;)
>>>
>> The VM keeps on crashing after a few hours
>>

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatthaei@debian.org
        patrick@linux-dev.org
*/

[toc] | [prev] | [next] | [standalone]

#58359 — Processed: Re: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

Processing commands for control@bugs.debian.org:

> forwarded #864642 https://bugzilla.kernel.org/show_bug.cgi?id=191201
Bug #864642 [src:linux] vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes
Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=191201'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
864642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864642
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web