[Kernel-packages] [Bug 1967721] Re: Laptop never resuming from standby
I attempted the upgrade again today. Running 5.15.0-43 I have no issues. Battery or Power it seems to resume reliably. Running on a Thinkpad X260 Thanks! -- 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/1967721 Title: Laptop never resuming from standby Status in linux package in Ubuntu: Confirmed Bug description: On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after suspending the laptop, it's never possible to wake it up. Neither keyboard nor power button work, only way is to long-press to force poweroff and restart. This did not happen with 21.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 08:30:52 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW 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.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+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 1983741] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1983741
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1983741
Title:
kernel crash and hung up while umounting xfs
Status in linux package in Ubuntu:
Incomplete
Bug description:
OS: Ubuntu 18.04.1
Using XFS with Ceph rdb and mount by OverlayFS, sometimes system hung up with
kernel crash like below:
2022-07-27 16:17
Jul 27 15:21:43 k8s-node-b01-17-05 kernel: [25666453.856553] VFS: Busy inodes
after unmount of overlay. Self-destruct in 5 seconds. Have a nice day...
Jul 27 15:22:01 k8s-node-b01-17-05 kernel: [25666471.122435] XFS (rbd59):
Unmounting Filesystem
Jul 27 15:22:25 k8s-node-b01-17-05 kernel: [25666495.392431] BUG: Dentry
d683c981{i=38c31f07,n=README_zh.md} still in use (1) [unmount of xfs
rbd23]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983741/+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 1983741] Re: kernel crash and hung up while umounting xfs
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1983741
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.
** Package changed: ubuntu => linux (Ubuntu)
--
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/1983741
Title:
kernel crash and hung up while umounting xfs
Status in linux package in Ubuntu:
Incomplete
Bug description:
OS: Ubuntu 18.04.1
Using XFS with Ceph rdb and mount by OverlayFS, sometimes system hung up with
kernel crash like below:
2022-07-27 16:17
Jul 27 15:21:43 k8s-node-b01-17-05 kernel: [25666453.856553] VFS: Busy inodes
after unmount of overlay. Self-destruct in 5 seconds. Have a nice day...
Jul 27 15:22:01 k8s-node-b01-17-05 kernel: [25666471.122435] XFS (rbd59):
Unmounting Filesystem
Jul 27 15:22:25 k8s-node-b01-17-05 kernel: [25666495.392431] BUG: Dentry
d683c981{i=38c31f07,n=README_zh.md} still in use (1) [unmount of xfs
rbd23]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983741/+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 1983741] [NEW] kernel crash and hung up while umounting xfs
You have been subscribed to a public bug:
OS: Ubuntu 18.04.1
Using XFS with Ceph rdb and mount by OverlayFS, sometimes system hung up with
kernel crash like below:
2022-07-27 16:17
Jul 27 15:21:43 k8s-node-b01-17-05 kernel: [25666453.856553] VFS: Busy inodes
after unmount of overlay. Self-destruct in 5 seconds. Have a nice day...
Jul 27 15:22:01 k8s-node-b01-17-05 kernel: [25666471.122435] XFS (rbd59):
Unmounting Filesystem
Jul 27 15:22:25 k8s-node-b01-17-05 kernel: [25666495.392431] BUG: Dentry
d683c981{i=38c31f07,n=README_zh.md} still in use (1) [unmount of xfs
rbd23]
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: ceph xfs
--
kernel crash and hung up while umounting xfs
https://bugs.launchpad.net/bugs/1983741
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
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 1981554] Re: [Ubuntu-22.04] Video mode is not working with the external monitor
HI Gnanendra, What version of the kernel are you using? This patch from comment #6 appears to already be in jammy https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969105 -- 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/1981554 Title: [Ubuntu-22.04] Video mode is not working with the external monitor Status in linux package in Ubuntu: Incomplete Bug description: Description: The SUT Dell EMC Poweredge R440 can not display video mode with external monitor when Ubuntu 22.04 boots. The video mode working properly under iDRAC virtual console. Steps to Reproduce: 1. Connect External monitor to SUT using VGA cable. 2. Mount ubuntu-22.04-live-server-amd64.iso by iDRAC virtual console. 3. Start to install the OS and click "Try or Install Ubuntu server". 4. The SUT can not display video mode with monitor when OS boots. Expected Results: Video mode should work properly when OS boots with external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981554/+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 1978333] Autopkgtest regression report (makedumpfile/1:1.6.5-1ubuntu1~18.04.7)
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.7) for bionic have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.5-1ubuntu1~18.04.7 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Committed Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Committed Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: In Progress Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties Open new terminal and try to ssh to azure VM, It does not succeed Force a reboot of the VM through the portal or serial console #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console # verify package version of kdump-tool # verify parameter is not listed in the kdump-config show output kdump-config unload kdump-config load kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #trigger another crash echo c >
[Kernel-packages] [Bug 1978333] Please test proposed package
Hello Heather, or anyone else affected, Accepted makedumpfile into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Committed Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Committed Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: In Progress Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties Open new terminal and try to ssh to azure VM, It does not succeed Force a reboot of the VM through the portal or serial console #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console # verify package version of kdump-tool # verify parameter is not listed in the kdump-config show output kdump-config unload kdump-config load kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL:
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
Hello Heather, or anyone else affected, Accepted makedumpfile into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.7-1ubuntu2.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed ** Changed in: makedumpfile (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Committed Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Committed Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: In Progress Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties Open new terminal and try to ssh to azure VM, It does not succeed Force a reboot of the VM through the portal or serial console #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console #
[Kernel-packages] [Bug 1958357] Re: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build
Automatically appears on boot up -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1958357 Title: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: just pop up with error message ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-25-generic Date: Wed Jan 19 09:14:55 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-450:450.119.03-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/450.119.03/build/nvidia-drm/nvidia-drm-crtc.c:234:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2020-10-13 (462 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 450.119.03-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1: nvidia 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/nvidia-graphics-drivers-450/+bug/1958357/+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 1942999] Re: [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address after hotplug tbt dock
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1942999 Title: [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address after hotplug tbt dock Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Confirmed 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 source package in Impish: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. Intel still doesn't provide any solution about their approach. In the meantime, this patch is still the only fix. Re-submit it to Jammy, oem-5.17 and Unstable kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+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 1981390] Re: Mass Storage Gadget driver truncates device >2TB
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
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/1981390
Title:
Mass Storage Gadget driver truncates device >2TB
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
[Impact]
I tried to use f_mass_storage to expose a 16TB hard drive attached to
Raspberry Pi to another computer.
On the remote computer the recognised drive has incorrect capacity and the
data is truncated.
After some debugging I noted the problem is caused by a bug in the
read capacity function of f_mass_storage in kernel version prior to
5.15, which had already been fixed upstream in mainline kernel since
v5.16
https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/
I tried the kernel from https://github.com/raspberrypi/linux version
rpi-5.16.y and confirmed that the problem is fixed at v5.16.
I wonder if the fix can be backported to the Ubuntu kernel.
Thank you very much!
Current kernel package version: linux-raspi (5.15.0-1011.13) jammy
Hardware: Raspberry Pi 4B
[Fix]
Backport commit bedbac5f66bf ("usb: gadget: storage: add support for
media larger than 2T")
[Test case]
See above.
[Where problems could occur]
Modifications are limited to the USB gadget mass storage driver, so
problems should only be seen on a client that uses this driver to
expose a USB drive to an attached USB host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+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 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on
Also have this issue again in 22.04.1 LTS version. -- 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/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855793/+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 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed -- 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/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983143/+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 1976438] Re: Fix sub-optimal I210 network speed
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1976438 Title: Fix sub-optimal I210 network speed Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] I210 may not reach maximum speed on Intel Alder Lake platforms. [Fix] Following the datasheet to ensure I210 is not in idle state when CPU is using PCIe link to perform TX. [Test] With the fix applied, the I210 TX/RX speed can reach ~94x MBps. [Where problems could occur] Since this changes how hardware idles, it can slightly increase power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1976438/+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 1973104] Re: e1000e report hardware hang
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1973104 Title: e1000e report hardware hang Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] e1000e hardware unit hang after s2idle May 06 15:34:49 ubuntu kernel: e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang: TDH <1> TDT <5> next_to_use <5> next_to_clean <1> buffer_info[next_to_clean]: time_stamp <1000587f0> next_to_watch <1> jiffies <1000589c0> next_to_watch.status <0> MAC Status <40080283> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> [Fix] Below commits fix this issue which have been included in v5.19-rc8 https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220508070905.1878172-1-sasha.nef...@intel.com/ 6cfa45361d3e Revert "e1000e: Fix possible HW unit hang after an s0ix exit" b49feacbeffc e1000e: Enable GPT clock before sending message to CSME [Test] Verified on the target machine, and confirmed the issue is gone. [Where problems could occur] The impact is low, it keeps the GPT clock enabled for CSME when e1000e_pm_resume() is called. With the new fix, the old workaround could be removed. I can't see this may introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1973104/+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 1982930] Re: ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1982930 Title: ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Testcase ubuntu_kernel_selftests.net:ioam6.sh fails in Focal with the 5.15 kernels with the following errors: 17:19:35 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/cl ient/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 17:19:35 DEBUG| [stdout] make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install 17:19:35 DEBUG| [stdout] make[1]: Entering directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 17:19:35 DEBUG| [stdout] INSTALL ./usr/include 17:19:35 DEBUG| [stdout] make[1]: Leaving directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 17:19:35 DEBUG| [stdout] TAP version 13 17:19:35 DEBUG| [stdout] 1..1 17:19:35 DEBUG| [stdout] # selftests: net: ioam6.sh 17:19:35 DEBUG| [stdout] # SKIP: iproute2 too old, missing ioam command 17:19:35 DEBUG| [stdout] not ok 1 selftests: net: ioam6.sh # exit=1 This is caused by an older version of iproute2 in Focal. The package has been updated in Jammy via bug 1951390 and the bug report says it should be updated in Focal as well. Even if the package is eventually updated, the testcase shouldn't throw a fatal error in this case and really return "SKIP" as the log message says. [Fix] The proper fix would be to make tools/testing/selftests/net/ioam6.sh return the Kselftest framework proper skip code instead of failing. [Testcase] Run the selftest script in Focal with a 5.15 kernel. [Where problems could occur] If the skip code is added to places where it shouldn't be added it could introduce false positives and not fail where it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1982930/+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 1983297] Re: Additional fix for TGL + AUO panel flickering
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1953613] Re: GPIO character device v1 API not enabled in kernel
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status:
[Kernel-packages] [Bug 1961483] Re: New upstream release 2022.02.18
Marked invalid as packages for a newer upstream release are already available. ** Changed in: wireless-regdb (Ubuntu Bionic) Status: In Progress => Invalid ** Changed in: wireless-regdb (Ubuntu) Status: In Progress => Invalid ** Changed in: wireless-regdb (Ubuntu Focal) Status: In Progress => Invalid ** Changed in: wireless-regdb (Ubuntu Jammy) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1961483 Title: New upstream release 2022.02.18 Status in wireless-regdb package in Ubuntu: Invalid Status in wireless-regdb source package in Bionic: Invalid Status in wireless-regdb source package in Focal: Invalid Status in wireless-regdb source package in Impish: Won't Fix Status in wireless-regdb source package in Jammy: Invalid Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1961483/+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 1979146] Re: Enable 6 GHz operation in US/CA
*** This bug is a duplicate of bug 1980145 *** https://bugs.launchpad.net/bugs/1980145 Fixed by LP: #1980145 which updated to the 2022.06.06 release. Marking as a duplicate of that bug. ** This bug has been marked a duplicate of bug 1980145 New upstream release 2022.06.06 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1979146 Title: Enable 6 GHz operation in US/CA Status in wireless-regdb package in Ubuntu: New Bug description: The current wireless-regdb package (2021.08.28-0ubuntu2) does not authorize usage of the Wi-Fi 6 GHz band in US/CA, even though the corresponding federal regulatory authorities have approved usage since late 2021. The latest release of wireless-regdb (2022.06.06) enables the Wi-Fi 6 GHz band in US/CA. Request upgrading the wireless-regdb package to 2022.06.06 to allow Ubuntu desktop users with 6 GHz Wi-Fi hardware to connect to 6 GHz Wi- Fi wireless routers. Most desktop motherboards shipped in the last year have included Intel AX210 Wi-Fi hardware, which supports the 6 GHz band. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1979146/+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 1972815] Re: Headset mic with Cirrus logic codec doesn't work
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1972815 Title: Headset mic with Cirrus logic codec doesn't work Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Headset mic doesn't be selected automatically after headset is plugged in. [Fix] Cirrus provides a fix for this issue https://patchwork.kernel.org/project/alsa-devel/cover/20220504161236.2490532-1-sbind...@opensource.cirrus.com/ Currently, they are included in v5.19-rc1 ec6a8aaafbc5 ALSA: hda/cs8409: Support manual mode detection for CS42L429cd827381310 ALSA: hda/cs8409: Use general cs42l42 include in cs8409 hda driver 7b43e6d79562 ASoC: cs42l42: Move CS42L42 register descriptions to general include [Test] Verified on the target platform, and confirmed these patches work. [Where problems could occur] These affect the mic detection on CS8409_BULLSEYE, CS8409_WARLOCK, CS8409_WARLOCK_MLK, CS8409_WARLOCK_MLK_DUAL_MIC, CS8409_CYBORG, and CS8409_ODIN platforms. Hard to tell if it introduce any regression, will keep an eye on it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972815/+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 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1982104 Title: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server. Attaching the console logs. Currently, it looks like disabling VT-D option in BIOS settings helps mitigate the issue. Console logs indicate something is wrong in iommu/dmar subsystem. [Fix] The IOMMU driver shares the pasid table for PCI alias devices. When the RID2PASID entry of the shared pasid table has been filled by the first device, the subsequent device will encounter the "DMAR: Setup RID2PASID failed" failure as the pasid entry has already been marked as present. As the result, the IOMMU probing process will be aborted. On the contrary, when any alias device is hot-removed from the system, for example, by writing to /sys/bus/pci/devices/.../remove, the shared RID2PASID will be cleared without any notifications to other devices. As the result, any DMAs from those rest devices are blocked. Sharing pasid table among PCI alias devices could save two memory pages for devices underneath the PCIe-to-PCI bridges. Anyway, considering that those devices are rare on modern platforms that support VT-d in scalable mode and the saved memory is negligible, it's reasonable to remove this part of immature code to make the driver feasible and stable. [Test Case] 1. use the target machine(Intel Sapphire Rapids) and install the kernel with the fix. 2. boot the target machine 3. check dmesg if the error message exists [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed [Where problems could occur] After enable intel_iommu, the errors may be occurred. We need to figure out one by one once the related errors are triggered in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982104/+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 1981950] Re: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1981950 Title: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] The system with atlantic NIC[1d6a:94c0] fails to resume from S3 and hang with the following errors Jun 7 13:13:54 ubuntu kernel: [ 116.000561] aq_nic_deinit+0xb4/0xd0 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000566] atl_resume_common+0x6d/0x110 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000571] aq_pm_resume_restore+0x13/0x20 [atlantic] Jun 7 13:13:54 ubuntu kernel: [ 116.000575] pci_pm_resume+0x5c/0x90 Jun 7 13:13:54 ubuntu kernel: [ 116.000578] ? pci_pm_thaw+0x80/0x80 Jun 7 13:13:54 ubuntu kernel: [ 116.000580] dpm_run_callback+0x4e/0x120 Jun 7 13:13:54 ubuntu kernel: [ 116.000582] device_resume+0xad/0x200 Jun 7 13:13:54 ubuntu kernel: [ 116.000583] async_resume+0x1e/0x40 Jun 7 13:13:54 ubuntu kernel: [ 116.000585] async_run_entry_fn+0x33/0x120 Jun 7 13:13:54 ubuntu kernel: [ 116.000586] process_one_work+0x220/0x3c0 Jun 7 13:13:54 ubuntu kernel: [ 116.000588] worker_thread+0x4d/0x3f0 Jun 7 13:13:54 ubuntu kernel: [ 116.000589] ? process_one_work+0x3c0/0x3c0 Jun 7 13:13:54 ubuntu kernel: [ 116.000591] kthread+0x12a/0x150 Jun 7 13:13:54 ubuntu kernel: [ 116.000592] ? set_kthread_struct+0x40/0x40 Jun 7 13:13:54 ubuntu kernel: [ 116.000593] ret_from_fork+0x22/0x30 Jun 7 13:13:54 ubuntu kernel: [ 116.000596] Jun 7 13:13:54 ubuntu kernel: [ 116.000596] ---[ end trace 9d3fcd41d27dae25 ]--- [Fix] aq_nic_deinit() has been called while suspending, so don't need to call it again on resuming. Applied below 2 commits from v5.19-rc7 fix the issue, and the 2 commits have been applied to stable kernel v5.10, v5.15, and v5.18. 2e15c51fefaf net: atlantic: remove aq_nic_deinit() when resume 0f3325076038 net: atlantic: remove deep parameter on suspend/resume functions [Test] Verified on the system with atlantic NIC[1d6a:94c0] and run S3 test for more than 200 times. [Where problems could occur] The 2 commits remove the redundant code, aq_nic_deinit() has been called while suspending, so we don't need to call it again while resuming, and this fix the issue. I don't think this would introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981950/+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 1981773] Re: Make cm32181 sensor work after system suspend
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/1981773 Title: Make cm32181 sensor work after system suspend Status in HWE Next: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] cm32181 ambient light sensor stops working after system suspend. [Fix] Add PM support for cm32181 so it can work after system suspend. [Test] The sysfs in_illuminance_input continues to change after system suspend. [Where problems could occur] This changeset is limited to a specific device, and it already lacks PM support - so the worst case is that it stops working after resume like it always has been. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981773/+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 1981173] Re: Clear PCI errors left from BIOS
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/1981173 Title: Clear PCI errors left from BIOS Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Errors like Master Abort can be flagged before setting up PCI devices. [Fix] Clear PCI status that BIOS handed over to the OS. [Test] Using `lspci`, no more errors after boot. [Where problems could occur] If there's any driver's probe routine depends on PCI status to have different behavior, this can cause some cracks. There doesn't seem to be any driver doing such insane thing though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981173/+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 1980060] Re: Fix AMDGPU blank screen when Type-C DP alt is in use
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1980060 Title: Fix AMDGPU blank screen when Type-C DP alt is in use Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] When Type-C DP/HDMI is in use, s0ix resume renders both eDP and DP outputs blank. [Fix] Query the firmware to ensure the DP alt status. [Test] Suspend and resume the system, both eDP and Type-C DP/HDMI are working. [Where problems could occur] This fix only applies to certain AMD GFX with certain firmware version, so the scope is very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980060/+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 1152324] Re: [Lenovo b485]: Can't install precise 12.04.2 or 12.04.3 from live image or via PXE
I think you should change the source it will works. You can also visit this webiste https://apkthanos.com/raid-shadow-legends-mod-apk/ to getting the interesting images related to differet games. I am sure you issue would be 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/1152324 Title: [Lenovo b485]: Can't install precise 12.04.2 or 12.04.3 from live image or via PXE Status in linux package in Ubuntu: Incomplete Bug description: Problem, I'm currently unable to install 12.04.2 via PXE or live cd image. When trying to install via PXE the machine will hang with the following kernel messages showing: [0.004205] [Firmware Info]: CPU: Re-enabling disabled Toplogy Extensions Support [0.004254] CPU: Physical Processor ID: - [0.004293] CPU: Processor Core ID: 0 [0.004322] mce: CPU supports 7 MCE banks p0.006443] ACPI: Core revision 20120320 Whey trying to install via Live CD or Live USB I receive the following message: "If you're seeing this the installation has failed", from this point I can select to boot into single user mode, or an automated install. Selecting either causes the machine to hang with a cursor in the top left corner. Reproducable?: Yes I've reset all BIOS settings to the default values. In 12.04.1 the system will attempt to boot from the key/CD after selecting "Install Ubuntu" and proceed (trackpad is disabled and Ubuntu Desktop never loads" When trying to boot raring live image, the machine simply reboots never displaying a Grub Menu option. I have confirmed that the live images I was using are working with other machines without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152324/+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 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => In Progress
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+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 1973065] Re: Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes
Hi,
any updates on this?
thx
--
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/1973065
Title:
Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes
Status in zfs-linux package in Ubuntu:
New
Bug description:
We are currently encounter an issue in the zfsutils-package with
encrypted zvols.
The service zfs-volume-wait throws the following error message:
"Apr 22 13:08:19 test1 zvol_wait[806]: cannot open
'rpool/export/vault/block': dataset does not exist"
How to reproduce the error:
1. zpool create main /dev/sdb
2. zfs create -o encryption=on -o keylocation=prompt -o keyformat=passphrase
-V 500M main/test
3. reboot
4. systemctl status zfs-volume-wait
● zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev
Loaded: loaded (/lib/systemd/system/zfs-volume-wait.service; enabled; vendor
preset: enabled)
Active: active (exited) since Fri 2022-04-22 13:08:19 UTC; 58s ago
Process: 758 ExecStart=/sbin/zvol_wait (code=exited, status=0/SUCCESS)
Main PID: 758 (code=exited, status=0/SUCCESS)
Apr 22 13:08:19 test1 systemd[1]: Starting Wait for ZFS Volume (zvol) links
in /dev...
Apr 22 13:08:19 test1 zvol_wait[758]: Testing 1 zvol links
Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 'rpool/export/vault/block':
dataset does not exist
Apr 22 13:08:19 test1 zvol_wait[758]: All zvol links are now present.
Apr 22 13:08:19 test1 systemd[1]: Finished Wait for ZFS Volume (zvol) links
in /dev.
zfs-volume-wait service calls /sbin/zvol_wait which is part of the package
"zfsutils-linux".
Line 29, in script "zvol_wait" seems to be causing this error:
27 filter_out_locked_zvols() {
28 while read -r zvol; do
29 if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" =
"unavailable" ]; then
30 echo "$zvol"
31 fi
32 done
33 }
It seems that this command does not respect the "zfs list" syntax, which
should be
"zfs list [-r|-d depth] [-H] [-o property[,...]] [ -t type[,...]] [ -s
property ] ... [ -S property ] ... [filesystem|volume|snapshot] ..."
(https://linux.die.net/man/8/zfs)
Bug was already reported here:
# https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969457
# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997980
This fix is causing the issue:
# https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405
I created an git patch which fixes the issue:
--- zvol_wait 2022-04-21 19:09:21.57200 +
+++ zvol_wait_new 2022-04-22 13:25:26.989422811 +
@@ -26,7 +26,7 @@
filter_out_locked_zvols() {
while read -r zvol; do
- if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" =
"unavailable" ]; then
+ if ! [ "$(zfs list -H -o keystatus "$zvol")" = "unavailable" ]; then
echo "$zvol"
fi
done
After the patch was applied the command works fine:
root@test1:/sbin# zvol_wait_new
Testing 1 zvol links
All zvol links are now present.
Did i miss anything or is this really a bug?
Thank you for your help
Further information:
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Package: zfsutils-linux
Version: 0.8.3-1ubuntu12.13
Priority: extra
Section: admin
Source: zfs-linux
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian ZFS on Linux maintainers
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1,297 kB
Provides: zfsutils
Depends: libnvpair1linux (= 0.8.3-1ubuntu12.13), libuutil1linux (=
0.8.3-1ubuntu12.13), libzfs2linux (= 0.8.3-1ubuntu12.13), libzpool2linux (=
0.8.3-1ubuntu12.13), python3, libblkid1 (>= 2.16), libc6 (>= 2.17), libuuid1
(>= 2.16)
Recommends: lsb-base, zfs-zed
Suggests: nfs-kernel-server, samba-common-bin (>= 3.0.23), zfs-initramfs |
zfs-dracut
Conflicts: zfs, zfs-fuse
Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (<<
0.7.9-2)
Replaces: spl (<< 0.7.9-2), spl-dkms
Homepage: https://zfsonlinux.org/
Task: ubuntu-live, xubuntu-live, ubuntustudio-dvd-live, ubuntukylin-live,
ubuntu-mate-live, ubuntu-budgie-live
Phased-Update-Percentage: 30
Download-Size: 354 kB
APT-Manual-Installed: yes
APT-Sources: http://landscape.test.local/repository/standalone/ubuntu
focal-updates/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1973065/+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 1018020] Re: Logitech webcam not working
The issue still occurs on 5.4.0-122 with c270 Logitech. @psychonaut The two Duplicate mentions you did above (105081 and 203763) seem to be completely irrelevant with this issue. Am I missing something? -- 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/1018020 Title: Logitech webcam not working Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Quantal: Fix Released Bug description: I have two cameras on my system (one internal webcam and in my screen and a USB Logitech C270). The internal camera works fine but the external USB camera does not work - it does not display in cheese or Google+ hangouts. lsbusb device: Bus 002 Device 016: ID 046d:0825 Logitech, Inc. Webcam C270 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-1-generic 3.5.0-1.1 ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3 Uname: Linux 3.5.0-1-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.2.5-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jono 1823 F pulseaudio /dev/snd/controlC0: jono 1823 F pulseaudio /dev/snd/pcmC0D0p: jono 1823 F...m pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf252 irq 45' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21cf,0013 HDA:80862805,80860101,0010' Controls : 38 Simple ctrls : 13 Card1.Amixer.info: Card hw:1 'U0x46d0x825'/'USB Device 0x46d:0x825 at usb-:00:1d.0-1.1.3, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0825' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6144 Mono: Capture 4190 [68%] [22.36dB] [on] Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Jun 26 09:34:55 2012 HibernationDevice: RESUME=UUID=c393e27b-dbde-45a2-b4ad-173dc6b0fd94 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: LENOVO 4239CTO ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-1-generic root=UUID=e2344bde-f7a5-45a6-9ea5-c99bb4243ae1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-1-generic N/A linux-backports-modules-3.5.0-1-generic N/A linux-firmware 1.82 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1018020/+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 1982477] Re: Black screen, i915 not loaded with 5.15.0-41 (but 5.15.0-40 works)
Then we will never know... unless someone can reproduce the bug (from a dist upgrade presumably). If that doesn't happen in the next 60 days (and there are no further comments) then the bug will close automatically. -- 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/1982477 Title: Black screen, i915 not loaded with 5.15.0-41 (but 5.15.0-40 works) Status in linux package in Ubuntu: Incomplete Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leo2796 F pulseaudio /dev/snd/controlC0: leo2796 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-03 (241 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. XPS 15 9510 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2022 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0WH7HY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd05/09/2022:br1.10:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn0WH7HY:rvrA00:cvnDellInc.:ct10:cvr:sku0A61: dmi.product.family: XPS dmi.product.name: XPS 15 9510 dmi.product.sku: 0A61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+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 1982477] Re: Black screen, i915 not loaded with 5.15.0-41 (but 5.15.0-40 works)
Unfortunately I accidentally deleted the history log file from June. I think this would have been the one where we could have found more information. -- 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/1982477 Title: Black screen, i915 not loaded with 5.15.0-41 (but 5.15.0-40 works) Status in linux package in Ubuntu: Incomplete Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leo2796 F pulseaudio /dev/snd/controlC0: leo2796 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-03 (241 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. XPS 15 9510 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2022 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0WH7HY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd05/09/2022:br1.10:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn0WH7HY:rvrA00:cvnDellInc.:ct10:cvr:sku0A61: dmi.product.family: XPS dmi.product.name: XPS 15 9510 dmi.product.sku: 0A61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+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 1983656] [NEW] SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
Public bug reported: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Trent Lloyd (lathiat) Status: Confirmed ** Tags: sts ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Trent Lloyd (lathiat) ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: sts -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Confirmed Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
Hi Sergio Thanks for the response. I'm actually running a desktop installation of Jammy (Ubuntu MATE), originally 20.04 and upgraded through the non-LTS releases. After a dist-upgrade the other day I found that the mysql-server-8.0 package could not be configured and I found errors in the error log like this: 2022-08-02T04:25:16.296624Z 1 [ERROR] [MY-012962] [InnoDB] The redo log file ./#innodb_redo/#ib_redo6 size 2908160 is not a multiple of innodb_page_size I found this bug which appeared to be related. I tried `fallocate` and discovered that it created a 0 byte file instead of a sparse file of the specified size. I had a power failure yesterday afternoon. When I try it now, it works as expected! I'm pretty sure `zfs version` is the same now as it was when I ran into this problem, but somehow the reboot seems to have fixed 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/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: Fix Released Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: Fix Released Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1982477] Re: Black screen, i915 not loaded with 5.15.0-41 (but 5.15.0-40 works)
If you can find older versions of /var/log/apt/history* that contain the string "linux-generic" then that might help us understand what happened. -- 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/1982477 Title: Black screen, i915 not loaded with 5.15.0-41 (but 5.15.0-40 works) Status in linux package in Ubuntu: Incomplete Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leo2796 F pulseaudio /dev/snd/controlC0: leo2796 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-03 (241 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. XPS 15 9510 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2022 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0WH7HY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd05/09/2022:br1.10:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn0WH7HY:rvrA00:cvnDellInc.:ct10:cvr:sku0A61: dmi.product.family: XPS dmi.product.name: XPS 15 9510 dmi.product.sku: 0A61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+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 1943524] Re: [EHL] Intel ishtp VNIC driver
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1943524 Title: [EHL] Intel ishtp VNIC driver Status in intel: New Status in intel lookout-canyon series: Fix Released Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-iotg package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Released Status in linux-intel-iotg source package in Focal: New Status in linux-intel-5.13 source package in Jammy: New Status in linux-intel-iotg source package in Jammy: New Status in linux-intel-5.13 source package in Kinetic: Invalid Status in linux-intel-iotg source package in Kinetic: New Bug description: Description The driver enables a virtual network interface for communicating with a dedicated low power chip over ISHTP Hardware: ElkhartLake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.13-yocto-210727T062416Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1943524/+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 1983640] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1983640
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu Jammy)
Status: New => Incomplete
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Jammy:
Incomplete
Status in linux source package in Kinetic:
Incomplete
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+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 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
** Summary changed:
- refactoring of overlayfs fix to report the right mnt_id of files opened from
map_files
+ refactoring of overlayfs fix to properly support shiftfs
** Description changed:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce patch:
- UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using zfs/ceph
as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy we're
not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
- #!/bin/bash
+ #!/bin/bash
- cat > test.py << EOF
- import sys
+ cat > test.py << EOF
+ import sys
- f = open("/proc/self/maps")
+ f = open("/proc/self/maps")
- for l in f.readlines():
- if "python" not in l:
- continue
- print(l)
- s = l.split()
- start, end = s[0].split("-")
- fname = s[-1]
- print(start, end, fname)
- break
- else:
- sys.exit(1)
+ for l in f.readlines():
+ if "python" not in l:
+ continue
+ print(l)
+ s = l.split()
+ start, end = s[0].split("-")
+ fname = s[-1]
+ print(start, end, fname)
+ break
+ else:
+ sys.exit(1)
- test_file1 = open(fname)
- test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
+ test_file1 = open(fname)
+ test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
- fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
- fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
+ fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
+ fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
- if fdinfo1 != fdinfo2:
- print("FAIL")
- print(test_file1)
- print(fdinfo1)
- print(test_file2)
- print(fdinfo2)
- sys.exit(1)
- print("PASS")
- EOF
- sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
+ if fdinfo1 != fdinfo2:
+ print("FAIL")
+ print(test_file1)
+ print(fdinfo1)
+ print(test_file2)
+ print(fdinfo2)
+ sys.exit(1)
+ print("PASS")
+ EOF
+ sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
- Import the right pieces from AUFS to properly support the fix and get
- rid of the AUFS dependency across all our kernels.
+ Import the right pieces from AUFS to properly support the fix and get
+ rid of the AUFS dependency across all our kernels and re-apply the
+ overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions in
overlayfs, especially when containers are used.
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Jammy:
Incomplete
Status in linux source package in Kinetic:
Incomplete
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Kernel-packages] [Bug 1982477] Re: Black screen, i915 not loaded with 5.15.0-41 (but 5.15.0-40 works)
I don't really know what else to add to the matter. Should we close this bug for now? I can always reopen it should the issue happen again on the next automatic Kernel update. At least this time I know which package to look for should there be any issues. -- 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/1982477 Title: Black screen, i915 not loaded with 5.15.0-41 (but 5.15.0-40 works) Status in linux package in Ubuntu: Incomplete Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leo2796 F pulseaudio /dev/snd/controlC0: leo2796 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-03 (241 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. XPS 15 9510 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2022 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0WH7HY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd05/09/2022:br1.10:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn0WH7HY:rvrA00:cvnDellInc.:ct10:cvr:sku0A61: dmi.product.family: XPS dmi.product.name: XPS 15 9510 dmi.product.sku: 0A61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+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 1983640] Re: refactoring of overlayfs fix to report the right mnt_id of files opened from map_files
** No longer affects: linux (Ubuntu Focal)
--
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/1983640
Title:
refactoring of overlayfs fix to report the right mnt_id of files
opened from map_files
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in linux source package in Kinetic:
New
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+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 1983640] [NEW] refactoring of overlayfs fix to report the right mnt_id of files opened from map_files
Public bug reported:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using zfs/ceph
as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy we're
not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python /mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions in
overlayfs, especially when containers are used.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
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/1983640
Title:
refactoring of overlayfs fix to report the right mnt_id of files
opened from map_files
Status in linux package in Ubuntu:
New
Status in linux source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux source package in Kinetic:
New
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+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
