** Affects: initramfs-tools
Importance: Unknown
Status: Fix Released
** Affects: initramfs-tools (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Affects: initramfs-tools (Ubuntu Trusty)
Importance: High
Assignee:
Fixed in Debian
** Project changed: linux => initramfs-tools
** Changed in: initramfs-tools
Status: Unknown => Fix Released
--
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/1771557
mportance: Undecided => High
** Changed in: initramfs-tools (Ubuntu Trusty)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu Trusty)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: initramfs-tools (Ubuntu Trusty)
Milestone: None => tr
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-gcp (Ubuntu)
--
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/1744300
Title:
** No longer affects: linux (Ubuntu Bionic)
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1744300
Title:
bt_iter() crash due to NULL pointer
Patch was modified (by adding the PCI_ID of device 1142A, which
confusingly is 1242!) and still the problem reproduces.
New approaches to be tried soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
As an informative note: it was observed that adapter "ASMedia Technology Inc.
ASM1142 USB 3.1 Host Controller [1b21:1242]" has a similar bug, but seems the
quirk (from kernel commit 9da5a1092b13), even if applied to right PCI_ID,
doesn't fix the issue.
I guess this was the case from the user
Public bug reported:
It was observed that while trying to use a 4K USB webcam connected to
USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does
not work and kernel log shows the following messages:
[431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Trusty)
Status: New => In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Xenial)
I
Public bug reported:
When kdumping in 3.13.0-85-generic, using the sysrq trigger "echo c >
/proc/sysrq-trigger", I got the following messages:
The kernel version is not supported.
The created dumpfile may be incomplete.
check_release: Can't get the kernel version.
makedumpfile Failed.
*
Hi Imperia, I built a mainline kernel (version 4.16) with a different
quirk that I think might help here. Can you test it? Thanks in advance!
Instructions (run all as root):
1) wget people.canonical.com/~gpiccoli/imperia416.tgz
2) mv imperia416.tgz /
3) tar -zxf imperia416.tgz
4)
Nice imperia, thanks for the report here. First we need to be sure it's exactly
the same adapter.
Can you provide the the output of "lspci -nn" ?
Then, if it's the same adapter:
0) Which Ubuntu version are you running? Which kernel version are you using?
Can you try in the latest 4.13 for
Thanks a lot Imperia! It's indeed the same PCI adapter, and it's even
better you're running an upstream kernel like this.
I'll analyze your logs in order to match with the ones I have here.
I might need some xhci traces to understand the TRBs operations (like the
enqueue and completion of TRBs).
Thanks again Imperia, the traces are fine. They're only 25MB, shouldn't
have caused any kind of disk issues, like out of space condition. Also,
I'd like to see the correlated kernel log to match the problematic TRBs
from the kernel log with trace information. Can you provide me the
relevant
Wow Imperia, you're being really helpful here, thank you very much!
To enable traces, these are the instructions I've provided to other
people affected so far:
0) Reboot the machine in order to put it in a consistent state;
1) echo "module xhci_hcd +flpt" >
Hi Roy, thanks for your quick response. First thing, I'd like to ask you
to attach the output of "lspci -vvv" and "dmidecode" in this LP so we
can validate the adapters and be sure they are exactly the same, and
also the motherboard type. Run both commands as root user.
After that, i'll ask you
Hi Guo, the Ubuntu kernels schedule can be checked here:
https://wiki.ubuntu.com/Kernel/Support .
Ubuntu kernel team chooses a kernel version for a specific release, and
once that release is available, there's a support schedule. Some
versions have long-term support, so they're called LTS.
In
, the PCI NIC was an "Intel 82599ES 10-Gigabit
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under
high load on the guest.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Tags: st
** 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 Kernel
Packages, which is subscribed
** 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 Kernel
Packages, 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].
** 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
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
** 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:
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797990
Title:
kdump fail due to
** 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
** 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
he guest, host gets its performance
back.
I'll investigate some commits upstream, including the one you suggested, and
once we figure the exact fix for this, will request SRU to the kernel team.
Thanks,
Guilherme
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Picco
odule parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
** Affects: makedumpfile (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Tags
Public bug reported:
Kernel has the "reset_devices" parameter that drivers can opt-in, and
perform special activity in case this parameter is parsed from command-
line. For example, in kdump kernels it hints the drivers that they
(maybe) are booting from a non-healthy condition and needs to issue
posed here is KDUMP_CMDLINE_REMOVE, which would
tentatively "sed"-out the options from the kernel command-line before
appending the new ones from KDUMP_CMDLINE_APPEND.
** Affects: makedumpfile (Ubuntu)
Importance: Low
Assignee: Guilherme G. Piccoli (gpiccoli)
Status:
nux (Debian)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
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/1749961
Title:
xhci_hcd: TRB DMA errors reported with ASMedia ASM11
905f05
-
- $ git describe --contains 71472fa9c52b1da27663c275d416d8654b905f05
- v4.12-rc1
+
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Description changed:
[Impact]
The fo
Kernel core dump analysis:
crash> set
PID: 23697
COMMAND: "kworker/u82:0"
TASK: 88370bcfaa80 [THREAD_INFO: 883708104000]
CPU: 33
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 23697 TASK: 88370bcfaa80 CPU: 33 COMMAND: "kworker/u82:0"
[...]
#3 [883708107b78] __bad_area_nosemaphore at
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification be
I've just tested a mainline kernel version 4.17.0, and nvme names didn't
float when using the kernel parameter "nvme_core.multipath=0", which
reinforces that the fix patch is present in 4.17, so Guo: I guess your
4.17 version is really based on 4.17-rc1.
Let me know if there's anything else to
Hi Mao, I see...the partner is not using a regular Ubuntu build.
This patch was introduced upstream in kernel 4.17, so it's not present in a
regular 4.15 or 4.16. It is present in our Ubuntu kernel though, because it was
backported and added, but I can't guarantee it's present in the custom
You're very welcome Guo! I'll mark this as resolved, in case you have questions,
feel free to comment here.
Cheers,
Guilherme
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Released
--
You received this
Hi Guo, thanks for your tests!
So, to confirm:
a) With Ubuntu kernel 4.15.0-34, using the kernel parameter
"nvme_core.multipath=0", you _don't_ see the issue;
b) With kernel 4.17.0-041700rc1-generic, even using the parameter
"nvme_core.multipath=0", you *can reproduce* the issue.
Right?
I've
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Hi Zhanglei, I've faced this issue some time ago - in fact, it's not
a bug, but some annoyance caused by the multipath introduction in the
nvme driver.
It started recently, after [0] - the introduction of NVMe multipath
brought a change in the way namespaces' "identity" is calculated. Basically,
Hi Zhanglei, thanks for the test and screenshot.
I can't say for sure, but based on the screenshot, seems they are still
running 4.15.0-29 - I'm seeing the BOOT_IMAGE entry in the
/proc/cmdline. Specifically, this doesn't mean much (one can boot like a
4.4 kernel and add a BOOT_IMAGE of a 4.15,
0f 43 53 54
[28663.498992] RIP [] ixgbe_xmit_frame_ring+0x81/0xf50
[ixgbe]
[28663.512112] RSP
[28663.518217] CR2: 0058
** Affects: linux (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Tags: sts
--
You received th
I tried here with a Bionic VM (kernel 4.15.0-34) and kdump worked fine, using
the default
config (128M reserved for the crash kernel).
I'll try to mimic the HW of Daniel's guest and perhaps the kernel
version, although it's super old and seems not available anymore.
@Paul, perhaps worth for you
A preliminary analysis of the problem, based in a crash dump collected.
>From dmesg, we have
[28663.018356] BUG: unable to handle kernel NULL pointer dereference at
0058
[28663.026266] IP: [] ixgbe_xmit_frame_ring+0x81/0xf50
[ixgbe]
Using addr2line to validate the line in the
lspci -nn output for this adapter:
04:00.1 Ethernet controller [0200]: Intel Corporation 82599 10 Gigabit Dual
Port Backplane Connection [8086:10f8] (rev 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz-
** Attachment added: "disassembly of relevant functions in crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794877/+attachment/5193816/+files/ixgbe_xmit_ring.asm
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: "lspci_-nnvv.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794877/+attachment/5193804/+files/lspci_-nnvv.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I was reading assembly and comparing with the code to evaluate the
accuracy of the registers during the dump, and also some points in which
it could has failed.
In the tx transmit function of ixgbe - ixgbe_xmit_frame(), we have the
following:
tx_ring = ring ? ring :
** Attachment added: "ethtool_-i_eth5.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794877/+attachment/5193805/+files/ethtool_-i_eth5.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
the
iommu after it was enabled before (which would show that the patch works fine
indeed, by allowing iommu to get disabled) - some drivers/devices may require
iommu to be enabled in order to work, in such case disabling it would prevent
the device to work.
** Affects: linux (Ubuntu)
Importanc
** Attachment added: "Fix scenario (iommu correctly disabled with the proposed
patch)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810328/+attachment/5226417/+files/iommu-patched
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Attachment added: "Issue scenario (iommu couldn't get disabled without the
patch)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810328/+attachment/5226416/+files/iommu-missing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Patch submitted to kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-January/097452.html
--
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/1810328
Title:
iommu -
The bug was verified in Xenial kernel 4.4.0-142.168 available in
-proposed.
I'm running in an AWS 2-cpu instance, which exhibits the issue if we run
a small reproducer script (a loop that basically changes IRQ affinity
for the NVMe MSIs/legacy interrupt among the CPUs and performs a 4K
write to
Verification was done in Xenial kernel 4.4.0-142, available in -proposed
pocket.
Basically, a regular boot with "intel_iommu=on" was completed, and then we
kexec'ed
the same kernel, but now with "intel_iommu=off". Everything works as expected;
before this patch inclusion, we saw DMAR errors (as
We're still pending the Xenial verification; I'm waiting for the trusty-
HWE kernel to be released in -proposed, since we have a user capable of
reproducing the crash in that version, so I'm planning to ask them to
try in the trusty-HWE package.
--
You received this bug notification because you
I was able to verify/test in both Bionic and Cosmic proposed kernels,
respectively: 4.15.0-44.47 and 4.18.0-14.15.
I don't have a reproducer, but to exercise the paths modified by the
patches, the following approach was taken:
(a) Open ssh connection to the host/test machine, and run the
Also verified that in an AWS instance running the aws kernel in
-proposed:
$ uname -rv
4.4.0-1075-aws #85-Ubuntu SMP Thu Jan 17 17:15:12 UTC 2019
$ dmesg #cleared that before testing
[ 5429.330967] nvme :00:04.0: I/O 10 QID 1 timeout, completion polled
[39630.417191] nvme :00:04.0: I/O
Some updates here: the patch was released in the -proposed pocket, and
is available in the kernel 4.4.0-1075-aws - to enable the proposed
repository please see this
https://wiki.ubuntu.com/Testing/EnableProposed. The plan is to have this
kernel released in the first week of February, after all
I'm investigating this issue, and built a kernel with the following two
patches:
a)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7776db1ccc1
b) A debug patch present in
http://lists.infradead.org/pipermail/linux-nvme/2017-February/008498.html
The idea of the
Public bug reported:
Description to be updated
[Impact]
* 1
[Test Case]
* 2
[Regression Potential]
* 3
** Affects: linux (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Tags: sts
--
You received this bug notification
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
There's news - a V6 patchset was proposed recently, that address this issue
and there are good chances to get merged:
https://marc.info/?l=linux-kernel=154103190111795
("[PATCHv6 0/7] tty: Hold write ldisc sem in tty_reopen()").
Will update here with SRU request when it gets merged.
Cheers,
** Description changed:
- Description to be updated
+ [Impact]
+ * NVMe controllers potentially could miss to send an interrupt, specially
+ due to bugs in virtual devices(which are common those days - qemu has its
+ own NVMe virtual device, so does AWS). This would be a difficult to
+ debug
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Patch sent to Ubuntu kernel mailing-list:
https://lists.ubuntu.com/archives/kernel-team/2018-December/097208.html
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu
** Patch added: "TEST patch for qemu nvme virtual device"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807393/+attachment/5220068/+files/0001-hw-block-nvme-NVMe-hack-to-forcibly-miss-an-interrup.patch
--
You received this bug notification because you are a member of Kernel
Packages,
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"
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
Vincent, I'll update the description to match the SRU requirements, but
your original description will still be available.
** Description changed:
- Hello!
+ [Impact]
+ the IBRS would be mistakenly enabled in the host when the switching
+ from an IBRS-enabled VM and that causes the performance
Gavin Guo had provided a patch to fix this issue, it's a SRU candidate:
https://lists.ubuntu.com/archives/kernel-team/2018-November/096844.html
I'll update this issue accordingly, thanks Gavin!
Cheers,
Guilherme
** Changed in: linux (Ubuntu)
Importance: Medium => High
** Changed in: linux
** Description changed:
[Impact]
- The following Oops was discovered by user:
+ * Line discipline code is racy when we have buffer being flush while the
+ tty is being initialized or reinitialized. For the first problem, we
+ have an upstream patch since January 2018: b027e2298bd5 ("tty: fix
** Description changed:
[Impact]
* Line discipline code is racy when we have buffer being flush while the
tty is being initialized or reinitialized. For the first problem, we
have an upstream patch since January 2018: b027e2298bd5 ("tty: fix data
race between tty_init_dev and flush
SRU request was submitted to kernel team.
* For Xenial and trusty-HWE (kernel 4.4):
https://lists.ubuntu.com/archives/kernel-team/2019-January/097556.html
* For Bionic (kernel 4.15) and Cosmic (kernel 4.18):
https://lists.ubuntu.com/archives/kernel-team/2019-January/097562.html
--
You
** Tags removed: xenial
--
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/1791758
Title:
ldisc crash on reopened tty
Status in linux package in Ubuntu:
In Progress
Status in linux
Medium
** Changed in: linux (Ubuntu Disco)
Importance: Critical => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: Guilherme G. Piccoli (gpiccoli) => Mauricio Faria de Oliveira
(mfo)
** Changed in: linux (Ubuntu Bionic)
Assignee: Guilherme G. Piccoli (gpiccoli) => Ma
igned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you a
tch.
** Affects: linux (Ubuntu)
Importance: Critical
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
**
** Attachment added: "dmesg snippet showing the error"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810781/+attachment/5227414/+files/dmesg-error
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => High
--
You
** Changed in: linux (Ubuntu Xenial)
Importance: High => Critical
--
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/1791758
Title:
ldisc crash on reopened tty
Status in linux package
** Changed in: makedumpfile (Ubuntu Trusty)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: makedumpfile (Ubuntu Bionic)
Assignee: (unas
mportance: Undecided => High
** Changed in: makedumpfile (Ubuntu Trusty)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs
mportance: Undecided => High
** Changed in: makedumpfile (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: makedumpfile (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (
cts: linux (Ubuntu)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Tags: sts
--
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/1813651
Tit
There was an userspace regression reported after the inclusion of these
backports;
it's being handled in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873.
The fix patch was released upstream and the SRU request was sent to kernel-team
ML (thanks smb!):
OK, so it seems it's really the minimum of reserved memory kernel needs in
Bionic that is affecting
the success of kdump here.
Thanks for the report Gaëtan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Correction: it happens in 4.19 also. I continue with the bisect process.
--
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/1813651
Title:
hpsa: DMAR invalid read
Status in linux package
than 8 days without issues.
* Also the patch is present in mainline kernel as well as supported
stable branches, and is already present in Ubuntu 4.4 kernel.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Tags: sts
Patch was posted in the mailing-list for the SRU process:
https://lists.ubuntu.com/archives/kernel-team/2019-February/098380.html
--
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/1815033
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
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/1815033
Title:
qlcnic: Firmware abo
Great, thanks Rehan!
--
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/1813873
Title:
Userspace break as a result of missing patch backport
Status in linux package in Ubuntu:
Fix
Hi Joe, can you please paste the output of "uname -a" from your system
that is presenting this issue?
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/1813873
Title:
Hi Putatieve, thanks for you attention here. Let me try to clarify what happens
here: the issue is present in kernel 4.4.0-142, 4.15.0-45 and 4.18.0-14. The
three versions were already released,
but the fix for the regression observed in this LP is present in the new
versions that are getting
You're welcome Putatieve, thanks for testing the Xenial 4.4.0-143
version!
And you're right, we will have a fix for Xenial-HWE - as soon it is available,
you will observe a new message from Brad Figg here, this time adding a tag
"verification-needed-bionic".
And then, likely the version for
Samuel, for now the suggestion is to keep kernel 4.15.0-43, as it
doesn't show the issue reported in this LP.
Soon (probably later today or tomorrow) the new version for 4.15 will
show up in -proposed pocket, so you can update to that version for
testing purposes, since that version will have the
1 - 100 of 102 matches
Mail list logo
