[Kernel-packages] [Bug 2063150] Re: No sound, stutters and clicks after upgrade to 24.04
I completely removed pulseaudio and left it removed: sudo apt remove pulseaudio Then I reinstalled pipewire: sudo apt install --reinstall pipewire Audio seems to be working fine now for a couple of weeks. Only problem that remaiins is alsamixer volumes are low or muted after every reboot. -- 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/2063150 Title: No sound, stutters and clicks after upgrade to 24.04 Status in linux package in Ubuntu: Expired Status in pipewire package in Ubuntu: Invalid Bug description: After upgrading from Ubuntu 23.10 to 24.04, it does not work on the computer. Work with: 1) Bluetooth 2) Jack 3.5 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:52:58 2024 InstallationDate: Installed on 2024-03-25 (28 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: pipewire UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+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 1950792] Re: No boot possible - Cannot open root device
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Expired Status in linux package in Ubuntu: Expired Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+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 1950792] Re: No boot possible - Cannot open root device
[Expired for MAAS because there has been no activity for 60 days.] ** Changed in: maas Status: Incomplete => Expired -- 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/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Expired Status in linux package in Ubuntu: Expired Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+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 2065076] Re: nvidia failure to resume from suspend; kernel fallback broken
-- 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/2065076 Title: nvidia failure to resume from suspend; kernel fallback broken Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-550 package in Ubuntu: Confirmed Bug description: I am unable to resume from suspend. The system comes back on but the screen is black. Switching to a virtual console to look for a solution is impossible as the keyboard appears to be dead. The issue is far from new and and goes as far back (for me) as 22.04. Until 23.10, however, it could be worked around by disabling the systemd suspend mechanism (disable nvidia-suspend, nvidia-hibernate and nvidia-resumpe). The system would then use the kernel driver fallback instead, which worked fine. Until now. I have tried nvida drivers 535 and 550. Neither worked. I have enabled the graphics-drivers ppa to test the latest available driver, which is a newer version of the 550 driver included in the repositories. No luck. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:codey 2877 F pipewire /dev/snd/controlC0: codey 2881 F wireplumber /dev/snd/controlC1: codey 2881 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 7 16:38:34 2024 InstallationDate: Installed on 2022-03-27 (772 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: System manufacturer System Product Name ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=3e125bf2-3409-4f46-8a06-bba9a5fa9032 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6063 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065076/+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 2077487] Re: Broken atime in 2.2.2-0ubuntu9 (noble's version)
It did not fix for me. please check below: root@zfs-test:/zfs# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.04.1 LTS Release:24.04 Codename: noble root@zfs-test:/zfs# dpkg -s zfsutils-linux | grep '^Version:' Version: 2.2.2-0ubuntu9.1 root@zfs-test:/zfs# touch file root@zfs-test:/zfs# stat file File: file Size: 0 Blocks: 1 IO Block: 131072 regular empty file Device: 0,33Inode: 128 Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) Access: 1970-01-01 00:00:00.0 + Modify: 2024-10-05 08:10:33.558526613 + Change: 2024-10-05 08:10:33.558526613 + Birth: 2024-10-05 08:10:33.558526613 + root@zfs-test:/zfs# cat file root@zfs-test:/zfs# stat file File: file Size: 0 Blocks: 1 IO Block: 131072 regular empty file Device: 0,33Inode: 128 Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) Access: 2024-10-05 08:10:39.050528093 + Modify: 2024-10-05 08:10:33.558526613 + Change: 2024-10-05 08:10:33.558526613 + Birth: 2024-10-05 08:10:33.558526613 + root@zfs-test:/zfs# uname -a Linux zfs-test 6.8.0-45-generic #45-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 30 12:02:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux -- 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/2077487 Title: Broken atime in 2.2.2-0ubuntu9 (noble's version) Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Status in linux-hwe-6.8 source package in Noble: Invalid Status in zfs-linux source package in Noble: Fix Committed Bug description: SRU Justification [Impact] * 2.2.2-0ubuntu9 has the 6.7 compat series, including https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, but does not include the fix for that commit (affects both pre-6.7 and post-6.7), https://github.com/openzfs/zfs/commit/f0bf7a247dbb030d68c7fd2b5526dd111cc775d0. This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel as writes to a file resetting atime back to 0 (reads still seem to work as expected though given that state), which of course breaks real-world things (in my case, I can no longer successfully run LLVM's test suite). Thanks to CONFIG_INIT_STACK_ALL_ZERO=y being the default it seems like this isn't a kernel memory disclosure and is instead a deterministic use of 0, so I don't believe this to be a blatant security vulnerability. This also explains the behaviour observed above. This needs fixing in noble, and then propagating back through whatever kernels are pulling in this version, since linux-modules vendors copies of the pre-built DKMS modules, with the current 6.8 HWE kernel using 2.2.2-0ubuntu9 explicitly. [Fix] * Include f0bf7a247dbb: "[PATCH] Linux 6.7 compat: zfs_setattr fix atime update" from upstream ZFS as quilt patch. [Test Case] * Build tested against Noble generic * Ran autopkgktests for regressions, none encountered * Ran the following test case: Using zfs-linux 2.2.2-0ubuntu9 $ cd /path/to/zfs $ rm -f foo $ touch foo $ stat foo $ # observe initial access time of 0 since epoch (1970-01-01) Using zfs-linux 2.2.2-0ubuntu9.1 $ cd /path/to/zfs $ rm -f foo $ touch foo $ stat foo $ # observe initial access time same as modify/change/birth Also see results attached as "zfs-bad" and "zfs-good", respectively [Where things could go wrong] * Low chance of regression, isolated instantiation and logic fix. * Addition of time delta check could cause issues during unexpected delay > 2 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077487/+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 2065076] Re: nvidia failure to resume from suspend; kernel fallback broken
Solution which added by Jurgen in post #8 didn't work with version 550. Any solution? -- 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/2065076 Title: nvidia failure to resume from suspend; kernel fallback broken Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-550 package in Ubuntu: Confirmed Bug description: I am unable to resume from suspend. The system comes back on but the screen is black. Switching to a virtual console to look for a solution is impossible as the keyboard appears to be dead. The issue is far from new and and goes as far back (for me) as 22.04. Until 23.10, however, it could be worked around by disabling the systemd suspend mechanism (disable nvidia-suspend, nvidia-hibernate and nvidia-resumpe). The system would then use the kernel driver fallback instead, which worked fine. Until now. I have tried nvida drivers 535 and 550. Neither worked. I have enabled the graphics-drivers ppa to test the latest available driver, which is a newer version of the 550 driver included in the repositories. No luck. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:codey 2877 F pipewire /dev/snd/controlC0: codey 2881 F wireplumber /dev/snd/controlC1: codey 2881 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 7 16:38:34 2024 InstallationDate: Installed on 2022-03-27 (772 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: System manufacturer System Product Name ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=3e125bf2-3409-4f46-8a06-bba9a5fa9032 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6063 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065076/+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 2077487] Re: Broken atime in 2.2.2-0ubuntu9 (noble's version)
Where is your module coming from though? Normally it’s pre-built in linux-modules or an HWE version thereof, so you need to either use the zfs-linux one or get an updated linux-modules. -- 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/2077487 Title: Broken atime in 2.2.2-0ubuntu9 (noble's version) Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Status in linux-hwe-6.8 source package in Noble: Invalid Status in zfs-linux source package in Noble: Fix Committed Bug description: SRU Justification [Impact] * 2.2.2-0ubuntu9 has the 6.7 compat series, including https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, but does not include the fix for that commit (affects both pre-6.7 and post-6.7), https://github.com/openzfs/zfs/commit/f0bf7a247dbb030d68c7fd2b5526dd111cc775d0. This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel as writes to a file resetting atime back to 0 (reads still seem to work as expected though given that state), which of course breaks real-world things (in my case, I can no longer successfully run LLVM's test suite). Thanks to CONFIG_INIT_STACK_ALL_ZERO=y being the default it seems like this isn't a kernel memory disclosure and is instead a deterministic use of 0, so I don't believe this to be a blatant security vulnerability. This also explains the behaviour observed above. This needs fixing in noble, and then propagating back through whatever kernels are pulling in this version, since linux-modules vendors copies of the pre-built DKMS modules, with the current 6.8 HWE kernel using 2.2.2-0ubuntu9 explicitly. [Fix] * Include f0bf7a247dbb: "[PATCH] Linux 6.7 compat: zfs_setattr fix atime update" from upstream ZFS as quilt patch. [Test Case] * Build tested against Noble generic * Ran autopkgktests for regressions, none encountered * Ran the following test case: Using zfs-linux 2.2.2-0ubuntu9 $ cd /path/to/zfs $ rm -f foo $ touch foo $ stat foo $ # observe initial access time of 0 since epoch (1970-01-01) Using zfs-linux 2.2.2-0ubuntu9.1 $ cd /path/to/zfs $ rm -f foo $ touch foo $ stat foo $ # observe initial access time same as modify/change/birth Also see results attached as "zfs-bad" and "zfs-good", respectively [Where things could go wrong] * Low chance of regression, isolated instantiation and logic fix. * Addition of time delta check could cause issues during unexpected delay > 2 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077487/+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 2077487] Re: Broken atime in 2.2.2-0ubuntu9 (noble's version)
I can confirm that zfs-dkms 2.2.2-0ubuntu9.1 in noble-proposed fixes this bug, and verified that it was reproducible with zfs-dkms 2.2.2-0ubuntu9, not just the linux-modules binary. ** Tags added: verification-done-noble -- 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/2077487 Title: Broken atime in 2.2.2-0ubuntu9 (noble's version) Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Status in linux-hwe-6.8 source package in Noble: Invalid Status in zfs-linux source package in Noble: Fix Committed Bug description: SRU Justification [Impact] * 2.2.2-0ubuntu9 has the 6.7 compat series, including https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, but does not include the fix for that commit (affects both pre-6.7 and post-6.7), https://github.com/openzfs/zfs/commit/f0bf7a247dbb030d68c7fd2b5526dd111cc775d0. This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel as writes to a file resetting atime back to 0 (reads still seem to work as expected though given that state), which of course breaks real-world things (in my case, I can no longer successfully run LLVM's test suite). Thanks to CONFIG_INIT_STACK_ALL_ZERO=y being the default it seems like this isn't a kernel memory disclosure and is instead a deterministic use of 0, so I don't believe this to be a blatant security vulnerability. This also explains the behaviour observed above. This needs fixing in noble, and then propagating back through whatever kernels are pulling in this version, since linux-modules vendors copies of the pre-built DKMS modules, with the current 6.8 HWE kernel using 2.2.2-0ubuntu9 explicitly. [Fix] * Include f0bf7a247dbb: "[PATCH] Linux 6.7 compat: zfs_setattr fix atime update" from upstream ZFS as quilt patch. [Test Case] * Build tested against Noble generic * Ran autopkgktests for regressions, none encountered * Ran the following test case: Using zfs-linux 2.2.2-0ubuntu9 $ cd /path/to/zfs $ rm -f foo $ touch foo $ stat foo $ # observe initial access time of 0 since epoch (1970-01-01) Using zfs-linux 2.2.2-0ubuntu9.1 $ cd /path/to/zfs $ rm -f foo $ touch foo $ stat foo $ # observe initial access time same as modify/change/birth Also see results attached as "zfs-bad" and "zfs-good", respectively [Where things could go wrong] * Low chance of regression, isolated instantiation and logic fix. * Addition of time delta check could cause issues during unexpected delay > 2 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077487/+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
