On 10.08.2017 15:09, Andrew Moore wrote:
> Both of those reports were me. I suspect the issue may be isolated to
> the HPE custom implementation of the ESXi 6.5u1 build. I haven't seen
> any similar reports of people using the vanilla 6.5u1 build.
Not surprising. It wouldn't be the first time HPE
On Tue, 8 Aug 2017 11:38:06 +0200 (CEST) Sven Hartge
wrote:
> Um 16:22 Uhr am 03.08.17 schrieb Sven Hartge:
> > On 03.08.2017 15:34, Patrick Matthäi wrote:
> >> Am 16.07.2017 um 23:42 schrieb Ben Hutchings:
> >>> On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote:
>
> > Could this be https:/
Um 16:22 Uhr am 03.08.17 schrieb Sven Hartge:
> On 03.08.2017 15:34, Patrick Matthäi wrote:
>> Am 16.07.2017 um 23:42 schrieb Ben Hutchings:
>>> On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote:
> Could this be https://bugzilla.kernel.org/show_bug.cgi?id=191201 ?
>>> Note that this has be
On 03.08.2017 15:34, Patrick Matthäi wrote:
> Am 16.07.2017 um 23:42 schrieb Ben Hutchings:
>> On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote:
Could this be https://bugzilla.kernel.org/show_bug.cgi?id=191201 ?
>> Note that this has been root-caused as a bug in the virtual device, not
>>
Processing commands for cont...@bugs.debian.org:
> severity #864642 normal
Bug #864642 [src:linux] vmxnet3: Reports suspect GRO implementation on vSphere
hosts / one VM crashes
Severity set to 'normal' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
severity #864642 normal
thanks
Am 16.07.2017 um 23:42 schrieb Ben Hutchings:
> Control: tag -1 moreinfo
>
> Sven asked this, but forgot to add you to the recipients:
>
> On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote:
>> Hi!
>>
>>> Could this be https://bugzilla.kernel.org/show_bug.cgi?id=1
Control: tag -1 moreinfo
Sven asked this, but forgot to add you to the recipients:
On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote:
> Hi!
>
> > Could this be https://bugzilla.kernel.org/show_bug.cgi?id=191201 ?
Note that this has been root-caused as a bug in the virtual device, not
the dri
Processing control commands:
> tag -1 moreinfo
Bug #864642 [src:linux] vmxnet3: Reports suspect GRO implementation on vSphere
hosts / one VM crashes
Added tag(s) moreinfo.
--
864642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864642
Debian Bug Tracking System
Contact ow...@bugs.debian.or
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
>>
>>
>>
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 M
Hi!
Could this be https://bugzilla.kernel.org/show_bug.cgi?id=191201 ?
Try the following, from comment 37
https://bugzilla.kernel.org/show_bug.cgi?id=191201#c37
| In the meantime, suggested workaround:
| - disable rx data ring: ethtool -G eth? rx-mini 0
Also adding "vmxnet3.rev.30 = FALSE" to
On Mon, 12 Jun 2017 10:02:56 +0200 =?UTF-8?Q?Patrick_Matth=c3=a4i?=
wrote:
> 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 implementat
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
13 matches
Mail list logo