[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-23.25

---
linux (4.15.0-23.25) bionic; urgency=medium

  * linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)

  * arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
- arm64: mmu: add the entry trampolines start/end section markers into
  sections.h
- arm64: sdei: Add trampoline code for remapping the kernel

  * Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
- ACPI: APEI: handle PCIe AER errors in separate function
- ACPI: APEI: call into AER handling regardless of severity

  * qla2xxx: Fix page fault at kmem_cache_alloc_node() (LP: #1770003)
- scsi: qla2xxx: Fix session cleanup for N2N
- scsi: qla2xxx: Remove unused argument from 
qlt_schedule_sess_for_deletion()
- scsi: qla2xxx: Serialize session deletion by using work_lock
- scsi: qla2xxx: Serialize session free in qlt_free_session_done
- scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
- scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
- scsi: qla2xxx: Prevent relogin trigger from sending too many commands
- scsi: qla2xxx: Fix double free bug after firmware timeout
- scsi: qla2xxx: Fixup locking for session deletion

  * Several hisi_sas bug fixes (LP: #1768974)
- scsi: hisi_sas: dt-bindings: add an property of signal attenuation
- scsi: hisi_sas: support the property of signal attenuation for v2 hw
- scsi: hisi_sas: fix the issue of link rate inconsistency
- scsi: hisi_sas: fix the issue of setting linkrate register
- scsi: hisi_sas: increase timer expire of internal abort task
- scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
- scsi: hisi_sas: fix return value of hisi_sas_task_prep()
- scsi: hisi_sas: Code cleanup and minor bug fixes

  * [bionic] machine stuck and bonding not working well when nvmet_rdma module
is loaded (LP: #1764982)
- nvmet-rdma: Don't flush system_wq by default during remove_one
- nvme-rdma: Don't flush delete_wq by default during remove_one

  * Warnings/hang during error handling of SATA disks on SAS controller
(LP: #1768971)
- scsi: libsas: defer ata device eh commands to libata

  * Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
- ata: do not schedule hot plug if it is a sas host

  * ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
- powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
- powerpc/64s: return more carefully from sreset NMI
- powerpc/64s: sreset panic if there is no debugger or crash dump handlers

  * fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
- fsnotify: Fix fsnotify_mark_connector race

  * Hang on network interface removal in Xen virtual machine (LP: #1771620)
- xen-netfront: Fix hang on device removal

  * HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
- net: hns: Avoid action name truncation

  * Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
- SAUCE: powerpc/perf: Fix memory allocation for core-imc based on
  num_possible_cpus()

  * Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev

  * smp_call_function_single/many core hangs with stop4 alone (LP: #1768898)
- cpufreq: powernv: Fix hardlockup due to synchronous smp_call in timer
  interrupt

  * Add d-i support for Huawei NICs (LP: #1767490)
- d-i: add hinic to nic-modules udeb

  * unregister_netdevice: waiting for eth0 to become free. Usage count = 5
(LP: #1746474)
- xfrm: reuse uncached_list to track xdsts

  * Include nfp driver in linux-modules (LP: #1768526)
- [Config] Add nfp.ko to generic inclusion list

  * Kernel panic on boot (m1.small in cn-north-1) (LP: #1771679)
- x86/xen: Reset VCPU0 info pointer after shared_info remap

  * CVE-2018-3639 (x86)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove x86_spec_ctrl_set()
- x86/bugs: Rework spec_ctrl base and mask logic
- x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
- x86/bugs: 

[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-23.25

---
linux (4.15.0-23.25) bionic; urgency=medium

  * linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)

  * arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
- arm64: mmu: add the entry trampolines start/end section markers into
  sections.h
- arm64: sdei: Add trampoline code for remapping the kernel

  * Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
- ACPI: APEI: handle PCIe AER errors in separate function
- ACPI: APEI: call into AER handling regardless of severity

  * qla2xxx: Fix page fault at kmem_cache_alloc_node() (LP: #1770003)
- scsi: qla2xxx: Fix session cleanup for N2N
- scsi: qla2xxx: Remove unused argument from 
qlt_schedule_sess_for_deletion()
- scsi: qla2xxx: Serialize session deletion by using work_lock
- scsi: qla2xxx: Serialize session free in qlt_free_session_done
- scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
- scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
- scsi: qla2xxx: Prevent relogin trigger from sending too many commands
- scsi: qla2xxx: Fix double free bug after firmware timeout
- scsi: qla2xxx: Fixup locking for session deletion

  * Several hisi_sas bug fixes (LP: #1768974)
- scsi: hisi_sas: dt-bindings: add an property of signal attenuation
- scsi: hisi_sas: support the property of signal attenuation for v2 hw
- scsi: hisi_sas: fix the issue of link rate inconsistency
- scsi: hisi_sas: fix the issue of setting linkrate register
- scsi: hisi_sas: increase timer expire of internal abort task
- scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
- scsi: hisi_sas: fix return value of hisi_sas_task_prep()
- scsi: hisi_sas: Code cleanup and minor bug fixes

  * [bionic] machine stuck and bonding not working well when nvmet_rdma module
is loaded (LP: #1764982)
- nvmet-rdma: Don't flush system_wq by default during remove_one
- nvme-rdma: Don't flush delete_wq by default during remove_one

  * Warnings/hang during error handling of SATA disks on SAS controller
(LP: #1768971)
- scsi: libsas: defer ata device eh commands to libata

  * Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
- ata: do not schedule hot plug if it is a sas host

  * ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
- powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
- powerpc/64s: return more carefully from sreset NMI
- powerpc/64s: sreset panic if there is no debugger or crash dump handlers

  * fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
- fsnotify: Fix fsnotify_mark_connector race

  * Hang on network interface removal in Xen virtual machine (LP: #1771620)
- xen-netfront: Fix hang on device removal

  * HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
- net: hns: Avoid action name truncation

  * Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
- SAUCE: powerpc/perf: Fix memory allocation for core-imc based on
  num_possible_cpus()

  * Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev

  * smp_call_function_single/many core hangs with stop4 alone (LP: #1768898)
- cpufreq: powernv: Fix hardlockup due to synchronous smp_call in timer
  interrupt

  * Add d-i support for Huawei NICs (LP: #1767490)
- d-i: add hinic to nic-modules udeb

  * unregister_netdevice: waiting for eth0 to become free. Usage count = 5
(LP: #1746474)
- xfrm: reuse uncached_list to track xdsts

  * Include nfp driver in linux-modules (LP: #1768526)
- [Config] Add nfp.ko to generic inclusion list

  * Kernel panic on boot (m1.small in cn-north-1) (LP: #1771679)
- x86/xen: Reset VCPU0 info pointer after shared_info remap

  * CVE-2018-3639 (x86)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove x86_spec_ctrl_set()
- x86/bugs: Rework spec_ctrl base and mask logic
- x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
- x86/bugs: 

[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-05-25 Thread Zheng Cui
Hi,

Our team has verified Ubuntu 18.04 + "proposed" solve the problem and as
far as I am concerned, we could mark the tag as "verification-done-
bionic":



Thanks,

-zheng

** Tags removed: verification-needed-bionic
** Tags added: verification-done-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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-05-24 Thread Zheng Cui
I have been posting the verification request to our QE team, and would
update here once I heard of anything.

-- 
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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-05-24 Thread Zheng Cui
Hi Joseph,

Would update #5 be sufficient for the verification? If so, we should be
able to update the tag to verification-done-bionic. Otherwise, let me
know what we should do next.

Thanks,

-zheng

-- 
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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-05-24 Thread Brad Figg
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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-05-15 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

-- 
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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-04-27 Thread Joseph Salisbury
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/092020.html

** Description changed:

+ == 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

-- 
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:
  In Progress

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:

[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-04-24 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

-- 
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:
  In Progress

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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-04-24 Thread Zheng Cui
Hi Joseph,

Our QE has verified the sandbox works well. Please see below



Thanks,

-zheng

-- 
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:
  Triaged
Status in linux source package in Bionic:
  Triaged

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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-04-23 Thread Joseph Salisbury
I built a test kernel with commit 745d0bd3af99ccc8c5f5822f808cd133eadad6ac.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1764892

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

-- 
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:
  Triaged
Status in linux source package in Bionic:
  Triaged

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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-04-23 Thread Joseph Salisbury
** Tags added: bionic kernel-da-key

-- 
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:
  Triaged
Status in linux source package in Bionic:
  Triaged

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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-04-20 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Confirmed

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => Triaged

-- 
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:
  Triaged
Status in linux source package in Bionic:
  Triaged

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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-04-20 Thread Zheng Cui
FYI, here are the patch links:

https://patchwork.kernel.org/patch/10193325/
https://patchwork.kernel.org/patch/10172415/

-- 
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:
  Triaged
Status in linux source package in Bionic:
  Triaged

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


[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic

2018-04-17 Thread Zheng Cui
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
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:
  Confirmed

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