And on an arm64 platform we have something similar:
15:55:45 DEBUG| [stdout] Number of CPUs: 4
15:55:45 DEBUG| [stdout] Number of CPUs Online: 4
15:55:45 DEBUG| [stdout]
15:55:45 DEBUG| [stdout] access STARTING
15:55:49 DEBUG| [stdout] [ 7016.776865] unregister_netdevice: waiting for eth0
to
Public bug reported:
stress-ng sctp stressor breaks 5.4.0.7-8 on s390x during ADT regression
testing:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal-canonical-kernel-team-
unstable/focal/s390x/l/linux/20191203_153629_d7a41@/log.gz
I can't easily reproduce this on a s390 VM instance.
--
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/1854968
Title:
stress-ng sctp stressor breaks 5.4.0.7-8 on s390x
Status in linux
net/core/dev.c netdev_wait_allrefs() states:
**
* netdev_wait_allrefs - wait until all references are gone.
* @dev: target net_device
*
* This is called when unregistering network devices.
*
* Any protocol or device that holds a reference should register
* for netdevice notification, and
This makes sense as the af-alg stressor now exercises a far wider set of
crypto engines.
--
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/1854968
Title:
stress-ng sctp stressor breaks
The unregister_netdevice message appears after the af-alg stressor
starts, so it maybe a crypto algo that is the root cause:
14:34:33 DEBUG| [stdout] af-alg STARTING
14:34:35 DEBUG| [stdout] [ 2895.954700] unregister_netdevice: waiting for lo to
become free. Usage count = 1
--
You received
This stress test has not changed much lately, so I'm assuming this is a
racy kernel regression.
Last stress-sctp changes in stress-ng were:
commit 27b045a498b360ccbc761c3b62e3dd38dd744f09
Author: Colin Ian King
Date: Sat Aug 10 13:25:34 2019 +0100
stress-sctp: voidify unused return
Same on 5.4.0.4-5 too but not on 5.4.0.3.4
--
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/1854959
Title:
stress-ng sysinfo stressor trips kernel oops on ppc64el with 5.4.0.7-8
Status
DEBUG| [stdout]
06:26:02 DEBUG| [stdout]
** Affects: linux (Ubuntu)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Col
Hi Dean,
I've prepared another debug test kernel that has 70+ of the drm patches
removed that were introduced between the 5.3.0-19 and 5.3.9-23 kernels.
If this stops the fan spinning then this implies the regression was
introduced in a drm graphics patch.
Updated revision r2 Debian packages can
CPU averages:
5.3.0-19: 2.03W, 99.6% idle, 0.1% in kernel, 93.5% in C10 state, 5.3% in C8
state, 1.66GHz
5.3.0-23: 13.71W, 99.3% idle, 0.1% in kernel, 92.3% in C10 state, 6.1% in C8
state, 2.05GHz
GPU averages:
5.3.0-19: 0.10W
5.3.0-23: 7.19W
ACPI thermal zone:
5.3.0-19:
@Dean, just one sanity check, do you have non-integer icon scaling on
your desktop?
--
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/1853044
Title:
5.3.0-23-generic causes fans to spin
** Also affects: linux (Ubuntu Focal)
Importance: Critical
Assignee: Colin Ian King (colin-king)
Status: Confirmed
** Also affects: linux-hwe (Ubuntu Focal)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status
Thanks Witold! Much appreciated.
** Tags added: verification-done verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
Title:
Double-escape in initramfs
I was hoping you could test the version in -proposed. Without it being
verified as fixed then the fix won't be released for Eoan.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
@Witold, is it possible for you to sanity check this, if it's not
verified it won't be fixed.
thanks
Colin
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
Title:
** Description changed:
+ == SRU Justification Disco, Eoan, Focal ==
+
+ Multiple squashfs filesystems with overlayfs cause file corruption issues
+ when modifying zero sized files
+
+ == Fix ==
+
+ The current fix is pending in
+
I'm doing some testing right now on the current upstream fix, hopefully
will SRU this by EOD.
--
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/1824407
Title:
remount of multilower moved
I've found 3 possible commits that may have contributed to this
regression. Can you install the kernel headers, image and module debs
in https://kernel.ubuntu.com/~cking/lp-1853044/ and see if this helps
fix the issue.
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
Also, when the fan is running at high speed can you do the following:
sudo apt-get install acpi
acpi -V
and add the output to the bug report
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Dean,
As a first triaging step, with the 5.3.0-23-generic and also the
5.3.0-19-generic kernel do you mind installing and running the following
command:
powerstat -Ra | tee powerstat-$(uname -r).log
and attaching the log files to the bug report. The command takes about
60 seconds to run.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member
No problem at all. I'll close this bug if that's OK.
** Changed in: zfs-linux (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853130
spl 102400 4 zfs,icp,znvpair,zcommon
so just remove zfs-dkms and you can still use zfs on the HWE 5.0.x
kernel on Bionic.
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King
This bug has not been updated with further information requested in
question 4 for over a year. Marking as Won't Fix.
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yes, minimal impact and reducing regression risk is key in SRUs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
Title:
Double-escape in initramfs DECRYPT_CMD
Status in
** Description changed:
+ == SRU Justification, Eoan ==
+
initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line
414:
DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'"
This is OK when the line is executed by shell, such as in line 430 or
436, but when plymouth is
Fix required only in zfs-linux-0.8.1 in Eoan.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
Title:
Double-escape in initramfs DECRYPT_CMD
Status in zfs-linux package in
Fixed in zfs-0.8.2 in focal.
** Also affects: zfs-linux (Ubuntu Focal)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: Triaged
** Changed in: zfs-linux (Ubuntu Focal)
Status: Triaged => Fix Released
** Also affects: zfs-linux (Ubuntu Eoan)
Importa
Thanks for the patch. Any specific version of zfs-linux this relates to?
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Statu
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are
pr_warn can be removed with a sauce patch, so no worries with that.
--
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/1824407
Title:
remount of multilower moved pivoted-root overlayfs
been iterating on a fix with upstream:
https://lkml.org/lkml/2019/11/7/317
--
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/1824407
Title:
remount of multilower moved pivoted-root
When I'm more awake tomorrow I'll send a patch upstream as a suggested
fix and see if we can get a good solution on the UUIDs worked out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Just love the way launchpad mangles pasted code.
--
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/1824407
Title:
remount of multilower moved pivoted-root overlayfs root, results in
I/O
I was thinking of a more generalized overlayfs solution that detects if
file systems don't initialize the superblock uuid and overlayfs
improvises by generating the internal overlayfs uuid, something like:
diff --git a/fs/overlayfs/copy_up.c b/fs/overlayfs/copy_up.c
index
The concern I have is for other file systems that also don't populate
the UUID - this seems to be a general problem for overlayfs. Perhaps a
UUID can be autogenerated based on the superblock rather than file
system specific UUID magic if the UUID is zero.
--
You received this bug notification
Adding a uuid into the superblock on squashfs seems to resolve the
issue. Since squashfs does not have UUID support, my hack below
generates one based on some squashfs superblock metadata that provides a
good enough UUID for our purposes.
diff --git a/fs/squashfs/super.c b/fs/squashfs/super.c
Comparing the previous debug with 2 squashfs overlayfs lowers with the
*same* data on ext4 as the 2 overlayfs lowers we have:
[ 56.257691] repro-nosquashf (1038): drop_caches: 3
[ 56.265075] ovl_get_fh: 112 dentry: etc/.pwd.lock name:
trusted.overlay.origin
[ 56.265077] ovl_get_fh: 115:
4.15: ovl_get_origin_fh detects zero sized files on lower paths and
treats these a special zero sized "copied up but origin unknown" magic.
[ 25.442916] ovl_check_origin: etc/.pwd.lock 2
[ 25.442918] ovl_get_origin_fh: 104 etc/.pwd.lock
[ 25.442919] ovl_get_origin_fh: 107 res=0
[
Installed the new zfsutils + zfs dkms to sanity check the kernel driver
part of the fix:
dmesg | grep ZFS
[ 22.420188] ZFS: Loaded module v0.8.1-1ubuntu14.1, ZFS pool version 5000,
ZFS filesystem version 5
And now the test:
root@eoan-amd64-uefi:~# mkdir /zfs-test
root@eoan-amd64-uefi:~# cd
So this is a 2-phase fix. The dkms package is updated, then we test
this, then this gets sync'd into the kernel. I'm testing it right now,
let me sanity check the zfs-dkms part first and get that updated as step
#1.
--
You received this bug notification because you are a member of Kernel
Replaced one of the two squashfs with read-only ext4 partitions and
can't reproduce the error. Seems that we need 2 stacked squashfs file
systems.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Replaced read-only squashfs with read-only ext4 partitions and can't
reproduce the error.
--
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/1824407
Title:
remount of multilower moved
And if we change use a different file: /root-tmp/var/log/ubuntu-
advantage.log we get the following error too:
[ 24.531406] SQUASHFS error: squashfs_read_data failed to read block
0x89c066e0b540
[ 24.531444] SQUASHFS error: Unable to read metadata cache entry
[89c066e0b540]
--
You
OK, now managed to get a reproducer script to kick this bug even outside
the early install context. Seems like we can force this bug by either
remounting OR sync'ing and dropping caches.
Attached is the reproducer script.
Run as root, we hit the error:
cat: /root-tmp/etc/.pwd.lock:
BTW, I can generate the mount move failure with the cut down script as
follows (which follows the same mount patterns as the casper script)
#!/bin/bash -x
mkdir -p /cdrom
mount -t iso9660 -o ro,noatime /dev/sr0 /cdrom
sleep 1
mkdir -p /cow
mount -t tmpfs -o 'rw,noatime,mode=755' tmpfs /cow
sleep
Hi Dimitri,
while debugging this I found the following in setup_unionfs() in
scripts/casper:
# move the first mount; no head in busybox-initramfs
for d in $(mount -t squashfs | cut -d\ -f 3); do
mkdir -p "${rootmnt}/rofs"
if [ "${UNIONFS}" = unionfs-fuse ]; then
Verified, seeing same ball-park performance improvements.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: zfs-linux (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849665
Title:
zfs diff: Unable to determine path
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux-hwe (Ubuntu Bionic)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
uploaded zfs-linux (0.8.1-1ubuntu14.1) eoan (will land in -proposed sometime
soon)
uploaded zfs-linux (0.0.1.1ubuntu16) focal
Once the packages are uploaded the dkms driver component will be sync'd
into the next kernel and then once this is in -proposed it can be fully
tested.
--
You received
I'll get this uploaded into -proposed once the current SRU backlog is
out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849665
Title:
zfs diff: Unable to determine path or stats
** Description changed:
+ == SRU Justification, Eoan ==
+
+ Using zfs diff on an encrypted dataset with large objects one can hit an
+ error such as follows:
+
+ # zfs diff nsnx/trusty-2a@snap1 nsnx/trusty-2a
+ + /nsnx/trusty-2a/bin
+ Unable to determine path or stats for object 5 in
With the fix:
root@eoan-amd64-efi:/home/cking# mkdir /zfs-test
root@eoan-amd64-efi:/home/cking# cd /zfs-test
root@eoan-amd64-efi:/zfs-test# truncate -s 10G file.img
root@eoan-amd64-efi:/zfs-test# zpool create -o ashift=12 -O acltype=posixacl -O
compression=lz4 -O xattr=sa -O normalization=formD
Confirming that upstream commit
https://github.com/zfsonlinux/zfs/commit/d359e99c38f66732d42278c32d52cfcf1839aa4f
fixes this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1847628
Title:
When using swap in ZFS, system stops when you start
A fix has landed in lxd, I refer you to the following comment:
https://github.com/lxc/lxd/issues/4656#issuecomment-541266681
Please check if this addresses the issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-use-a-zvol-as-a-swap-
device
..there are known issues with swap on ZFS not working well on heavily
memory loaded systems.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
A swapfile on ZFS is a bad idea. Swapped out pages get pushed through
the vfs into zfs and each page of swap will be magnified in the number
of free pages required to get this page out to disk.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
The error: "zfs[9317]: cannot mount '/': directory is not empty" seems
to suggest that this is a root mounted zfs. Is that so?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1846424
** Description changed:
== SRU Justification Eoan ==
Now that 5.4 contains a fix to the bootup regression due to the lack of
entropy at bootable we should apply this fix and also revert the revert
of commit "Revert "ext4: make __ext4_get_inode_loc plug"".
== Fix ==
So, to
is now zero.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
or 5.3 kernels then one can remove zfs-dkms.
Can you provide more information about the error?
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (
and
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=7447c7b658e3a6cc40496a75033c007e4a91f166
** Changed in: stress-ng
Importance: Undecided => High
** Changed in: stress-ng
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: ubuntu-kernel
I've managed to reproduce this on pepe, seems like the autotest is being
OOM'd in preference to the actual cloning processes. I'll see if I can
figure out how to stop this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Fix committed: https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=8e618fb7b00ecc206fe3ea73084492ebb5835747
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: ubuntu-kernel-tests
Status: Incomplete =&g
d in: ubuntu-kernel-tests
Assignee: Colin Ian King (colin-king) => (unassigned)
** Changed in: linux (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
And for Standard_D2s_v3
IP addr Mac AddrKernel Reboots
104.42.252.54 00:0d:3a:32:df:92 5.0.0-1020-azure500
104.42.150.26 00:0d:3a:31:1b:50 5.0.0-1020-azure500
104.42.147.144 00:0d:3a:32:d8:2f 5.0.0-1020-azure500
40.112.129.232
@Joseph, so I can reproduce this hang/crash issue across a variety of
instances. I can't get any info back on a console, so debugging this is
not easy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-kernel-tests
Importance: Undecide
Get more failures with Standard_B1ms
IP addr Mac AddrKernel Reboots
52.160.101.11 00:0d:3a:5b:a0:7c 5.0.0-1020-azure10
137.135.51.101 00:0d:3a:31:20:fc 5.0.0-1020-azure500
137.135.50.133 00:0d:3a:31:27:0f 5.0.0-1020-azure396 [hang]
See: https://github.com/lxc/lxd/issues/4656#issuecomment-535531229
In https://github.com/lxc/lxd/blob/master/lxd/storage_zfs_utils.go#L255
the umount is done by
err := unix.Unmount(mountpoint, unix.MNT_DETACH)
The umount2(2) manpage writes about MNT_DETACH:
Perform a lazy unmount: make
I kicked off another ~20K reboot tests with Standard_B2S instances and
hit hangs again:
IP addr Mac AddrKernel Reboots
104.42.3.16100:0d:3a:37:82:ee 5.0.0-1020-azure100
13.91.5.23 00:0d:3a:5a:74:23 5.0.0-1020-azure57
So the best way to reproduce this issue is to run ~500 reboots across
multiple instances rather than 5000-1 reboots on once instance.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
See above, I ran several thousand reboot tests on a lot of Basic_A3
instances, ranging from 50, 250 to 500 reboots. Only one failed. So
this is *really* hard to reproduce.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
IP addr Mac AddrKernel Reboots
13.64.67.18600:0d:3a:3a:dd:04 5.0.0-1016-azure50
104.42.152.115 00:0d:3a:35:b1:e6 5.0.0-1016-azure50
65.52.121.205 00:0d:3a:3b:0f:52 5.0.0-1016-azure50
13.88.28.42 00:0d:3a:3b:c7:da
This bug has been dormant for a while with no update. I'm marking it as
won't fix. If this is still and issue, please re-open this bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: thermald (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1811730
Title:
Thermald does not set max CPU after reseting
Been digging into this a bit further with lxc 3.17 on Eoan.
lxc launch ubuntu:bionic zfs-bug-test
Creating zfs-bug-test
Starting zfs-bug-test
lxc delete zfs-bug-test --force
Error: Failed to destroy ZFS filesystem: Failed to run: zfs destroy -r
default/containers/z1: cannot destroy
@Robert, was there a specific class of virtual machine you were using
when this issue occurred?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while
** Changed in: linux-azure (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while rebooting cloud
@Joseph, any ideas how we can progress on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while rebooting cloud instance
Status in linux-azure
I can reproduce this on 4.15.0-38 but not on a more recent kernel, e.g.
4.15.0-64, so I think this has been fixed. I'll close this for now as
fixed released, but feel free to re-open it if we see the same issue
again.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
**
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
>From "Comment bridged from LTC Bugzilla" in a bug discussion:
"FWIW, I verified this on z14, and there clearly lz4 is (as expected)
the fastest decompression algorithm.
With vanilla 5.3-rc6 and defconfig I get the following kernel uncompression
times:
lzo: 27us
lz4: 24us
An initrd
Also enable LZ4 for s390x as IBM has provided us with some positive
feedback about using this.
--
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/1840934
Title:
Change kernel compression
The ZFS destroy checks the reference count on the dataset with
zfs_refcount_count(>ds_longholds) != expected_holds and returns
EBUSY in dsl_destroy_head_check_impl.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
latter 1-2 weeks of this cycle
--
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/1832384
Title:
Unable to unmount apparently unused filesystem
Status in linux package in Ubuntu:
See also: https://wiki.ubuntu.com/Kernel/StableReleaseCadence
and https://kernel.ubuntu.com/
--
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/1832384
Title:
Unable to unmount apparently
We generally have a 3 week release cycle on kernels, so if it's in
-proposed it probably in the later 1-2 weeks of this cycle.
--
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/1832384
Assignee: Colin Ian King (colin-king)
Status: Triaged
** Also affects: lxc (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Disco)
Importance: Undecided
That's really helpful to know John, thanks for the feedback.
--
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/1832384
Title:
Unable to unmount apparently unused filesystem
Status in
Do we have any hunches on how to reproduce this issue?
--
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/1779156
Title:
lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
Cosmic is now end-of-life. Does this still occur on Disco?
** Changed in: linux (Ubuntu)
Importance: High => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Pa
The following run as root will cause the instances to hang and then
reboot (by the watchdog?)
#include
#include
#include
#include
#include
int main(void)
{
for (;;) {
int fd;
fd = open("/dev/hpet", O_RDONLY | O_NONBLOCK);
close(fd);
Seems to occur when exercising /dev/hpet
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1841747
Title:
dev test in ubuntu_stress_smoke_test crashes AWS c5.large with Disco
Status
@Dimitri,
Seems that for initramfs lz4 makes a lot of sense, see:
https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/boot-speed-
initramfs-decompression-eoan.ods
The load times for LZ4 is slower than the previous default, however, the
decompression time makes up for this unless one is booting
801 - 900 of 2248 matches
Mail list logo