The patch is now upstream in 4.4.20 and 4.7.3, both released on 7th of
September.
>From what I know, it's not in the Ubuntu kernels yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581777
Title:
This seems to be a problem in ESXi, it was promised to be fixed in 6.0
Update 3 which hasn't been released as of yet.
However there is now a workaround patch that will make it to 4.4 and 4.7
stable trees:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-
queue.git;a=summary
queue-4.4/
Reported to Thomas Gleixner and linux-kernel:
https://lkml.org/lkml/2016/7/23/93
Jiang Liu is no longer reachable under the address specified in
MAINTAINERS: "Recipient address rejected: User unknown in virtual
mailbox table".
--
You received this bug notification because you are a member of Ubu
Foster "Forst" Snowhill, the issue you are reporting is an upstream one.
Could you please report this problem following the instructions verbatim
at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate
mailing list (TO Jiang Liu, and Thomas Gleixner CC linux-kernel)?
Please provide a di
** Tags added: bisect-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581777
Title:
igb transmit queue times out
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
Also, the bug is present in 4.7-rc7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581777
Title:
igb transmit queue times out
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Attachment added: "Bisect for bug"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581777/+attachment/4703544/+files/Bisect.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: kernel-bug-exists-upstream-4.6-rc7 needs-bisect
** Tags added: kernel-
52f518a3a7c2f80551a38d38be28bc9f335e713c is the first bad commit
Full bisect log attached.
A couple of notes:
1. Often the bug is not reproduced the first time the system is booted
with a given kernel version. Subsequent boots reproduce the bug.
2. In order to get bootable kernels from commit
Foster "Forst" Snowhill, the next step is to fully commit bisect from
kernel 3.19 to 4.4 in order to identify the last good kernel commit,
followed immediately by the first bad one. This will allow for a more
expedited analysis of the root cause of your issue. Could you please do
this following htt
Bug reported to Intel Ethernet Driver mailing list:
http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-
Mon-20160516/005444.html
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
Tested with latest mainline kernel (linux-
image-4.6.0-040600rc7-generic), problem persists, appropriate tag added.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
12 matches
Mail list logo
