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
nee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802073
Title:
No network in AWS (EC-Classic) after stopping and starting instance
To m
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
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,
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs,
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791758
Title:
ldisc crash on reopened tty
To manage notifications about this bug go to:
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 y
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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791758
Title:
ldisc crash on reopened tty
To manage notifications about this bug
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800566
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 (
** 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
Kernel was validated by the user that reported the issue - ran for more than 72h
with no problems.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
There is a report of hard lockup induced by a long delay in lapic expiration
timer.
We'll provide SRU request here for merging the fixes in 4.4 kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Guilherme G. Piccoli (gpiccoli)
Status
** Description changed:
- There is a report of hard lockup induced by a long delay in lapic expiration
timer.
- We'll provide SRU request here for merging the fixes in 4.4 kernel.
+ [Impact]
+
+ * There is a long-time report of an issue with the TSC delay present
+ in wait_lapic_expire() -
SRU request sent to the kernel team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-February/098872.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817918
Title:
Hard lockups
I've managed to verify this on kernel 4.4.0-143-generic, the problem
isn't reproducible anymore.
Worth noticing that when using the kernel 4.4.0-143 in both host and
guest, we cannot change MSR bit anymore from within the guest, so the
performance drop is not observed.
** Tags removed:
on, they should used KDUMP_CMDLINE instead.
** Affects: makedumpfile (Ubuntu)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: makedumpfile (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: makedumpfile (Ubuntu Bio
e: Medium => Undecided
** Changed in: makedumpfile (Ubuntu Cosmic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: makedumpfile (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: makedumpfile (Ubuntu Xenial)
Ass
Thanks all for the tests.
@md_5: According to https://kernel.ubuntu.com, the promotion of the
-proposed packages to -updates is scheduled to March, 4th.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
SRU release status LP: https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1819067
Thanks Odd_Bloke, for the pointer!
** Changed in: cloud-init (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in:
Tested kernel in -proposed, version 4.4.0-144-generic (in Xenial).
Problem does not reproduce anymore.
I've used tscdeadline_delay test wrote by Thadeu Cascardo as a kvm-unit-
tests "module" - this specific test is not upstream yet, Cascardo wrote
for this LP in particular and is
The userspace regression is fixed in latest available kernels for all series:
Xenial (Trusty-HWE): 4.4.0-143
Bionic (Xenial-HWE): 4.15.0-46
Cosmic (Bionic-HWE): 4.18.0-16
Disco (development series): 5.0.0-7.8
Cheers,
Guilherme
--
You received this bug notification because you are a member of
Problem is resolved in Bionic's latest version of cloud-init, released
yesterday:
$ dpkg -l | grep cloud-init
ii cloud-init 18.5-45-g3554ffe8-0ubuntu1~18.04.1
I've manually upgraded the package after bringing-up my EC2 Classic instance,
so notice the AWS image doesn't have the latest cloud-init
Hi Edgar, I've changed it back =)
It should be Fix Committed if the patch is present/merged in the kernel, but
kernel wasn't released yet. Once it gets released, it'll get changed to Fix
Released.
Cheers,
Guilherme
** Changed in: linux (Ubuntu Bionic)
Status: Fix Released => Fix
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
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
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
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
** Changed in: makedumpfile (Ubuntu Bionic)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
** Changed in: makedu
** Changed in: makedumpfile (Ubuntu Trusty)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)
** Changed in: makedumpfile (Ubuntu
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813873
Title:
Userspace break
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815033
Title:
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815033
Title:
qlcnic: Firmware aborts/ha
Great, thanks Rehan!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813873
Title:
Userspace break as a result of missing patch backport
To manage notifications about this bug go to:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813651
Title:
hpsa: DM
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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!):
Correction: it happens in 4.19 also. I continue with the bisect process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813651
Title:
hpsa: DMAR invalid read
To manage notifications about this bug
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795659
Title:
kernel panic using CIFS share smb2_push_mandatory_locks
To manage notifications about this bug go to:
** Tags removed: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816743
Title:
Add systemd's kdump service command-line regardless if user provides
or not KDUMP_CMDLINE_APPEND
To manage
** Tags removed: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813651
Title:
hpsa: DMAR invalid read
To manage notifications about this bug go to:
** Tags removed: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800873
Title:
Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-
line
To manage notifications about this
hanged in: makedumpfile (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Also affects: makedumpfile (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: makedumpfil
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800873
Title:
Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-
line
To manage notifications about this bug
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
To manage notifications about this bug go to:
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800566
Title:
Make the reset_devices parameter default for kdump kernels
To manage notifications about this bug go to:
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813651
Title:
hpsa: DMAR invalid read
To manage notifications about this bug go to:
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816743
Title:
Add systemd's kdump service command-line regardless if user provides
or not KDUMP_CMDLINE_APPEND
To manage
-series)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Cosmic)
Assi
** Attachment added: "system_details.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832082/+attachment/5272083/+files/system_details.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824981
Title:
cifs set_oplock buffer overflow in strcat
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1824981 ***
https://bugs.launchpad.net/bugs/1824981
** This bug is no longer a duplicate of bug 1813928
kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!
** This bug has been marked a duplicate of bug 1824981
cifs set_oplock buffer
*** This bug is a duplicate of bug 1824981 ***
https://bugs.launchpad.net/bugs/1824981
This LP is a duplicate for #1824981 - I'll mark it as dup.
Thanks,
Guilherme
** Tags added: sts
** This bug has been marked a duplicate of bug 1824981
cifs set_oplock buffer overflow in strcat
--
Hi Christoph, thank you very much for your work in this LP! Both the
debug part and finally your patch. I was looking the same set of issues
in parallel, with another user that reported the same crashes.
So, regarding your question in comment #15 ("are those gonna be
backportet to 4.x-generic?"),
New => Confirmed
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => High
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Disco
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Guilherme G.
** Attachment added: "no_issue_dev.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813651/+attachment/5260387/+files/no_issue_dev.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "issue_dev.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813651/+attachment/5260386/+files/issue_dev.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813651
I've narrowed down the problem for devices in HBA mode; if device is in RAID
mode (despite if it's effectively using some raid level or has only 1 disk), it
does not reproduce the issue. I'll attach files with outputs from HP RAID
utility (accessed in BIOS) for both cases.
I continue the
Great Bryan, the model of your USB controller is the same reported in
this LP; also, given the outputs you provided, the network interface
"enx90203a19dcb6" in under one of those USB controllers - you mentioned
you see the TRB DMA errors and the interface stops responding. Is the
problematic
Hi, have some news in this one. I've emailed Microsoft CIFS maintainers, they
recommended the following patch as a potential fix:
b98749cac4a6 ("CIFS: keep FileInfo handle live during oplock break").
There's a PPA with a kernel built including this patch, for those
interested in testing:
Hi Chris, as per comment #21, the issue exists in kernel 4.18.0-14, and was
fixed in 4.18.0-15.
So, you need to update your kernel.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Gabe! I agree with you, would be really nice to have a quirk for that.
It would be more easy to analyze that possibility with a datasheet for this
adapter, which unfortunately I don't have.
I'm on vacation until next week, I'll try to discuss that in linux-usb when I'm
back, and pursue a
** Description changed:
[Impact]
- Crash kernels include an obsolete "nousb" parameter by default, which can
cause confusion since it's been deprecated in newer kernel versions.
+ * Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users
** Description changed:
[Impact]
- Crash kernels do not advise some subsystems to perform a reset by default.
- [Description]
- 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
This is the debdiff with this LP's proposed modifications.
I'd like to specially thanks Cascardo and Heitor for the discussions and joint
work in this issue.
** Changed in: makedumpfile (Ubuntu Eoan)
Status: Confirmed => In Progress
** Patch added: "lp1800566_eoan.debdiff"
This is the debdiff containing the proposed solution for this LP.
I'd like to thanks specially Cascardo and Heitor for the fruitful discussions
with regards the direction we should take in this LP.
** Changed in: makedumpfile (Ubuntu Cosmic)
Status: In Progress => Confirmed
** Changed
*** This bug is a duplicate of bug 1800566 ***
https://bugs.launchpad.net/bugs/1800566
I'll mark this bug as duplicate from LP #1800566 - we'll track progress
only in that bug, the SRU for this will be worked along with the
reset_devices thing.
Thanks,
Guilherme
** This bug has been
This is a mock reproducer of this issue by faking a 20s delay in virtio-
net after its link is up.
To enable that, user needs to build virtio-net with the hereby attached
patch, and insert:
"echo 1 > /sys/module/virtio_net/parameters/droppkt"
in the /usr/sbin/kdump-config before the network
tus: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Disco)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Eoan)
Status: Confirmed => In Progress
** Summary changed:
- Make the reset_devices parameter default for kdump kernels
+ Make reset_devices parameter default for kdump and decouple kdump systemd
service from the KDUMP_CMDLINE_APPEND
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: makedumpfile (Ubuntu)
Assignee: Heitor Alves de Siqueira (halves) => Guilherme G. Piccoli
(gpiccoli)
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: Heitor Alves de Siqueira (halves) => Guilherme G. Piccoli
(gpiccoli)
** Changed in: makedumpfile (Ubuntu
ion => Confirmed
** Changed in: makedumpfile (Ubuntu Eoan)
Status: Opinion => Confirmed
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: Heitor Alves de Siqueira (halves) => Guilherme G. Piccoli
(gpiccoli)
** Changed in: makedumpfile (Ubuntu Bionic)
Assignee: Heitor Alves
SRU submitted to kernel mailing-list: https://lists.ubuntu.com/archives
/kernel-team/2019-July/101925.html
I've marked Xenial->Disco as "In Progress", because we need acceptance from
kernel team.
On the other hand, Devel series (Eoan/Ff) will get the fix via regular rebase
with
Linus tree,
** Description changed:
- For the customer OpenStack deployment we deploy infra nodes on Dell R630
- servers. The servers have onboard Broadcom's NetXtreme II BCM57800 NIC
- (quad port: 2x1G ports, 2x10G ports). For each port in UP state, we
- observe 100% CPU load. So in total, we observe 4 CPUs
.
Cheers,
Guilherme
** Bug watch added: Debian Bug tracker #830771
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830771
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
*
Hi Bryan, thanks for the report. It could be the same issue, can you
provide the full dmesg, and also the outputs of the following commands:
"lspci -nnvvv", "lspci -t" and "ls -l /sys/class/net"?
The issue was fixed for the first reporter via a FW update in the
ASMedia adapter; unfortunately this
Hi Terry, I'm planning to post an update this week.
It seems the problem is related with physical block size adjustments,
after the introduction of the patch: "eb53a3ea3e00 scsi: hpsa: limit transfer
length to 1MB, not 512kB"
Without this patch I don't see the issue anymore. But I'm
Public bug reported:
TBA
** Affects: linux (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: linux (Ubuntu Xenial)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824981
Title:
cifs set_oplock buffer overflow in strcat
To manage
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of
This issue affects only kernels after 4.17 and before 5.2, hence it's
fixed on Bionic and Eoan, and won't be fixed in Cosmic (4.18) since it
is EOL.
Patches submitted to kernel-team ML: https://lists.ubuntu.com/archives
/kernel-team/2019-July/102287.html
Cheers,
Guilherme
--
You received
** Description changed:
- TBD
+ [Impact]
+
+ * During raid0 error path testing, by removing one member of the array,
+ we've noticed after kernel 4.18 we can trigger a crash depending if
+ there's I/O in-flight during the array removal. When debugging the
+ issue, a second problem was found,
101 - 200 of 873 matches
Mail list logo
