[Kernel-packages] [Bug 2012908] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657757/+files/UdevDb.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657758/+files/WifiSyslog.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27
[Kernel-packages] [Bug 2012908] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657756/+files/RfKill.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657759/+files/acpidump.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2
The issue doesn't show when using the 525 driver. -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54 gandalf kernel: R13: 55f37389c120 R14: R15: 55f373909080 mars
[Kernel-packages] [Bug 2011817] Re: Intel Alder Lake GPU performance much lower in 6.1/6.2 compared to 5.19
** Changed in: linux (Ubuntu) Milestone: None => ubuntu-23.04 -- 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/2011817 Title: Intel Alder Lake GPU performance much lower in 6.1/6.2 compared to 5.19 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Intel Alder Lake GPU performance is much lower in 6.1 compared to 5.19. For example, benchmarking gnome-shell main running on Xorg: 6.1.0-16-generic 30.02 FPS, average: 15.5ms, peak: 16.4ms intel_gpu_top says 211/208 MHz despite gt_min_freq_mhz==300 5.19.0-21-generic 60.00 FPS, average: 8.3ms, peak: 8.7ms intel_gpu_top says 542/560 MHz The issue is so severe in 6.1.0-16-generic that even triple buffering can't fix it for Xorg sessions. It does for Wayland though. I can work around it with `cp gt_max_freq_mhz gt_min_freq_mhz` but probably shouldn't need to. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.1.0-16-generic 6.1.0-16.16 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1730 F wireplumber /dev/snd/seq:dan1727 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Mar 16 19:31:50 2023 InstallationDate: Installed on 2022-11-28 (108 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=3a6db1e7-0341-452a-80e1-2895838feeac ro quiet splash vt.handoff=7 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.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230302.git60971a64-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2011817/+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 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 1986717] Re: [SRU]Update ice driver to support E823 devices
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2196 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4382 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-23559 -- 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/1986717 Title: [SRU]Update ice driver to support E823 devices Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification: [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low These patches did not cherry pick cleanly I had to make some minor changes. Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+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 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
This bug was fixed in the package linux-aws-5.19 - 5.19.0-1022.23~22.04.1 --- linux-aws-5.19 (5.19.0-1022.23~22.04.1) jammy; urgency=medium * jammy/linux-aws-5.19: 5.19.0-1022.23~22.04.1 -proposed tracker (LP: #2011999) [ Ubuntu: 5.19.0-1022.23 ] * kinetic/linux-aws: 5.19.0-1022.23 -proposed tracker (LP: #2011996) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux-aws-5.19 (5.19.0-1021.22~22.04.1) jammy; urgency=medium * jammy/linux-aws-5.19: 5.19.0-1021.22~22.04.1 -proposed tracker (LP: #2008286) * Packaging resync (LP: #1786013) - [Packaging] update variants * dependency on crda obsolete according to Debian (LP: #1958918) - [Packaging] aws-5.19: crda|wireless crda is obsolete [ Ubuntu: 5.19.0-1021.22 ] * kinetic/linux-aws: 5.19.0-1021.22 -proposed tracker (LP: #2008287) * kinetic/linux: 5.19.0-37.38 -proposed tracker (LP: #2008305) * XPS 9320 screen flicker on UHD panel 3840x2400 (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 (LP: #2000709) - selftest: net: Improve IPV6_TCLASS/IPV6_HOPLIMIT tests apparmor compatibility * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2023-0469 - io_uring/filetable: fix file reference underflow * Improve arp_ndisc_evict_nocarrier.sh test result processing (LP: #2006546) - selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier * Make cm32181 sensor work after system suspend (LP: #1981773) - iio: light: cm32181: Add PM support * Fix Thunderbolt device hotplug fail when connect via thunderbolt dock (LP: #1991366) - PCI: Fix used_buses calculation in pci_scan_child_bus_extend() - PCI: Pass available buses even if the bridge is already configured - PCI: Move pci_assign_unassigned_root_bus_resources() - PCI: Fix whitespace and indentation - PCI: Fix typo in pci_scan_child_bus_extend() * arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K (LP: #1968310) - selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier * Screen freeze after resuming from suspend (nvme0: I/O timeout) (LP: #1996048) - PCI: vmd: Disable MSI remapping after suspend * RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode (LP: #1993561) - drm/i915/display: Drop check for doublescan mode in modevalid - drm/i915/display: Prune Interlace modes for Display >=12 * udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) (LP: #2000708) - selftests/net: mv bpf/nat6to4.c to net folder * selftests/.../nat6to4 breaks the selftests build (LP: #1996536) - selftests: net: Add cross-compilation support for BPF programs - selftests: net: Fix O=dir builds * CVE-2023-0266 // CVE-2023-0266 was assigned for this issue. - ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * Kinetic update: upstream stable patchset 2023-02-02 (LP: #2004602) - clk: generalize devm_clk_get() a bit - clk: Provide new devm_clk helpers for prepared and enabled clocks - mmc: mtk-sd: Fix missing clk_disable_unprepare in msdc_of_clock_parse() - arm64: dts: rockchip: keep I2S1 disabled for GPIO function on ROCK Pi 4 series - arm: dts: rockchip: fix node name for hym8563 rtc - arm: dts: rockchip: remove clock-frequency from rtc - ARM: dts: rockchip: fix ir-receiver node names - arm64: dts: rockchip: fix ir-receiver node names - ARM: dts: rockchip: rk3188: fix lcdc1-rgb24 node name - fs: use acquire ordering in __fget_light() - ARM: 9251/1: perf: Fix stacktraces for tracepoint events in THUMB2 kernels - ARM: 9266/1: mm: fix no-MMU ZERO_PAGE() implementation - ASoC: wm8962: Wait for updated value of WM8962_CLOCKING1 register - spi: mediatek: Fix DEVAPC Violation at KO Remove - ARM: dts: rockchip: disable arm_global_timer on rk3066 and rk3188 - ASoC: rt711-sdca: fix the latency time of clock stop prepare state machine transitions - 9p/fd: Use P9_HDRSZ for header size - regulator: slg51000: Wait after asserting CS pin - ALSA: seq: Fix function prototype mismatch in
[Kernel-packages] [Bug 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-41218 -- 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/1951447 Title: ubuntu_kernel_selftests: net:udpgso_bench.sh failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: 04:41:59 DEBUG| [stdout] # selftests: net: udpgso_bench.sh 04:41:59 DEBUG| [stdout] # ipv4 04:41:59 DEBUG| [stdout] # tcp 04:42:00 DEBUG| [stdout] # tcp tx: 2736 MB/s46415 calls/s 46415 msg/s 04:42:00 DEBUG| [stdout] # tcp rx: 2737 MB/s46161 calls/s 04:42:01 DEBUG| [stdout] # tcp tx: 2735 MB/s46392 calls/s 46392 msg/s 04:42:01 DEBUG| [stdout] # tcp rx: 2739 MB/s46226 calls/s 04:42:02 DEBUG| [stdout] # tcp tx: 2717 MB/s46092 calls/s 46092 msg/s 04:42:02 DEBUG| [stdout] # tcp zerocopy 04:42:02 DEBUG| [stdout] # ./udpgso_bench_tx: connect: Connection refused 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: PASS=17 SKIP=0 FAIL=1 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: ^[[0;31mFAIL^[[0m 04:42:54 DEBUG| [stdout] not ok 1 selftests: net: udpgso_bench.sh # exit=1 04:42:54 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 04:42:54 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 252, in run_once raise error.TestError(test_name + ' failed.') TestError: net:udpgso_bench.sh failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951447/+subscriptions --
[Kernel-packages] [Bug 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-41218 -- 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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+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 2012907] [NEW] bluetooth does not work on my HONOR MagicBook 16 Series
Public bug reported: Hello. bluetooth does not work on my HONOR MagicBook 16 Series. Bluetooth does not turn on through the settings ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 18:57:58 2023 InstallationDate: Installed on 2023-03-25 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2012907 Title: bluetooth does not work on my HONOR MagicBook 16 Series Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Hello. bluetooth does not work on my HONOR MagicBook 16 Series. Bluetooth does not turn on through the settings ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 18:57:58 2023 InstallationDate: Installed on 2023-03-25 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2012907/+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 2012918] [NEW] Spotify completely freezes Ubuntu
Public bug reported: Mar 27 12:50:37 juliuswork kernel: [ 9754.386159] amdgpu :05:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32781, for process spotify pid 23781 thread spotify:cs0 pid 23841) Mar 27 12:50:37 juliuswork kernel: [ 9754.386161] amdgpu :05:00.0: amdgpu: in page starting at address 0x800104a2 from IH client 0x12 (VMC) Mar 27 12:50:37 juliuswork kernel: [ 9754.386164] amdgpu :05:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140050 Mar 27 12:50:37 juliuswork kernel: [ 9754.386165] amdgpu :05:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Mar 27 12:50:37 juliuswork kernel: [ 9754.386166] amdgpu :05:00.0: amdgpu: MORE_FAULTS: 0x0 Mar 27 12:50:37 juliuswork kernel: [ 9754.386167] amdgpu :05:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 27 12:50:37 juliuswork kernel: [ 9754.386168] amdgpu :05:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Mar 27 12:50:37 juliuswork kernel: [ 9754.386170] amdgpu :05:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 27 12:50:37 juliuswork kernel: [ 9754.386171] amdgpu :05:00.0: amdgpu: RW: 0x1 Mar 27 12:50:38 juliuswork kernel: [ 9755.937890] sysrq: This sysrq operation is disabled. Mar 27 12:50:39 juliuswork kernel: [ 9756.179881] sysrq: This sysrq operation is disabled. Mar 27 12:50:39 juliuswork kernel: [ 9756.521888] sysrq: This sysrq operation is disabled. Mar 27 12:50:39 juliuswork kernel: [ 9756.803881] sysrq: Emergency Sync Mar 27 12:50:39 juliuswork kernel: [ 9756.812831] Emergency Sync complete Mar 27 12:50:39 juliuswork kernel: [ 9757.025886] sysrq: This sysrq operation is disabled. Mar 27 12:50:41 juliuswork kernel: [ 9758.415886] sysrq: This sysrq operation is disabled. Mar 27 12:50:41 juliuswork kernel: [ 9758.598109] sysrq: This sysrq operation is disabled. Mar 27 12:50:42 juliuswork kernel: [ 9759.389853] gmc_v9_0_process_interrupt: 187338 callbacks suppressed Mar 27 12:50:42 juliuswork kernel: [ 9759.389859] amdgpu :05:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32781, for process spotify pid 23781 thread spotify:cs0 pid 23841) Mar 27 12:50:42 juliuswork kernel: [ 9759.389866] amdgpu :05:00.0: amdgpu: in page starting at address 0x800104a2 from IH client 0x12 (VMC) Mar 27 12:50:42 juliuswork kernel: [ 9759.389870] amdgpu :05:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Mar 27 12:50:42 juliuswork kernel: [ 9759.389872] amdgpu :05:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Mar 27 12:50:42 juliuswork kernel: [ 9759.389874] amdgpu :05:00.0: amdgpu: MORE_FAULTS: 0x1 Mar 27 12:50:42 juliuswork kernel: [ 9759.389876] amdgpu :05:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389877] amdgpu :05:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Mar 27 12:50:42 juliuswork kernel: [ 9759.389878] amdgpu :05:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389879] amdgpu :05:00.0: amdgpu: RW: 0x1 Mar 27 12:50:42 juliuswork kernel: [ 9759.389882] amdgpu :05:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32781, for process spotify pid 23781 thread spotify:cs0 pid 23841) Mar 27 12:50:42 juliuswork kernel: [ 9759.389885] amdgpu :05:00.0: amdgpu: in page starting at address 0x800104a2 from IH client 0x12 (VMC) Mar 27 12:50:42 juliuswork kernel: [ 9759.389888] amdgpu :05:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140050 Mar 27 12:50:42 juliuswork kernel: [ 9759.389889] amdgpu :05:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Mar 27 12:50:42 juliuswork kernel: [ 9759.389890] amdgpu :05:00.0: amdgpu: MORE_FAULTS: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389892] amdgpu :05:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389893] amdgpu :05:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Mar 27 12:50:42 juliuswork kernel: [ 9759.389894] amdgpu :05:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389895] amdgpu :05:00.0: amdgpu: RW: 0x1 Mar 27 12:50:42 juliuswork kernel: [ 9759.389907] amdgpu :05:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32781, for process spotify pid 23781 thread spotify:cs0 pid 23841) Mar 27 12:50:42 juliuswork kernel: [ 9759.389909] amdgpu :05:00.0: amdgpu: in page starting at address 0x800104a2 from IH client 0x12 (VMC) Mar 27 12:50:42 juliuswork kernel: [ 9759.389912] amdgpu :05:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140050 Mar 27 12:50:42 juliuswork kernel: [ 9759.389913] amdgpu :05:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Mar 27 12:50:42 juliuswork kernel: [ 9759.389914] amdgpu :05:00.0: amdgpu: MORE_FAULTS: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389915] amdgpu :05:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389917] amdgpu :05:00.0: amdgpu:
[Kernel-packages] [Bug 2008136] Re: netfilter: flowtable: add counter support in HW offload
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2008136 Title: netfilter: flowtable: add counter support in HW offload Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) While conntrack tuples are offloaded to hardware and conntrack packet accounting is enabled, offloaded packets aren't counted. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. ef803b3cf96a netfilter: flowtable: add counter support in HW offload 9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add() note: need to change a little due to cherry-pick conflict with 24384e28586c netfilter: flowtable: Set offload timeouts according to proto values * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a TCP connection, e.g: on mlx5 VF1 iperf -s on mlx5 VF2 iperf -c -t 10 Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi tcp and see no iperf tcp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i See counters (packets=.*) advancing while tuples were offloaded: ipv4 2 tcp 6 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008136/+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 2007581] Re: gpio: Restrict usage of GPIO chip irq members before initialization
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2007581 Title: gpio: Restrict usage of GPIO chip irq members before initialization Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] GPIO chip irq members are exposed before they could be completely initialized and this leads to race conditions. One such issue was observed for the gc->irq.domain variable which was accessed through the pwr-mlxbf.c driver in gpiochip_to_irq() before it could be initialized by gpiochip_add_irqchip(). This resulted in Kernel NULL pointer dereference. This is a well known issue in the linux community and was fixed via 2 commits: 5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320 and 06fb4ecfeac7e00d6704fa5ed19299f2fefb3cc9 (since the previous commit caused a regression) This race condition is intermittent and hard to reproduce. [Fix] * Cherry pick: 5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320 to fix the bug at stake * cherry-pick: 06fb4ecfeac7e00d6704fa5ed19299f2fefb3cc9 to fix a regression introduced by the previous commit [Test Case] * Check that the gpio-mlxbf2.c driver is loaded with no kernel panic * check that all drivers dependent on gpio-mlxbf2.c driver are loaded (mlxbf-gige and pwr-mlxbf) * do 5000 reboots to make sure this race condition no longer happens [Regression Potential] This could cause some regression with the use of gpio interrupts so it is important to test the dependent drivers mlxbf-gige and pwr-mlxbf. Trigger power reset interrupt to test pwr-mlxbf and bring down/up the oob_net0 interface to test mlxbf-gige. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2007581/+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 2012964] [NEW] package linux-image-5.19.0-38-generic (not installed) failed to install/upgrade: el subproceso instalado paquete linux-image-5.19.0-38-generic script pre-removal
Public bug reported: No installed 5.19 because not support Nvidia GT210 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 12:12:47 2023 ErrorMessage: el subproceso instalado paquete linux-image-5.19.0-38-generic script pre-removal devolvió el código de salida de error 1 InstallationDate: Installed on 2023-03-27 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-38-generic (not installed) failed to install/upgrade: el subproceso instalado paquete linux-image-5.19.0-38-generic script pre-removal devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2012964 Title: package linux-image-5.19.0-38-generic (not installed) failed to install/upgrade: el subproceso instalado paquete linux- image-5.19.0-38-generic script pre-removal devolvió el código de salida de error 1 Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: No installed 5.19 because not support Nvidia GT210 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 12:12:47 2023 ErrorMessage: el subproceso instalado paquete linux-image-5.19.0-38-generic script pre-removal devolvió el código de salida de error 1 InstallationDate: Installed on 2023-03-27 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-38-generic (not installed) failed to install/upgrade: el subproceso instalado paquete linux-image-5.19.0-38-generic script pre-removal devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2012964/+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 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
Same Issue with my Sound Blaster Recon3D / Z-Series I have tried 5.19.0-35 and 5.19.0-38 Works only for kernel 5.19.0-32 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009243 Title: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: 2023-03-03 Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1). Clobbered my Sound Blaster AE-7. Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup). Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35. Tried again to install 5.19.0-35 the same way, just to be sure. The SB AE-7 got clobbered again. So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel. Current hardware config: Asus Prime Z790-P wifi mobo. Intel Core i3-13100 processor (with Intel UHD 730 graphics). Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz. 3 x Nvme SSD. Boot drive is Western Digital Black SN770 500gb. Asus Nvidia RTX-3050 PCIe graphics card. Creative Labs Sound Blaster AE-7 audio card (PCIe). On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI. UEFI is AMI/BIOS, revision 0812. Linux Mint 21.1 is running on barebones hardware, no VM involved. No other O/S's are installed on the machine. - Running sudo lspci -vnvn > lspci-vnvn.log gave the following error message... pcilib: sysfs_read_vpd: read failed: No such device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikey 4106 F wireplumber /dev/snd/controlC0: mikey 4106 F wireplumber /dev/snd/seq:mikey 4105 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-31 (32 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: vera Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2023 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0812 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-P WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx: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: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009243/+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 1904906] Comment bridged from LTC Bugzilla
--- Comment From gcwil...@us.ibm.com 2023-03-27 11:56 EDT--- This was fixed and closed on the Canonical side. Moving to closed on ours. -- 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/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+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 1639924] Re: Kernel livepatch support for for s390x
The following kernel incl. the needed patches for jammy: 5.15.0.70.68 | jammy-proposed -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Invalid Status in linux source package in Jammy: Fix Committed Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' bf212f7750 create-diff-object: error on unsupported rela in symbol conversion 3f8e1062cc create-diff-object: support R_X86_64_NONE in kpatch_replace_sections_syms() 79f45d1b0a create-diff-object: fix kpatch_replace_sections_syms() for non-text
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Confirming the proposed 5.4.0-1099 packages resolve the NFS bug on Bionic running in AWS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic
[Kernel-packages] [Bug 2012953] 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 2012953 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/2012953 Title: No HDMI with Intel Iris Xe Graphics Status in linux package in Ubuntu: Incomplete Bug description: Hi I have a XMG Focus 17 laptop. i7-12700H with Intel Iris Xe Graphics Nvidia RTX 3060. Dualboot LinuxMint 21.1 (based on Ubuntu 22.04) / Windows 10 Kernel 5.15.0-67-generic HDMI output (2nd screen, TV) works fine with : -Windows -LinuxMint with Nvidia card activated BUT don't work with : LinuxMint with Intel Graphic GPU. I have the same pb on another laptop DELL VOSTRO 5630 (no Nvidia, only Intel GPU), running LinuxMint 21.1 too. So the issue comes from the Intel Iris GPU. My hdmi wires are OK. Here are some command lines ouputs : $ inxi -bG System: Host: vincent-XMG-FOCUS-M22 Kernel: 5.15.0-67-generic x86_64 bits: 64 Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera Machine: Type: Laptop System: SchenkerGmbH product: XMG FOCUS (M22) v: N/A serial: Mobo: NB01 model: NP5x_NP6x_NP7xPNP serial: UEFI: INSYDE v: 1.07.09RTR2 date: 12/01/2022 Battery: ID-1: BAT0 charge: 51.3 Wh (100.0%) condition: 51.3/52.5 Wh (97.8%) CPU: Info: 14-core (6-mt/8-st) 12th Gen Intel Core i7-12700H [MST AMCP] speed (MHz): avg: 715 min/max: 400/4600:4700:3500 Graphics: Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: N/A Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~144Hz OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.2.5 Network: Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi Device-2: Intel Ethernet I219-V driver: e1000e Drives: Local Storage: total: 2.73 TiB used: 1.13 TiB (41.5%) Info: Processes: 386 Uptime: 3h 12m Memory: 15.34 GiB used: 3.21 GiB (20.9%) Shell: Bash inxi: 3.3.13 --- $ grep . /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-DP-3/status:disconnected /sys/class/drm/card0-DP-4/status:disconnected /sys/class/drm/card0-eDP-1/status:connected Thanks a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012953/+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 2012960] [NEW] Screens flickers to black after software updater updated nvidia-driver-525 and linux-image-5.19.0
Public bug reported: after mentioned updates screens flickers to complete black and back... system near unusable (sorry for typos but cant see much so i write here mostly blind whilst i have about half a second a view of my desktop ) I attach here some outputs from the logs (jopurnal -xe) and outputs of ubuntu-drivers devbices and nvidia smi hope it helps ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-525 525.89.02-0ubuntu0.22.10.1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 18:49:17 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2019-10-08 (1265 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-525 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Attachment added: "logoutput_4_bugreport" https://bugs.launchpad.net/bugs/2012960/+attachment/5657959/+files/logoutput_4_bugreport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2012960 Title: Screens flickers to black after software updater updated nvidia- driver-525 and linux-image-5.19.0 Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: after mentioned updates screens flickers to complete black and back... system near unusable (sorry for typos but cant see much so i write here mostly blind whilst i have about half a second a view of my desktop ) I attach here some outputs from the logs (jopurnal -xe) and outputs of ubuntu-drivers devbices and nvidia smi hope it helps ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-525 525.89.02-0ubuntu0.22.10.1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 18:49:17 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2019-10-08 (1265 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-525 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-525/+bug/2012960/+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 1988836] Autopkgtest regression report (linux-restricted-modules-gcp-5.19/5.19.0-1020.22~22.04.2+1)
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.19 (5.19.0-1020.22~22.04.2+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (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/jammy/update_excuses.html#linux-restricted-modules-gcp-5.19 [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 linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1786013] Autopkgtest regression report (linux-restricted-modules-gcp-5.19/5.19.0-1020.22~22.04.2+1)
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.19 (5.19.0-1020.22~22.04.2+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (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/jammy/update_excuses.html#linux-restricted-modules-gcp-5.19 [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 linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2012953] [NEW] No HDMI with Intel Iris Xe Graphics
Public bug reported: Hi I have a XMG Focus 17 laptop. i7-12700H with Intel Iris Xe Graphics Nvidia RTX 3060. Dualboot LinuxMint 21.1 (based on Ubuntu 22.04) / Windows 10 Kernel 5.15.0-67-generic HDMI output (2nd screen, TV) works fine with : -Windows -LinuxMint with Nvidia card activated BUT don't work with : LinuxMint with Intel Graphic GPU. I have the same pb on another laptop DELL VOSTRO 5630 (no Nvidia, only Intel GPU), running LinuxMint 21.1 too. So the issue comes from the Intel Iris GPU. My hdmi wires are OK. Here are some command lines ouputs : $ inxi -bG System: Host: vincent-XMG-FOCUS-M22 Kernel: 5.15.0-67-generic x86_64 bits: 64 Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera Machine: Type: Laptop System: SchenkerGmbH product: XMG FOCUS (M22) v: N/A serial: Mobo: NB01 model: NP5x_NP6x_NP7xPNP serial: UEFI: INSYDE v: 1.07.09RTR2 date: 12/01/2022 Battery: ID-1: BAT0 charge: 51.3 Wh (100.0%) condition: 51.3/52.5 Wh (97.8%) CPU: Info: 14-core (6-mt/8-st) 12th Gen Intel Core i7-12700H [MST AMCP] speed (MHz): avg: 715 min/max: 400/4600:4700:3500 Graphics: Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: N/A Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~144Hz OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.2.5 Network: Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi Device-2: Intel Ethernet I219-V driver: e1000e Drives: Local Storage: total: 2.73 TiB used: 1.13 TiB (41.5%) Info: Processes: 386 Uptime: 3h 12m Memory: 15.34 GiB used: 3.21 GiB (20.9%) Shell: Bash inxi: 3.3.13 --- $ grep . /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-DP-3/status:disconnected /sys/class/drm/card0-DP-4/status:disconnected /sys/class/drm/card0-eDP-1/status:connected Thanks a lot ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/2012953 Title: No HDMI with Intel Iris Xe Graphics Status in linux package in Ubuntu: Incomplete Bug description: Hi I have a XMG Focus 17 laptop. i7-12700H with Intel Iris Xe Graphics Nvidia RTX 3060. Dualboot LinuxMint 21.1 (based on Ubuntu 22.04) / Windows 10 Kernel 5.15.0-67-generic HDMI output (2nd screen, TV) works fine with : -Windows -LinuxMint with Nvidia card activated BUT don't work with : LinuxMint with Intel Graphic GPU. I have the same pb on another laptop DELL VOSTRO 5630 (no Nvidia, only Intel GPU), running LinuxMint 21.1 too. So the issue comes from the Intel Iris GPU. My hdmi wires are OK. Here are some command lines ouputs : $ inxi -bG System: Host: vincent-XMG-FOCUS-M22 Kernel: 5.15.0-67-generic x86_64 bits: 64 Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera Machine: Type: Laptop System: SchenkerGmbH product: XMG FOCUS (M22) v: N/A serial: Mobo: NB01 model: NP5x_NP6x_NP7xPNP serial: UEFI: INSYDE v: 1.07.09RTR2 date: 12/01/2022 Battery: ID-1: BAT0 charge: 51.3 Wh (100.0%) condition: 51.3/52.5 Wh (97.8%) CPU: Info: 14-core (6-mt/8-st) 12th Gen Intel Core i7-12700H [MST AMCP] speed (MHz): avg: 715 min/max: 400/4600:4700:3500 Graphics: Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: N/A Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~144Hz OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.2.5 Network: Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi Device-2: Intel Ethernet I219-V driver: e1000e Drives: Local Storage: total: 2.73 TiB used: 1.13 TiB (41.5%) Info: Processes: 386 Uptime: 3h 12m Memory: 15.34 GiB used: 3.21 GiB (20.9%) Shell: Bash inxi: 3.3.13 --- $ grep . /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-DP-3/status:disconnected /sys/class/drm/card0-DP-4/status:disconnected /sys/class/drm/card0-eDP-1/status:connected Thanks a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012953/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Can confirm that 5.15.0-1033 seems to have resolved the NFS bug on Jammy running on AWS. Is there a timeframe for the same patch to be applied to the 5.19 kernel train? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill:
[Kernel-packages] [Bug 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
Same Issue with my Sound Blaster Recon3D / Z-Series I have tried 5.19.0-35 and 5.19.0-38 Works only for kernel 5.19.0-32 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009243 Title: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: 2023-03-03 Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1). Clobbered my Sound Blaster AE-7. Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup). Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35. Tried again to install 5.19.0-35 the same way, just to be sure. The SB AE-7 got clobbered again. So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel. Current hardware config: Asus Prime Z790-P wifi mobo. Intel Core i3-13100 processor (with Intel UHD 730 graphics). Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz. 3 x Nvme SSD. Boot drive is Western Digital Black SN770 500gb. Asus Nvidia RTX-3050 PCIe graphics card. Creative Labs Sound Blaster AE-7 audio card (PCIe). On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI. UEFI is AMI/BIOS, revision 0812. Linux Mint 21.1 is running on barebones hardware, no VM involved. No other O/S's are installed on the machine. - Running sudo lspci -vnvn > lspci-vnvn.log gave the following error message... pcilib: sysfs_read_vpd: read failed: No such device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikey 4106 F wireplumber /dev/snd/controlC0: mikey 4106 F wireplumber /dev/snd/seq:mikey 4105 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-31 (32 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: vera Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2023 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0812 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-P WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx: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: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009243/+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 2003730] Re: Ubuntu 22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52
Ok, thx Thorsten - closing it form this side too as Fix Released. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: ubuntu-z-systems Status: Triaged => Fix Released -- 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/2003730 Title: Ubuntu 22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52 Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Up to linux-image-5.15.0-52-generic the dbgsym packages are available, for the most recent 5.15.0 kernels they are missing. They are required for dump analysis. Please add them to the updates pool. Reported by: Thorsten Diehl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003730/+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 2003816] Re: Regression in ext4 during online resize
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: Fix Committed Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+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 2004132] Re: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2196 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4382 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-23559 -- 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/2004132 Title: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2004132 [Impact] xfstests btrfs/154 fails on both Bionic and Focal, leading to a kernel oops and the btrfs volume being forced readonly. In btrfs, item key collision is allowed for some item types, namely dir item and inode references. When inserting items into the btree, there are two objects, the btrfs_item and the item data. These objects must fit within the btree nodesize. When a hash collision occurs, and we call btrfs_search_slot() to place the objects in the tree, when btrfs_search_slot() reaches the leaf node, a check is performed to see if we need to split the leaf. The check is incorrect, returning that we need to split the leaf, since it thinks that both btrfs_item and the item data need to be inserted, when in reality, the item can be merged with the existing one and no new btrfs_item will be inserted. split_leaf() will return EOVERFLOW from following code: if (extend && data_size + btrfs_item_size_nr(l, slot) + sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(fs_info)) return -EOVERFLOW; In the rename case, btrfs_check_dir_item_collision() is called early stages of treewalking, and correctly calculates the needed size, taking into account that a hash collision has occurred. data_size = sizeof(*di) + name_len; if (data_size + btrfs_item_size_nr(leaf, slot) + sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(root->fs_info)) The two sizes reported from btrfs_check_dir_item_collision() and btrfs_search_slot() are different, and rename fails due to split_leaf() returning -EOVERFLOW, leading to transaction abort and forcing the volume readonly. Kernel oops: BTRFS: Transaction aborted (error -75) WARNING: CPU: 0 PID: 2921 at /build/linux-fTmV3T/linux-4.15.0/fs/btrfs/inode.c:10217 btrfs_rename+0xcf1/0xdf0 [btrfs] CPU:
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2196 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4382 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-23559 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2006453 Title: Fix selftests/ftracetests/Meta-selftests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+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 2006391] Re: net:fcnal-test.sh 'nettest' command not found on F/K
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 -- 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/2006391 Title: net:fcnal-test.sh 'nettest' command not found on F/K Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: On Focal and Kinetic the fcnal-test.sh does not run because it reports that 'nettest' command not found; skipping tests This is due to the nettest binary not being found in the path and skipping the tests, but it is built and exists in the net directory where the tests are run. There are also other tests in selftests/net that are skipped due to the binary being missing. There is a patch upstream "selftests/net: Find nettest in current directory" (bd5e1e42826f18147afb0) that fixes this by looking in the current directory. The patch is in Jammy through stable updates, but the patch hasnt made it to the other stable trees yet for whatever reasons so might as well just cherry-pick them into F/K. - [Impact] fcnal-test.sh in selftests/net gets skipped with 'nettest' command not found because its looking for the nettest binary in the path and not in the current directory where the binary is built and run from. There are also other tests in net that are skipped due to this binary not being found. [Fix] Add the current directory to the path and check again. This patch exists in Jammy through a stable update but hasn't made it to the other upstream-stable trees yet, but might as well get the patch in our other trees to enable this test to run. [Backport] For focal patch skip the pmtu.sh file as nettest is not run there and is not checked. Also minor context adjustments on return variable. [Potential regression] None. Just enabling the tests to run. [Tests] Verified tests are now not skipped and run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006391/+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 2007219] Re: xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2196 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4382 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-23559 -- 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/2007219 Title: xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2007219 [Impact] A deadlock exists in the XFS filesystem that occurs when the XFS log buffer becomes completely exhausted. XFS maintains a circular ring buffer for the log, and it is a fixed size. To be able to create a transaction, you need to be able to reserve space on the log buffer. Certain ioend transactions, such as file append, can be preallocated for a negligible performance gain. This takes up space in the log buffer, and these preallocated ioends are placed on a workqueue, behind other ioends that are not preallocated. The deadlock occurs when the XFS log buffer is running low on space, and an ioend append transaction comes in. It is preallocated, consuming nearly all of the remaining XFS log buffer space, and is placed at the very end of the ioend workqueue. The kernel then takes a ioend from the top of the ioend workqeueue, creates a transaction, xfs_trans_alloc(), attempts to allocate space for it, xfs_trans_reserve(), xfs_log_reserve(), and then waits in a while loop checking free space in the log, xlog_grant_head_check(), xlog_grant_head_wait(). Since there is no space, the thread sleeps with schedule(). This happens with all ioend transactions, since the log is exhausted and I/O is not moving. Since I/O never moves, the thread is never woken up, and we get hung task timeouts, with system failure shortly afterward. An example hung task timeout is: INFO: task kworker/60:0:4002982 blocked for more than 360 seconds. Tainted: G OE 5.4.0-137-generic #154-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kworker/60:0D0 4002982 2 0x90004080 Workqueue: xfs-conv/dm-3 xfs_end_io [xfs] Call Trace: __schedule+0x2e3/0x740 schedule+0x42/0xb0 xlog_grant_head_wait+0xb9/0x1e0 [xfs] xlog_grant_head_check+0xde/0x100 [xfs] xfs_log_reserve+0xc9/0x1e0
[Kernel-packages] [Bug 2003730] Re: Ubuntu 22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52
--- Comment From thorsten.di...@de.ibm.com 2023-03-27 04:16 EDT--- (In reply to comment #6) > It looks to me that the automatic debug-symbols package generation and > publication for the various linux-generic kernels works again. > Would you agree if this LP bug gets closed? Oops, I lost this one from the radar. Sure, yes. Dbgsym packages are now available as expected. Closing this bug. ** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin22042 -- 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/2003730 Title: Ubuntu 22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: Up to linux-image-5.15.0-52-generic the dbgsym packages are available, for the most recent 5.15.0 kernels they are missing. They are required for dump analysis. Please add them to the updates pool. Reported by: Thorsten Diehl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003730/+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 2011854] Re: cmos_interrupt not getting called
This bug was fixed in the package linux-oracle-5.15 - 5.15.0-1032.38~20.04.1 --- linux-oracle-5.15 (5.15.0-1032.38~20.04.1) focal; urgency=medium * focal/linux-oracle-5.15: 5.15.0-1032.38~20.04.1 -proposed tracker (LP: #2012656) [ Ubuntu: 5.15.0-1032.38 ] * jammy/linux-oracle: 5.15.0-1032.38 -proposed tracker (LP: #2012655) * cmos_interrupt not getting called (LP: #2011854) - SAUCE: Revert "rtc: rtc-cmos: Do not check ACPI_FADT_LOW_POWER_S0" linux-oracle-5.15 (5.15.0-1031.37~20.04.1) focal; urgency=medium * focal/linux-oracle-5.15: 5.15.0-1031.37~20.04.1 -proposed tracker (LP: #2008340) [ Ubuntu: 5.15.0-1031.37 ] * jammy/linux-oracle: 5.15.0-1031.37 -proposed tracker (LP: #2008342) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 2012698] Re: Plymouth is just a plain black screen
** Changed in: linux (Ubuntu) Milestone: None => ubuntu-23.04 ** Changed in: plymouth (Ubuntu) Milestone: None => ubuntu-23.04 -- 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/2012698 Title: Plymouth is just a plain black screen Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Bug description: Plymouth never displays anything -- the boot process is a plain black screen. Workaround: Tap Esc once to see text mode. Tap Esc a second time to get the Plymouth graphical screen. I only figured that out when I had been waiting too long for the disk decryption prompt. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth 22.02.122-3ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Fri Mar 24 13:50:04 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2023-03-24 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) MachineType: LENOVO 21CBCTO1WW ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2023 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET71W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3AET71W(1.36):bd01/31/2023:br1.36:efr1.17:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012698/+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 2009063] Re: Consistent autopkgtest failures in xdp-tools lunar with 6.1.0 kernel
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- 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/2009063 Title: Consistent autopkgtest failures in xdp-tools lunar with 6.1.0 kernel Status in linux package in Ubuntu: Fix Released Status in xdp-tools package in Ubuntu: Invalid Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
Hello Stefan, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.21 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: systemd (Ubuntu Focal) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in linux source package in Focal: New Status in systemd source package in Focal: Fix Committed Bug description: [Impact] The armhf autopkgtests currently fail in Focal due to this, and failures are not marked as regressions. This limits our ability to catch other regressions on armhf. [Test Plan] The boot-and-services autopkgtest should not fail on armhf. Specifically, the test_no_failed test should ignore systemd-remount-fs.service failures on armhf only. [Where problems could occur] The fix is limited to the boot-and-services autopkgtest, so there is limited risk. Any bugs would show up in that test. [Original Description] This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.21 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: systemd (Ubuntu Focal)
Status: Triaged => Fix Committed
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1933090
Title:
systemd/245.4-4ubuntu3.6 ADT test failure with linux-
hwe-5.11/5.11.0-20.21~20.04.1
Status in linux-hwe-5.11 package in Ubuntu:
Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in linux-hwe-5.11 source package in Focal:
Won't Fix
Status in linux-hwe-5.15 source package in Focal:
Invalid
Status in systemd source package in Focal:
Fix Committed
Bug description:
[SRU Impact]
Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c,
test_protect_syscall
sysctl is called with the expectation the error result is EFAULT and not
ENOSYS.
This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp,
oem, gke, oracle).
[Fix]
Assertion checks if either EFAULT or ENOSYS is returned. This way it will
work for focal-5.4 kernels and focal-5.15 kernels.
[Test to reproduce the issue]
1. Create a vm and install one of the focal-5.15 kernels (i.e
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
2. Run the autotests for upstream and/or root-unittests:
autopkgtest --test-name=upstream systemd -- qemu
[Test to verify the fix]
1. Same as above
2. Apply the fix in your local repo and run the tests using your local repo
autopkgtest --test-name=upstream -- qemu
[Where problems could occur]
This is not gonna affect end users since it is a change in the test only.
It may impact autotests, but it's a very low probability.
[Original Description]
This is a scripted bug report about ADT failures while running systemd
tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
is caused by the dep8 tests of the tested source or the kernel has yet
to be determined.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz
In arm64, ppc64el and s390x, 'root-unittests' fails with:
/* test_protect_sysctl */
Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function
test_protect_sysctl(). A
borting.
sysctlseccomp terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) ==
EXIT_SUCCESS' failed at s
rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
FAIL: test-seccomp (code: 134)
In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
apparently is caused by the same 'test-seccomp.c:311' assertion
failure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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 2012908] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657754/+files/ProcInterrupts.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars
[Kernel-packages] [Bug 2012908] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657753/+files/ProcEnviron.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27
[Kernel-packages] [Bug 2012908] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657747/+files/Lspci-vt.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657750/+files/Lsusb-v.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657749/+files/Lsusb-t.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657751/+files/ProcCpuinfo.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27
[Kernel-packages] [Bug 2012908] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657755/+files/ProcModules.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27
[Kernel-packages] [Bug 2012908] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657752/+files/ProcCpuinfoMinimal.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12:
[Kernel-packages] [Bug 2007441] Re: Jammy update: v5.15.87 upstream stable release
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 2006937] Re: Update the NVIDIA 525 series to 525.89.02
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.89.02-0ubuntu0.22.04.1 --- nvidia-graphics-drivers-525 (525.89.02-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2006937): - Fixed a bug that could cause banding or flickering of color gradients on DisplayPort monitors. * debian/templates/control.in: - Switch libcuda1 and libnvidia-ml1 Provides to libcuda.so.1 and libnvidia-ml.so.1. This makes CUDA (from Multiverse) installable again. -- Alberto Milone Tue, 28 Feb 2023 10:47:21 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy) Status: Triaged => Fix Released ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Focal) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2006937 Title: Update the NVIDIA 525 series to 525.89.02 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-525 source package in Bionic: Triaged Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] 525.89.02 [Kinetic, Jammy] * New upstream release (LP: #2006937): - Fixed a bug that could cause banding or flickering of color gradients on DisplayPort monitors. * debian/templates/control.in: - Switch libcuda1 and libnvidia-ml1 Provides to libcuda.so.1 and libnvidia-ml.so.1. This makes CUDA (from Multiverse) installable again. [Focal, Bionic] * New upstream release (LP: #2006937): - Fixed a bug that could cause banding or flickering of color gradients on DisplayPort monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2006937/+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 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2196 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4382 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-23559 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-41218 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0045 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0266 -- 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/2006692 Title: net:fcnal-test.sh didn't return a non-zero value even with some sub- tests failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The net/fcnal-test.sh on F/J won't return a non-zero value even with some sub test cases failed, here is an example on Jammy: # Tests passed: 857 # Tests failed: 5 ok 1 selftests: net: fcnal-test.sh Therefore it's marked as PASSED on our report and making it difficult to spot these failures: # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] [Fix] * 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code This patch can be cherry-picked into Focal and Jammy kernel. We don't have this test in Bionic, and this patch has already landed on Kinetic and OEM-5.17 [Test] Run the patched test, the return value will be 1 whenever the number of failed test cases is not 0. [Where problems could occur] Change limited to testing tools, but we're expected to see new failures in Jammy. With bug 2006391 fixed later on, we will see failures reported in F/K as well. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1987507] Re: Migrate oem-20.04 to hwe-5.15
** Description changed: - Migrate oem-5.14 to hwe-5.15 now that there should be no functional - regressions left anymore. + [Impact] + Migrate oem-5.14 to hwe-5.15 now that there should be no functional regressions left anymore. + + [Test case] + Update a machine with oem-5.14 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. + + [Where things could go wrong] + In theory we might miss a package to transition, but at this point this is unlikely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987507 Title: Migrate oem-20.04 to hwe-5.15 Status in linux-meta-hwe-5.15 package in Ubuntu: Invalid Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Invalid Status in linux-meta-hwe-5.15 source package in Focal: New Status in linux-restricted-modules-hwe-5.15 source package in Focal: New Bug description: [Impact] Migrate oem-5.14 to hwe-5.15 now that there should be no functional regressions left anymore. [Test case] Update a machine with oem-5.14 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. [Where things could go wrong] In theory we might miss a package to transition, but at this point this is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+bug/1987507/+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 2012755] Re: [IOTG][RPL] Enable Time Coordinated Compute interface driver
** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-intel-iotg (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-intel-iotg (Ubuntu Jammy) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux-intel-iotg (Ubuntu) Assignee: Philip Cox (philcox) => (unassigned) -- 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/2012755 Title: [IOTG][RPL] Enable Time Coordinated Compute interface driver Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake & Alder Lake & Ice Lake & Raptor Lake Target Release: 22.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.19-linux-221019T120731Z Based on LP bug https://bugs.launchpad.net/intel/+bug/1929903, there are some more updates for this driver as following. 0017-Support-RPL-in-measurement-function.tcc 0018-Assume-default-hardware-prefetch-bitmask-in-measuremen.tcc 0019-tcc-fix-patch-style-problem.tcc 0020-tcc-Map-and-show-crl-version-number-in-proc.tcc 0022-tcc-Update-hardware-prefetcher-disable-bits-for-ADL-an.tcc 0023-tcc-Choose-different-L3-cache-miss-perf-event-for-ADL-.tcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2012755/+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 2003816] Re: Regression in ext4 during online resize
The issue is also present in Jammy distro kernel (linux- image-5.15.0-67-generic) and e2fsprofs 1.46.5-2ubuntu1.1 How to reproduce : * Create an openstack instance and user virtio-scsi as block device controller * Add a Cinder volume (backed by PureStorage/iSCSI) * format the whole volume : mkfs.ext4 /dev/sdb * mount it somewhere : mount /dev/sdb /mnt/test * resize volume from Cinder, check with lsblk that the volume is properly expanded * online resize the volume without unmounting it : resize2fs /mnt/test It works but doing it a second time fails most of the time with the "Superblock checksum does not match superblock" error. Unmounting and doing a fsck fix the problem easily but the "online" feature is severely degraded if you need to do things offline ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: Fix Committed Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+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 2012698] Re: Plymouth is just a plain black screen
** Changed in: plymouth (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/2012698 Title: Plymouth is just a plain black screen Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Bug description: Plymouth never displays anything -- the boot process is a plain black screen. Workaround: Tap Esc once to see text mode. Tap Esc a second time to get the Plymouth graphical screen. I only figured that out when I had been waiting too long for the disk decryption prompt. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth 22.02.122-3ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Fri Mar 24 13:50:04 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2023-03-24 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) MachineType: LENOVO 21CBCTO1WW ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2023 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET71W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3AET71W(1.36):bd01/31/2023:br1.36:efr1.17:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012698/+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 2012918] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012918 Title: Spotify completely freezes Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Mar 27 12:50:37 juliuswork kernel: [ 9754.386159] amdgpu :05:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32781, for process spotify pid 23781 thread spotify:cs0 pid 23841) Mar 27 12:50:37 juliuswork kernel: [ 9754.386161] amdgpu :05:00.0: amdgpu: in page starting at address 0x800104a2 from IH client 0x12 (VMC) Mar 27 12:50:37 juliuswork kernel: [ 9754.386164] amdgpu :05:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140050 Mar 27 12:50:37 juliuswork kernel: [ 9754.386165] amdgpu :05:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Mar 27 12:50:37 juliuswork kernel: [ 9754.386166] amdgpu :05:00.0: amdgpu: MORE_FAULTS: 0x0 Mar 27 12:50:37 juliuswork kernel: [ 9754.386167] amdgpu :05:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 27 12:50:37 juliuswork kernel: [ 9754.386168] amdgpu :05:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Mar 27 12:50:37 juliuswork kernel: [ 9754.386170] amdgpu :05:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 27 12:50:37 juliuswork kernel: [ 9754.386171] amdgpu :05:00.0: amdgpu: RW: 0x1 Mar 27 12:50:38 juliuswork kernel: [ 9755.937890] sysrq: This sysrq operation is disabled. Mar 27 12:50:39 juliuswork kernel: [ 9756.179881] sysrq: This sysrq operation is disabled. Mar 27 12:50:39 juliuswork kernel: [ 9756.521888] sysrq: This sysrq operation is disabled. Mar 27 12:50:39 juliuswork kernel: [ 9756.803881] sysrq: Emergency Sync Mar 27 12:50:39 juliuswork kernel: [ 9756.812831] Emergency Sync complete Mar 27 12:50:39 juliuswork kernel: [ 9757.025886] sysrq: This sysrq operation is disabled. Mar 27 12:50:41 juliuswork kernel: [ 9758.415886] sysrq: This sysrq operation is disabled. Mar 27 12:50:41 juliuswork kernel: [ 9758.598109] sysrq: This sysrq operation is disabled. Mar 27 12:50:42 juliuswork kernel: [ 9759.389853] gmc_v9_0_process_interrupt: 187338 callbacks suppressed Mar 27 12:50:42 juliuswork kernel: [ 9759.389859] amdgpu :05:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32781, for process spotify pid 23781 thread spotify:cs0 pid 23841) Mar 27 12:50:42 juliuswork kernel: [ 9759.389866] amdgpu :05:00.0: amdgpu: in page starting at address 0x800104a2 from IH client 0x12 (VMC) Mar 27 12:50:42 juliuswork kernel: [ 9759.389870] amdgpu :05:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Mar 27 12:50:42 juliuswork kernel: [ 9759.389872] amdgpu :05:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Mar 27 12:50:42 juliuswork kernel: [ 9759.389874] amdgpu :05:00.0: amdgpu: MORE_FAULTS: 0x1 Mar 27 12:50:42 juliuswork kernel: [ 9759.389876] amdgpu :05:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389877] amdgpu :05:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Mar 27 12:50:42 juliuswork kernel: [ 9759.389878] amdgpu :05:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389879] amdgpu :05:00.0: amdgpu: RW: 0x1 Mar 27 12:50:42 juliuswork kernel: [ 9759.389882] amdgpu :05:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32781, for process spotify pid 23781 thread spotify:cs0 pid 23841) Mar 27 12:50:42 juliuswork kernel: [ 9759.389885] amdgpu :05:00.0: amdgpu: in page starting at address 0x800104a2 from IH client 0x12 (VMC) Mar 27 12:50:42 juliuswork kernel: [ 9759.389888] amdgpu :05:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140050 Mar 27 12:50:42 juliuswork kernel: [ 9759.389889] amdgpu :05:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Mar 27 12:50:42 juliuswork kernel: [ 9759.389890] amdgpu :05:00.0: amdgpu: MORE_FAULTS: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389892] amdgpu :05:00.0: amdgpu: WALKER_ERROR: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389893] amdgpu :05:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Mar 27 12:50:42 juliuswork kernel: [ 9759.389894] amdgpu :05:00.0: amdgpu: MAPPING_ERROR: 0x0 Mar 27 12:50:42 juliuswork kernel: [ 9759.389895] amdgpu :05:00.0: amdgpu: RW: 0x1 Mar 27 12:50:42 juliuswork kernel: [ 9759.389907] amdgpu :05:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32781, for process spotify pid 23781 thread spotify:cs0 pid 23841) Mar 27 12:50:42 juliuswork kernel: [ 9759.389909] amdgpu :05:00.0: amdgpu: in page starting at address 0x800104a2 from IH client 0x12 (VMC) Mar 27 12:50:42 juliuswork kernel: [ 9759.389912] amdgpu :05:00.0: amdgpu:
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 ** Changed in: linux-aws (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug was fixed in the package linux-aws - 5.4.0-1099.107 --- linux-aws (5.4.0-1099.107) focal; urgency=medium * focal/linux-aws: 5.4.0-1099.107 -proposed tracker (LP: #2012000) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux-aws (5.4.0-1098.106) focal; urgency=medium * focal/linux-aws: 5.4.0-1098.106 -proposed tracker (LP: #2008358) [ Ubuntu: 5.4.0-145.162 ] * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Kleber Sacilotto de Souza Fri, 17 Mar 2023 11:53:44 +0100 ** Changed in: linux-aws (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-41218 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug was fixed in the package linux-aws - 5.15.0-1033.37 --- linux-aws (5.15.0-1033.37) jammy; urgency=medium * jammy/linux-aws: 5.15.0-1033.37 -proposed tracker (LP: #2011997) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux-aws (5.15.0-1032.36) jammy; urgency=medium * jammy/linux-aws: 5.15.0-1032.36 -proposed tracker (LP: #2008308) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) [ Ubuntu: 5.15.0-68.75 ] * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 1999882] Re: [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part
This bug was fixed in the package linux - 5.4.0-146.163 --- linux (5.4.0-146.163) focal; urgency=medium * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.4.0-145.162) focal; urgency=medium * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389) * [SRU]Update ice driver to support E823 devices (LP: #1986717) - ice: Add device ids for E822 devices - ice: add support for E823 devices * btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision (LP: #2004132) - btrfs: correctly calculate item size used when item key collision happens * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part (LP: #1999882) - KVM: s390x: fix SCK locking - KVM: s390: pv: don't allow userspace to set the clock under PV * CVE-2021-3669 - ipc: replace costly bailout check in sysvipc_find_ipc() * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391) - selftests/net: Find nettest in current directory * xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion (LP: #2007219) - xfs: drop submit side trans alloc for append ioends * CVE-2022-4382 - USB: gadgetfs: Fix race between mounting and unmounting * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447) - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed (LP: #2006692) - selftests: net/fcnal-test.sh: add exit code * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453) - SAUCE: Fix ftrace/Meta-selftests bashism check * CVE-2023-23559 - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid -- Luke Nowakowski-Krijger Fri, 17 Mar 2023 11:08:20 -0700 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3669 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2196 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4382 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-23559 -- 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/1999882 Title: [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Description: KVM: s390: pv: don't allow userspace to set the clock under PV Symptom: Timer issues and RCU stalls after suspending and resuming an IBM Secure Execution guest Problem: KVM and QEMU try to set the guest's TOD clock after resume under PV, even though that is not permitted under SE. Hence,their view of the guest clock may deviate from the ultravisor's, possibly causing KVM to re-dispatch the guest too late on clock comparator interrupts. Solution: Don't set the clock after resume under PV. Note that kernel and QEMU patches are required in lockstep, to avoid a warning message in QEMU. Reproduction: 1. Start SE guest using libvirt. 2. Pause the guest using "virsh suspend", wait for a few seconds, resume using "virsh resume". 3. Run "time sleep 1" in the guest. 4. The sleep will sleep much longer than one second. Upstream-ID: 6973091d1b50ab4042f6a2d495f59e9db3662ab8 Preventive fix: yes Author:Nico Boehr Please note that fixing the described problem requires patches for the kernel as well as for QEMU. This bug covers the kernel part, whereas the required QEMU part is described and handled in the following related bug: Bug?200901 - [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - qemu part Both parts, the kernel and the qemu patches should be applied / released at the same time to avoid problems resulting in the following warning message for customers: 'warning: Unable to set KVM guest TOD clock: Operation not supported' To manage notifications about this bug go
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 2012908] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657746/+files/Lspci.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657748/+files/Lsusb.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657744/+files/CurrentDmesg.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27
[Kernel-packages] [Bug 2012908] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657745/+files/IwConfig.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2012908/+attachment/5657743/+files/AlsaInfo.txt -- 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: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2012908] [NEW] nvidia driver 515 fails to boot on kernel 6.2
Public bug reported: 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: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54 gandalf kernel: R13: 55f37389c120 R14: R15: 55f373909080 mars 27 10:33:54 gandalf kernel: Also, the last entry before I had to do a hard shutdown was this: mars 27 10:34:54 gandalf systemd-udevd[1023]: nvidia: Spawned process '/sbin/modprobe nvidia-drm' [1124] is taking longer than 59s to complete I'm attaching the kernel logs up to the beginning of userspace logs. I can provide more if necessary. My driver package: ii nvidia-driver-515 515.86.01-0ubuntu3 amd64 My graphics card: 0b:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti]
[Kernel-packages] [Bug 1998244] Re: kselftest net/fib_nexthop_nongw.sh fails
This bug was fixed in the package linux-kvm - 6.2.0-1002.2
---
linux-kvm (6.2.0-1002.2) lunar; urgency=medium
* lunar/linux-kvm: 6.2.0-1002.2 -proposed tracker (LP: #2012486)
* Miscellaneous Ubuntu changes
- [Config] inherit debian.master annotation
- [Config] updateconfigs following 6.2 rebase
* Miscellaneous upstream changes
- Revert "UBUNTU: [Config] updateconfigs following 6.2 rebase"
-- Paolo Pisati Wed, 22 Mar 2023 09:46:35
+0100
** Changed in: linux-kvm (Ubuntu Lunar)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1998244
Title:
kselftest net/fib_nexthop_nongw.sh fails
Status in linux-kvm package in Ubuntu:
Fix Released
Status in linux-kvm source package in Jammy:
Fix Released
Status in linux-kvm source package in Kinetic:
Fix Released
Status in linux-kvm source package in Lunar:
Fix Released
Bug description:
18272 03:33:07 DEBUG| Persistent state client._record_indent
now set to 2
18273 03:33:07 DEBUG| Persistent state
client.unexpected_reboot now set to
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh',
'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh')
18274 03:33:07 DEBUG| Waiting for pid 58525 for 2700 seconds
18275 03:33:07 WARNI| System python is too old, crash
handling disabled
18276 03:33:07 DEBUG| Running 'make run_tests -C net
TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
18277 03:33:07 DEBUG| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
18278 03:33:07 DEBUG| [stdout] make --no-builtin-rules
ARCH=x86 -C ../../../.. headers_install
18279 03:33:07 DEBUG| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18280 03:33:08 DEBUG| [stdout] INSTALL ./usr/include
18281 03:33:08 DEBUG| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18282 03:33:08 DEBUG| [stdout] TAP version 13
18283 03:33:08 DEBUG| [stdout] 1..1
18284 03:33:08 DEBUG| [stdout] # selftests: net:
fib_nexthop_nongw.sh
18285 03:33:08 DEBUG| [stdout] # Error: Unknown device type.
18286 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18287 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18288 03:33:08 DEBUG| [stdout] # TEST: nexthop: get route
with nexthop without gw[ OK ]
18289 03:33:18 DEBUG| [stdout] # TEST: nexthop: ping through
nexthop without gw [FAIL]
18290 03:33:18 DEBUG| [stdout] not ok 1 selftests: net:
fib_nexthop_nongw.sh # exit=1
18291 03:33:18 DEBUG| [stdout] make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
--
SRU Justification:
[Impact]
* Without Kernel support for the Dummy net driver, it is not possible
to successfully run selftests that use it. This includes as per this
bug net/fib_nexthop_nongw.sh, but also could potentially include other
such as rtnetlink.sh, fib_rule_tests.sh, forwarding/* etc.
[Fix]
* Custom patch to enable CONFIG_DUMMY=m
[Test Plan]
* Before the fix, the net/fib_nexthop_nongw.sh script will fail in the
specific line which does
$ ip -n h1 link add name eth0 type dummy
Error: Unknown device type.
After the fix it does not fail.
[Where problems could occur]
* The regression can be considered as low, since we are adding
functionality not previously present.
[Other Info]
* There does not seem to be a historical reason for removing it from
linux-kvm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1998244/+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 2012917] [NEW] linux-image-6.2.0-18-generic panics at boot
Public bug reported: Ubuntu 23.04 running linux-image-6.2.0-18-generic panics at boot. Complains about not finding a boot filesystem. System boots normally with linux-image 6.1.15 Don't know how to collect data on this apart from taking a photo of the assert. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: boot crash -- 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/2012917 Title: linux-image-6.2.0-18-generic panics at boot Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 23.04 running linux-image-6.2.0-18-generic panics at boot. Complains about not finding a boot filesystem. System boots normally with linux-image 6.1.15 Don't know how to collect data on this apart from taking a photo of the assert. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2012917/+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 2012590] Re: Fix broken micmute LED on AMD ACP DMIC
Updated to Jammy 1.2.6.3-1ubuntu1.5, Mic-mute LED works as expected. ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2012590 Title: Fix broken micmute LED on AMD ACP DMIC Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Mic-mute LED is broken on some AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012590/+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 2012590] Re: Fix broken micmute LED on AMD ACP DMIC
Thanks to @seb128 for your kindly help. ** Changed in: alsa-ucm-conf (Ubuntu Kinetic) Importance: Undecided => Critical ** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2012590 Title: Fix broken micmute LED on AMD ACP DMIC Status in HWE Next: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Sometimes Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012590/+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 2012590] Re: Fix broken micmute LED on AMD ACP DMIC
Also kinetic 1.2.6.3-1ubuntu4.2 ** Description changed: [Impact] - Mic-mute LED is broken on some AMD ACP DMIC. + Sometimes Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD ACP DMIC. [Fix] - Update Mic LED settings for ACP DMIC, + Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2012590 Title: Fix broken micmute LED on AMD ACP DMIC Status in HWE Next: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Sometimes Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD ACP DMIC. [Fix] Update Mic LED settings for ACP DMIC, turn the LED on when only internal mic is off. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012590/+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 2003816] Re: Regression in ext4 during online resize
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: Fix Committed Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug was fixed in the package linux - 5.15.0-69.76 --- linux (5.15.0-69.76) jammy; urgency=medium * jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092) * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325) - NFS: Correct timing for assigning access cache timestamp linux (5.15.0-68.75) jammy; urgency=medium * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING - tpm: acpi: Call acpi_put_table() to fix memory leak - tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak - tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak - SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails - kcsan: Instrument memcpy/memset/memmove with newer Clang - ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio -
[Kernel-packages] [Bug 2007585] Re: Jammy update: v6.1.12 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2007584] Re: Jammy update: v6.1.11 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2007583] Re: Jammy update: v6.1.10 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2007516] Re: screen flicker after PSR2 enabled
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2007578] Re: Jammy update: v6.1.9 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 1972898] Re: Kernel Bug: 22.04, EXT4, samba (smbd) on MDADM raid6: Copying large volume of files.
I just got bit by this, too. Was transferring ~40T via rsync to a new NAS setup... got about 12T in and it just stopped. Eventually realized the mountpoint was unresponsive. Rebooting and kicking rsync back off resulted in the same scenario almost immediately. The machine in question is running 5.15.27. I'm going to upgrade the kernel and see if the problem persists... Does anyone know if this is fixed or being worked on upstream already? -- 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/1972898 Title: Kernel Bug: 22.04,EXT4, samba (smbd) on MDADM raid6: Copying large volume of files. Status in linux package in Ubuntu: Confirmed Bug description: 60 Drive MDADM Raid 6, ext4, Ubuntu 22.04. Issue reproduced on both Supermicro SSG-6048R and HP ProLiant DL380 servers. System was stable on Ubuntu 20.04. Unstable following upgrade to 22.04 (kernel version 5.15) To reproduce kernel error, copy thousands of files (~1tb of data) to samba-share from any windows computer. After some time(seconds to minutes), a Kernel error is thrown, smbd process is unresponsive and cannot be killed, file transfer stops, the mounted drive freezes (directory operations including ls,mv,cp on the mount are not possible) and the system needs to be hard-rebooted. Quite an unhappy outcome :) I then moved the 60 drives to an external enclosure, and connected to a new computer (HP ProLiant DL380). After assembling the raid drive, with a fresh install of Ubuntu 22.04 on the new system, the kernel error was reproduced. I cannot reproduce the error copying via nfs or copying files on the drive itself. Single files or small transfers proceed without error. Filesystem passes fsck. Happy to assist in troubleshooting in any way. Kernel error message from both systems follows. **New System (HP ProLiant DL380) Kernel Error** May 10 01:32:49 nas3 kernel: [ 1463.900175] [ cut here ] May 10 01:32:49 nas3 kernel: [ 1463.900179] kernel BUG at fs/ext4/xattr.c:2071! May 10 01:32:49 nas3 kernel: [ 1463.900214] invalid opcode: [#1] SMP PTI May 10 01:32:49 nas3 kernel: [ 1463.900233] CPU: 0 PID: 5989 Comm: smbd Not tainted 5.15.0-27-generic #28-Ubuntu May 10 01:32:49 nas3 kernel: [ 1463.900939] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 04/25/2017 May 10 01:32:49 nas3 kernel: [ 1463.901560] RIP: 0010:ext4_xattr_block_set+0xbba/0xbd0 May 10 01:32:49 nas3 kernel: [ 1463.902190] Code: c7 45 8c f4 ff ff ff eb b4 48 8b 7d 90 48 c7 c1 7f 12 61 a8 ba 2d 08 00 00 48 c7 c6 d0 3c 25 a8 e8 9b 6f ff ff e9 a5 fe ff ff <0> May 10 01:32:49 nas3 kernel: [ 1463.903445] RSP: 0018:a59e0b51f9c0 EFLAGS: 00010206 May 10 01:32:49 nas3 kernel: [ 1463.904080] RAX: 0003 RBX: 97aa0490b680 RCX: a860a8e7 May 10 01:32:49 nas3 kernel: [ 1463.904727] RDX: 0261 RSI: RDI: 0003cca0 May 10 01:32:49 nas3 kernel: [ 1463.905384] RBP: a59e0b51fa70 R08: 97aa21824138 R09: May 10 01:32:49 nas3 kernel: [ 1463.906051] R10: 97aa0f6e87e0 R11: 97aae9073ff0 R12: May 10 01:32:49 nas3 kernel: [ 1463.906738] R13: 97ada77feac0 R14: 0003165b R15: May 10 01:32:49 nas3 kernel: [ 1463.907411] FS: 7f06ceb61a40() GS:97b93f80() knlGS: May 10 01:32:49 nas3 kernel: [ 1463.908049] CS: 0010 DS: ES: CR0: 80050033 May 10 01:32:49 nas3 kernel: [ 1463.908697] CR2: 55c076d0d4f8 CR3: 00029e6fe003 CR4: 001706f0 May 10 01:32:49 nas3 kernel: [ 1463.909349] Call Trace: May 10 01:32:49 nas3 kernel: [ 1463.909989] May 10 01:32:49 nas3 kernel: [ 1463.910624] ? jbd2_journal_get_write_access+0x43/0x90 May 10 01:32:49 nas3 kernel: [ 1463.911360] ext4_xattr_set_handle+0x487/0x620 May 10 01:32:49 nas3 kernel: [ 1463.912032] __ext4_set_acl+0xc1/0x130 May 10 01:32:49 nas3 kernel: [ 1463.912689] ext4_init_acl+0xe8/0x160 May 10 01:32:49 nas3 kernel: [ 1463.913327] __ext4_new_inode+0xf60/0x14e0 May 10 01:32:49 nas3 kernel: [ 1463.913962] ? path_parentat+0x4c/0x90 May 10 01:32:49 nas3 kernel: [ 1463.914595] ext4_mkdir+0x157/0x330 May 10 01:32:49 nas3 kernel: [ 1463.915265] vfs_mkdir+0x142/0x200 May 10 01:32:49 nas3 kernel: [ 1463.915883] do_mkdirat+0x120/0x140 May 10 01:32:49 nas3 kernel: [ 1463.916501] __x64_sys_mkdirat+0x51/0x70 May 10 01:32:49 nas3 kernel: [ 1463.917115] do_syscall_64+0x5c/0xc0 May 10 01:32:49 nas3 kernel: [ 1463.917733] ? exit_to_user_mode_prepare+0x37/0xb0 May 10 01:32:49 nas3 kernel: [ 1463.918365] ? syscall_exit_to_user_mode+0x27/0x50 May 10 01:32:49 nas3 kernel: [ 1463.919035] ? __x64_sys_newfstatat+0x1c/0x20 May 10 01:32:49 nas3 kernel: [ 1463.919665] ?
[Kernel-packages] [Bug 1967131] Re: CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic
Re-opening as until linux-kvm is deprecated or the CPC team moves over to using linux-virtual for KVM images, this is the kernel we're dealing with and that kernel should be functional. ** Changed in: linux-kvm (Ubuntu) Status: Invalid => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967131 Title: CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic Status in linux-kvm package in Ubuntu: Triaged Bug description: -kvm flavor has CONFIG_NR_CPUS=64 although -generic has CONFIG_NR_CPUS=8192 these days. It will be a problem especially when launching a VM on top of a hypervisor with more than 64 CPU threads available. Then the guest can only use up to 64 vCPUs even when more vCPUs are allocated by a hypervisor. I've checked the latest available package for Jammy, but there was no change around CONFIG_NR_CPUS. https://launchpad.net/ubuntu/+source/linux-kvm/5.15.0-1003.3 $ lsb_release -r Release:20.04 $ dpkg -S /boot/config* linux-modules-5.4.0-105-generic: /boot/config-5.4.0-105-generic linux-modules-5.4.0-1059-kvm: /boot/config-5.4.0-1059-kvm $ grep CONFIG_NR_CPUS /boot/config* /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_BEGIN=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_END=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_DEFAULT=8192 /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS=8192 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_BEGIN=2 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_END=512 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_DEFAULT=64 /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS=64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1967131/+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 2012939] [NEW] Pull-request to address a number of issues in the nvidia-tegra -1010.10
Public bug reported: [Impact] Adding these patches address a number of differences between the Ubuntu kernel and the internal NVIDIA kernel. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2012939 Title: Pull-request to address a number of issues in the nvidia-tegra -1010.10 Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches address a number of differences between the Ubuntu kernel and the internal NVIDIA kernel. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2012939/+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 1998285] Re: 5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
5.15.0-69-generic -no change as far I can tell.
--
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/1998285
Title:
5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
Status in linux package in Ubuntu:
Confirmed
Bug description:
from dmesg
1.313665] UBSAN: shift-out-of-bounds in
/build/linux-JjvoxS/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
[1.313668] shift exponent 64 is too large for 64-bit type 'long long
unsigned int'
there is also a crash but i don't know if it's related.
1.313671] Call Trace:
[1.313672]
[1.313673] show_stack+0x52/0x5c
[1.313676] dump_stack_lvl+0x4a/0x63
[1.313678] dump_stack+0x10/0x16
[1.313679] ubsan_epilogue+0x9/0x49
[1.313680] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[1.313682] initialize_nocpsch.cold+0x15/0x59 [amdgpu]
[1.313841] device_queue_manager_init+0x208/0x3b0 [amdgpu]
[1.313946] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu]
[1.314079] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu]
[1.314178] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu]
[1.314323] amdgpu_device_init.cold+0x25b/0x7db [amdgpu]
[1.314463] ? do_pci_enable_device+0xdb/0x110
[1.314466] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
[1.314556] amdgpu_pci_probe+0x1ce/0x260 [amdgpu]
[1.314642] local_pci_probe+0x48/0x90
[1.314644] pci_device_probe+0x119/0x1f0
[1.314645] really_probe+0x21f/0x420
[1.314647] __driver_probe_device+0x119/0x190
[1.314648] driver_probe_device+0x23/0xc0
[1.314650] __driver_attach+0xbd/0x1f0
[1.314651] ? __device_attach_driver+0x120/0x120
[1.314652] bus_for_each_dev+0x7c/0xd0
[1.314654] driver_attach+0x1e/0x30
[1.314655] bus_add_driver+0x148/0x220
[1.314656] driver_register+0x95/0x100
[1.314657] __pci_register_driver+0x68/0x70
[1.314659] amdgpu_init+0x7c/0x1000 [amdgpu]
[1.314747] ? 0xc0fc
[1.314748] do_one_initcall+0x46/0x1e0
[1.314750] ? kmem_cache_alloc_trace+0x19e/0x2e0
[1.314752] do_init_module+0x52/0x260
[1.314753] load_module+0xb2b/0xbc0
[1.314754] __do_sys_finit_module+0xbf/0x120
[1.314756] __x64_sys_finit_module+0x18/0x20
[1.314757] do_syscall_64+0x59/0xc0
[1.314758] ? ksys_lseek+0x85/0xc0
[1.314759] ? exit_to_user_mode_prepare+0x37/0xb0
[1.314761] ? syscall_exit_to_user_mode+0x27/0x50
[1.314762] ? __x64_sys_lseek+0x18/0x20
[1.314763] ? do_syscall_64+0x69/0xc0
[1.314764] entry_SYSCALL_64_after_hwframe+0x61/0xcb
[1.314766] RIP: 0033:0x7fef87ab8a3d
[1.314767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
[1.314768] RSP: 002b:7fffe67aa7c8 EFLAGS: 0246 ORIG_RAX:
0139
[1.314770] RAX: ffda RBX: 55d1d00078a0 RCX:
7fef87ab8a3d
[1.314771] RDX: RSI: 7fef87c4f441 RDI:
0018
[1.314772] RBP: 0002 R08: R09:
0002
[1.314772] R10: 0018 R11: 0246 R12:
7fef87c4f441
[1.314773] R13: 55d1d002ea30 R14: 55d1d0011600 R15:
55d1d002eb10
[1.314774]
[1.314778]
gpu is Amd r 380 tonga 4Gb.
I was adviced to try 6.0 series of kernel and I dont see the ubsan error
there but I would like to get the fixes backported 5.15 series.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarkko 1322 F pulseaudio
/dev/snd/controlC1: jarkko 1322 F pulseaudio
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-09-19 (71 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: ASUS System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1007-oem
root=UUID=62a471af-17fd-40e2-9304-b3e113e4f47f ro quiet splash
ProcVersionSignature: Ubuntu 6.0.0-1007.7-oem 6.0.3
RelatedPackageVersions:
linux-restricted-modules-6.0.0-1007-oem N/A
linux-backports-modules-6.0.0-1007-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: vanessa
Uname: Linux 6.0.0-1007-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
[Kernel-packages] [Bug 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2009014] Re: Some QHD panels fail to refresh when PSR2 enabled
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2008871] Re: Screen backlight keeps in minimized and can't change it with amdgpu
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1013.13 --- linux-oem-6.0 (6.0.0-1013.13) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1013.13 -proposed tracker (LP: #2008351) * CVE-2023-1281 - net/sched: tcindex: update imperfect hash filters respecting rcu * CVE-2023-1032 - net: avoid double iput when sock_alloc_file fails * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip -- Timo Aaltonen Thu, 16 Mar 2023 17:59:47 +0200 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Won't Fix => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2196 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1032 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1281 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2006945] Re: New DG2 workarounds
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 1999375] Re: Update dg2_dmc to 2.08
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
This bug was fixed in the package lttng-modules - 2.12.5-1ubuntu2~20.04.5 --- lttng-modules (2.12.5-1ubuntu2~20.04.5) focal; urgency=medium * Backport fixes to jbd2 format in 5.4.229 (LP: #2004644) - d/p/0013-fix-jbd2-use-the-correct-print-format.patch - d/p/0014-fix-jbd2-use-the-correct-print-format-v5.10.163.patch - d/p/0015-fix-jbd2-upper-bound-for-v5.10.163.patch - d/p/0016-fix-jbd2-use-the-correct-print-format-v5.4.229.patch -- Roxana Nicolescu Fri, 03 Feb 2023 11:09:19 +0200 ** Changed in: lttng-modules (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in lttng-modules source package in Bionic: Fix Released Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Released Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: Fix Released Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: Fix Released Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout]
