Hi Guilherme, Thadeu,
The re-spinned packages have been uploaded to Bionic and Eoan.
Xenial didn't change, and is still in the upload queue (which
I'll go check about on next week.)
Disco didn't change, and has been removed from the upload queue.
(After discussions with other people, it turns ou
** Changed in: makedumpfile (Ubuntu Disco)
Status: In Progress => Won't Fix
** Changed in: makedumpfile (Ubuntu Disco)
Importance: High => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
** Changed in: makedumpfile (Ub
** Changed in: makedumpfile (Ubuntu Disco)
Importance: Low => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpf
** Changed in: makedumpfile (Ubuntu Disco)
Status: In Progress => Won't Fix
** Changed in: makedumpfile (Ubuntu Disco)
Importance: Low => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
You received this bug notifi
The intel-microcode package [1] had an update in mid November 2019
(version "3.20191115"ish) with an entry apparently related to the
symptoms seen in the kernel log you provided:
'Unexpected Page Faults in Guest Virtualization Environment (SKL-188,
KBL-144, CFL-136 errata)'
If you're running on I
nce: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linu
Hello Hari,
Glad to see you around on bugs again. :)
Could you please confirm whether the fix for this bug also addresses LP bug
1655280?
(i.e., the verification for xenial would be equivalent/also validate that other
bug.)
Thanks,
Mauricio
--
You received this bug notification because you a
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubu
** Description changed:
+ [Impact]
+
+ * The bcache code in Bionic lacks several fixes to handle
+I/O errors in both backing devices and caching devices.
+
+ * Partial or permanent errors in backing or caching devices,
+specially in writeback mode, can lead to data loss and/or
+the
Hi Fred,
At this time it's only available in the netboot images (network
installs) [1].
It should be available on ISOs in Eoan release 19.10 and next
Bionic point-release 18.04.3 (currently scheduled to August [2]).
We'll put some documentation about the installer kernel/preseed parameters soon
Fred,
Glad to know it.
Thanks for the additional testing and feedback.
cheers,
Mauricio
--
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/1817321
Title:
installer does not support iSCSI i
Tests with xfstests
===
The xfstests test suite has been run on the original
and modified kernels -- on all cache modes available
(writethrough, writeback, writearound, none).
Summary: no regressions observed; apparently one FIX
achieved in the writearound cache mode (generic/371)
** Attachment added: "test-bcache-cache-modes.xfstests.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275531/+files/test-bcache-cache-modes.xfstests.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Tests with fio
==
The fio tool has been run for performance tests on the original
and modified kernels in sequential (rw) and random read/write (randrw)
on all cache modes available (writethrough, writeback, writearound, none).
Summary: no regressions observed, same IOPS and BW metri
** Attachment added: "test-bcache-cache-modes.fio.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275532/+files/test-bcache-cache-modes.fio.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Tests with I/O errors
=
The I/O error tests in the caching and backing device have been
simulated with the device mapper dm-linear and dm-error targets.
The tests are based on the patch messages, which describe a
problem and/or expected behavior, so to exercise the change.
Co
** Attachment added: "setup-sda.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275534/+files/setup-sda.sh
--
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/1
** Attachment added: "setup.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275533/+files/setup.sh
--
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/1829563
** Attachment added: "setup-two-bcache-one-cache.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275535/+files/setup-two-bcache-one-cache.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I/O Error Test 6
Make sure that if two bcache devices share a cache device,
only one bcache device is offlined in case of I/O errors
in only one backing device.
Original
# uname -rv
4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
# ./setup-two-bcache-one-
I/O Error Test 3
commit "bcache: fix inaccurate io state for detached bcache devices"
Probçem: on detached bcache devices, iostat reports non-zero 'avgqu-sz'
and '%util' even after IO stopped.
Original kernel: iostat fields are non-zero on I/O idle.
Modified kernel: iostat fiel
I/O Error Test 5
commit "bcache: stop bcache device when backing device is offline"
Problem: bcache is unaware that a backing device goes offline,
and accepts writes.
Original kernel: bcache doesn't realize backing device is offline.
Modified kernel: bcache device is removed aft
I/O Error Test 2
commit "bcache: add stop_when_cache_set_failed option to backing device"
Problem: upon too many io errors on cache device, bcache code retires cache set,
but it doesn't stop the bcache device.
(in writeback mode, if it continue to write, writes go to backing dev
I/O Error Test 1
commit "bcache: add CACHE_SET_IO_DISABLE to struct cache_set flags"
Problem: the cacheset is not retired immediately on I/O errors in
cache device if I/O requests keep coming.
Original kernel: bcache device remains on top of caching device,
and 'fio' never finis
I/O Error Test 4
commit "bcache: add io_disable to struct cached_dev"
Problem: in case of the backing device hits I/o errors or is
disconected, the I/O can still be accepted to the bcache device.
Original kernel: dd writes in writeback mode to failed backing device complete.
Mod
** Description changed:
[Impact]
- * The bcache code in Bionic lacks several fixes to handle
-I/O errors in both backing devices and caching devices.
+ * The bcache code in Bionic lacks several fixes to handle
+ I/O errors in both backing devices and caching devices.
- * Partial
[B][PATCH 00/11] LP#1829563 bcache: risk of data loss on I/O errors in backing
or caching devices
https://lists.ubuntu.com/archives/kernel-team/2019-July/101989.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
I/O Error Test 7
commit: "bcache: fix ioctl in flash device"
This test needs QEMU+GDB since there's no way to set the variable
from the kernel, because it references incorrect memory/pointer.
In the original kernel, the ioctl() to a flash-only volume
goes from ioctl_dev() down t
I/O Error Test 6 (for the Cosmic kernel)
commit: 'Revert "bcache: set CACHE_SET_IO_DISABLE in
bch_cached_dev_error()"'
Problem: if one backing device hits I/O errors the cache device
is disabled, but if that cache device is shared by other bcache
devices they stop too (even with
[C][PATCH 0/2] LP#1829563 bcache: pending patches for Cosmic
https://lists.ubuntu.com/archives/kernel-team/2019-July/102001.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/1829563
Titl
I/O Error Test 6 (for the Disco kernel)
commit: 'Revert "bcache: set CACHE_SET_IO_DISABLE in
bch_cached_dev_error()"'
Problem: if one backing device hits I/O errors the cache device
is disabled, but if that cache device is shared by other bcache
devices they stop too (even with n
[D/E][PATCH 0/1] LP#1829563 bcache: pending patch for Disco/Eoan
https://lists.ubuntu.com/archives/kernel-team/2019-July/102006.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/1829563
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Invalid
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Chan
Marking Bionic as Fix Released as the kernel from bionic-proposed has
been promoted to bionic-updates.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Released
--
You received this bug notificati
Marking Bionic as Fix Released as the kernel from bionic-proposed has
been promoted to bionic-updates.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Hi Drew,
Yes, the HWE kernel syncs automatically from the normal kernel as it
moves forward.
Once Disco gets the patch, the HWE from Disco in Bionic should get it as
well (same version number plus ~18.04.1 suffix).
--
You received this bug notification because you are a member of Kernel
Package
Disco currently has the e1000e fix in disco-proposed (version 5.0.0-30.32),
also available as linux-hwe kernel in bionic-proposed.
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, wh
Disco currently has the mpt3sas fix in disco-proposed (version 5.0.0-30.32),
also available as linux-hwe kernel in bionic-proposed.
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, w
Test on Bionic
Before:
$ uname -a
Linux bionic 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ echo 9 | sudo tee /proc/sys/kernel/printk
9
$ sudo losetup --find --show --partscan rlv_grkgld.1mb
[ 48.192538] partition (null) (5 pp's found) is not
Test on Xenial
Before:
Last login: Wed Aug 15 19:29:38 2018 from 192.168.122.1
$ uname -a
Linux bionic 4.4.0-133-generic #159-Ubuntu SMP Fri Aug 10 07:31:43 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ echo 9 | sudo tee /proc/sys/kernel/printk
Public bug reported:
[Impact]
* Users with disks/LUNs used for AIX operating system installations
previously, which possibly undergone overwrites/corruption on the
partition table, might hit kernel failures during partition scan
of such disk/LUN, and possibly hang the system (seen with
Test on Trusty
Before:
$ uname -a
Linux bionic 3.13.0-155-generic #205-Ubuntu SMP Fri Aug 10 15:53:26 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ echo 9 | sudo tee /proc/sys/kernel/printk
9
$ sudo losetup --find --show --partscan rlv_grkgld.1mb
[
Test on Cosmic:
Before:
$ uname -a
Linux bionic 4.17.0-7-generic #8-Ubuntu SMP Fri Aug 3 15:55:36 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
$ echo 9 | sudo tee /proc/sys/kernel/printk
9
$ sudo losetup --find --show --partscan rlv_grkgld.1mb
[ 37.274451] partition (null) (20 pp's found) is not
The logs and kernel version provided in the test comments should be sufficient
to understand/confirm the problem and affected versions.
Changing the status of the bug to Confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because
This is the patch for trusty debian-installer to pick up this new xenial
hwe kernel.
It's been tested by the customer with the SF 8000 series NICs on amd64
bare metal (back when using test packages from their private PPA), so
the netboot install works on that NIC model.
I built it on PPA for the
@slashd thanks for the pointers.
Yesterday/today I worked on understanding and providing a workaround for this,
but a more complete solution (more updates to secure-boot related packages)
is already in the works (in cyphermox's PPAs) and should be rolled out soon,
according to him.
Once that hits
The secure boot packages on trusty-proposed are now correct (LP: #1708245),
and the d-i rebuild on amd64 is in progress (verified successfully on PPA).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
The debian-installer images in trusty-proposed work correctly; changing
verification tags to done.
I tested in the following platforms, with plain and LVM partitioning (details
in comment #10).
- amd64 bare-metal & qemu-kvm guest
- i386 qemu-kvm guest
- arm64 qemu guest
- ppc64el qemu guest
The
SRU Verification: all 3 stable releases successfully survive the disk
probe/partition scan of the disk image with corrupted AIX partition
table.
Updating verification tags. Thanks!
Trusty:
---
$ uname -a
Linux trusty 3.13.0-159-generic #209-Ubuntu SMP Wed Sep 12 10:01:59 UTC 2018
x86_64 x86_64
Reverting linux's status from Incomplete to New, as the problem has been
already diagnosed and fixes submitted.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
I should read the bot comments more attentively.
Setting bug status to Confirmed.
** 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
** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1783152
Title:
Enable basic support for Solarflare 8000
Marcelo @mhcerri,
Would you be able to provide a test kernel for bionic/linux-hwe so that
@lazamarius1 can provide test results for -generic?
I'll be happy to do that as well if you're short on time right now.
(I guess the patchset is the same you posted for linux-azure.)
Thanks,
Mauricio
--
Y
Hi Marcelo (@mhcerri),
We have another user who confirmed the 2 patches submitted for linux-
azure also fix the problem on linux(-generic).
srcu: Prohibit call_srcu() use under raw spinlocks
srcu: Lock srcu_data structure in srcu_gp_start()
Could they be submitted for linux as well?
Thank
Verification successful on trusty-proposed.
Updates kernel (goes above 2000 connections)
---
root@petilil:~# uname -a
Linux petilil 3.13.0-165-generic #215-Ubuntu SMP Wed Jan 16 11:46:47 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
root@petilil:~# iptables -F
root@petilil:~# iptables -A INPUT -p tcp
Hi @lazamarius1,
The fix for linux generic should be applied in the next kernel SRU cycle.
The current cycle ends on late February [1].
[1] https://kernel.ubuntu.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
Public bug reported:
(I'll add the SRU template + testing steps and post to ML shortly.)
A customer reported a CPU soft lockup on Trusty HWE kernel from Xenial
when detaching a virtio-scsi drive, and provided a crashdump that shows
2 things:
1) The soft locked up CPU is waiting for another CPU t
Problem Analysis
The dmesg log 'crash/201809061748/dmesg.201809061748' shows the CPU soft lockup
occurs 25 seconds after the 'sdb' virtio-scsi drive is removed.
This seems to indicate the events are related (there's usually an extra 2s-3s
between an event and the report of the 2
Organic Testcase:
It usually reproduces the problem in the 1st or 2nd iteration.
With the fix the problem did not reproduce in 35 iterations.
** Description changed:
- (I'll add the SRU template + testing steps and post to ML shortly.)
+ [Impact]
+
+ * Detaching virtio-scsi disk in Xenial gues
Patches posted to kernel-team mailing list [1].
[1] https://lists.ubuntu.com/archives/kernel-team/2018-October/096072.html
[SRU Xenial][PATCH 0/2] Improve our SAUCE for virtio-scsi reqs counter (fix
CPU soft lockup)
** Description changed:
[Impact]
- * Detaching virtio-scsi disk in Xe
Organic Testcase
set -x
instancename=USER-trusty
firstdevice=sdb
seconddevice=sdc
diskname=USER-disk-1
gcloud compute --project "PROJECT" ssh --zone "ZONE" "$instancename" --command
'(tar -C /var/issue/first -cf - .) | (tar -C /var/issue/second -xpf -)'
gcloud compute --project "
Synthetic Test Case
===
Create a Xenial KVM guest
---
mfo@rotom:~$ uvt-simplestreams-libvirt sync release=xenial arch=amd64
mfo@rotom:~$ uvt-kvm create --mem 4096 --cpu 2 --disk 16 mfo-sf194614
release=xenial arch=amd64
Modify the virsh XML to add a virtio-scsi controller + disk
Verification successful on Bionic.
---
$ apt-cache madison linux-image-4.15.0-39-generic
linux-image-4.15.0-39-generic | 4.15.0-39.42 | http://archive.ubuntu.com/ubuntu
bionic-proposed/main amd64 Packages
$ sudo apt-get install -y linux-image-4.15.0-39-generic=4.15.0-39.42
$ sudo reboot
$ uname
Verification successful on Cosmic.
---
$ apt-cache madison linux-image-4.18.0-11-generic
linux-image-4.18.0-11-generic | 4.18.0-11.12 | http://archive.ubuntu.com/ubuntu
cosmic-proposed/main amd64 Packages
$ sudo apt-get install -y linux-image-4.18.0-11-generic=4.18.0-11.12
$ sudo reboot
$ uname
Verification successful with the kernel in xenial-proposed.
Updating verification tags.
Details
===
Guest:
---
root@mfo-sf194614:~# apt-cache madison linux-image-4.4.0-139-generic
linux-image-4.4.0-139-generic | 4.4.0-139.165 |
http://archive.ubuntu.com/ubuntu/ xenial-proposed/main amd64 Pa
Public bug reported:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the
test on unstable:
-
original:
$ uname -a
Linux mfo-sf194734 4.19.0-1-generic #2 SMP Mon Oct 8 14:38:01 -03 2018
x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e
test on Cosmic
--
original:
$ uname -a
Linux mfo-sf194734 4.18.0-9-generic #10-Ubuntu SMP Fri Oct 5 16:49:44 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff
** Summary changed:
- regression in 'ip --family bridge neigh' since linux v4.12+
+ regression in 'ip --family bridge neigh' since linux v4.12
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
** Description changed:
[Impact]
- * Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
+ * Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
- * Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
-such request/family c
** 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/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4
test on Bionic
--
original:
$ uname -a
Linux mfo-sf194734 4.15.0-37-generic #40-Ubuntu SMP Tue Oct 2 15:36:54 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:f
autopkgtests for ubuntu-fan
(triggered by this iproute2 upload)
The test failure in ubuntu-fan's lxd test (the thing
that is failing in these autopkgtests) does look flaky.
Looking at autopkgtest logs for ubuntu-fan on xenial, there's a series of
retriggers
for the _same_ version of docker.io th
autopkgtests for open-vm-tools,
failures in amd64 and i386.
These are consistently failing since May 14th, 2018
for a lot of other packages, thus not a change from
this upload.
Thanks,
Mauricio
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Public bug reported:
[Impact]
* An VM's VF cannot receive IPv6 multicast traffic
from other VMs' VFs in the same Mellanox adapter
_if_ its VF trust setting is not enabled, and on
Xenial currently iproute2 _cannot_ enable it.
* This breaks IPv6 NDP (Neighbor Discovery Protocol)
in t
** Patch added: "iproute2_xenial_vf-trust.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+attachment/5207579/+files/iproute2_xenial_vf-trust.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in
Hi Eric,
Thanks for reviewing.
This is the debdiff v2, addressing the points you brought up (numbered patches,
bug-ubuntu dep3 tag).
cheers,
Mauricio
** Patch removed: "iproute2_xenial_vf-trust.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+attachment/5207579/+fil
Hi Eric,
This is the v3 debdiff with the patches updated to apply with no offset
messages per your request.
Thanks,
Mauricio
--
Applying patch debian/patches/1008-vf_trust_dddf1b44126e.patch
patching file include/linux/if_link.h
Applying patch debian/patches/1009-vf_trust_b6d77d9ee312.patch
pa
Verification successful on xenial-proposed.
Updated verification tags.
Steps
=
Setup 1) Enable xenial-proposed and install the iproute2 package:
---
$ echo 'deb http://archive.ubuntu.com/ubuntu xenial-proposed main restricted' |
sudo tee /etc/apt/sources.list.d/xenial-proposed.list
deb htt
** 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 know
** 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 know
** 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 know
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 'p
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"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5210405/+files/sf202166.dmesg.
** Also affects: debian-installer (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux-lts-xenial (Ubuntu Precise)
Importance: Undecided
Status: New
** No longer affects:
d
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
linux patch posted to the kernel-team mailing list:
[B/C/D/Unstable][PATCH] UBUNTU: d-i: add iscsi_ibft to scsi-modules
https://lists.ubuntu.com/archives/kernel-team/2019-February/098745.html
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification bec
Test for scsi-modules udeb in Disco:
---
Check the original/modified udeb contents:
$ dpkg-deb -c scsi-modules-4.19.0-13-generic-di_4.19.0-13.14_amd64.udeb | grep
iscsi_ibft.ko
$
$ dpkg-deb -c
scsi-modules-4.19.0-13-generic-di_4.19.0-13.14+test20190221b1_amd64.udeb | grep
iscsi_ibft.ko
-rw-r-
Public bug reported:
[Impact]
* Systems running under memory pressure may hit stalls in the
order of seconds to minutes in systemd-logind and lxd mount
operations (e.g., ZFS backend), which get stuck in D state.
* The processes stuck in D state have a common stack trace,
(cat /proc/PI
Also verified this with stress-ng's memory stressor class.
The system gets under memory pressure to the point of
calling shrink_slab() 10s to 100s thousand times a second
(verified with ftrace; function tracer; shrink_slab filter).
$ sudo stress-ng --class memory --all -1 &
# echo shrink_slab >
[X/B][PATCH] mm: do not stall register_shrinker()
https://lists.ubuntu.com/archives/kernel-team/2019-February/098791.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/1817628
Title:
Re
cosmic-proposed:
---
verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.
root@petilil:~# uname -rv
4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019
root@petilil:~# echo writeback > /sys/block/bcache0/bcache/cach
bionic-proposed:
---
verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.
root@petilil:~# uname -rv
4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019
root@petilil:~# echo writeback > /sys/block/bcache0/bcache/cach
xenial-proposed:
---
verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.
root@petilil:~# uname -rv
4.4.0-143-generic #169-Ubuntu SMP Thu Feb 7 07:56:38 UTC 2019
root@petilil:~# echo writeback > /sys/block/bcache0/bcache/ca
For documentation purposes, this is the block device setup
configured in the system to debug/test/fix/verify the bug.
disk partitioning:
# fdisk /dev/sdb # create sdb1 and sbd2, 100G each.
bcache backing device: LVM volume in partition 1
# pvcreate /dev/sdb1
# vgcreate vg-test /dev/sdb1
# lvcre
trusty-proposed:
---
verification successful.
executed the reproducer 3x on the system used to debug/test/fix this problem.
no bug/oops observed.
root@petilil:~# uname -rv
3.13.0-166-generic #216-Ubuntu SMP Thu Feb 7 14:07:53 UTC 2019
root@petilil:~# echo writeback > /sys/block/bcache0/bcache/ca
** Description changed:
[Impact]
+
+ * Adapter resets periodically during high-load activity.
+
+ * I/O stalls until reset/reinit is complete (latency) and I/O performance
+ degrades across cluster (e.g., low throughput from data spread over nodes).
* The mpt3sas driver relies in a FW que
** Description changed:
[Impact]
* Adapter resets periodically during high-load activity.
* I/O stalls until reset/reinit is complete (latency) and I/O performance
degrades across cluster (e.g., low throughput from data spread over nodes).
* The mpt3sas driver relies in a FW que
Patch submitted to kernel-team mailing list, got 2 ACKs.
https://lists.ubuntu.com/archives/kernel-team/2019-January/097471.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/1810781
Titl
tu)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Incomplete
** Tags: bionic
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Kernel
Packages
201 - 300 of 727 matches
Mail list logo
