** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797990
Title:
kdump fail due to an IRQ storm
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu Disco)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package linux - 4.4.0-140.166
---
linux (4.4.0-140.166) xenial; urgency=medium
* linux: 4.4.0-140.166 -proposed tracker (LP: #1802776)
* Bypass of mount visibility through userns + mount propagation (LP: #1789161)
- mount: Retest MNT_LOCKED in
This bug was fixed in the package linux - 4.15.0-42.45
---
linux (4.15.0-42.45) bionic; urgency=medium
* linux: 4.15.0-42.45 -proposed tracker (LP: #1803592)
* [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405)
- KVM: s390: reset crypto attributes for all vcpus
- KVM:
This bug was fixed in the package linux - 4.18.0-12.13
---
linux (4.18.0-12.13) cosmic; urgency=medium
* linux: 4.18.0-12.13 -proposed tracker (LP: #1802743)
* [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405)
- s390/zcrypt: Add ZAPQ inline function.
- s390/zcrypt:
** Attachment added: "lp1797990_verification.tgz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5215743/+files/lp1797990_verification.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Maurício for submitting the patches and taking care of the bug
while I was out.
I've verified all the 3 releases (in fact, I've also verified Trusty HWE) with
a similar
test as used by Maurício, "dmesg -t | sort" and the kernels are running fine.
During kdump, with the "pci=clearmsi"
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
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a
Attaching for documentation purposes,
Tarball with 'dmesg -t | sort' for boot/kexec & option disabled/enabled,
in Xenial, Bionic, Cosmic, Disco.
** Attachment added: "sf202166.dmesg.tar.xz"
Patch set v2 submitted to the kernel-team mailing list
for Xenial, Bionic, Cosmic, Disco.
[SRU X][PATCH v2 0/3] Add kernel parameter 'pci=clearmsi' to clear MSI(X)s
early on boot
https://lists.ubuntu.com/archives/kernel-team/2018-November/096631.html
[SRU B][PATCH v2 0/3] Add kernel parameter
** Description changed:
[Impact]
* A kexec/crash kernel might get stuck and fail to boot
(for crash kernel, kdump fails to collect a crashdump)
if a PCI device is buggy/stuck/looping and triggers a
continuous flood of MSI(X) interrupts (that the kernel
does not yet
** Description changed:
[Impact]
* A kexec/crash kernel might get stuck and fail to boot
(for crash kernel, kdump fails to collect a crashdump)
if a PCI device is buggy/stuck/looping and triggers a
continuous flood of MSI(X) interrupts (that the kernel
does not yet
** Description changed:
+ [Impact]
+
+ * A kexec/crash kernel might get stuck and fail to boot
+(for crash kernel, kdump fails to collect a crashdump)
+if a PCI device is buggy/stuck/looping and triggers a
+continuous flood of MSI(X) interrupts (that the kernel
+does not yet
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797990
Title:
kdump fail due to an IRQ storm
To manage notifications about this bug go to:
** Patch added: "Export pci capabilities function from AGP to early-PCI code"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5202666/+files/0002-x86-PCI-Export-find_cap-to-be-used-in-early-PCI-code.patch
--
You received this bug notification because you are a member
** Patch added: "Parameter to enable quirk in early boot to disable MSIs on
kexec"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5202667/+files/0003-x86-quirks-Add-parameter-to-clear-MSIs-early-on-boot.patch
--
You received this bug notification because you are a
Patches sent to the mailing lists today.
** Patch added: "Patch 1: Scan all PCI busses"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5202664/+files/0001-x86-quirks-Scan-all-busses-for-early-PCI-quirks.patch
--
You received this bug notification because you are a
Mailing list archive URL: https://marc.info/?l=linux-pci=153988799707413
(navigate using "next in list")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797990
Title:
kdump fail due to an IRQ storm
** Description changed:
We have reports of a kdump failure in Ubuntu (in x86 machine) that was
narrowed down to a MSI irq storm coming from a PCI network device.
The bug manifests as a lack of progress in the boot process of the kdump
kernel, and a storm of kernel messages like:
** Attachment added: "lspci tree output of a single root bridge PCI topology"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5201885/+files/lspci_single_root.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "lspci tree output of a multi root bridge PCI topology"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5201886/+files/lspci_multi_root.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
One problem faced during this approach was that the early-quirks code in
x86 performs a recursive search in the PCI bus descending from the
"first" bus :00, and walking through all secondary busses by jumping
between bridges. For historical perspective about this code's evolution,
see [0].
During the investigation, we've noticed that PCI specification mentions
the need of MSI/MSI-X capability to be disabled during a system
boot/reset; from PCI Local Bus specification 3.0, sections 6.8.1.3 and
6.8.2.3: "[...] MSI Enable: This bit’s state after reset is 0 (MSI is
disabled)."
PCI
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Guilherme G. Piccoli
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
28 matches
Mail list logo
