This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764892 Title: e1000e msix interrupts broken in linux-image-4.15.0-15-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == Linux kernel 4.15 has introduced a bug in e1000e msix interrupt drivers, which violates the e1000e specification. Specifically, the driver configures auto-clearing of the "OTHER" interrupt types, and the "OTHER" interrupt handler expects to see an uncleared interrupt source for the "OTHER" types; consequently, the link state change interrupts are not identified by the driver, and thus the virtual E1000e device doesn't function correctly inside VMware VMs. This patch Fixes: 4aea7a5c5e94 ("e1000e: Avoid receiver overrun interrupt bursts") == Fix == 745d0bd3af99 ("e1000e: Remove Other from EIAC") == Regression Potential == Low. Fixes an existing regression and limited to e1000e driver. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Original Bug Description == Hi Ubuntu folks, Linux kernel 4.15 has introduced a bug in e1000e msix interrupt drivers, which violates the e1000e specification. Specifically, the driver configures auto-clearing of the "OTHER" interrupt types, and the "OTHER" interrupt handler expects to see an uncleared interrupt source for the "OTHER" types; consequently, the link state change interrupts are not identified by the driver, and thus the virtual E1000e device doesn't function correctly inside VMware VMs. I have verified that Linux kernel 4.16.2 has fixed the issues and our on-perm QE has verified 4.16-RC functions correctly inside VMware VMs. Could you please crossport the fix from linux-4.16 into Ubuntu 18.04 that would be frozen in 2 days? Here are the change history: https://lkml.org/lkml/2018/3/25/248 Benjamin Poirier (7): e1000e: Remove Other from EIAC Partial revert "e1000e: Avoid receiver overrun interrupt bursts" e1000e: Fix queue interrupt re-raising in Other interrupt e1000e: Avoid missed interrupts following ICR read e1000e: Fix check_for_link return value with autoneg off Revert "e1000e: Separate signaling for link check/link up" e1000e: Fix link check race condition Thanks, -zheng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
