I have confirmed that this issue with not being able to capture kernel
dump with a mantic arm64 kernel is not new. using the arm64 6.5 kernel
(6.5.0-5) in the release pocket I captured the following during test.
```
ubuntu@cloudimg:~$ sudo kdump-config show
DUMP_MODE: kdump
USE_KDUMP:
@xnox I have successfully verified that -proposed arm64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host. See
https://people.canonical.com/~philroche/20231003-mantic-minimal-
proposed-kernel/ for cloud-init logs, some debug output and test
I have also successfully verified that -proposed amd64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host with older hardware (ThinkPad T460
with 6th gen intel i5 which is the same hardware which we were able to
reproduce the issue on previo
Public bug reported:
After upgrading from 22.04 to 23.04 the intel wifi driver is not
loading, I am seeing the following in dmesg:
[ 215.024382] Loading of unsigned module is rejected
[ 262.051998] [ cut here ]
[ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/gene
Alos seeing this:
[2.691388] iwlwifi_compat: loading out-of-tree module taints kernel.
[2.698204] Loading modules backported from iwlwifi
[2.698208] iwlwifi-stack-public:master:9904:0e80336f
--
You received this bug notification because you are a member of Kernel
Packages, which is s
I have removed the backports and now i'm getting this:
sudo dmesg |grep -i wifi
[3.412202] Intel(R) Wireless WiFi driver for Linux
[3.412300] iwlwifi :00:14.3: enabling device ( -> 0002)
[3.525445] iwlwifi :00:14.3: CSR_RESET = 0x10
[3.525473] iwlwifi :00:14.3: Host
@Matthew No luck i'm afraid I removed the module and I'm still getting
the same issue. @Jeremy is there any other steps I can try ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs
Windows was installed but it’s removed now. I have seen suggestions to
create a bootable usb to disable the WiFi adapter but I’m not sure if
that would work
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https:
For reference, I also tried on a 22.04 cloud image with 5.15 kernel
```
ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting
--numjobs=8 --name=fiojob1 --filename=/dev/sda
fiojob1: (g=0): rw=write,
Google have provided a non synthetic `fio` impact
> Performance was severally degraded when accessing Persistent Volumes
provided by Portworx/PureStorage.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Providing exact reproducer steps using Qemu locally -
Launch script:
https://gist.github.com/philroche/8242106415ef35b446d7e625b6d60c90 and
cloud image I used for testing @ http://cloud-
images.ubuntu.com/minimal/releases/focal/release/
```
# Download the VM launch script
wget --output-document=
@kamalmostafa indeed yes. I had missed this.
See below for the output from 20.04 with 5.15 kernel.
```
ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting
--numjobs=8 --name=fiojob1 --filename=/
I am NOT seeing the same on 22.04
```
ubuntu@cloudimg:~$ uname --kernel-release
5.15.0-87-generic
ubuntu@cloudimg:~$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_UR
I have reproduced with @amalmostafa's updated script with a separate
disk too. I see no segfault and no EXT4 errors but the regression in
performance is still present but not as great as in my previous tests.
```
### Ubuntu 20.04 with 5.4 kernel and data disk
ubuntu@cloudimg:~$ sudo fio --ioengin
The diff in process count from kernel change image -> kernel change +
seed change image is actually a reduction in processes - see diff @
https://pastebin.ubuntu.com/p/PXtQM9gB2K/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
@paelzer
> The change of the image build sadly combined it all
See the description noting
https://people.canonical.com/~philroche/20230824-manticl-minimal-
LP2032933/ which should help in determining where the changes were
introduced as I have provided three images across the various stages of
ch
I have uploaded further data now to
https://people.canonical.com/~philroche/20230824-manticl-minimal-
LP2032933/server-metrics/ with kernelmodules, kernelconfig, services,
timers etc. for each of the three images being inspected. This
additional data was gathered with a modified fork of the `server
** Description changed:
- The Mantic (Ubuntu 23.10) images are undergoing some big changes prior
- to 23.10 release in October.
+ The Mantic (Ubuntu 23.10) download/qcow2 images available @
https://cloud-images.ubuntu.com/minimal/
+ are undergoing some big changes prior to 23.10 release in Octobe
@paelzer given the above findings and discussion, I would like to mark
this as Invalid for cloud-images project and continue the conversation
in the context of kernel only. +1 / -1 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
The issue is in zfs-linux, where the merge from debian
http://launchpadlibrarian.net/535966758/zfs-
linux_2.0.2-1ubuntu5_2.0.3-8ubuntu1.diff.gz once again reverted some of
the fixes and rolled back the patch to an earlier version. The fix was
already reverted erronously in hirsute during the debian
Please run apport-collect to attach logs so that we can debug your setting.
@baling: why subscribing zsys to this bu? There is no mention of zsys being
used here, it seems directly a manual zfs setup.
** Package changed: zsys (Ubuntu) => zfs-linux (Ubuntu)
--
You received this bug notification
We wrote on another bug report BertN45 to not upgrade your bpool. Only
power users will use zpool status command to list and we expect them to
know the implication.
I think I'll retarget this bug for preventing bpool upgrade.
** Summary changed:
- Confusing zpool status in Ubuntu 19.10 installed
Public bug reported:
As we are not going to own in the end org.zsys, move our identifier tags
to com.ubuntu.zsys.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: zsys (Ubuntu
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: grubzfs-testsuite (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Fix Committed
** Changed in: grubzfs-testsuite (Ubuntu)
Status: New => Fi
Public bug reported:
# zpool create -o ashift=12 -O atime=off -O canmount=off -O normalization=formD
-O mountpoint=/ -R /mnt rpool /dev/vda2
# zfs create rpool/ROOT -o canmount=off -o mountpoint=none
# zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
# zfs create rpool/ROOT/ubuntu_123456/var
** Description changed:
-
# zpool create -o ashift=12 -O atime=off -O canmount=off -O
normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2
# zfs create rpool/ROOT -o canmount=off -o mountpoint=none
# zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
# zfs create rpool/ROOT/ubun
** Description changed:
# zpool create -o ashift=12 -O atime=off -O canmount=off -O
normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2
# zfs create rpool/ROOT -o canmount=off -o mountpoint=none
# zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
# zfs create rpool/ROOT/ubuntu_
** Description changed:
- # zpool create -o ashift=12 -O atime=off -O canmount=off -O
normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2
- # zfs create rpool/ROOT -o canmount=off -o mountpoint=none
- # zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
- # zfs create rpool/ROOT/ubuntu_
** Bug watch added: Github Issue Tracker for ZFS #8833
https://github.com/zfsonlinux/zfs/issues/8833
** Also affects: zfs via
https://github.com/zfsonlinux/zfs/issues/8833
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Thanks for testing the upgrade to 19.10. The only reason you would boot
with an older version of a kernel and zfs itself is due to your update
between 19.04 to 19.10 failed. Can you share the upgrade logs
/var/log/upgrade content and /var/log/dist-upgrade?
The weird part is that do-release-upgrade
The upgrade failed, in your logs, you have:
"/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.2.0-15-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=bf02ddd4-8d65-40d6-ab24-4fc8a5673dc6)
I: Set the RESUME variable to override this.
/etc
The issue seems to be related to a change in ZFS 0.8 initramfs script.
The initramfs script for ZFS does a normal ZFS import.
ZFS import now forces to export a pool before importing it back again on a
different system. This is a security feature to ensure the same pool isn't
imported on two diff
Public bug reported:
We (Canonical CPC) are seeing an issue with today's build of the bionic
minimal cloud images. Boot stops at "Starting Initial cloud-init job
(metadata service crawler)..." for nearly 5 minutes (booting on
scalingstack and locally with kvm) this is with a new kernel, but
otherw
The meta-packages have been rolled back and the fix is in progress of
being applied and uploaded.
--
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/1779961
Title:
Boot delays with 4.15.0-24
** Also affects: systemd (Ubuntu)
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/1867007
Title:
zfs-initramfs fails with multiple rpool on
Hey Balint. I just added the task post ZFS upload (the upload was
yesterday and I added the task this morning) so indeed, there is some
work needed, part of it being in systemd.
Basically, systemd isn’t capable of mounting datasets when pool names are
duplicated on a machine
zfs-mount-generator g
Thanks for your bug report! This is now fixed in zfs-linux
0.8.3-1ubuntu10 in focal.
** Package changed: zsys (Ubuntu) => zfs-linux (Ubuntu)
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packag
See my previous comment: this is only related to zfs-linux with the
version I mentioned. Also, we didnt’ make any change to grub for ZFS
since 26 February, and if you have an empty grub.cfg, this may be due to
other bugs, like multiple rpool/bpool, which isn’t what this one was
about. Ensure that y
This is probably because your bpool is not in the zfs cache file.
Either reinstall from the beta image which has a fix in the installer, or:
- clean up any files and directories (after unmounting /boot/grub and
/boot/efi) under /boot (not /boot itself)
- zpool import bpool
- zpool set cachefile=
Public bug reported:
Install zsys on a non ZFS system without the kernel module loaded leaded
to a segfault.
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to z
Sorry Colin, this was ZSys and I targetted the wrong component when
filing batch-bugs for ZSys 0.5 upload.
Fixed in https://launchpad.net/ubuntu/+source/zsys/0.5.0.
** Package changed: zfs-linux (Ubuntu) => zsys (Ubuntu)
** Changed in: zsys (Ubuntu)
Status: Incomplete => Fix Released
--
Public bug reported:
As stated on bug #1876052, the default acceleration mode option is none
of the 3 nvidia settings option.
It’s displayed as "Performance mode" when you launch it for the first time,
however:
- default launch is Intel (so no performance mode)
- there is a "Use dedicated card"
Public bug reported:
Fresh install of 20.04 LTS with nvidia binary driver from our archive.
(dual Intel/Nvidia setup)
No setting change has been done. The card supports "On demand".
Tested with Firefox (about:support) and Chrome (config:cpu). Both are showing
the same result:
- default launch -
Your patch makes sense Richard and I think it will be a good upstream
candidates. In all approaches you proposed, this is my prefered one
because this is the most flexible IMHO.
Tell me when you get a chance to test it and maybe John, you can confirm
this fixes it for you?
--
You received this b
On an installed packaged system, the files are in different directories
(and don’t have the .in extension as they have been built with the
prefix replacement). Their names and locations are:
/lib/systemd/system/zfs-mount.service
/lib/systemd/system-generators/zfs-mount-generator
--
You received
Great to hear John! Thanks for confirming and thanks to Richard for the
patch.
I’m happy to SRU it to focal once it’s proposed upstream. (Keep me
posted Richard, you can drop a link here and I will monitor)
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
Following some debug of the docker.io package in universe, we (Canonical
CPC) discovered that the ubuntu-fan package from main and the netcat-
traditional package from universe were being installed.
This was due to the following dependency/recommends tree:
* docker.io (in un
It appears that a bug was already filed against netcat
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1780316
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1861704
Ti
Can you try to reproduce an upgrade without your 40_custom file?
I don't think your pool manual upgrade has any link to this.
--
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/1843222
Ti
Public bug reported:
If /var/lib is a dataset not under /ROOT/, as proposed
in the ubuntu root on zfs upstream guide
(https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS), we end up
with a race where some services, like systemd-random-seed are writing under
/var/lib, while zfs-mou
** Also affects: zfs
Importance: Undecided
Status: New
** Description changed:
- If /var/lib is a dataset not under /ROOT/, as proposed
- in the ubuntu root on zfs upstream guide
- (https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS), we end up
- with a race where some
Marking the zfs-linux task as won't fix after looking more deeply about
cause/consequences of forcing -f on every boot:
- zfs 0.8, as told previously, tag with which system the pool was associated
with and refuse to import previously unexported pool, as they can still be
attached to any systems
Public bug reported:
There is a race between empty cache file for the mount generator and fstab
which contains /boot/grub.
With zfs on root, the generator is the only solution to avoid races. However in
0.8 it misses cache invalidation (when rollbacking or booting on other
datasets).
This is a
Confirming that it’s fixed on the same machine with 550.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2061079
Title:
GTK-ngl (new default backend) rendering issue
I have a Acer Aspire E5-511-C5QS with the same issue with BIOS, i try
solution from TOXIC (toxicpublic) in #185, but says invalid EFI file
path, also i can't try solution from Paul Sladen(#173) because i can't
boot Ubuntu, only Grub Shows and allow me to boot my Windows 10
partition, i hope someon
I fixed my laptop Acer E5-511-C5QS, it has all the described issues BIOS save
won't change and i was unable to boot from a Liveusb, so i follow #554 and i
use bruteforce procedure drescribed in #560 and find that my partition was
(hd0,9) equivalent to sda9, i get stuck in initramfs, and i use #5
101 - 156 of 156 matches
Mail list logo
