[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
In the next few days, when I get some "spare" time... I will spin up a few test Jammy VM's to capture what depends it has to pull in from other repo's, so that the depends can be ID'ed and maybe those packages can be added to that Jammy package in this new PPA. Otherwise, as I just found out with a User, it put him into broken packages depends hell. Doing that while possibly bringing in those depends would simplify that... as just add the PPA and go with it. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Works great. Tested, and a lot simpler, because there are builds for
Jammy, Mantic and Noble.
The command log for the updated work-around using the "Backports build PPA"
>>>
sudo su -
zpool export -a
zpool import -N -R /mnt rpool
zpool import -N -R /mnt bpool
UUID=$(zfs list | awk '/^bpool\/BOOT\/ubuntu_/ {print $1}' | sed
's/bpool\/BOOT\/ubuntu_//g')
zfs import rpool/ROOT/ubuntu_$UUID
zfs import bpool/BOOT/ubuntu_$UUID
zfs mount -a
mount --make-private --rbind /dev /mnt/dev
mount --make-private --rbind /proc /mnt/proc
mount --make-private --rbind /sys /mnt/sys
mount --make-private --rbind /run /mnt/run
chroot /mnt /bin/bash --login
mount -a
# Add the "Backports build PPA" for Grub2 2.12
add-apt-repository ppa:ubuntu-uefi-team/backports-build
apt update
# Install the Grub2 packages
apt install grub-efi-amd64 grub-efi-amd64-signed
# This will pull in some needed depends of Grub2 2.12~rc1 from the Nolble Repo's
# Reinstall/configure grub
grub-install --target=x86_64-efi --efi-directory=/boot/efi \
--bootloader-id=ubuntu --recheck --no-floppy
# Update the intramfs images
update-intramfs -c -k all
# Change the repo sources back to Jammy
cp /etc/apt/sources.list.jammy /etc/apt/sources.list
apt update
# Test: (Skip if snapshots already exist...)
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204a
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204b
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204c
zfs list -t snapshot
# Output:
#NAME USED AVAIL REFER MOUNTPOINT
#bpool/BOOT/ubuntu_2nlhsy@20230204a 0B - 298M -
#bpool/BOOT/ubuntu_2nlhsy@20230204b 0B - 298M -
#bpool/BOOT/ubuntu_2nlhsy@20230204c 0B - 298M -
# Exit Gracefully:
exit
mount | grep -v zfs | tac | awk '/\/mnt/ {print $3}' | \
xargs -i{} umount -lf {}
zpool export -a
reboot
>>>
--
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/2051999
Title:
Grub2 2.06 has upstream bug that results in Non-booting with ZFS after
snapshot of bpool.
Status in grub2 package in Ubuntu:
Confirmed
Status in grub2-unsigned package in Ubuntu:
Confirmed
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
There is an upstream Bug with Grub where if you create snapshots of bpool, it
results in a non-booting System. The problem was found to be an upstream Bug
with Grub2:
https://savannah.gnu.org/bugs/index.php?64297
Multiple Ubuntu 22.04.3 Users Affected:
https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug
https://ubuntuforums.org/showthread.php?t=2494957
Brought up as an issue at OpenZFS:
https://github.com/openzfs/zfs/issues/13873
If you look at this comment
(https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was
found the Savanaugh at GNU released a fix for it in Grub2 2.12, here:
https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c
Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch
to Grub2 2.06 so that Users are not caught of in this bug for or
currently supported LTS Release.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: grub-efi-amd64 2.06-2ubuntu14.4
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Thu Feb 1 16:40:28 2024
InstallationDate: Installed on 2021-09-23 (861 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: grub2-unsigned
UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series
Link to this bug, just for package 'nvidia-driver-390': https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-390/+bug/2051436, which is a duplicate of : https://bugs.launchpad.net/ubuntu/jammy/+source/nvidia-graphics- drivers-390/+bug/2028165 For nvidia-driver-390, there is another work-around now, credit to Daniel Letzeisen (dtl131) with builds for mantic & Jammy, that works with the 6.5.0 series kernels until the patch is released: >>> sudo add-apt-repository ppa:dtl131/nvidiaexp sudo apt update sudo apt install nvidia-drivers-390 >>> I tested it and confirm it installs builds, and work fine with 6.5.0-17. -- 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/2051457 Title: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series Status in dkms package in Ubuntu: Confirmed Status in gcc-defaults package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: Since Jammy went to the 6.5.0 kernel series, that kernel series was compiled with gcc-12. The previous 6.2.0 series kernels were compiled with gcc-11. The current version of gcc in jammy is 11.4. Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc fail to build the modules, because of a gcc compiler version mismatch between what the current running kernel was built by, and the module being built. I recognized this while helping Users with NVidia driver compile errors on the forum, and came up with this work-around for them: https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164 Summary: Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler. Since then, this work-around has helped to resolve problems with running the 6.5.0 series kernels and building modules for other applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for use with the 6.5.0 series. I have run this for over a month as my default with no ill affects. I have continued to recommend this work-around to many user to solve their problems... *** I think it is time to look at pushing through gcc-12 as the default compiler for 22.04.3 through the normal updates channel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gcc 4:11.2.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Sun Jan 28 08:23:37 2024 InstallationDate: Installed on 2022-09-19 (496 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
@mkukri --- >>> The question is, are we going to backport the fix to 2.06 and push that to the updates channel, or can this wait for the 2.12 SRU sometimes after April? >>> What does that mean? Option #1 -- The cherry picked Grub2 2.12 ZFS related commit code gets applied to Grub2 2.06 as a patch? Option #2 -- After April, when Grub2 2.12 gets published and released as a "stable release update," that it also gets released to Jammy and Mantic? But you said it has the potential to break Jammy? I'm not seeing that in my tests yet, but I believe you. Here is how I see the logic of this, but it means nothing, as I am not in the decision process, but: For option 1, that would take time anyways, and the Noble April Release is less than 2 months. So option #2 would be about the same wait with a whole lot less work involved by everyone. *** Until then, I have three working work-arounds for this non-booting error: Work-around #1-- The above work-around, which you say may break some things. Work-around #2-- I do have another work-around, that involves booting from an Installer LiveUSB. Backing up the content of bpool to a created backup directory "somehwere" (size needed is less than 2GB), saving the old UUID that was used in the old dataset name to a file. I used another USB Flash drive. Destroy the old bpool pool. Create the new bpool with these explicit creation options: >>> zpool create \ -o ashift=12 \ -o autotrim=on \ -o cachefile=/etc/zfs/zpool.cache \ -o feature@async_destroy=enabled \ -o feature@empty_bpobj=active \ -o feature@lz4_compress=active \ -o feature@multi_vdev_crash_dump=disabled \ -o feature@spacemap_histogram=active \ -o feature@enabled_txg=active \ -o feature@hole_birth=active \ -o feature@extensible_dataset=disabled \ -o feature@embedded_data=active \ -o feature@bookmarks=disabled \ -o feature@filesystem_limits=disabled \ -o feature@large_blocks=disabled \ -o feature@large_dnode=disabled \ -o feature@sha512=disabled \ -o feature@skein=disabled \ -o feature@edonr=disabled \ -o feature@userobj_accounting=disabled \ -o feature@encryption=disabled \ -o feature@project_quota=disabled \ -o feature@device_removal=disabled \ -o feature@obsolete_counts=disabled \ -o feature@zpool_checkpoint=disabled \ -o feature@spacemap_v2=disabled \ -o feature@allocation_classes=disabled \ -o feature@resilver_defer=disabled \ -o feature@bookmark_v2=disabled \ -o feature@redaction_bookmarks=disabled \ -o feature@redacted_datasets=disabled \ -o feature@bookmark_written=disabled \ -o feature@log_spacemap=disabled \ -o feature@livelist=disabled \ -o feature@device_rebuild=disabled \ -o feature@zstd_compress=disabled \ -o feature@draid=disabled \ -o feature@zilsaxattr=disabled \ -o feature@head_errlog=disabled \ -o feature@blake3=disabled \ -o feature@block_cloning=disabled \ -o feature@vdev_zaps_v2=disabled \ -o compatibility=grub2,ubuntu-22.04 \ -O devices=off \ -O acltype=posixacl \ -O xattr=sa \ -O compression=lz4 \ -O normalization=formD \ -O relatime=on \ -O canmount=off -O mountpoint=/boot -R /mnt\ bpool /dev/disk/by-id/ata-QEMU_HARDDISK_QM3-part3 >>> Set the UUID VAR from the old UIUID stored in the file, then recreate the bpool filesystem datasets >>> zfs create -o canmount=off -o mountpoint=none bpool/BOOT bpool/BOOT zfs create -o mountpoint=/boot bpool/BOOT/ubuntu_$UUID >>> rsync the old bpool contents back into the new bpool... Export the new bpool and reboot. Work-around #3-- Is to back up and reinstall, telling the user not to do any snapshots of bpool until this problem is resolved. Work-arounds #1 & #3 make no changes to the pool options. Work-around #3 has the risk of losing the user data. Work-around #2 is a whole lot of work, and has the highest risk factor of them all... And the options used are different than was installed... But it works with Grub2 2.06. @Mate: What do you think on this? What should we tell Users until April? -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS:
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
So yes. Grub2 2.12 with those patches fixes this issue for Jammy, Mantic and Noble. We need to apply the fix to all these releases. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
The command log for the work-around for a broken jammy install:
>>>
sudo su -
zpool export -a
zpool import -N -R /mnt rpool
zpool import -N -R /mnt bpool
UUID=$(zfs list | awk '/^bpool\/BOOT\/ubuntu_/ {print $1}' | sed
's/bpool\/BOOT\/ubuntu_//g')
zfs import rpool/ROOT/ubuntu_$UUID
zfs import bpool/BOOT/ubuntu_$UUID
zfs mount -a
mount --make-private --rbind /dev /mnt/dev
mount --make-private --rbind /proc /mnt/proc
mount --make-private --rbind /sys /mnt/sys
mount --make-private --rbind /run /mnt/run
chroot /mnt /bin/bash --login
mount -a
cp /etc/apt/sources.list /etc/apt/sources.list.jammy
sudo nano /etc/sources.list.noble
With these contents:
deb http://us.archive.ubuntu.com/ubuntu/ noble main restricted universe
multiverse
deb http://us.archive.ubuntu.com/ubuntu/ noble-updates main restricted universe
multiverse
deb http://us.archive.ubuntu.com/ubuntu/ noble-backports main restricted
universe multiverse
deb http://security.ubuntu.com/ubuntu noble-security main restricted universe
multiverse
cp /etc/apt/sources.list.noble /etc/sources.list
apt update
add-apt-repository ppa:ubuntu-uefi-team/build
nano /etc/apt/sources.list.d/ubuntu-uefi-team-ubuntu-build-jammy.list
#change the active line to:
deb [trusted=yes]
https://ppa.launchpadcontent.net/ubuntu-uefi-team/build/ubuntu/ noble main
# save and exit
apt update
apt install grub-efi-amd64 grub-efi-amd64-signed
# This will pull in the depends from Grub2 2.12~rc1 from the Nolble Repo's
grub-install --target=x86_64-efi --efi-directory=/boot/efi \
--bootloader-id=ubuntu --recheck --no-floppy
update-intramfs -c -k all
# Change the repo sources back to Jammy
cp /etc/apt/sources.list.jammy /etc/apt/sources.list
apt update
Test:
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204a
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204b
zfs snapshot bpool/BOOT/ubuntu_2nlhsy@20230204c
# Or if there are still snapshots of bpool there...
zfs list -t snapshot
#Output:
#NAME USED AVAIL REFER MOUNTPOINT
#bpool/BOOT/ubuntu_2nlhsy@20230204a 0B - 298M -
#bpool/BOOT/ubuntu_2nlhsy@20230204b 0B - 298M -
#bpool/BOOT/ubuntu_2nlhsy@20230204c 0B - 298M -
#Exit Gracefully:
exit
mount | grep -v zfs | tac | awk '/\/mnt/ {print $3}' | \
xargs -i{} umount -lf {}
zpool export -a
reboot
>>>
--
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/2051999
Title:
Grub2 2.06 has upstream bug that results in Non-booting with ZFS after
snapshot of bpool.
Status in grub2 package in Ubuntu:
Confirmed
Status in grub2-unsigned package in Ubuntu:
Confirmed
Status in zfs-linux package in Ubuntu:
New
Bug description:
There is an upstream Bug with Grub where if you create snapshots of bpool, it
results in a non-booting System. The problem was found to be an upstream Bug
with Grub2:
https://savannah.gnu.org/bugs/index.php?64297
Multiple Ubuntu 22.04.3 Users Affected:
https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug
https://ubuntuforums.org/showthread.php?t=2494957
Brought up as an issue at OpenZFS:
https://github.com/openzfs/zfs/issues/13873
If you look at this comment
(https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was
found the Savanaugh at GNU released a fix for it in Grub2 2.12, here:
https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c
Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch
to Grub2 2.06 so that Users are not caught of in this bug for or
currently supported LTS Release.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: grub-efi-amd64 2.06-2ubuntu14.4
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Thu Feb 1 16:40:28 2024
InstallationDate: Installed on 2021-09-23 (861 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: grub2-unsigned
UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
@rlaager --- When I said reconfigure, i did: >>> sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi \ --bootloader-id=ubuntu --recheck --no-floppy >>> So yes, was that. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Wahoo! Found the magic combination. chrooted into the broken jammy system. Add a Noble sources list. Add the ppa. Edit the added /etc/apt/sources.list.d/ubuntu-uefi-team-ubuntu-build-jammy.list's active line to: >>> deb [trusted=yes] https://ppa.launchpadcontent.net/ubuntu-uefi-team/build/ubuntu/ noble main >>> Update the apt cache Install grub-efi-amd64 & grub-efi-amd64-signed from the ppa. Reconfigure Grub2 and update the initramfs images. Change the sources list back to the original jammy sources.list There were still existing snapshots there. Exit the chroot. Umount the mounts. Export the pools. Reboot. Booted fine. Fixed. Successful. Booting from Grub2 2.12. Writing up the work-around to fix it. I can post it on my ZFS -Fixes/Work-Arounds GitHub Repo. ...Or I can post it here. Maybe here is best. That way it is a known work-around for broken affected systems, until we can figure out the next step. The next step would be, how do we get Grub2 2.12 into Jammy through the updates channel? I would say it first needs to go to jammy proposed, then tested that it works through an update process. Then respin the installer ISO or include it in the next point release.. Since there is a fix, we don't need to create new victims. Just thinking out loud. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Since it is also built for Mantic, I would expect it works for Mantic Also. (Will confirm later.) I spun up a Jammy ZFS image. Changed the sources list to Noble. Added the PPA. Installed packages 'grub2 & shim'... Let it pull in the depends it needed. Change the sources.list back to jammy. Did some snapshots of bpool. Reconfigured grub, as it would do in an update... It said that was successful, so at that point was hopeful. Had fingers crossed. Rebooted, failed. Booted straight to BIOS. Shutdown > Cold boot > Failed. Booted straight to BIOS. So Grub2 2.12 works for the problems with Mantic and Noble, but not as a fix to Jammy 22.04. That sort of goes back to those last 4 patches (Grub2 related to ZFS) working to fix this problem for Noble & Mantic, but (somehow) need to be backported to fix Jammy. Dang. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Forgot to mention... Those "@feature" changes, that are suspected as being the problems when enabled... unfortunately cannot be done on an already created bpool. Those can only be set at pool "creation time". So I'm working on a script to recreate bpool which those specific option settings from the existing bpool, offline from an installer LiveUSB, environment. If I try it from online, it will not export the bpool. It just says "busy". Using an additional USB flash drive to temporarily hold the backup from bpool to destroy and recreate the bpool. That is the path I'm investigating and testing currently. That currently is, in the absence of a Grub2 2.12 that works with those conditions. If the new Grub2 2.12 does work with the older option setting, then a lot of thigs will be resolved, and a work-around will not be needed to fix existing installs nor new options set in ubuntu-desktop-installer. I installed just Grub 2.12~rc1 to 22.04.3 with the associated long line of depends. It wasn't pretty. And it did not correct the problem. That was not an answer to recommend. But at this point in time, because of Grub 2.12 not building and is vaporware. We don't have enough here to test, and make informed decisions. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
I'm working on trying various differing work-arounds with what is there natively. I tried building the newest git on Grub2 2.12. Fails building at a point which is says way fixed for the error i am getting, but still fails on the make at the same point. (asorti ot defined) I'm also working on another theory, recreating bpool with differing options, on the theory that on the creation of bpool, that some on the zpool options are causing Grub2 to fail with those added challenges. I'll keep you up-to date how those go. Trying to balance my time between "real life", helping the upstream Intel Graphics Support Engineers with drivers issues with Ubuntu, and helping Users with other issues. ...All while trying to find underlying information answers for this issue. What get's me, it that "feature" or "ability" that this is failing on, being able to snapshot bpool, because that is the failure point we need to protect from, was covered by Zsys, and why Canonical came up with that in the first place. It worked in 20.04 LTS... There was not a problem there, with that installed. We were able to do that in that release. Marketing-wise, it put Ubuntu ahead of things with that "need" covered well. Zsys was removed from being a default install (no mention why), but I still see commits to it. The need to make snapshots of the boot related files is still there. I wish I knew more on the why Zsys feel from favor. I thought basically,besides some minor changes, it was a great idea to do what it was intended to do. Some users, have gone around this problem by using ZFS Boot Menu (ZBM). But that is not a solution, Rather it removes the conditions, by what they have to do in the restructure to make it work. For it, bpool cannot exist. There cannot be a separate /boot. /boot has to be inside the root pool, and not inside it's own ZFS dataset... If this restructure is done this way, then those conditions do not exist. That is why is works. No that ZBM gets around the problem itself. If you crate a dataset for /boot itself, to make snapshots of boot related files, then ZBM does not work, even before the snapshots are made. It simply cannot find the boot related files, that way. (At all.) So to do a snapshot of boot related files, after that restructure, you end up having to snapshot the whole root pool, No, we need to find a way to get Grub2 and ZFS to play together nicely, and be stable. -- 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/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Also affect Mantic... ** Also 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 zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series
Ubfan1 and I have talking about this out on the Forum: Were we have to help other Users with this. RE: https://ubuntuforums.org/showthread.php?t=2494834 I think his idea on something is genius: That if the compiler version is brought in by the kernel on kernel updates as a dependency, so that the compiler is of the same version as the Kernel was compiled with... Noting that it doesn't not have to replace the old compiler, can be additional, along side it, then this solves this problem. He just tested this on some fresh 22.04.3 installs and it works. Sorry, It's hard to grasp that the answer is "Not going to fix", ...when there is a drastic problem that is being caused by the current update path, that is causing Users to have non-working installations. We are just here to report it and to help in any way to resolve it. If this is not the accepted solution, then lets work together to find one that is. -- 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/2051457 Title: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series Status in dkms package in Ubuntu: New Status in gcc-defaults package in Ubuntu: Won't Fix Status in linux package in Ubuntu: New Bug description: Since Jammy went to the 6.5.0 kernel series, that kernel series was compiled with gcc-12. The previous 6.2.0 series kernels were compiled with gcc-11. The current version of gcc in jammy is 11.4. Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc fail to build the modules, because of a gcc compiler version mismatch between what the current running kernel was built by, and the module being built. I recognized this while helping Users with NVidia driver compile errors on the forum, and came up with this work-around for them: https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164 Summary: Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler. Since then, this work-around has helped to resolve problems with running the 6.5.0 series kernels and building modules for other applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for use with the 6.5.0 series. I have run this for over a month as my default with no ill affects. I have continued to recommend this work-around to many user to solve their problems... *** I think it is time to look at pushing through gcc-12 as the default compiler for 22.04.3 through the normal updates channel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gcc 4:11.2.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Sun Jan 28 08:23:37 2024 InstallationDate: Installed on 2022-09-19 (496 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2051457 Title: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series Status in dkms package in Ubuntu: New Status in gcc-defaults package in Ubuntu: Won't Fix Status in linux package in Ubuntu: New Bug description: Since Jammy went to the 6.5.0 kernel series, that kernel series was compiled with gcc-12. The previous 6.2.0 series kernels were compiled with gcc-11. The current version of gcc in jammy is 11.4. Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc fail to build the modules, because of a gcc compiler version mismatch between what the current running kernel was built by, and the module being built. I recognized this while helping Users with NVidia driver compile errors on the forum, and came up with this work-around for them: https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164 Summary: Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler. Since then, this work-around has helped to resolve problems with running the 6.5.0 series kernels and building modules for other applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for use with the 6.5.0 series. I have run this for over a month as my default with no ill affects. I have continued to recommend this work-around to many user to solve their problems... *** I think it is time to look at pushing through gcc-12 as the default compiler for 22.04.3 through the normal updates channel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gcc 4:11.2.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Sun Jan 28 08:23:37 2024 InstallationDate: Installed on 2022-09-19 (496 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series
** Also affects: dkms (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2051457 Title: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series Status in dkms package in Ubuntu: New Status in gcc-defaults package in Ubuntu: Won't Fix Bug description: Since Jammy went to the 6.5.0 kernel series, that kernel series was compiled with gcc-12. The previous 6.2.0 series kernels were compiled with gcc-11. The current version of gcc in jammy is 11.4. Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc fail to build the modules, because of a gcc compiler version mismatch between what the current running kernel was built by, and the module being built. I recognized this while helping Users with NVidia driver compile errors on the forum, and came up with this work-around for them: https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164 Summary: Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler. Since then, this work-around has helped to resolve problems with running the 6.5.0 series kernels and building modules for other applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for use with the 6.5.0 series. I have run this for over a month as my default with no ill affects. I have continued to recommend this work-around to many user to solve their problems... *** I think it is time to look at pushing through gcc-12 as the default compiler for 22.04.3 through the normal updates channel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gcc 4:11.2.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Sun Jan 28 08:23:37 2024 InstallationDate: Installed on 2022-09-19 (496 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2051457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051601] [NEW] package nvidia-firmware-535-535.154.05 535.154.05-0ubuntu0.23.10.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: Fresh install...Not doing anything other than installing brave and this error kicked off ProblemType: Package DistroRelease: Ubuntu 23.10 Package: nvidia-firmware-535-535.154.05 535.154.05-0ubuntu0.23.10.1 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-compute-535_535.113.01-0ubuntu3_i386.deb ./pool/main/l/linux-firmware/linux-firmware_20230919.git3672ccab-0ubuntu2.1_amd64.deb CasperMD5CheckResult: fail Date: Mon Jan 29 23:28:48 2024 Dependencies: ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2024-01-29 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-firmware-535-535.154.05 535.154.05-0ubuntu0.23.10.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2051601 Title: package nvidia-firmware-535-535.154.05 535.154.05-0ubuntu0.23.10.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: Fresh install...Not doing anything other than installing brave and this error kicked off ProblemType: Package DistroRelease: Ubuntu 23.10 Package: nvidia-firmware-535-535.154.05 535.154.05-0ubuntu0.23.10.1 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-compute-535_535.113.01-0ubuntu3_i386.deb ./pool/main/l/linux-firmware/linux-firmware_20230919.git3672ccab-0ubuntu2.1_amd64.deb CasperMD5CheckResult: fail Date: Mon Jan 29 23:28:48 2024 Dependencies: ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2024-01-29 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-firmware-535-535.154.05 535.154.05-0ubuntu0.23.10.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2051601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038777] Re: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
I have a user that is affected by this bug. I am asking him to post here
with his info. I ask that you reopen this... For him = His is a VM in
Hyper-V.
RE: https://ubuntuforums.org/showthread.php?t=2494675
>From what I can see, there was a Kernel Bug that was patched for this
error upstream: https://lore.kernel.org/lkml/1691401853-26974-1-git-
send-email-ssen...@linux.microsoft.com/T/
I'm wondering if that patch applied to kernel 6.5.0-14? (Ubuntu 22.04.3)
If so or not, he is still getting this error. Maybe we could get this
kick-started back to life, to get this investigated and resolved(?)
--
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/2038777
Title:
UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
Status in linux package in Ubuntu:
Expired
Bug description:
HiperV VM network problems
[ 19.259297]
[ 19.259536] UBSAN: array-index-out-of-bounds in
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
[ 19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
[ 19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted
6.5.0-7-generic #7-Ubuntu
[ 19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
[ 19.259899] Call Trace:
[ 19.259901]
[ 19.259902] dump_stack_lvl+0x48/0x70
[ 19.259908] dump_stack+0x10/0x20
[ 19.259909] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 19.259912] netvsc_receive+0x437/0x490 [hv_netvsc]
[ 19.259917] netvsc_poll+0x176/0x4b0 [hv_netvsc]
[ 19.259921] __napi_poll+0x30/0x1f0
[ 19.259924] net_rx_action+0x181/0x2e0
[ 19.259925] __do_softirq+0xd6/0x346
[ 19.259927] ? _raw_spin_unlock+0xe/0x40
[ 19.259929] __irq_exit_rcu+0x75/0xa0
[ 19.259932] irq_exit_rcu+0xe/0x20
[ 19.259933] sysvec_hyperv_callback+0x92/0xd0
[ 19.259935]
[ 19.259935]
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.8
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CrashDB: ubuntu
Date: Sun Oct 8 23:09:45 2023
InstallationDate: Installed on 2021-03-07 (945 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64
(20210201.2)
PackageArchitecture: all
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
XDG_RUNTIME_DIR=
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
VarLogDistupgradeLspcitxt:
VarLogDistupgradeXorgFixuplog:
INFO:root:/usr/bin/do-release-upgrade running
INFO:root:No xorg.conf, exiting
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 oct 9 20:46 seq
crw-rw 1 root audio 116, 33 oct 9 20:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-03-07 (948 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64
(20210201.2)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lspci-vt:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
XDG_RUNTIME_DIR=
ProcFB: 0 hyperv_drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags:
[Kernel-packages] [Bug 2050032] Re: mpt3sas causes kernel stack trace
full dmesg output ** Attachment added: "output of dmesg" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050032/+attachment/5741313/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2050032 Title: mpt3sas causes kernel stack trace Status in linux-hwe-6.5 package in Ubuntu: New Bug description: [ 22.989826] [ 22.989831] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [ 22.989838] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [ 22.989843] CPU: 23 PID: 0 Comm: swapper/23 Not tainted 6.5.0-14-generic #14~22.04.1-Ubuntu [ 22.989850] Hardware name: Supermicro H8DG6/H8DGi/H8DG6/H8DGi, BIOS 2.0b 03/01/2012 [ 22.989854] Call Trace: [ 22.989858] [ 22.989862] dump_stack_lvl+0x48/0x70 [ 22.989877] dump_stack+0x10/0x20 [ 22.989883] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 22.989895] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [ 22.989962] mpt3sas_scsih_event_callback+0x21f/0x630 [mpt3sas] [ 22.990022] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [ 22.990078] _base_process_reply_queue+0x3a0/0x720 [mpt3sas] [ 22.990133] _base_interrupt+0x4e/0x70 [mpt3sas] [ 22.990188] __handle_irq_event_percpu+0x4f/0x1c0 [ 22.990197] handle_irq_event+0x39/0x80 [ 22.990202] handle_edge_irq+0x8c/0x250 [ 22.990208] __common_interrupt+0x56/0x110 [ 22.990217] common_interrupt+0x9f/0xb0 [ 22.990224] [ 22.990226] [ 22.990228] asm_common_interrupt+0x27/0x40 [ 22.990239] RIP: 0010:cpuidle_idle_call+0xa2/0x190 [ 22.990248] Code: 00 4c 89 e2 4c 89 ee 48 89 df e8 c9 98 c1 00 4c 89 ee 48 89 df 89 c2 e8 9c a7 ff ff 65 48 8b 04 25 80 28 03 00 f0 80 48 02 20 <9c> 58 0f 1f 40 00 f6 c4 02 0f 84 8b 00 00 00 48 8b 45 d8 65 48 2b [ 22.990253] RSP: 0018:b627443a7eb0 EFLAGS: 0202 [ 22.990259] RAX: 9edde8178000 RBX: a58e52e0 RCX: [ 22.990263] RDX: RSI: RDI: [ 22.990266] RBP: b627443a7ee0 R08: R09: [ 22.990269] R10: R11: R12: 0001 [ 22.990272] R13: 9ed9ea75cc00 R14: R15: [ 22.990279] do_idle+0x82/0xf0 [ 22.990285] cpu_startup_entry+0x1d/0x20 [ 22.990290] start_secondary+0x129/0x160 [ 22.990300] secondary_startup_64_no_verify+0x17e/0x18b [ 22.990311] [ 22.99031 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2050032] [NEW] mpt3sas causes kernel stack trace
Public bug reported: [ 22.989826] [ 22.989831] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [ 22.989838] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [ 22.989843] CPU: 23 PID: 0 Comm: swapper/23 Not tainted 6.5.0-14-generic #14~22.04.1-Ubuntu [ 22.989850] Hardware name: Supermicro H8DG6/H8DGi/H8DG6/H8DGi, BIOS 2.0b 03/01/2012 [ 22.989854] Call Trace: [ 22.989858] [ 22.989862] dump_stack_lvl+0x48/0x70 [ 22.989877] dump_stack+0x10/0x20 [ 22.989883] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 22.989895] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [ 22.989962] mpt3sas_scsih_event_callback+0x21f/0x630 [mpt3sas] [ 22.990022] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [ 22.990078] _base_process_reply_queue+0x3a0/0x720 [mpt3sas] [ 22.990133] _base_interrupt+0x4e/0x70 [mpt3sas] [ 22.990188] __handle_irq_event_percpu+0x4f/0x1c0 [ 22.990197] handle_irq_event+0x39/0x80 [ 22.990202] handle_edge_irq+0x8c/0x250 [ 22.990208] __common_interrupt+0x56/0x110 [ 22.990217] common_interrupt+0x9f/0xb0 [ 22.990224] [ 22.990226] [ 22.990228] asm_common_interrupt+0x27/0x40 [ 22.990239] RIP: 0010:cpuidle_idle_call+0xa2/0x190 [ 22.990248] Code: 00 4c 89 e2 4c 89 ee 48 89 df e8 c9 98 c1 00 4c 89 ee 48 89 df 89 c2 e8 9c a7 ff ff 65 48 8b 04 25 80 28 03 00 f0 80 48 02 20 <9c> 58 0f 1f 40 00 f6 c4 02 0f 84 8b 00 00 00 48 8b 45 d8 65 48 2b [ 22.990253] RSP: 0018:b627443a7eb0 EFLAGS: 0202 [ 22.990259] RAX: 9edde8178000 RBX: a58e52e0 RCX: [ 22.990263] RDX: RSI: RDI: [ 22.990266] RBP: b627443a7ee0 R08: R09: [ 22.990269] R10: R11: R12: 0001 [ 22.990272] R13: 9ed9ea75cc00 R14: R15: [ 22.990279] do_idle+0x82/0xf0 [ 22.990285] cpu_startup_entry+0x1d/0x20 [ 22.990290] start_secondary+0x129/0x160 [ 22.990300] secondary_startup_64_no_verify+0x17e/0x18b [ 22.990311] [ 22.99031 ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apport-bug file for system with problem" https://bugs.launchpad.net/bugs/2050032/+attachment/5741312/+files/apport.linux-image-6.5.0-14-generic.xafv6z8g.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2050032 Title: mpt3sas causes kernel stack trace Status in linux-hwe-6.5 package in Ubuntu: New Bug description: [ 22.989826] [ 22.989831] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [ 22.989838] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [ 22.989843] CPU: 23 PID: 0 Comm: swapper/23 Not tainted 6.5.0-14-generic #14~22.04.1-Ubuntu [ 22.989850] Hardware name: Supermicro H8DG6/H8DGi/H8DG6/H8DGi, BIOS 2.0b 03/01/2012 [ 22.989854] Call Trace: [ 22.989858] [ 22.989862] dump_stack_lvl+0x48/0x70 [ 22.989877] dump_stack+0x10/0x20 [ 22.989883] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 22.989895] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [ 22.989962] mpt3sas_scsih_event_callback+0x21f/0x630 [mpt3sas] [ 22.990022] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [ 22.990078] _base_process_reply_queue+0x3a0/0x720 [mpt3sas] [ 22.990133] _base_interrupt+0x4e/0x70 [mpt3sas] [ 22.990188] __handle_irq_event_percpu+0x4f/0x1c0 [ 22.990197] handle_irq_event+0x39/0x80 [ 22.990202] handle_edge_irq+0x8c/0x250 [ 22.990208] __common_interrupt+0x56/0x110 [ 22.990217] common_interrupt+0x9f/0xb0 [ 22.990224] [ 22.990226] [ 22.990228] asm_common_interrupt+0x27/0x40 [ 22.990239] RIP: 0010:cpuidle_idle_call+0xa2/0x190 [ 22.990248] Code: 00 4c 89 e2 4c 89 ee 48 89 df e8 c9 98 c1 00 4c 89 ee 48 89 df 89 c2 e8 9c a7 ff ff 65 48 8b 04 25 80 28 03 00 f0 80 48 02 20 <9c> 58 0f 1f 40 00 f6 c4 02 0f 84 8b 00 00 00 48 8b 45 d8 65 48 2b [ 22.990253] RSP: 0018:b627443a7eb0 EFLAGS: 0202 [ 22.990259] RAX: 9edde8178000 RBX: a58e52e0 RCX: [ 22.990263] RDX: RSI: RDI: [ 22.990266] RBP: b627443a7ee0 R08: R09: [ 22.990269] R10: R11: R12: 0001 [ 22.990272] R13: 9ed9ea75cc00 R14: R15: [ 22.990279]
[Kernel-packages] [Bug 2049248] Re: Kernel 6.5 breaks display brightness controls and sets it to 100% all the time
I believe, as pointed out in https://bugs.launchpad.net/bugs/2032174 , it has to do with kernel 6.5, source package 'linux'. & source package 'linux-oem-6.5' ... This seems similar, yet a different problem. It was there for the 6.2.0 series of kernels, but disappeared last week when the HWE stack went to 6.5.0 series kernels. I have similar hardware than the reporter. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049248 Title: Kernel 6.5 breaks display brightness controls and sets it to 100% all the time Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Since kernel 6.5, monitor brightness is set to 100%, and cannot be changed: The brightness controls have disappeared from Settings, and brightness doesn't respond to the keypad controls. See the attached screenshot, showing the difference between the settings in kernels 6.2 and 6.5. This applies to Ubuntu 22.04 and 23.10, whether using Wayland or X.Org. It's possible (when using X.Org) to adjust the brightness with… $ xrandr --output [monitor] --brightness [brightness] e.g. on my machine… $ xrandr --output eDP-1 --brightness 0.5 … but, unfortunately, it doesn't last long — anywhere between a less than a second later and about a minute later, the screen reverts to 100% brightness. As a workaround, I am running the following command in the background… $ while true; do xrandr --output eDP-1 --brightness 0.5; sleep 1s; done … which results in the screen at the correct brightness, but frequently flashing! Tested on: • Ubuntu 22.04 — Kernel 6.2.0-39 and prior works correctly — Kernel 6.5.0-14 has the problem • Ubuntu 23.10 — Kernel 6.5.0-9 has the problem $ sudo lshw -numeric -C display *-display description: VGA compatible controller product: CometLake-S GT2 [UHD Graphics 630] [8086:9BC5] vendor: Intel Corporation [8086] physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 05 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 resolution=1920,1080 resources: irq:145 memory:c100-c1ff memory:d000-dfff ioport:3000(size=64) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 13 07:19:58 2024 InstallationDate: Installed on 2022-08-28 (502 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031973] Re: package nvidia-dkms-520 520.61.05-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-520 package post-installation script subprocess returned error exit stat
This is kernel 6.2 + nvidia issue, I've fixed by this patch https://github.com/NVIDIA/open-gpu-kernel-modules/issues/429 ** Bug watch added: github.com/NVIDIA/open-gpu-kernel-modules/issues #429 https://github.com/NVIDIA/open-gpu-kernel-modules/issues/429 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-520 in Ubuntu. https://bugs.launchpad.net/bugs/2031973 Title: package nvidia-dkms-520 520.61.05-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-520 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-520 package in Ubuntu: Confirmed Bug description: I was trying to install Cuda 11.8, which requires nvidia driver version 520. Installation failed, probably because of some recent incompatibility issue with this driver's version (520) and then I was removing what was installed of Cuda through `$sudo apt remove --purge '^cuda-.*' when this error arose. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-520 520.61.05-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Aug 19 14:07:01 2023 ErrorMessage: installed nvidia-dkms-520 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-01-12 (218 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-520 Title: package nvidia-dkms-520 520.61.05-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-520 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/2031973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032136] Re: System reboot to BIOS boot menu
Is same with kernel 6.2.0-37-generic. But, is resolved if I use boot parameter "reboot=acpi" in /etc/default/grub -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2032136 Title: System reboot to BIOS boot menu Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Ever since update of Linux kernel to 6.2.0-26, this laptop (Lenovo Thinkpad T520) on reboot, goes to a boot loop directly to the BIOS Boot menu. On from there, still stuck in that loop. It displays an error message just before the BIOS Boot menu, but flashes by too fast to actually make out what is there. If it shutdown, and cold boot, it boots normally to the Grub2 Boot menu. There is a problem somewhere. This machine is ZFS-On-Root. Another User says he is having this same problem, but on an LVM2 install. The common denominator seems to be the update to Linux kernel 6.2.0-26. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Aug 20 14:14:56 2023 InstallationDate: Installed on 2021-09-23 (696 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-17 (368 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2032136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
@jimmymmick -- From LTS to a dev interim version? Maybe if other things supported newer hardware, but I am on 13th Gen iCore and still doing fine on 22.04.3. The HWE stack is the Lunar kernels (6.2.0-x). But Lunar loses support soon any ways... In fact if you update to Mantic (23.10) right now, it will flat not work. I'm testing zfs-linux 2.2.2 right now, and got it pushed through to Noble Main. Mantic is affected to, if you created your modules from earlier. Rick S above, was Mantic and affected. zfsutils-linux 2.2.2 breaks zfs-dkms 2.2.2, so that is not going to work. (I know need to file separate bug on that.) I would recommend using my work-around from comment #24. I just got all machines out fro under zfs-dkms now. zfs-dkms is not longer needed by 97% of users now. If for some reason you do need an out-of-series Linux kernel, then rebuild the modules for that kernel... Those instructions are in comment #28. Exclude zfs-dkms from that. I have one machine here that I test new kernels on. -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To recreate: - Install Ubuntu 22.04.3. - Update to current. - Install package 'zfs-dkms' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
Wait... I seem to be confused by this: >>> mafoelffen@noble-d05:~$ apt-cache show zfsutils-linux | grep 'Package:\|Breaks:' Package: zfsutils-linux Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>> 2.2.2-0ubuntu1...), zfs-dkms (<< 2.2.2-0ubuntu1) >>> Does that mean, even though zfs-dkms is built from zfs-linux 2.2.2, that if installed it will break ZFS... and therefore no longer works? On Rick's 2.2.2 blew out access to all his pools. He had to revert to 2.2.1, and restore plus add zfs-dkms back in, just to stay running. My machine is still doing fine. Should we start a new bug report against zfs-dkms for Noble on the above? That just doesn't sound logical somehow. -- 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/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: In Progress Status in zfs-linux source package in Noble: Fix Committed Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Just passed on to me from FL140: https://github.com/openzfs/zfs/issues/15586#issuecomment-1836806381 Is an updated script to manually build and install the OpenZFS native deb packages, including 'zfs-dkms' 2.2.2. ** Bug watch added: github.com/openzfs/zfs/issues #15586 https://github.com/openzfs/zfs/issues/15586 -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To recreate: - Install Ubuntu 22.04.3. - Update to current. - Install package 'zfs-dkms' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
Rick and I have been testing the Proposed 2.2.2 packages in Noble since yesterday morning. Great so far. @fl140 -- Thanks you for the link. I'll pass that on. Waiting to see if anything of this helps with: zfs-dkms 2.1.5-1ubuntu6~22.04.2 https://bugs.launchpad.net/ubuntu/+source/zfs- linux/+bug/2044630... But I know that is (1) focal-lunar (some Mantic), and (2) most likely just a regression issue like the last update had with zfs-dkms 2.1.5-1ubuntu6~22.04.1 https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2030100. Where the make did not recognize that kernels after 5.19.0 are supported. It's not needed by most now, but some of us still need it for out of series kernel testing. -- 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/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: In Progress Status in zfs-linux source package in Noble: Fix Committed Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
@xnox -- Thank you!!! This is what I see in Noble right now: >>> mafoelffen@noble-d05:~$ apt list -a zfsutils-linux Listing... Done zfsutils-linux/noble-proposed 2.2.2-0ubuntu1 amd64 zfsutils-linux/noble,now 2.2.1-0ubuntu1 amd64 [installed] >>> So it 2.2.1 got pushed to Noble main, with 2.2.2 to Noble Proposed (so far)... Rick S and I can start testing/verifying that today from Noble Proposed. Any idea on when it might hit the Snap 'ubuntu-desktop-installer' beta channel, so we can start testing it in the Noble installer? -- 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/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: In Progress Status in zfs-linux source package in Noble: Fix Committed Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
From what I got after that... It errors in dpkg, so it leaves the old modules built for the kernels that it did upgrade to successfully (there). Mine error'ed out when it tried to upgrade from 6.2.0-36 to 6.2.0-37. If worried me also, BUT... It did reboot. Since linux-image-6.2.0-37-generic errored out during the install, it does not add it to the Grub2 grub.cfg menu, so on reboot, it booted into 6.2.0-36 as the running kernel, on the modules it built. Each time it tried to do anything (updates), it would install anything new manually, but not actually do any of the updates. It looked like they were updating, then hit that zfs-dkms error. From the output, it initially looked like it installed all the update except zfs-dkms, but that assumption was wrong. Next time I tried to update, it tried to update those same exact packages that were in that previous update (grouping), plsu anything newly added to those-- which tells me it did not upgrade any of them. This morning, I see that Mantic and Noble got updates for zfs-dkms... But I haven't heard yet about Lunar. I don't see anything in any of my Jammy machine's updates. The work-around I came up with... I haven't found an easier way. If you remove it before that update failure, then you do not need to reinstall linux-headers-XXX and update the instramfs files... Because it didn't hit the bug yet where it failed to build the modules. BUT... And this is a big "BUT", something with zfs-dkms is somewhat 'evil'. When you remove it, somehow it exports all the zpools besides rpool!!! *** It does not do that immediately. *** Somehow, between the shutdown and reboot it exports all the pools besides rpool. I don't know why, but it just does. (That is why I refered to zfs-dkms' as soemhow being 'evil'. It has deep roots.) While still booted, before that, everything is still mounted. You can export and import the pools. It does not matter. On the next boot, after removing package 'zfs-dkms', nothing is mounted except for rpool. That work-around has instructions on how to import/mount everything back up and how to get it booting again. *** Like I found out, package 'zfs-linux' is not needed anymore to build the zfs module during a kernel update. That was added by Canonical in- kernel. No one announced that change when that happened. We (Us Users) know that now. Only a few of us still need zfs-dkms for out-of-series kernels, and testing DEV and Proposed packages, where weird circumstances are presented. But we are doing things that are "not normal", for the sake of Ubuntu and it's users. -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To recreate: - Install Ubuntu 22.04.3. - Update to current. - Install package 'zfs-dkms' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
@seth-arnold -- Thank you for those links. Those explain a lot of what is currently happening, and the changes coming down. This was comforting from robn: "If you can't get an updated ZFS (2.2.2, 2.1.14, or a patch from your vendor) then 'dmu_offset_next_sync=0' is the next best thing." Anyone know how long it might be before it gets built by Launchpad? zfs- linux 2.2.2 was released last week. Noble was slated for 2.2.1. Now that looks like for 2.2.2. Waiting for it to hit so Rick S and I can start testing it for Noble... Now just sitting on my thumbs and chewing through my lip. In the meanwhile, thinking of moving Noble from my VM test-cases to physical on my main laptop (Jammy ZFS-On-Root), so I can test these on "Metal" with 2.2.2 when it comes down. And test the 2.1.14 on my other 4 machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
@toekneefan -- Our tests of 2.2.1 from Noble Proposed showed that it was actually "enabled" by default, instead of being disabled like they said they did in it's release notes... So the rpool installs as "active", and any other pools created with feature=default (or just omitted) are created as that being "enabled"... So assuming that was turned off, turned out to be wrong. The only way I got that feature to create new pools with feature@block_cloning=disabled, was to explicitly pass that in the creation statement. The Canonical 'ubuntu-desktop-installer' team needs to know they need to add option that to the ZFS scripted installer script... In my debug traces during the install, they are passing "features=default"... If that feature does need to be turned off. I guess that only really matters if these patches for the Bug works and prevents it when they hit us and are applied. That "is" why turning off that feature was done for the meantime. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
I wondered why my old bug report has not gotten any attention. Being a duplicate of this bug didn't help, but at least someone from the security team marked it as a duplicate of this bug. BUT... On Bug Reports filed against zfs-linux, there are 55 bugs, with not one single person assigned, that are either marked as new, or confirmed, just because there were multiple users affected... Has anyone else, besides me, wondered why they are not even getting triaged? We do our due diligence to report these issues. I do my research, testing try to find answers, and work-around's... That we "can" get past what is wrong. I keep trying to keep faith in this support system. We try to make a difference, and do things for the betterment of Ubuntu. It does not seem sometimes like we are being taken seriously, or being heard. What other choices do we have? Compile it ourselves or add it to our own PPA"s? For actively supported versions, this seems like it should just be dealt with right? Especially for LTS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
This is my merge fo a Bug Report marked as a duplicate of this one: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969 In the OpenZFS patch thread, they had said that feature@block_cloning, because of the underlying bug, OpenZFS had said they turned that feature off by default in 2.2.1. (They actually didn't.) 2.2.1 is in Noble Proposed. Rick S. and I have been testing it (in DEV Noble) ever since I reported my Bug Report which recently has been marked as a duplicate of this Bug... (Noted above) In my tests, in version 2.2.1, that package does not turn off that feature by default. Noble (with zfsutils 2.2.1) creates the rpool with feature@block_cloning=Active, as a default. I debugged the install activity for noble during the ZFS install, and it is passing features=defaults... That is not something that was injected i the code of ubuntu-desktop-installer, so it still set as a default. Just to test that, I confirmed it. If you create a new pool by defaults, that feature gets set to enabled, unless you explicitly give it: -o feature@block_cloning=disabled My previous proposal was for 2.2.1 to get pushed out of Noble Proposed to Noble Main. But that was before we found out that was was said about 2.2.1 was wrong. Now my proposal is to build 2.2.2, move it to Noble proposed, so Rick S. and I can test and verify it... The move it to Noble Main. Those go along with backporting the patch back through Focal. Yes that feature@block_cloning uncovered the Bug, and increases the likelihood that it occurs, but... The underlying bug in the code goes back to code from 2012. Focal is still in support. Ubuntu Pro ESM is another matter, which 14.04 is still in ESM, and still has 4 months left... But is also affected by this Bug/CVE. We had also started a thread on this in the Noble Dev section: https://ubuntuforums.org/showthread.php?t=2492927=14167819 OpenZFS did release zfs-linux 2.2.2 last week. But I do not see any zfs- linux builds yet of that there. Yes we know if only happens during a cp (does nto affect rsync), but the OpenZFs patches seem to work on the ZFS end of things... This summarizes what we had there in that bug report, into this one... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Here is the link: https://github.com/Mafoelffen1/OpenZFS-Ubuntu-Admin/blob/main/ZFS-DKMS-WORK-AROUND.md It is tested. It is somewhat daunting... But it works. -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To recreate: - Install Ubuntu 22.04.3. - Update to current. - Install package 'zfs-dkms' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
I've tested it and handed it off to Rick for him to look it over and test (second set of eyes)... -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To recreate: - Install Ubuntu 22.04.3. - Update to current. - Install package 'zfs-dkms' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
** Description changed: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic - configure: error: - *** None of the expected "iops->get_acl()" interfaces were detected. - *** This may be because your kernel version is newer than what is - *** supported, or you are using a patched custom kernel with - *** incompatible modifications. - *** - *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 - *** Compatible Kernels: 3.10 - 5.19 - + configure: error: + *** None of the expected "iops->get_acl()" interfaces were detected. + *** This may be because your kernel version is newer than what is + *** supported, or you are using a patched custom kernel with + *** incompatible modifications. + *** + *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 + *** Compatible Kernels: 3.10 - 5.19 + ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): - installed zfs-dkms package post-installation script subprocess returned error exit status 10 + installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) + + To recreate: + - Install Ubuntu 22.04.3. + - Update to current. + - Install package 'zfs-dkms' -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To recreate: - Install Ubuntu 22.04.3. - Update to current. - Install package 'zfs-dkms' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
<> Rick S and I have talked a lot today... trying to remember: I added a repo on my GitHub on: Open-ZFS-Admin > "How To Uninstall package 'zfs-dkms' And Survive" We had to remember: - Why we actually started using it. Ubuntu, in the past, did not rebuild the zfs module, so we needed zfs- dkms so that when kernels were updated, that the 'zfs' modules were built for the new kernel... - If it is actually needed anymore Not for normal users... I will explain that. I think sometime around 22.04.x, canonical started adding the zfs-modules in-kernel. Confirmed that, if you install Ubuntu 22.04.3 as ZFS-On_Root, and do updates, zfs- dkms is not an installed package, and the 'zfs' modules are built during a kernel update. So it is not actually needed any longer by normal users. - Why Rick S (1fallen) and I still need to use package 'zfs-dkms', if it is not required as a default package anymore... We do DEV testing and ZFS version (zfs-linux) testng/validations... We need it becaseu we often install and use kernels from the Ubuntu mainline repo. Which does not have the added Ubuntu mod's and additions. That, and (I hate to say this) sometimes Canonical forgets to add things, and has regression issues. This package has save our behinds sometimes. I am embarrassed at Launchpad's participation with this. i will take the baton and help them with that. When I get that done, and Rick and i get that tested, i will publish the link to that here. When I get those instructions -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
It blew 1fallen's machine out of the water. Before doing anything, backup your bpool and rpool via rsync so you have a fall back point. Start a thread on UbuntuForums > Installations and Updates. I will talk you through a work-around to uninstall zfs-dkms and everything else I did to get around it. It's too long a process for this bug report, There was lessons learned by both I and 1fallen, where both ours crashed and we had to recover from that. Like I said. Get good backups now, While it's still broken, but still bootable. -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
zfs-linux 2.2.2 released tonight... In the changelog: dnode_is_dirty: check dnode and its data for dirtiness #15571 #15526 Which is the above patch for CVE 2023-49298 -- 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/2044969 Title: Upstream bug: ZFS feature@block_cloning causes data corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: Noble DAILY ISO 2023.11.27 & Current Mantic Installers. some copied files are corrupted (chunks replaced by zeros) ISSUE #15526 RE:https://github.com/openzfs/zfs/issues/15526 zpool feature@block_cloning came out with version 2.2.0 of zfs-linux, this is not the root of that bug, but exacerbates the underlying bug. The bug was reported, and version 2.2.1 was released with that feature turned off by default, so that would be a problem out of the gate. There is a patch out which got approved, merged and built tonight that, after testing, seems to correct that: dnode_is_dirty: check dnode and its data for dirtiness #15571 https://github.com/openzfs/zfs/pull/15571 Unfortunately, Mantic was released with version 2.2.0. Current DEV Noble also has 2.2.0. This feature in the default ZFS install scripts for both Mantic and Noble, with the current default, In bpool, feature@block_cloning is disable, but for rpool, the same feature is enabled, so "at risk". This feature is set at pool creation time. You cannot set this feature to disable without destroying the pool and recreating it fresh. Have good backups, via rsync. cp is affected, but not rsync. Version 2.2.1 has this feature disabled by default. It was released Nov 21, 2023. I am proposing that the patched build from tonight get pushed through for Mantic when it hits from upstream... And possibly pushing 2.2.1 through for Noble, where we can thoroughly test it in this current DEV Cycle. Also, this was filed because of Security as it relates to data integrity concerns: CVE-2023-49298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: zfsutils-linux 2.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 27 19:58:32 2023 InstallationDate: Installed on 2023-11-23 (4 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
That blew out the ability to boot. Ended up having to remove zfs-dkms. Reinstalling kernel and boot. Back up. zfs-dkms is broken big time for 22.04. -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
I got tired of waiting for anyone to triage this... I removed package zfs-dkms so I could applied my updates... They upgraded successfully. Including building the modules for kernel 6.2.0-37-generic. Then installed package zfs-dkms, where it failed again on building the module for 6.2.0-37. -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
It is not just preventing upgrades, it is preventing the upgrade to Linux kernel 6.2.0-37-generic >>> mafoelffen@Mikes-ThinkPad-T520:~$ modinfo zfs | grep -e '^filename\|^version' filename: /lib/modules/6.2.0-36-generic/kernel/zfs/zfs.ko version:2.1.9-2ubuntu1.1 mafoelffen@Mikes-ThinkPad-T520:~$ uname -r 6.2.0-36-generic mafoelffen@Mikes-ThinkPad-T520:~$ ls /boot/ | grep -e 'initrd\.img-[5-6]\|vmlinuz-[5-6]' initrd.img-5.15.0-89-generic initrd.img-6.2.0-36-generic initrd.img-6.2.0-37-generic vmlinuz-5.15.0-89-generic vmlinuz-6.2.0-36-generic vmlinuz-6.2.0-37-generic >>> -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
To install 2.2.1, i had to enable proposed in sources, then explicitly install: >>> sudo apt install -y zfsutils-linux=2.2.1-0ubuntu1 libnvpair3linux=2.2.1-0ubuntu1 libuutil3linux=2.2.1-0ubuntu1 libzfs4linux=2.2.1-0ubuntu1 libzpool5linux=2.2.1-0ubuntu1 zfs-dkms=2.2.1-0ubuntu1 >>> To get all the dependencies. I did tha before the install of Noble, then again after the install to reinstall what it rsync'ed from the Snap image to /target, so they would be 2.2.1. But there is still something wrong with that. Debuggin whta is being passed... >>> # Autogenerated by Subiquity: 2023-11-29 04:40:40.713721 UTC install: error_tarfile: /var/log/installer/curtin-errors.tar ... storage: config: ... - vdevs: - partition-3 pool: rpool mountpoint: / pool_properties: ashift: 12 autotrim: 'on' version: null fs_properties: acltype: posixacl atime: null canmount: 'off' compression: lz4 devices: 'off' dnodesize: auto normalization: formD relatime: 'on' sync: standard xattr: sa default_features: true id: zpool-1 type: zpool - pool: zpool-1 volume: ROOT properties: canmount: 'off' mountpoint: none id: zfs-2 type: zfs ... >>> You can see that it says: "default_features: true" But the zpool property feature@block_cloning is still returning as "active" <-- Which is strange, because that should say either "enabled" or "disabled"... To confirm, with everything as 2.2.1, hwere OpenZFS siad that that feature is specifically 'disabled', I created another pool, and it was "enabled" by default. I had to destroy the zpool and explicitly tell it to be disabled in the creation statement. -- 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/2044969 Title: Upstream bug: ZFS feature@block_cloning causes data corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: Noble DAILY ISO 2023.11.27 & Current Mantic Installers. some copied files are corrupted (chunks replaced by zeros) ISSUE #15526 RE:https://github.com/openzfs/zfs/issues/15526 zpool feature@block_cloning came out with version 2.2.0 of zfs-linux, this is not the root of that bug, but exacerbates the underlying bug. The bug was reported, and version 2.2.1 was released with that feature turned off by default, so that would be a problem out of the gate. There is a patch out which got approved, merged and built tonight that, after testing, seems to correct that: dnode_is_dirty: check dnode and its data for dirtiness #15571 https://github.com/openzfs/zfs/pull/15571 Unfortunately, Mantic was released with version 2.2.0. Current DEV Noble also has 2.2.0. This feature in the default ZFS install scripts for both Mantic and Noble, with the current default, In bpool, feature@block_cloning is disable, but for rpool, the same feature is enabled, so "at risk". This feature is set at pool creation time. You cannot set this feature to disable without destroying the pool and recreating it fresh. Have good backups, via rsync. cp is affected, but not rsync. Version 2.2.1 has this feature disabled by default. It was released Nov 21, 2023. I am proposing that the patched build from tonight get pushed through for Mantic when it hits from upstream... And possibly pushing 2.2.1 through for Noble, where we can thoroughly test it in this current DEV Cycle. Also, this was filed because of Security as it relates to data integrity concerns: CVE-2023-49298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: zfsutils-linux 2.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 27 19:58:32 2023 InstallationDate: Installed on 2023-11-23 (4 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
** Information type changed from Private Security to Public Security ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-49298 -- 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/2044969 Title: Upstream bug: ZFS feature@block_cloning causes data corruption Status in zfs-linux package in Ubuntu: New Bug description: Noble DAILY ISO 2023.11.27 & Current Mantic Installers. some copied files are corrupted (chunks replaced by zeros) ISSUE #15526 RE:https://github.com/openzfs/zfs/issues/15526 zpool feature@block_cloning came out with version 2.2.0 of zfs-linux, this is not the root of that bug, but exacerbates the underlying bug. The bug was reported, and version 2.2.1 was released with that feature turned off by default, so that would be a problem out of the gate. There is a patch out which got approved, merged and built tonight that, after testing, seems to correct that: dnode_is_dirty: check dnode and its data for dirtiness #15571 https://github.com/openzfs/zfs/pull/15571 Unfortunately, Mantic was released with version 2.2.0. Current DEV Noble also has 2.2.0. This feature in the default ZFS install scripts for both Mantic and Noble, with the current default, In bpool, feature@block_cloning is disable, but for rpool, the same feature is enabled, so "at risk". This feature is set at pool creation time. You cannot set this feature to disable without destroying the pool and recreating it fresh. Have good backups, via rsync. cp is affected, but not rsync. Version 2.2.1 has this feature disabled by default. It was released Nov 21, 2023. I am proposing that the patched build from tonight get pushed through for Mantic when it hits from upstream... And possibly pushing 2.2.1 through for Noble, where we can thoroughly test it in this current DEV Cycle. Also, this was filed because of Security as it relates to data integrity concerns: CVE-2023-49298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: zfsutils-linux 2.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 27 19:58:32 2023 InstallationDate: Installed on 2023-11-23 (4 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Seems to also affect Mantic, if it was installed as jammy, the upgraded to Mantic. But doesn't seem to affect Mantic system if they were installed fresh as Mantic. All Tests, so far, show it does not affect Noble at all (either upgraded from Mantic or installed fresh). -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Posted a warning out on the Forum: https://ubuntuforums.org/showthread.php?t=2492886=14166863#post14166863 -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Attempt at remove and reinstall of package zfs-dkms failed (see attached) No, Crashed again on zks-dkms. Can't et past it. And only affects Jammy. ** Attachment added: "reinstall-output.txt" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723680/+files/reinstall-output.txt -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
No. Lunar upgraded fine to that package version with the same kernel. But: on this 22.04.3 machine now: >>> mafoelffen@Mikes-B460M:/data/ISO$ apt list zfs-dkms Listing... Done zfs-dkms/jammy-updates,jammy-updates,jammy-security,jammy-security,now 2.1.5-1ubuntu6~22.04.2 all [installed] N: There is 1 additional version. Please use the '-a' switch to see it mafoelffen@Mikes-B460M:/data/ISO$ sudo apt install --reinstall zfs-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 25 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. E: Internal Error, No file name for zfs-dkms:amd64 >>> Look at the error on the end... -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
This is not a problem for Noble, as it uses >>> fs-dkms/noble,noble 2.2.0-0ubuntu3 all >>> Not a problem for Mantic, as it uses: >>> zfs-dkms/mantic,mantic 2.2.0~rc3-0ubuntu4 all >>> BUT-- In today's updates for Lunar: >>> libzfs4linux/lunar-updates,lunar-security 2.1.9-2ubuntu1.2 amd64 [upgradable from: 2.1.9-2ubuntu1.1] zfs-dkms/lunar-updates,lunar-updates,lunar-security,lunar-security 2.1.9-2ubuntu1.2 all [upgradable from: 2.1.9-2ubuntu1.1] zfs-initramfs/lunar-updates,lunar-security 2.1.9-2ubuntu1.2 amd64 [upgradable from: 2.1.9-2ubuntu1.1] zfs-zed/lunar-updates,lunar-security 2.1.9-2ubuntu1.2 amd64 [upgradable from: 2.1.9-2ubuntu1.1] zfsutils-linux/lunar-updates,lunar-security 2.1.9-2ubuntu1.2 amd64 [upgradable from: 2.1.9-2ubuntu1.1] >>> I will clone that test machine and see if it will crash on Lunar with that update... BRB. -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
I remember this error on zfs-dkms when the kernel ranges went from 5.19 to 6.2.0-X... With package zfs-dkms 2.1.5-1ubuntu6~22.04.1. RE: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2030100 That was fixed a few updates after that, but now we are back to this: >>> *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 >>> Which makes me think that the patch that was applied for that last package, was not applied to this new one. *** Should I post a warning on the Forum in Section "Installations & Updates", for ZFS users not to apply updates until this is resolved? I've already sent a few PM's out to members I know this will affect... -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
** Attachment added: "zfs-make.log" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723611/+files/zfs-make.log -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
There weer no other make logs for any other kernels present(???) >>> mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ ls /var/lib/dkms/zfs/2.1.5/ 5.15.0-89-generic source >>> -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
** Attachment added: "zfs-dkms-2.1.5_5.15.0-89-generic_make.log" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723604/+files/zfs-dkms-2.1.5_5.15.0-89-generic_make.log -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
** Attachment added: "zfs-dkms.0.crash" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723603/+files/zfs-dkms.0.crash -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] [NEW] zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Public bug reported: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028186] Re: zfs with encryption: sluggish resume from suspend, intermittent freezes
FWIW, I switched back to ext4 and am no longer experiencing the same issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2028186 Title: zfs with encryption: sluggish resume from suspend, intermittent freezes Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: I had been using Jammy on a Thinkpad T470 for months without problems. I decided to try a fresh Ubuntu Desktop install using ZFS, using the install-time option for full-disk encryption. After using the fresh install for a little while, I noticed that the system was "more sluggish" in the ZFS configuration (which was disappointing, but tolerable). The "sluggishness" is especially noticeable when resuming from suspend. Typically, I'll look at the system clock and notice that it does not change for ~tens of seconds. On some occasions, it will freeze completely (even after waiting many minutes) and require a reboot. Given that this the only difference between a "perfectly working system" and "problematic system" was the filesystem change, I strongly suspect ZFS as the cause (and/or perhaps enabling the full-disk encryption option for it during the install). Any advice on how to further triage this and narrow down the issue would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 19 10:03:03 2023 InstallationDate: Installed on 2023-03-22 (119 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2028186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032136] Re: System reboot to BIOS boot menu
This is still affected with Linux kernel 6.2.0-33-genric on this laptop. Nothing has changed. It still will not do a "reboot" without ending up at a BIOS Boot menu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2032136 Title: System reboot to BIOS boot menu Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Ever since update of Linux kernel to 6.2.0-26, this laptop (Lenovo Thinkpad T520) on reboot, goes to a boot loop directly to the BIOS Boot menu. On from there, still stuck in that loop. It displays an error message just before the BIOS Boot menu, but flashes by too fast to actually make out what is there. If it shutdown, and cold boot, it boots normally to the Grub2 Boot menu. There is a problem somewhere. This machine is ZFS-On-Root. Another User says he is having this same problem, but on an LVM2 install. The common denominator seems to be the update to Linux kernel 6.2.0-26. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Aug 20 14:14:56 2023 InstallationDate: Installed on 2021-09-23 (696 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-17 (368 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2032136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed
Stuck on Recovering Journal (clean) after upgrading to Ubuntu 22.04.4 LTS I have a NVIDIA Corporation GA104GL [RTX A4000] (rev a1) Kernal: 6.2.0-35-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038745 Title: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Lunar: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: [Impact] NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to latest Ubuntu 22.04.3 kernel and firmware Not repro with NV21 XL or W6800 [Fix] Cherry-pick the latest PMFW https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin [Other Info] The IMU FW included in Linux firmware package needs to be paired with the latest PMFW smu_13_0_0.bin for Navi31 Jammy firmware updates only include latest IMU firmware. https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux- firmware 20220329.git681281e4-0ubuntu3.19 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin (Missing) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039491] [NEW] zfs 2.2.0 released
Public bug reported: Now that zfs 2.2.0 has been release can you move to a released version of zfs instead of a release candidate. ** 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 zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2039491 Title: zfs 2.2.0 released Status in zfs-linux package in Ubuntu: New Bug description: Now that zfs 2.2.0 has been release can you move to a released version of zfs instead of a release candidate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2039491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973827] Re: Laptop freezes when recovering from suspend / sleep mode
ack; filed bug 2028186. -- 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/1973827 Title: Laptop freezes when recovering from suspend / sleep mode Status in gnome-shell package in Ubuntu: Expired Status in zfs-linux package in Ubuntu: New Bug description: When I lock the laptop and unlock it - I have no issues. If I allow it to lock and then sleep, or close the lid and suspend - when I open it again, I get the login prompt but cannot use mouse / keyboard. The only solution I have is to press and hold the power button and force shutdown and then boot back up Description: Ubuntu 22.04 LTS Release: 22.04 No particular package being used. I would expect the system to recover from suspend / sleep and allow me to enter password. The laptop froze completely. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue May 17 21:45:17 2022 InstallationDate: Installed on 2022-04-22 (25 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028186] [NEW] zfs with encryption: sluggish resume from suspend, intermittent freezes
Public bug reported: I had been using Jammy on a Thinkpad T470 for months without problems. I decided to try a fresh Ubuntu Desktop install using ZFS, using the install-time option for full-disk encryption. After using the fresh install for a little while, I noticed that the system was "more sluggish" in the ZFS configuration (which was disappointing, but tolerable). The "sluggishness" is especially noticeable when resuming from suspend. Typically, I'll look at the system clock and notice that it does not change for ~tens of seconds. On some occasions, it will freeze completely (even after waiting many minutes) and require a reboot. Given that this the only difference between a "perfectly working system" and "problematic system" was the filesystem change, I strongly suspect ZFS as the cause (and/or perhaps enabling the full-disk encryption option for it during the install). Any advice on how to further triage this and narrow down the issue would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 19 10:03:03 2023 InstallationDate: Installed on 2023-03-22 (119 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: I had been using Jammy on a Thinkpad T470 for months without problems. I decided to try a fresh Ubuntu Desktop install using ZFS, using the install-time option for full-disk encryption. After using the fresh install for a little while, I noticed that the system was "more sluggish" in the ZFS configuration (which was disappointing, but tolerable). The "sluggishness" is especially noticeable when resuming from suspend. Typically, I'll look at the system clock and notice that it does not change for ~tens of seconds. On some occasions, it will freeze completely (even after waiting many minutes) and require a reboot. Given that this the only difference between a "perfectly working system" - and "problematic system" was enabling the ZFS option, I strongly suspect + and "problematic system" was the filesystem change, I strongly suspect ZFS as the cause (and/or perhaps enabling the full-disk encryption option for it during the install). Any advice on how to further triage this and narrow down the issue would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 19 10:03:03 2023 InstallationDate: Installed on 2023-03-22 (119 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2028186 Title: zfs with encryption: sluggish resume from suspend, intermittent freezes Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: I had been using Jammy on a Thinkpad T470 for months without problems. I decided to try a fresh Ubuntu Desktop install using ZFS, using the install-time option for full-disk encryption. After using the fresh install for a little while, I noticed that the system was "more sluggish" in the ZFS configuration (which was disappointing, but tolerable). The "sluggishness" is especially noticeable when resuming from suspend. Typically, I'll look at the system clock and notice that it does not change for ~tens of seconds. On some occasions, it will freeze completely (even after waiting many minutes) and require a reboot. Given that this the only difference between a "perfectly working system" and "problematic system"
[Kernel-packages] [Bug 1973827] Re: Laptop freezes when recovering from suspend / sleep mode
I'm seeing a similar issue on a laptop which was working fine until I reinstalled Ubuntu Jammy with ZFS (with full-disk encryption enabled). Sometimes it freezes for several seconds, but sometimes I wait hours and it never recovers. I don't think this is a gnome-shell issue, but I'm unsure how to go about troubleshooting it. ** Also 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 zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1973827 Title: Laptop freezes when recovering from suspend / sleep mode Status in gnome-shell package in Ubuntu: Expired Status in zfs-linux package in Ubuntu: New Bug description: When I lock the laptop and unlock it - I have no issues. If I allow it to lock and then sleep, or close the lid and suspend - when I open it again, I get the login prompt but cannot use mouse / keyboard. The only solution I have is to press and hold the power button and force shutdown and then boot back up Description: Ubuntu 22.04 LTS Release: 22.04 No particular package being used. I would expect the system to recover from suspend / sleep and allow me to enter password. The laptop froze completely. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue May 17 21:45:17 2022 InstallationDate: Installed on 2022-04-22 (25 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017364] Re: laptop boots but external display not activated
Workaround: boot with laptop open and close once the desktop appears. The same problems appears when the laptop awakens from sleep mode. The workaround for this is to CTL-ALT-F2 followed by CTL-ALT-F1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2017364 Title: laptop boots but external display not activated Status in linux-signed package in Ubuntu: New Bug description: upgrade from 22.10 to 23.04 went smoothly on my Dell laptop. I have an external monitor that on a dock. It works fine in 22.10 but won't activate properly with 23.04. If I boot with laptop lid closed I get the grub screen and then, once it boots, neither screen works. Reverting the kernel back to 5.19.0-40-generic does work as expected, but the new kernel with 6.2.0-20-generic does not, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2017364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024113] Re: Linux 6.2.0-20 kernel update tries to install low latency and oracle versions
It is doing the same thing again (see original message) when trying to run the update to kernel 6.2.0-1005. -- 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/2024113 Title: Linux 6.2.0-20 kernel update tries to install low latency and oracle versions Status in linux package in Ubuntu: Confirmed Bug description: when I ran software updates to update my 23.04 Budgie system today to Linux 6.2.0-20-generic apt treis to install the low latency and Oracle versions of the kernel too, breaking my system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow
What's interesting is on a Dell Optiplex 3080 with a Realtek 8169 adapter I have similar symptoms (extremely slow downloads in the KB/s, and frequent packet drops seen in captures). I'm seeing this also on Dell Precision 3650's with Intel I219-LM (rev 11) adapters. The workaround above to disable auto power control resolves these symptoms on BOTH the Realtek 8169 and the Intel I219-LM adapters. Oddly enough, a Dell Precision 3630 with a slightly different variant of the Intel I219-LM (rev10) does not have the same issues. Not sure if any of this helps, but I was surprised to see it's not just Intel cards with these linux power control speed and packet loss symptoms... Mike -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Won't Fix Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e on TGP PCH encounters a network speed issue that rx speed is below 1MB/s [Fix] Intel provides 2 patches to fix this https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=263466 [Test] Verified by our Dell and Lenovo platforms and the bug reporter. [Where problems could occur] The fix only applies to e1000e with TGP PCH, and add a flag "E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and should not lead to other regressions. = We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017364] [NEW] laptop boots but external display not activated
Public bug reported: upgrade from 22.10 to 23.04 went smoothly on my Dell laptop. I have an external monitor that on a dock. It works fine in 22.10 but won't activate properly with 23.04. If I boot with laptop lid closed I get the grub screen and then, once it boots, neither screen works. Reverting the kernel back to 5.19.0-40-generic does work as expected, but the new kernel with 6.2.0-20-generic does not, ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2017364 Title: laptop boots but external display not activated Status in linux-signed package in Ubuntu: New Bug description: upgrade from 22.10 to 23.04 went smoothly on my Dell laptop. I have an external monitor that on a dock. It works fine in 22.10 but won't activate properly with 23.04. If I boot with laptop lid closed I get the grub screen and then, once it boots, neither screen works. Reverting the kernel back to 5.19.0-40-generic does work as expected, but the new kernel with 6.2.0-20-generic does not, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2017364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008823] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661371/+files/acpidump.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661370/+files/WifiSyslog.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio
[Kernel-packages] [Bug 2008823] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661369/+files/UdevDb.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661368/+files/ProcModules.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio
[Kernel-packages] [Bug 2008823] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661367/+files/ProcInterrupts.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name:
[Kernel-packages] [Bug 2008823] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661366/+files/ProcCpuinfoMinimal.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M.
[Kernel-packages] [Bug 2008823] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661365/+files/ProcCpuinfo.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio
[Kernel-packages] [Bug 2008823] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661364/+files/Lsusb-v.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661363/+files/Lspci-vt.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661362/+files/Lspci.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661361/+files/CurrentDmesg.txt -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name:
[Kernel-packages] [Bug 2008823] Re: /sys/kernel/boot_params/data leaks random data
apport information ** Tags added: apport-collected staging ** Description changed: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2019-10-17 (1265 days ago) + InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M + |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M + MachineType: retsamarret To be filled by O.E.M. + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro + ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-38-generic N/A + linux-backports-modules-5.19.0-38-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.12 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + StagingDrivers: atomisp_lm3554 atomisp_gmin_platform + Tags: jammy uec-images staging + Uname: Linux 5.19.0-38-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) + UserGroups: adm cdrom dip lxd plugdev sudo + _MarkForUpload: True + dmi.bios.date: 04/21/2017 + dmi.bios.release: 5.6 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 5.6.5 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: Aptio CRB + dmi.board.vendor: AMI Corporation + dmi.board.version: To be filled by O.E.M. + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias:
[Kernel-packages] [Bug 2014231] Re: gcc produces DWARF5, gdb requires DWARF4
Have moved status to 'Confirmed' without attaching kernel log files as I
believe these are not relevant.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
On Ubuntu 22.04.2 LTS using fully updated gcc and gdb, I find that by
default gcc produces DWARF5 debug files which gdb cannot read, with the
following error:
Dwarf Error: DW_FORM_line_strp used without required section
If I add the flags `-gdwarf-4 -gstrict-dwarf` to `gcc` then it produces
output which gdb can read.
I would have expected the created and required versions of DWARF to
- match between these two programs.
+ match between these two programs when everything is up-to-date, within
+ the same distro.
(I found the following two issues which appear to be people also
suffering from gcc newly producing DWARF5, in different contexts:
https://github.com/golang/vscode-go/issues/1914
https://github.com/haikuports/haikuports/issues/4987 ; as mentioned
however, the mismatch between what gcc produces and what gdb accepts
seems to be a specific problem, which I suppose may be likely to break
e.g. existing working debug instructions, etc.)
---
Package: gcc
Version: 4:11.2.0-1ubuntu1
$ gcc --version
gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Package: gdb
Version: 12.1-0ubuntu1~22.04
$ gdb --version
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
-
Using default gcc output (i.e. with no flags specifying DWARF version):
(gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000
add symbol table from file "{...}/shimx64.efi.debug" at
- .text_addr = 0x561b000
- .data_addr = 0x5681000
+ .text_addr = 0x561b000
+ .data_addr = 0x5681000
(y or n) y
Reading symbols from {...}/shimx64.efi.debug...
Dwarf Error: DW_FORM_line_strp used without required section
(No debugging symbols found in {...}/shimx64.efi.debug)
- (gdb)
-
+ (gdb)
After adding `-gdwarf-4 -gstrict-dwarf` to gcc compile flags:
(gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000
add symbol table from file "{...}/shimx64.efi.debug" at
- .text_addr = 0x561b000
- .data_addr = 0x5681000
+ .text_addr = 0x561b000
+ .data_addr = 0x5681000
(y or n) y
Reading symbols from {...}/shimx64.efi.debug...
(gdb)
--
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/2014231
Title:
gcc produces DWARF5, gdb requires DWARF4
Status in linux package in Ubuntu:
Confirmed
Bug description:
On Ubuntu 22.04.2 LTS using fully updated gcc and gdb, I find that by
default gcc produces DWARF5 debug files which gdb cannot read, with
the following error:
Dwarf Error: DW_FORM_line_strp used without required section
If I add the flags `-gdwarf-4 -gstrict-dwarf` to `gcc` then it
produces output which gdb can read.
I would have expected the created and required versions of DWARF to
match between these two programs when everything is up-to-date, within
the same distro.
(I found the following two issues which appear to be people also
suffering from gcc newly producing DWARF5, in different contexts:
https://github.com/golang/vscode-go/issues/1914
https://github.com/haikuports/haikuports/issues/4987 ; as mentioned
however, the mismatch between what gcc produces and what gdb accepts
seems to be a specific problem, which I suppose may be likely to break
e.g. existing working debug instructions, etc.)
---
Package: gcc
Version: 4:11.2.0-1ubuntu1
$ gcc --version
gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Package: gdb
Version: 12.1-0ubuntu1~22.04
$ gdb --version
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Using default gcc output (i.e. with no flags specifying DWARF
version):
(gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000
add symbol table from file "{...}/shimx64.efi.debug" at
.text_addr = 0x561b000
.data_addr = 0x5681000
(y or n) y
Reading symbols from {...}/shimx64.efi.debug...
Dwarf Error: DW_FORM_line_strp used without required section
(No debugging symbols found in {...}/shimx64.efi.debug)
(gdb)
After adding `-gdwarf-4 -gstrict-dwarf` to gcc compile flags:
(gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000
add symbol table from file "{...}/shimx64.efi.debug" at
.text_addr = 0x561b000
.data_addr = 0x5681000
(y or n) y
Reading symbols from {...}/shimx64.efi.debug...
(gdb)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014231/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014231] [NEW] gcc produces DWARF5, gdb requires DWARF4
Public bug reported:
On Ubuntu 22.04.2 LTS using fully updated gcc and gdb, I find that by
default gcc produces DWARF5 debug files which gdb cannot read, with the
following error:
Dwarf Error: DW_FORM_line_strp used without required section
If I add the flags `-gdwarf-4 -gstrict-dwarf` to `gcc` then it produces
output which gdb can read.
I would have expected the created and required versions of DWARF to
match between these two programs.
(I found the following two issues which appear to be people also
suffering from gcc newly producing DWARF5, in different contexts:
https://github.com/golang/vscode-go/issues/1914
https://github.com/haikuports/haikuports/issues/4987 ; as mentioned
however, the mismatch between what gcc produces and what gdb accepts
seems to be a specific problem, which I suppose may be likely to break
e.g. existing working debug instructions, etc.)
---
Package: gcc
Version: 4:11.2.0-1ubuntu1
$ gcc --version
gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Package: gdb
Version: 12.1-0ubuntu1~22.04
$ gdb --version
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Using default gcc output (i.e. with no flags specifying DWARF version):
(gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000
add symbol table from file "{...}/shimx64.efi.debug" at
.text_addr = 0x561b000
.data_addr = 0x5681000
(y or n) y
Reading symbols from {...}/shimx64.efi.debug...
Dwarf Error: DW_FORM_line_strp used without required section
(No debugging symbols found in {...}/shimx64.efi.debug)
(gdb)
After adding `-gdwarf-4 -gstrict-dwarf` to gcc compile flags:
(gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000
add symbol table from file "{...}/shimx64.efi.debug" at
.text_addr = 0x561b000
.data_addr = 0x5681000
(y or n) y
Reading symbols from {...}/shimx64.efi.debug...
(gdb)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/2014231
Title:
gcc produces DWARF5, gdb requires DWARF4
Status in linux package in Ubuntu:
New
Bug description:
On Ubuntu 22.04.2 LTS using fully updated gcc and gdb, I find that by
default gcc produces DWARF5 debug files which gdb cannot read, with
the following error:
Dwarf Error: DW_FORM_line_strp used without required section
If I add the flags `-gdwarf-4 -gstrict-dwarf` to `gcc` then it
produces output which gdb can read.
I would have expected the created and required versions of DWARF to
match between these two programs.
(I found the following two issues which appear to be people also
suffering from gcc newly producing DWARF5, in different contexts:
https://github.com/golang/vscode-go/issues/1914
https://github.com/haikuports/haikuports/issues/4987 ; as mentioned
however, the mismatch between what gcc produces and what gdb accepts
seems to be a specific problem, which I suppose may be likely to break
e.g. existing working debug instructions, etc.)
---
Package: gcc
Version: 4:11.2.0-1ubuntu1
$ gcc --version
gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Package: gdb
Version: 12.1-0ubuntu1~22.04
$ gdb --version
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Using default gcc output (i.e. with no flags specifying DWARF version):
(gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000
add symbol table from file "{...}/shimx64.efi.debug" at
.text_addr = 0x561b000
.data_addr = 0x5681000
(y or n) y
Reading symbols from {...}/shimx64.efi.debug...
Dwarf Error: DW_FORM_line_strp used without required section
(No debugging symbols found in {...}/shimx64.efi.debug)
(gdb)
After adding `-gdwarf-4 -gstrict-dwarf` to gcc compile flags:
(gdb) add-symbol-file {...}/shimx64.efi.debug 0x0561B000 -s .data 0x05681000
add symbol table from file "{...}/shimx64.efi.debug" at
.text_addr = 0x561b000
.data_addr = 0x5681000
(y or n) y
Reading symbols from {...}/shimx64.efi.debug...
(gdb)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014231/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007439] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module failed to build
I can confirm this occurred on my machine, it was not an external HDD. I have an MSI MS-7976 motherboard and a Samsung M.2 SSD. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/2007439 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: on Mac Mini 2014. Booted into Ubuntu from external HDD. directed here from software updater ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass DKMSKernelVersion: 5.19.0-32-generic Date: Wed Feb 15 15:50:03 2023 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:603:14: error: implicit declaration of function ‘pci_alloc_consistent’; did you mean ‘osl_dma_alloc_consistent’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2023-02-09 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageVersion: 6.30.223.271+bdcom-0ubuntu8 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/2007439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994060] Re: dkms drivers not built or installed
try doing dkms autoinstall: Error! Your kernel headers for kernel 5.17.0-1020-oem cannot be found. Please install the linux-headers-5.17.0-1020-oem package or use the --kernelsourcedir option to tell DKMS where it's located. Error! Your kernel headers for kernel 5.17.0-1020-oem cannot be found. Please install the linux-headers-5.17.0-1020-oem package or use the --kernelsourcedir option to tell DKMS where it's located. Error! Your kernel headers for kernel 5.17.0-1020-oem cannot be found. Please install the linux-headers-5.17.0-1020-oem package or use the --kernelsourcedir option to tell DKMS where it's located. The kernel header have alls been install upto now (Missing depend for) doing apt-get install linux-headers-5.17.0-1020-oem cause the dkms to build and install. sound like a missing depend 5.17 stuff version 5.15. The 5.15 installed the header for every upgraded kernel version but when the apt installed the 5.17 kernel it did not install the kernel headers. ** Attachment added: "dpkg -l after installing kernel header file myself" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.17/+bug/1994060/+attachment/5626473/+files/installed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1994060 Title: dkms drivers not built or installed Status in linux-signed-oem-5.17 package in Ubuntu: New Bug description: The system updated kernels to 5.17.0-1020-oem from 5.15.0-52-generic The dkms driver did not install on the new kernel. I Have 3 dkms drivers installed. They all build on 5.15.0.52 kernel. I have look and the lib/modules/kenerl-version/update does not exists The 3 dkms moudles: nvidia/520.56.06 virtualbox/6.1.38 zfs/2.1.6, 5.15.0-52-generic mike@mike-think:/lib/modules$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy mike@mike-think:/lib/modules$ uname -a Linux mike-think 5.17.0-1020-oem #21-Ubuntu SMP PREEMPT Fri Oct 14 09:33:24 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux mike@mike-think:/lib/modules/5.17.0-1020-oem$ ls initrd/ modules.builtin.bin modules.softdep kernel/ modules.builtin.modinfo modules.symbols modules.aliasmodules.dep modules.symbols.bin modules.alias.binmodules.dep.bin vdso/ modules.builtin modules.devname modules.builtin.alias.bin modules.order ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1020-oem 5.17.0-1020.21 ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15 Uname: Linux 5.17.0-1020-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Mon Oct 24 14:07:31 2022 InstallationDate: Installed on 2020-03-30 (937 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.17 UpgradeStatus: Upgraded to jammy on 2022-10-07 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.17/+bug/1994060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994060] [NEW] dkms drivers not built or installed
Public bug reported: The system updated kernels to 5.17.0-1020-oem from 5.15.0-52-generic The dkms driver did not install on the new kernel. I Have 3 dkms drivers installed. They all build on 5.15.0.52 kernel. I have look and the lib/modules/kenerl-version/update does not exists The 3 dkms moudles: nvidia/520.56.06 virtualbox/6.1.38 zfs/2.1.6, 5.15.0-52-generic mike@mike-think:/lib/modules$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy mike@mike-think:/lib/modules$ uname -a Linux mike-think 5.17.0-1020-oem #21-Ubuntu SMP PREEMPT Fri Oct 14 09:33:24 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux mike@mike-think:/lib/modules/5.17.0-1020-oem$ ls initrd/modules.builtin.bin modules.softdep kernel/modules.builtin.modinfo modules.symbols modules.alias modules.dep modules.symbols.bin modules.alias.bin modules.dep.bin vdso/ modules.builtinmodules.devname modules.builtin.alias.bin modules.order ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1020-oem 5.17.0-1020.21 ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15 Uname: Linux 5.17.0-1020-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Mon Oct 24 14:07:31 2022 InstallationDate: Installed on 2020-03-30 (937 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.17 UpgradeStatus: Upgraded to jammy on 2022-10-07 (16 days ago) ** Affects: linux-signed-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1994060 Title: dkms drivers not built or installed Status in linux-signed-oem-5.17 package in Ubuntu: New Bug description: The system updated kernels to 5.17.0-1020-oem from 5.15.0-52-generic The dkms driver did not install on the new kernel. I Have 3 dkms drivers installed. They all build on 5.15.0.52 kernel. I have look and the lib/modules/kenerl-version/update does not exists The 3 dkms moudles: nvidia/520.56.06 virtualbox/6.1.38 zfs/2.1.6, 5.15.0-52-generic mike@mike-think:/lib/modules$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy mike@mike-think:/lib/modules$ uname -a Linux mike-think 5.17.0-1020-oem #21-Ubuntu SMP PREEMPT Fri Oct 14 09:33:24 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux mike@mike-think:/lib/modules/5.17.0-1020-oem$ ls initrd/ modules.builtin.bin modules.softdep kernel/ modules.builtin.modinfo modules.symbols modules.aliasmodules.dep modules.symbols.bin modules.alias.binmodules.dep.bin vdso/ modules.builtin modules.devname modules.builtin.alias.bin modules.order ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1020-oem 5.17.0-1020.21 ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15 Uname: Linux 5.17.0-1020-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Mon Oct 24 14:07:31 2022 InstallationDate: Installed on 2020-03-30 (937 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.17 UpgradeStatus: Upgraded to jammy on 2022-10-07 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.17/+bug/1994060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991725] [NEW] fails to sign kernel modules
Public bug reported: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in dkms package in Ubuntu: New Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
Not only the resolution is wrong for the USB-C display but also the order is different. Unplugging and plugging the connector seems to fix the issue (Ubuntu 22 LTS). -- 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/1978980 Title: [amdgpu] Wrong external screen resolution after wake up from sleep Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04, running KDE) I started experiencing a problem with external screen resolution after the wake up from sleep. The monitor resolution is small (1280x768) and doesn't respect the setting prior the sleep (1920x1200). After the wake up from sleep: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1280x768 59.94* # a list of lower resolutions ``` There is an error when trying to change the setting to the highest resolution supported by the monitor (which is not included in the above list). ``` > xrandr --output DisplayPort-1 --mode 1920x1200 xrandr: cannot find mode 1920x1200 ``` After the turn off and turn on of the external monitor, the resolution is somehow added to the xrandr list: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95 + # a list of resolutions 1280x768 59.94* # a list of lower resolutions ``` Now it is possible to change the resolution: ``` > xrandr --output DisplayPort-1 --mode 1920x1200 # no output, the resolution was successfully changed ``` After the change, the resolution is successfully changed and xrandr gives proper output: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95*+ # a list of lower resolutions ``` The problem is not present on fresh start. However, it is consistently present after the wake up from sleep. What can cause the problem and how may I fix it? Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the external monitor is connected via USB-C. There are no problems with laptop screen resolution, only external monitor is affected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jun 16 18:12:05 2022 DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2019-08-21 (1030 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20NE000BMC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET44W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000BMC dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495: dmi.product.family: ThinkPad E495 dmi.product.name: 20NE000BMC dmi.product.sku:
[Kernel-packages] [Bug 1970957] Re: suspend problem
Can confirm on Lenovo ThinkPad L13Yoga. Kernel 5.15.0-46. Deactivating the security chip in BIOS and other proposed solutions in different forum and here to no avail. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981727] Re: kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK)
Perhaps this comment from the changes log is relevant: amd/display: set backlight only if required -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1981727 Title: kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK) Status in linux-hwe-5.15 package in Ubuntu: New Bug description: A recent update to 5.15.0-41 results in my laptop screen (Dell Precision 7520) being unable to come up to full brightness. I have verified that I can revert to 5.13.0-52 and the problem is not there. I looked at /sys/class/backlight/nv_backlight/max_brightness which lists 1023 in the newer kernel and 100 in the older one. I have verified that changing the brightness manually does change /sys/class/backlight/nv_backlight/brightness, all the way up to 1023, but it's just not enough... the screen is still very dim. The other screen (standalone monitor through docking station) on a two-headed display is fine. I tried to write 100 into max_brightness but of course, the "file" is read-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1981727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981727] Re: kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK)
For whatever reason I don't have crashdb.conf ... kordosky@miketop5:~$ apport-collect 1981727 Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 596, in app = GTKUserInterface() File "/usr/share/apport/apport-gtk", line 56, in __init__ apport.ui.UserInterface.__init__(self) File "/usr/lib/python3/dist-packages/apport/ui.py", line 206, in __init__ self.crashdb = apport.crashdb.get_crashdb(None) File "/usr/lib/python3/dist-packages/apport/crashdb.py", line 822, in get_crashdb with open(conf) as f: FileNotFoundError: [Errno 2] No such file or directory: '/etc/apport/crashdb.conf' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1981727 Title: kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK) Status in linux-hwe-5.15 package in Ubuntu: New Bug description: A recent update to 5.15.0-41 results in my laptop screen (Dell Precision 7520) being unable to come up to full brightness. I have verified that I can revert to 5.13.0-52 and the problem is not there. I looked at /sys/class/backlight/nv_backlight/max_brightness which lists 1023 in the newer kernel and 100 in the older one. I have verified that changing the brightness manually does change /sys/class/backlight/nv_backlight/brightness, all the way up to 1023, but it's just not enough... the screen is still very dim. The other screen (standalone monitor through docking station) on a two-headed display is fine. I tried to write 100 into max_brightness but of course, the "file" is read-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1981727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981727] Re: kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK)
Verified that the behavior is the same when the laptop is used stand- alone, unconnected to a docking station. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1981727 Title: kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK) Status in linux-hwe-5.15 package in Ubuntu: New Bug description: A recent update to 5.15.0-41 results in my laptop screen (Dell Precision 7520) being unable to come up to full brightness. I have verified that I can revert to 5.13.0-52 and the problem is not there. I looked at /sys/class/backlight/nv_backlight/max_brightness which lists 1023 in the newer kernel and 100 in the older one. I have verified that changing the brightness manually does change /sys/class/backlight/nv_backlight/brightness, all the way up to 1023, but it's just not enough... the screen is still very dim. The other screen (standalone monitor through docking station) on a two-headed display is fine. I tried to write 100 into max_brightness but of course, the "file" is read-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1981727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981727] [NEW] kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK)
Public bug reported: A recent update to 5.15.0-41 results in my laptop screen (Dell Precision 7520) being unable to come up to full brightness. I have verified that I can revert to 5.13.0-52 and the problem is not there. I looked at /sys/class/backlight/nv_backlight/max_brightness which lists 1023 in the newer kernel and 100 in the older one. I have verified that changing the brightness manually does change /sys/class/backlight/nv_backlight/brightness, all the way up to 1023, but it's just not enough... the screen is still very dim. The other screen (standalone monitor through docking station) on a two-headed display is fine. I tried to write 100 into max_brightness but of course, the "file" is read-only. ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-signed-hwe-5.15 (Ubuntu) => linux-hwe-5.15 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1981727 Title: kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK) Status in linux-hwe-5.15 package in Ubuntu: New Bug description: A recent update to 5.15.0-41 results in my laptop screen (Dell Precision 7520) being unable to come up to full brightness. I have verified that I can revert to 5.13.0-52 and the problem is not there. I looked at /sys/class/backlight/nv_backlight/max_brightness which lists 1023 in the newer kernel and 100 in the older one. I have verified that changing the brightness manually does change /sys/class/backlight/nv_backlight/brightness, all the way up to 1023, but it's just not enough... the screen is still very dim. The other screen (standalone monitor through docking station) on a two-headed display is fine. I tried to write 100 into max_brightness but of course, the "file" is read-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1981727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967960] Re: LightDM login display corrupted in 22.04 Beta
** 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/1967960 Title: LightDM login display corrupted in 22.04 Beta Status in linux package in Ubuntu: Confirmed Bug description: This problem appeared on an older machine I am using to test 22.04 Beta: Biostar MCP6P-M2+ mainboard with AMD Sempron 3400+ CPU and nVidia 7200 GS graphic card, using either VGA or DVI connection to a NEC 1920x1200 LED monitor. If I remember correctly, it occurred after installing all of the updates that were available on April 4. On boot the LightDM login screen is shredded by horizontal lines (photo attached) but when I enter my password the uncorrupted login screen briefly appears and my user session opens properly. I installed gdm3 and using that display manager the login screen appears normally. In all cases the monitor reports 1920x1200, 74.0 kHz horizontal, 59.8 Hz vertical on the VGA connection. If I use a 1280x1024 LCD monitor there is no problem with the LightDM login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877226] Re: nvidia - external display unavailable after screen goes to sleep
The same observed with NVIDIA 470.86 driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1877226 Title: nvidia - external display unavailable after screen goes to sleep Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: On ubuntu 20.04 (Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) with nvidia proprietary driver 440.64 with an nvidia MX250 (Lenovo T590): 1) Attach monitor via HDMI 2) Monitor is properly detected. Gnome-control-center sees the correct monitor and sets it to join displays. No issue 3) activate lock screen (window key + L) 4) wait for screens to go to sleep 5) wake up screens to login again (external monitor flashes briefly) 6) login 7) system no longer uses external display and returns to single display 8) open gnome-control-center -> displays. Single Display is active 9) Attempt to select join displays 10) Error at the top of gnome-control-center: Changes cannot be applied - This could be due to hardware limitations 11) select mirror - click apply 12) a keep settings dialogue will pop-up briefly before the screen goes blank. When the screen comes back on, both screens come back on, with a new keep settings dialogue. 13) select keep settings. gnome-control-center now shows Joing Displays as being active. not/not mirror. Notes: -changing prime-select to nvidia vs adaptive does not change the issue -setting power profile to performance in nvidia-settings does not change the issue gnome-control-center info: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status nvidia-driver-440: Installed: 440.82+really.440.64-0ubuntu6 Candidate: 440.82+really.440.64-0ubuntu6 Version table: *** 440.82+really.440.64-0ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 06:16:15 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-24 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942316] Re: Touchpad doesn't work at all on Asus TUF Gaming F15 FX506HC-HN007T, after fresh instalation.
Same here 0. Ubuntu version: Ubuntu 20.04.3 LTS 1. Laptop model: Asus TUF Gaming F15 FX506HM-HN019T 2. Touchpad manufacturer: Unknown 3. The problem started right after installing ubuntu, I realised it when I was selecting the language the touchpad did not work at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1942316 Title: Touchpad doesn't work at all on Asus TUF Gaming F15 FX506HC-HN007T, after fresh instalation. Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: 0. Ubuntu version: Ubuntu 18.04.5 LTS 1. Laptop model: Asus TUF Gaming F15 FX506HC-HN007T 2. Touchpad manufacturer: Unknown 3. The problem started right after installing ubuntu, I realised it when I was selecting the language the touchpad did not work at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 1 12:55:35 2021 InstallationDate: Installed on 2021-09-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1942316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950492] Re: wifi stops working on Dell XPS 9310
This appears to be triggered by commit 4f73581836f031611b281c8c6017202f36afbf6b, the change is reported as a bug in the 5.13 kernel as well and appears to have been brought into the 5.11 HWE kernel. https://bugzilla.kernel.org/show_bug.cgi?id=214455 -- 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/1950492 Title: wifi stops working on Dell XPS 9310 Status in linux package in Ubuntu: Incomplete Bug description: After updating to linux 5.13.0-22 wifi stops working on Dell XPS 9310 with QCA6390. There are two errors in dmesg: 1. mhi: qcom_mhi_qrtr mhi0_IPCR: invalid ipcrouter packet 2. ath11k ath11k_pci :72:00.0: failed to register fw indication: -110 ath11k_pci :72:00.0: failed to send qmi firmware indication: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950492] Re: wifi stops working on Dell XPS 9310
Same problem here with Ubuntu 20.04 on a Dell XPS 15 9500, but in my case it was triggered by update from kernel 5.11.0-38-generic to 5.11.0-40-generic. Apt history shows the update as occurring last Friday morning, and the next time I rebooted (the day after) the WiFi module stopped working, message in dmesg as above. After the error, the WiFi module is not even visible to the BIOS. The only way to get the WiFi module to appear again is to remove the back of the laptop and disconnect the battery, but if I boot Linux it immediately is knocked out again. -- 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/1950492 Title: wifi stops working on Dell XPS 9310 Status in linux package in Ubuntu: Incomplete Bug description: After updating to linux 5.13.0-22 wifi stops working on Dell XPS 9310 with QCA6390. There are two errors in dmesg: 1. mhi: qcom_mhi_qrtr mhi0_IPCR: invalid ipcrouter packet 2. ath11k ath11k_pci :72:00.0: failed to register fw indication: -110 ath11k_pci :72:00.0: failed to send qmi firmware indication: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)
I see the same error on HP Elitebook 820 G3 on iwlwifi_1 using linux-
firmware 1.187.20 on Ubuntu 20.04
--
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/1803881
Title:
thermal thermal_zone4: failed to read out thermal zone (-61)
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
Thermald can't read zone4. It's making my fan go crazy, this issue
seems to be a bit more controlled in 18.10.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
sudo apt-cache policy thermald
thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
*** 1.7.0-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
cat /sys/class/thermal/thermal_zone4/type
iwlwifi
find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
/sys/class/thermal/thermal_zone4/uevent
/sys/class/thermal/thermal_zone4/trip_point_5_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_3_type
passive
/sys/class/thermal/thermal_zone4/trip_point_4_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_2_type
passive
/sys/class/thermal/thermal_zone4/power/runtime_active_time
0
/sys/class/thermal/thermal_zone4/power/runtime_active_kids
0
/sys/class/thermal/thermal_zone4/power/runtime_usage
0
/sys/class/thermal/thermal_zone4/power/runtime_status
unsupported
/sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone4/power/async
disabled
/sys/class/thermal/thermal_zone4/power/runtime_suspended_time
0
/sys/class/thermal/thermal_zone4/power/runtime_enabled
disabled
/sys/class/thermal/thermal_zone4/power/control
auto
/sys/class/thermal/thermal_zone4/available_policies
power_allocator user_space bang_bang fair_share step_wise
/sys/class/thermal/thermal_zone4/policy
step_wise
/sys/class/thermal/thermal_zone4/trip_point_3_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_1_type
passive
/sys/class/thermal/thermal_zone4/k_d
cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
/sys/class/thermal/thermal_zone4/sustainable_power
cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
/sys/class/thermal/thermal_zone4/type
iwlwifi
/sys/class/thermal/thermal_zone4/trip_point_7_type
passive
/sys/class/thermal/thermal_zone4/offset
cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
/sys/class/thermal/thermal_zone4/slope
cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_2_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_0_type
passive
/sys/class/thermal/thermal_zone4/trip_point_6_type
passive
/sys/class/thermal/thermal_zone4/emul_temp
cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
/sys/class/thermal/thermal_zone4/k_po
cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
/sys/class/thermal/thermal_zone4/integral_cutoff
cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
/sys/class/thermal/thermal_zone4/k_i
cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_1_temp
-32768000
/sys/class/thermal/thermal_zone4/k_pu
cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
/sys/class/thermal/thermal_zone4/temp
46000
/sys/class/thermal/thermal_zone4/trip_point_7_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_5_type
passive
/sys/class/thermal/thermal_zone4/trip_point_0_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_6_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_4_type
passive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803881/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950385] Re: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel
*** This bug is a duplicate of bug 1574582 *** https://bugs.launchpad.net/bugs/1574582 ** This bug has been marked a duplicate of bug 1574582 HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager -- 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/1950385 Title: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel Status in linux package in Ubuntu: Confirmed Bug description: Focal Fossa 20.04.1 HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem. I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible with updated libc from Ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mp 2798 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-07 (554 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 03f0:9d1d HP, Inc HP lt4120 Snapdragon X5 LTE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 820 G3 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 ro quiet splash resume=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 resume_offset=698368 vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.52 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.52 dmi.board.name: 807C dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.asset.tag: 5CG60906BD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook820G3:pvr:skuL4Q17AV:rvnHP:rn807C:rvrKBCVersion85.79:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G3 dmi.product.sku: L4Q17AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950385] Re: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel
Debug loop from Modem Manager with endless loop on modem initialization on kernel 5.13.x. ** Attachment added: "Debug Log from Modem Manager" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+attachment/5540476/+files/ModemManager.Debug.log -- 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/1950385 Title: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel Status in linux package in Ubuntu: Confirmed Bug description: Focal Fossa 20.04.1 HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem. I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible with updated libc from Ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mp 2798 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-07 (554 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 03f0:9d1d HP, Inc HP lt4120 Snapdragon X5 LTE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 820 G3 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 ro quiet splash resume=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 resume_offset=698368 vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.52 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.52 dmi.board.name: 807C dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.asset.tag: 5CG60906BD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook820G3:pvr:skuL4Q17AV:rvnHP:rn807C:rvrKBCVersion85.79:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G3 dmi.product.sku: L4Q17AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950385] Re: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel
***I have a recent Fossil's ModemManager 1.16.6-2-20.04 and under kernel 5.8.x it works: ModemManager.service - Modem Manager Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor > Active: active (running) since Fri 2021-11-12 14:46:59 CET; 2h 19min ago Main PID: 661 (ModemManager) Tasks: 5 (limit: 19006) Memory: 11.6M CGroup: /system.slice/ModemManager.service ├─ 661 /usr/sbin/ModemManager └─1054 /usr/libexec/qmi-proxy nov 12 14:47:03 UB820 ModemManager[661]: [modem0/sim0] couldn't load li> nov 12 14:47:03 UB820 ModemManager[661]: [modem0] couldn't load list of> nov 12 14:47:03 UB820 ModemManager[661]: [modem0] couldn't load UE mode> nov 12 14:47:04 UB820 ModemManager[661]: [modem0] state changed (unknow> nov 12 14:47:04 UB820 ModemManager[661]: [modem0] state changed (disabl> nov 12 14:47:04 UB820 ModemManager[661]: [modem0] power state updated: > nov 12 14:47:04 UB820 ModemManager[661]: [modem0] state changed (enabli> nov 12 14:47:05 UB820 ModemManager[661]: [modem0] 3GPP registration sta> nov 12 14:47:05 UB820 ModemManager[661]: [modem0] 3GPP registration sta> nov 12 14:47:05 UB820 ModemManager[661]: [modem0] state changed (enable> ***After Ubuntu update to recent kernel 5.1x (5.10.x,5.11.x,5.13.x) ModemManager stays the same version and displays: sudo systemctl status ModemManager ● ModemManager.service - Modem Manager Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-11-12 17:08:24 CET; 1min 30s ago Main PID: 818 (ModemManager) Tasks: 3 (limit: 18992) Memory: 6.7M CGroup: /system.slice/ModemManager.service └─818 /usr/sbin/ModemManager nov 12 17:09:53 UB820 ModemManager[818]: [base-manager] couldn't check support for device '/sys/devices/pci:00/:00:14.0/usb1/> nov 12 17:09:54 UB820 ModemManager[818]: [base-manager] port cdc-wdm0 released by device '/sys/devices/pci:00/:00:14.0/usb1/1> nov 12 17:09:54 UB820 ModemManager[818]: [base-manager] port wwan0 released by device '/sys/devices/pci:00/:00:14.0/usb1/1-3' nov 12 17:09:54 UB820 ModemManager[818]: [base-manager] couldn't check support for device '/sys/devices/pci:00/:00:14.0/usb1/> nov 12 17:09:54 UB820 ModemManager[818]: [base-manager] port cdc-wdm0 released by device '/sys/devices/pci:00/:00:14.0/usb1/1> nov 12 17:09:54 UB820 ModemManager[818]: [base-manager] port wwan0 released by device '/sys/devices/pci:00/:00:14.0/usb1/1-3' nov 12 17:09:54 UB820 ModemManager[818]: [base-manager] couldn't check support for device '/sys/devices/pci:00/:00:14.0/usb1/> nov 12 17:09:54 UB820 ModemManager[818]: [base-manager] port cdc-wdm0 released by device '/sys/devices/pci:00/:00:14.0/usb1/1> nov 12 17:09:54 UB820 ModemManager[818]: [base-manager] port wwan0 released by device '/sys/devices/pci:00/:00:14.0/usb1/1-3' nov 12 17:09:54 UB820 ModemManager[818]: [base-manager] couldn't check support for device '/sys/devices/pci:00/:00:14.0/usb1/ -- 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/1950385 Title: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel Status in linux package in Ubuntu: Confirmed Bug description: Focal Fossa 20.04.1 HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem. I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible with updated libc from Ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mp 2798 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-07 (554 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 03f0:9d1d HP, Inc HP lt4120 Snapdragon X5 LTE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 820 G3 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 ro quiet splash resume=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 resume_offset=698368 vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
[Kernel-packages] [Bug 1950385] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1950385/+attachment/5540349/+files/acpidump.txt ** 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/1950385 Title: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel Status in linux package in Ubuntu: Confirmed Bug description: Focal Fossa 20.04.1 HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem. I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible with updated libc from Ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mp 2798 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-07 (554 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 03f0:9d1d HP, Inc HP lt4120 Snapdragon X5 LTE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 820 G3 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 ro quiet splash resume=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 resume_offset=698368 vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.52 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.52 dmi.board.name: 807C dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.asset.tag: 5CG60906BD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook820G3:pvr:skuL4Q17AV:rvnHP:rn807C:rvrKBCVersion85.79:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G3 dmi.product.sku: L4Q17AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950385] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1950385/+attachment/5540347/+files/UdevDb.txt -- 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/1950385 Title: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel Status in linux package in Ubuntu: Confirmed Bug description: Focal Fossa 20.04.1 HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem. I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible with updated libc from Ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mp 2798 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-07 (554 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 03f0:9d1d HP, Inc HP lt4120 Snapdragon X5 LTE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 820 G3 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 ro quiet splash resume=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 resume_offset=698368 vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.52 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.52 dmi.board.name: 807C dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.asset.tag: 5CG60906BD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook820G3:pvr:skuL4Q17AV:rvnHP:rn807C:rvrKBCVersion85.79:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G3 dmi.product.sku: L4Q17AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
