[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#689429: marked as done (vmxnet3 driver with package drops on ESXi 5.0)



Your message dated Sun, 07 Feb 2016 22:43:09 +0000
with message-id <E1aSY2v-0006KU-Uk@deadeye>
and subject line Closing bugs assigned to linux-2.6 package
has caused the Debian Bug report #689429,
regarding vmxnet3 driver with package drops on ESXi 5.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
689429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689429
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-46
Severity: important

Hello,

first, I can not check, if Wheezy is also affected.

Using ESXi 5.0 with Linux guests (in this case many amd64 Squeeze machines with three vmxnet3 adapter for each VM) could cause package drops, here especially on using UDP (name resolving). So I saw that some machines produced ~ 20 drops / day.
This has been fixed by VMware last week:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032587

Could you please adopt this fix for Squeeze (maybe also Wheezy)?

Cheers

--- End Message ---
--- Begin Message ---
Version: 3.4.1-1~experimental.1+rm

Debian 6.0 Long Term Support has now ended, and the 'linux-2.6' source
package will no longer be updated.  This bug is being closed on the
assumption that it does not affect the kernel versions in newer Debian
releases.

If you can still reproduce this bug in a newer release, please reopen
the bug report and reassign it to 'src:linux' and the affected version
of the package.  You can find the package version for the running
kernel by running:

    uname -v

or the versions of all installed kernel packages by running:

    dpkg -l 'linux-image-[34]*' | grep ^.i

and looking at the third column.

I apologise that we weren't able to provide a specific resolution for
this bug.

Ben.

-- 
Ben Hutchings - Debian developer, member of Linux kernel and LTS teams

--- End Message ---

Reply to: