[Kernel-packages] [Bug 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2
I have exactly the same problem (this is on a Gigabyte Aero 15 YD 11th gen laptop), and had the same fix of migrating from v515 to v525. Annoyingly Software&Updates -> Additional Drivers is totally broken for me, too---when I select the driver and click apply something happens and a progress bar goes across the screen, and then I just get an empty error box (no title or actual message though). If someone could tell me how to extract logs from that so I could make a new issue, I'd be happy to oblige. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2012908 Title: nvidia driver 515 fails to boot on kernel 6.2 Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: I just updated my Lunar install, which brought me the 6.2 kernel, and it failed to start, stalling after enumerating my USB devices, until something times out with a message saying that the udev event queue failed to be drained. When attempting to move on to the normal graphics boot from rescue mode once the timeout is hit, I simply get a black screen. I'm blaming this on the nvidia driver because of this appearing in the log: mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for more than 120 seconds. mars 27 10:33:54 gandalf kernel: Tainted: P OE 6.2.0-18-generic #18-Ubuntu mars 27 10:33:54 gandalf kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mars 27 10:33:54 gandalf kernel: task:systemd-udevd state:D stack:0 pid:304 ppid:258flags:0x4006 mars 27 10:33:54 gandalf kernel: Call Trace: mars 27 10:33:54 gandalf kernel: mars 27 10:33:54 gandalf kernel: __schedule+0x2aa/0x610 mars 27 10:33:54 gandalf kernel: schedule+0x63/0x110 mars 27 10:33:54 gandalf kernel: schedule_preempt_disabled+0x15/0x30 mars 27 10:33:54 gandalf kernel: __mutex_lock.constprop.0+0x3f8/0x7a0 mars 27 10:33:54 gandalf kernel: ? __kmem_cache_alloc_node+0x19d/0x340 mars 27 10:33:54 gandalf kernel: ? nv_drm_calloc+0x1e/0x40 [nvidia_drm] mars 27 10:33:54 gandalf kernel: __mutex_lock_slowpath+0x13/0x20 mars 27 10:33:54 gandalf kernel: mutex_lock+0x3c/0x50 mars 27 10:33:54 gandalf kernel: __nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_connector_detect+0xe/0x20 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_helper_probe_detect_ctx+0xa3/0x120 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: check_connector_changed+0x52/0x200 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: drm_helper_hpd_irq_event+0xbc/0x170 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: nv_drm_load+0x2e7/0x480 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_dev_register+0x10e/0x250 [drm] mars 27 10:33:54 gandalf kernel: nv_drm_probe_devices+0x111/0x200 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_init_module+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_init+0x1e/0x60 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_linux_drm_init+0xe/0xff0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: do_one_initcall+0x5e/0x250 mars 27 10:33:54 gandalf kernel: do_init_module+0x7b/0x260 mars 27 10:33:54 gandalf kernel: load_module+0xc76/0xd60 mars 27 10:33:54 gandalf kernel: ? kernel_read_file+0x2a4/0x320 mars 27 10:33:54 gandalf kernel: __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: ? __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: __x64_sys_finit_module+0x18/0x30 mars 27 10:33:54 gandalf kernel: do_syscall_64+0x5b/0x90 mars 27 10:33:54 gandalf kernel: ? ksys_mmap_pgoff+0x120/0x260 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 ORIG_RAX: 0139 mars 27 10:33:54 gandalf kernel: RAX: ff
[Kernel-packages] [Bug 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2
(Extra sad is that external monitors are broken on the ~3000 Series Laptop GPUs with v525, see https://github.com/NVIDIA/open-gpu-kernel- modules/issues/419. So 23.04 might cause some problems upon release, until a package for the fixed v530 comes out.) ** Bug watch added: github.com/NVIDIA/open-gpu-kernel-modules/issues #419 https://github.com/NVIDIA/open-gpu-kernel-modules/issues/419 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2012908 Title: nvidia driver 515 fails to boot on kernel 6.2 Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: I just updated my Lunar install, which brought me the 6.2 kernel, and it failed to start, stalling after enumerating my USB devices, until something times out with a message saying that the udev event queue failed to be drained. When attempting to move on to the normal graphics boot from rescue mode once the timeout is hit, I simply get a black screen. I'm blaming this on the nvidia driver because of this appearing in the log: mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for more than 120 seconds. mars 27 10:33:54 gandalf kernel: Tainted: P OE 6.2.0-18-generic #18-Ubuntu mars 27 10:33:54 gandalf kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mars 27 10:33:54 gandalf kernel: task:systemd-udevd state:D stack:0 pid:304 ppid:258flags:0x4006 mars 27 10:33:54 gandalf kernel: Call Trace: mars 27 10:33:54 gandalf kernel: mars 27 10:33:54 gandalf kernel: __schedule+0x2aa/0x610 mars 27 10:33:54 gandalf kernel: schedule+0x63/0x110 mars 27 10:33:54 gandalf kernel: schedule_preempt_disabled+0x15/0x30 mars 27 10:33:54 gandalf kernel: __mutex_lock.constprop.0+0x3f8/0x7a0 mars 27 10:33:54 gandalf kernel: ? __kmem_cache_alloc_node+0x19d/0x340 mars 27 10:33:54 gandalf kernel: ? nv_drm_calloc+0x1e/0x40 [nvidia_drm] mars 27 10:33:54 gandalf kernel: __mutex_lock_slowpath+0x13/0x20 mars 27 10:33:54 gandalf kernel: mutex_lock+0x3c/0x50 mars 27 10:33:54 gandalf kernel: __nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_connector_detect+0xe/0x20 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_helper_probe_detect_ctx+0xa3/0x120 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: check_connector_changed+0x52/0x200 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: drm_helper_hpd_irq_event+0xbc/0x170 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: nv_drm_load+0x2e7/0x480 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_dev_register+0x10e/0x250 [drm] mars 27 10:33:54 gandalf kernel: nv_drm_probe_devices+0x111/0x200 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_init_module+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_init+0x1e/0x60 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_linux_drm_init+0xe/0xff0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: do_one_initcall+0x5e/0x250 mars 27 10:33:54 gandalf kernel: do_init_module+0x7b/0x260 mars 27 10:33:54 gandalf kernel: load_module+0xc76/0xd60 mars 27 10:33:54 gandalf kernel: ? kernel_read_file+0x2a4/0x320 mars 27 10:33:54 gandalf kernel: __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: ? __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: __x64_sys_finit_module+0x18/0x30 mars 27 10:33:54 gandalf kernel: do_syscall_64+0x5b/0x90 mars 27 10:33:54 gandalf kernel: ? ksys_mmap_pgoff+0x120/0x260 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 ORIG_RAX: 0139 mars 27 10:33:54 gandalf kernel: RAX: ffda RBX: 55f373907c60 RCX: 7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RDX: RSI
[Kernel-packages] [Bug 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2
After updating the machine doesn't hang anymore, but I do get: me@mymachine:~$ nvidia-smi Failed to initialize NVML: Driver/library version mismatch at the terminal now. (Also, this version of 515 seems to bork external displays on my machine too... :() -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2012908 Title: nvidia driver 515 fails to boot on kernel 6.2 Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Bug description: I just updated my Lunar install, which brought me the 6.2 kernel, and it failed to start, stalling after enumerating my USB devices, until something times out with a message saying that the udev event queue failed to be drained. When attempting to move on to the normal graphics boot from rescue mode once the timeout is hit, I simply get a black screen. I'm blaming this on the nvidia driver because of this appearing in the log: mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for more than 120 seconds. mars 27 10:33:54 gandalf kernel: Tainted: P OE 6.2.0-18-generic #18-Ubuntu mars 27 10:33:54 gandalf kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mars 27 10:33:54 gandalf kernel: task:systemd-udevd state:D stack:0 pid:304 ppid:258flags:0x4006 mars 27 10:33:54 gandalf kernel: Call Trace: mars 27 10:33:54 gandalf kernel: mars 27 10:33:54 gandalf kernel: __schedule+0x2aa/0x610 mars 27 10:33:54 gandalf kernel: schedule+0x63/0x110 mars 27 10:33:54 gandalf kernel: schedule_preempt_disabled+0x15/0x30 mars 27 10:33:54 gandalf kernel: __mutex_lock.constprop.0+0x3f8/0x7a0 mars 27 10:33:54 gandalf kernel: ? __kmem_cache_alloc_node+0x19d/0x340 mars 27 10:33:54 gandalf kernel: ? nv_drm_calloc+0x1e/0x40 [nvidia_drm] mars 27 10:33:54 gandalf kernel: __mutex_lock_slowpath+0x13/0x20 mars 27 10:33:54 gandalf kernel: mutex_lock+0x3c/0x50 mars 27 10:33:54 gandalf kernel: __nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_connector_detect+0xe/0x20 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_helper_probe_detect_ctx+0xa3/0x120 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: check_connector_changed+0x52/0x200 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: drm_helper_hpd_irq_event+0xbc/0x170 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: nv_drm_load+0x2e7/0x480 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_dev_register+0x10e/0x250 [drm] mars 27 10:33:54 gandalf kernel: nv_drm_probe_devices+0x111/0x200 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_init_module+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_init+0x1e/0x60 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_linux_drm_init+0xe/0xff0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: do_one_initcall+0x5e/0x250 mars 27 10:33:54 gandalf kernel: do_init_module+0x7b/0x260 mars 27 10:33:54 gandalf kernel: load_module+0xc76/0xd60 mars 27 10:33:54 gandalf kernel: ? kernel_read_file+0x2a4/0x320 mars 27 10:33:54 gandalf kernel: __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: ? __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: __x64_sys_finit_module+0x18/0x30 mars 27 10:33:54 gandalf kernel: do_syscall_64+0x5b/0x90 mars 27 10:33:54 gandalf kernel: ? ksys_mmap_pgoff+0x120/0x260 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 ORIG_RAX: 0139 mars 27 10:33:54 gandalf kernel: RAX: ffda RBX: 55f373907c60 RCX: 7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RDX: RSI: 55f373889af0 RDI: 0012 mars 27 10:33:54 gandalf kernel: RBP: 55f373889af0 R08: R09: 7ffc
[Kernel-packages] [Bug 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot
I have just upgraded to 23.10 beta and have a large number of these spammed to the console. Does that patch fix the problem? Is there any more information you need?/why didn't that patch go into Linux 6.5? -- 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/2028830 Title: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu release: sune@jekaterina:~/src/deb$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 sune@jekaterina:~/src/deb$ Package: linux-image- unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also affected) Expectation: System boots normally Actual results: See below On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing list, I hereby submit the following: Do note that two "types" are mentioned, and that I am willing the assist in testing, as, obviously, I have a system with a controller covered by the mpt3sas driver. This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is similar to rcs 1 and 2: UBSAN: array-index-out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12 index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12 index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index—out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of-bounds in /home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7 index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c::21 index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]' UBSAN: array-index—out—of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of—bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12 index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [EDIT] the next error, repeating for ~1½ hours before finishing boot, was unrelated to mpt2sas and UBSAN. That error was "Timed out for waiting the udey queue being empty." Bug subject altered to reflect this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
FYI everyone, another corruption-with-zeros bug was found (so this issue
was not completely fixed): https://github.com/openzfs/zfs/issues/15933
The fixed was committed last week, and is not yet part of a release:
https://github.com/openzfs/zfs/pull/16019
** Bug watch added: github.com/openzfs/zfs/issues #15933
https://github.com/openzfs/zfs/issues/15933
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Jammy:
Fix Released
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
@Paul no, it isn't. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: Incomplete Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1318951] Re: kernel update fails with /boot on FAT32
This bug just caused me the 24.04.1 installer to crash during a fresh install (due to VFAT /boot). -- 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/1318951 Title: kernel update fails with /boot on FAT32 Status in dpkg package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-base package in Ubuntu: Confirmed Status in dpkg package in Debian: New Status in linux-base package in Debian: New Bug description: My latest system upgrade failed because it can't upgrade the kernel: $sudo env LANGUAGE=en_US apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-signed-image-3.13.0-24-generic : Depends: linux-image-3.13.0-24-generic (= 3.13.0-24.47) but 3.13.0-24.46 is installed E: Unmet dependencies. Try using -f. When trying to install linux-image-3.13.0-24-generic manually it fails because it can't create a backup link for the old kernel. This really doesn't surprise me, because /boot is on a fat32 filesystem ( EFI System Partition ) so it shouldn't be possible to create any links at all. My fstab entries for boot are as follows: UUID=0E1E-3E58/mnt/efi vfatdefaults 0 2 /mnt/efi/ubuntu /boot none bind0 0 Here is the output of me trying to install the kernel manually: $sudo env LANGUAGE=en_US apt-get install linux-image-3.13.0-24-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: efibootmgr secureboot-db shim Use 'apt-get autoremove' to remove them. Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools Recommended packages: grub-pc grub-efi-amd64 grub-efi-ia32 grub lilo The following packages will be upgraded: linux-image-3.13.0-24-generic 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 114 not fully installed or removed. Need to get 0 B/15,0 MB of archives. After this operation, 1.024 B disk space will be freed. (Reading database ... 205799 files and directories currently installed.) Preparing to unpack .../linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb ... Done. Unpacking linux-image-3.13.0-24-generic (3.13.0-24.47) over (3.13.0-24.46) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb (--unpack): unable to make backup link of `./boot/vmlinuz-3.13.0-24-generic' before installing new version: Operation not permitted dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb E : Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1318951/+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
