[Kernel-packages] [Bug 2051410] Re: AMD-GPU, decrease video resolution leads to black screen
** Description changed: Only the highest resolution can be set (1920x1080). If the resolution will be set to e.g,: 1280x720, only a black screen will be seen. Also games, or "Wine" application does not work, former resolution settings can not be changed, start the "Wine" application leads also to a black screen (rebooting necessary). Additionalinformation Xorg.0.log, resolution modified : [ 4028.159] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4028.170] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4028.170] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4253.595] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4254.499] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4254.499] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4254.508] (II) AMDGPU(0): Allocate new frame buffer 1280x720 [ 4254.509] (II) AMDGPU(0): => pitch 5120 bytes [ 4254.859] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4254.859] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4254.859] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4255.673] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4255.674] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4255.674] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.307] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.307] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.307] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.768] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.768] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.768] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4274.945] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4274.945] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4274.969] (II) AMDGPU(0): Allocate new frame buffer 1920x1080 [ 4274.984] (II) AMDGPU(0): => pitch 7680 bytes [ 4276.213] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.213] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.213] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4276.327] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.327] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.327] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.060] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.060] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.060] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.180] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.180] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.180] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4292.371] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4293.277] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4293.277] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4293.293] (II) AMDGPU(0): Allocate new frame buffer 1680x1050 [ 4293.294] (II) AMDGPU(0): => pitch 7168 bytes [ 4293.642] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4293.642] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4293.642] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.332] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.332] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.332] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.416] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.416] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.416] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4295.110] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4295.110] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4295.110] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4313.944] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4313.944] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4313.953] (II) AMDGPU(0): Allocate new frame buffer 1920x1080 [ 4313.954] (II) AMDGPU(0): => pitch 7680 bytes
[Kernel-packages] [Bug 2051410] [NEW] AMD-GPU, decrease video resolution leads to black screen
Public bug reported: Only the highest resolution can be set (1920x1080). If the resolution will be set to e.g,: 1280x720, only a black screen will be seen. Also games, or "Wine" application does not work, former resolution settings can not be changed, start the "Wine" application leads also to a black screen (rebooting necessary). Additionalinformation Xorg.0.log, resolution modified : [ 4028.159] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4028.170] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4028.170] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4253.595] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4254.499] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4254.499] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4254.508] (II) AMDGPU(0): Allocate new frame buffer 1280x720 [ 4254.509] (II) AMDGPU(0): => pitch 5120 bytes [ 4254.859] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4254.859] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4254.859] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4255.673] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4255.674] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4255.674] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.307] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.307] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.307] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.768] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.768] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.768] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4274.945] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4274.945] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4274.969] (II) AMDGPU(0): Allocate new frame buffer 1920x1080 [ 4274.984] (II) AMDGPU(0): => pitch 7680 bytes [ 4276.213] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.213] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.213] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4276.327] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.327] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.327] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.060] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.060] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.060] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.180] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.180] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.180] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4292.371] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4293.277] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4293.277] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4293.293] (II) AMDGPU(0): Allocate new frame buffer 1680x1050 [ 4293.294] (II) AMDGPU(0): => pitch 7168 bytes [ 4293.642] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4293.642] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4293.642] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.332] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.332] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.332] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.416] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.416] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.416] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4295.110] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4295.110] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4295.110] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4313.944] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4313.944] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4313.953] (II) AMDGPU(0): Allocate new frame buffer 1920x1080 [ 4313.954] (II) AMDGPU(0): => pitch 7680 bytes lspci -k 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex Subsystem: Advanced Micro Devices,
[Kernel-packages] [Bug 2039009] Re: do not ship ZSTD compressed modules in jammy/hwe-6.5 kernels
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039009 Title: do not ship ZSTD compressed modules in jammy/hwe-6.5 kernels Status in linux package in Ubuntu: Expired Status in linux source package in Jammy: Expired Bug description: Providing zstd compressed modules may break user-space scripts/tools/binaries that are relying on the .ko naming schema. The kernel can still support ZSTD compressed modules (via CONFIG_MODULE_COMPRESS_ZSTD), but our shipped kernel modules will be just regular .ko files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039009/+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 2039009] Re: do not ship ZSTD compressed modules in jammy/hwe-6.5 kernels
[Expired for linux (Ubuntu Jammy) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039009 Title: do not ship ZSTD compressed modules in jammy/hwe-6.5 kernels Status in linux package in Ubuntu: Expired Status in linux source package in Jammy: Expired Bug description: Providing zstd compressed modules may break user-space scripts/tools/binaries that are relying on the .ko naming schema. The kernel can still support ZSTD compressed modules (via CONFIG_MODULE_COMPRESS_ZSTD), but our shipped kernel modules will be just regular .ko files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039009/+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 2039010] Re: revert support for arbitrary symbol length in modversion in hwe kernels
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039010 Title: revert support for arbitrary symbol length in modversion in hwe kernels Status in linux package in Ubuntu: Expired Status in linux source package in Jammy: Expired Bug description: The following patch may break user-space, providing an actual ABI change: UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion This is not critical for new releases (also considering that the potential breakage is unlikely to happen, unless some tools/scripts/apps are inspecting modules' internals - likely only kmod tools, that are ok with this change), but for LTS releases it is just safer to prevent adding this change. Keep in mind that this patch is required to enable Rust support in the generic kernel, but it is not required for hwe kernels, because we do not enable Rust support for them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039010/+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 2039010] Re: revert support for arbitrary symbol length in modversion in hwe kernels
[Expired for linux (Ubuntu Jammy) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039010 Title: revert support for arbitrary symbol length in modversion in hwe kernels Status in linux package in Ubuntu: Expired Status in linux source package in Jammy: Expired Bug description: The following patch may break user-space, providing an actual ABI change: UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion This is not critical for new releases (also considering that the potential breakage is unlikely to happen, unless some tools/scripts/apps are inspecting modules' internals - likely only kmod tools, that are ok with this change), but for LTS releases it is just safer to prevent adding this change. Keep in mind that this patch is required to enable Rust support in the generic kernel, but it is not required for hwe kernels, because we do not enable Rust support for them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039010/+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 2043962] Re: [Mediatek] mt8195-demo: enable CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP
[Expired for linux (Ubuntu Noble) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Noble) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043962 Title: [Mediatek] mt8195-demo: enable CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP Status in linux package in Ubuntu: Expired Status in linux source package in Noble: Expired Bug description: [SRU Justification] [Impact] emmc storage is not usable after booting. [Fix] CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP need to be built-in to supply clock and power as early as possible, in order to have the emmc storage for further installation. both of the modules were in initramfs already but still not be able to bring up the emmc. according to mediatek, these two drivers should be built-in for further peripherals usage. [Test Case] 1. build test. 2. testing on the target device, mediatek g1200 evk board, and check the emmc storage could be recognize and mountable after booting. [Where problems could occur] the risk would be low because both drivers are only used on mediatek platform. [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043962/+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 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux-aws (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic Status in linux-aws package in Ubuntu: Incomplete Status in linux-hwe-6.5 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Confirmed Bug description: Loading the nvidia driver dkms modules with "modprove nvidia" will result in the host hanging and being completely unusable. This was reproduced using both the linux generic and linux-aws kernels on lunar and mantic using an AWS g5g.xlarge instance. To reproduce using the generic kernel: # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge. # Install the linux generic kernel from lunar-updates: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o DPkg::Options::=--force-confold linux-generic # Boot to the linux-generic kernel (this can be accomplished by removing the existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel) $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws linux-image-aws linux-modules-6.2.0-1008-aws linux-headers-6.2.0-1008-aws linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws $ reboot # Install the Nvidia 535-server driver DKMS package: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server # Enable the driver $ sudo modprobe nvidia # At this point the system will hang and never return. # A reboot instead of a modprobe will result in a system that never boots up all the way. I was able to recover the console logs from such a system and found (the full captured log is attached): [1.964942] nvidia: loading out-of-tree module taints kernel. [1.965475] nvidia: module license 'NVIDIA' taints kernel. [1.965905] Disabling lock debugging due to kernel taint [1.980905] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 [2.012715] [ 62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 62.025807] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=3301 [ 62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4) [ 62.027018] Task dump for CPU 3: [ 62.027290] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000e [ 62.028066] Call trace: [ 62.028273] __switch_to+0xbc/0x100 [ 62.028567] 0x228 Timed out for waiting the udev queue being empty. Timed out for waiting the udev queue being empty. [ 242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 242.045655] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=12303 [ 242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4) [ 242.046874] Task dump for CPU 3: [ 242.047146] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000f [ 242.047922] Call trace: [ 242.048128] __switch_to+0xbc/0x100 [ 242.048417] 0x228 Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... [ 384.001142] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [modprobe:215] [ 384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P OE 6.2.0-26-generic #26-Ubuntu [ 384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018 [ 384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4 [ 384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4 [ 384.006108] sp : 889a3a70 [ 384.006381] x29: 889a3a70 x28: 0003 x27:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.15.0.1051.46)
All autopkgtests for the newly accepted linux-meta-oracle (5.15.0.1051.46) for jammy have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.35-0ubuntu3.6 (arm64) 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-meta-oracle [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 2046657] Re: mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- 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/2046657 Title: mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The msdhci-of-dwcmshc driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. [Test Case] * Boot BF3 platform, verify no new errors [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2046657/+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 2049922] Re: PCI ATS quirk patch needed for IDPF
Patches sent to mailing list:
Focal: https://lists.ubuntu.com/archives/kernel-team/2024-January/148463.html
Bionic: https://lists.ubuntu.com/archives/kernel-team/2024-January/148458.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2049922
Title:
PCI ATS quirk patch needed for IDPF
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Bionic:
In Progress
Status in linux-gcp source package in Focal:
In Progress
Bug description:
[Impact]
* Request from Google to include Intel patches for IDPF support if used from
out-of-tree module to prevent system instability.
[Fixes]
f18b1137d38c ("PCI: Extract ATS disabling to a helper function")
a18615b1cfc0 ("PCI: Disable ATS for specific Intel IPU E2000 devices")
[Test Case]
* Compile test
* Boot test
* Test on non-IDPF instance
* Tested by Google
[Where things could go wrong]
* Low chance of regression, changes very isolated
[Other Info]
* SF #00376470
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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 2049922] Re: PCI ATS quirk patch needed for IDPF
** Description changed:
[Impact]
- * Request from Google to include Intel patches for IDPF support if used from
out-of-tree module to
- prevent system instability
+ * Request from Google to include Intel patches for IDPF support if used from
+ out-of-tree module to prevent system instability.
- [Fix]
+ [Fixes]
+ f18b1137d38c ("PCI: Extract ATS disabling to a helper function")
+ a18615b1cfc0 ("PCI: Disable ATS for specific Intel IPU E2000 devices")
- * Upstream
-
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.7=a18615b1cfc04f00548c60eb9a77e0ce56e848fd
[Test Case]
* Compile test
* Boot test
* Test on non-IDPF instance
+ * Tested by Google
[Where things could go wrong]
* Low chance of regression, changes very isolated
[Other Info]
* SF #00376470
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2049922
Title:
PCI ATS quirk patch needed for IDPF
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Bionic:
In Progress
Status in linux-gcp source package in Focal:
In Progress
Bug description:
[Impact]
* Request from Google to include Intel patches for IDPF support if used from
out-of-tree module to prevent system instability.
[Fixes]
f18b1137d38c ("PCI: Extract ATS disabling to a helper function")
a18615b1cfc0 ("PCI: Disable ATS for specific Intel IPU E2000 devices")
[Test Case]
* Compile test
* Boot test
* Test on non-IDPF instance
* Tested by Google
[Where things could go wrong]
* Low chance of regression, changes very isolated
[Other Info]
* SF #00376470
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
Ran AppArmor tests from the QA Regression Tests [1] and POSIX mqueue tests from the AppArmor test suite and they all passed as expected. georgia@sec-jammy-amd64:/tmp/apparmor-3.0.4/tests/regression/apparmor$ uname -a Linux sec-jammy-amd64 5.15.0-1048-intel-iotg #54-Ubuntu SMP Thu Jan 18 18:39:09 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux georgia@sec-jammy-amd64:~/qrt-test-apparmor$ sudo ./test-apparmor.py . -- Ran 62 tests in 1246.031s OK (skipped=2) georgia@sec-jammy-amd64:/tmp$ apt source apparmor georgia@sec-jammy-amd64:/tmp$ cd apparmor-3.0.4/tests/regression/apparmor/ georgia@sec-jammy-amd64:/tmp/apparmor-3.0.4/tests/regression/apparmor$ USE_SYSTEM=1 make georgia@sec-jammy-amd64:/tmp/apparmor-3.0.4/tests/regression/apparmor$ sudo ./posix_mq.sh [sudo] password for georgia: BAD PASSWORD: The password fails the dictionary check - it is based on a dictionary word xpass: POSIX MQUEUE (confined root - mqueue label 1) xpass: POSIX MQUEUE (confined root - mqueue label 1 : mq_notify) xpass: POSIX MQUEUE (confined root - mqueue label 1 : select) xpass: POSIX MQUEUE (confined root - mqueue label 1 : poll) xpass: POSIX MQUEUE (confined root - mqueue label 1 : epoll) xpass: POSIX MQUEUE (confined root - mqueue label 2) xpass: POSIX MQUEUE (confined root - mqueue label 2 : mq_notify) xpass: POSIX MQUEUE (confined root - mqueue label 2 : select) xpass: POSIX MQUEUE (confined root - mqueue label 2 : poll) xpass: POSIX MQUEUE (confined root - mqueue label 2 : epoll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : mq_notify) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : select) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : poll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : epoll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : mq_notify) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : select) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : poll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : epoll) [1] https://launchpad.net/qa-regression-testing ** Tags removed: verification-needed-jammy-linux-intel-iotg ** Tags added: verification-done-jammy-linux-intel-iotg -- 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/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+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 2007055] Re: cifs/samba mount not preserving file timestamps
cat /proc/mounts gives me something like: //rn214/user /media/rn214/user cifs rw,nosuid,nodev,relatime,vers=3.1.1,cache=strict,username=user,domain=DOMAIN,uid=1000,noforceuid,gid=1000,noforcegid,addr=10.1.2.3,file_mode=0770,dir_mode=0770,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1 0 0 (slightly anonymized) the other entries look very similar, i. e. with vers=3.1.1. They originate from such entries in /etc/fstab: //rn214/user /media/rn214/user cifs noauto,users,credentials=/home/user/.smbcredentials,iocharset=utf8,uid=1000,gid=1000,file_mode=0770,dir_mode=0770 0 0 On the rn214 typing samba -V gives me: -bash: samba: command not found , hence I pasted the result of smbstatus as root. There it said: Samba version 4.8.0 The script with rsync instead of cp executed with unspectacular results: Source modtime: 2020-01-01 12:34:56.0 +0100 Target modtime: 2020-01-01 12:34:56.0 +0100 PASS: Modtime preserved So this exact version of SAMBA on my particular version of Linux Mint Mate with that particular the Ubuntu Kernel with the aforementioned SMB mounts connected to a D-Link DGB-108 talking to that particular NetGear NAS with exactly that version of Linux 4.4.218.alpine.1/ReadyNASOS 6.10.8 seem preserve the modification time stamp at least for the two test instances covering the exact same parameters of rsync and cp. If that sounds a bit sarcastic: Yeah, intentionally so. For sure does not raise my confidence in allowing future updates. Eat that, Linux lovers! -- 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/2007055 Title: cifs/samba mount not preserving file timestamps Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Incomplete Bug description: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs
[Kernel-packages] [Bug 1613393] Re: Provide linux-perf package
We (server team) are working on the src:tuned[0] package, and several of its profiles make use of the python perf module. That module comes from the linux kernel AFAIK, and we are just not building it. In Fedora, it's shipped in the bin:python3-perf package: [root@f39 ~]# rpm -ql python3-perf /usr/lib/.build-id /usr/lib/.build-id/80 /usr/lib/.build-id/80/9022196f598cb3327545c2d497b1d9fdf55630 /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/PKG-INFO /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/SOURCES.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/dependency_links.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/top_level.txt /usr/lib64/python3.12/site-packages/perf.cpython-312-x86_64-linux-gnu.so /usr/share/licenses/python3-perf /usr/share/licenses/python3-perf/COPYING Built from the kernel-tools package in their case[1]. 0. https://launchpad.net/ubuntu/+source/tuned 1. https://src.fedoraproject.org/rpms/kernel-tools/blob/rawhide/f/kernel-tools.spec#_148 -- 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/1613393 Title: Provide linux-perf package Status in linux package in Ubuntu: Triaged Bug description: Debian renamed their linux-tools package to linux-perf a year ago. https://anonscm.debian.org/cgit/kernel/linux.git/commit/debian/changelog?id=c2faa8 The Debian package perf-tools-unstable followed the new name so I had to upload an Ubuntu version to revert that change. It would be nice if we didn't have to maintain that difference in Ubuntu. https://bugs.debian.org/795090 https://launchpad.net/ubuntu/+source/perf-tools- unstable/0.0.1~20160212+git0c13e83-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613393/+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 2045069] Re: Azure: Deprecate Netvsc and implement MANA direct
This bug is awaiting verification that the linux-azure/6.5.0-1012.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2045069 Title: Azure: Deprecate Netvsc and implement MANA direct Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Microsoft has asked for the inclusion of 3 patches that deprecate the use of netvsc in favor of MANA direct. hv_netvsc: Mark VF as slave before exposing it to user-mode: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8 hv_netvsc: Fix race of register_netdevice_notifier and VF register: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db hv_netvsc: fix race of netvsc and VF register_netdevice: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837 [Test Plan] Microsoft tested [Regression potential] User space that relies on netvsc will likely fail [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045069/+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 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
Verified that with linux-aws-edge 6.5.0.1012.12~22.04.1 the DKMS installation via $ sudo apt install -y nvidia-driver-535-server on an AWS g5g.xlarge goes through the driver comes up fine. Trying the same with linux-generic-hwe-22.04-edge 6.5.0-17-generic #17~22.04.1 on an Ampere Altra with 2x NVIDIA L4 still runs into the same hang with nvidia-headless-535-server (535.154.05-0ubuntu0.22.04.1). -- 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/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic Status in linux-aws package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525-server package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Confirmed Bug description: Loading the nvidia driver dkms modules with "modprove nvidia" will result in the host hanging and being completely unusable. This was reproduced using both the linux generic and linux-aws kernels on lunar and mantic using an AWS g5g.xlarge instance. To reproduce using the generic kernel: # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge. # Install the linux generic kernel from lunar-updates: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o DPkg::Options::=--force-confold linux-generic # Boot to the linux-generic kernel (this can be accomplished by removing the existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel) $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws linux-image-aws linux-modules-6.2.0-1008-aws linux-headers-6.2.0-1008-aws linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws $ reboot # Install the Nvidia 535-server driver DKMS package: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server # Enable the driver $ sudo modprobe nvidia # At this point the system will hang and never return. # A reboot instead of a modprobe will result in a system that never boots up all the way. I was able to recover the console logs from such a system and found (the full captured log is attached): [1.964942] nvidia: loading out-of-tree module taints kernel. [1.965475] nvidia: module license 'NVIDIA' taints kernel. [1.965905] Disabling lock debugging due to kernel taint [1.980905] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 [2.012715] [ 62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 62.025807] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=3301 [ 62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4) [ 62.027018] Task dump for CPU 3: [ 62.027290] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000e [ 62.028066] Call trace: [ 62.028273] __switch_to+0xbc/0x100 [ 62.028567] 0x228 Timed out for waiting the udev queue being empty. Timed out for waiting the udev queue being empty. [ 242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 242.045655] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=12303 [ 242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4) [ 242.046874] Task dump for CPU 3: [ 242.047146] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000f [ 242.047922] Call trace: [ 242.048128] __switch_to+0xbc/0x100 [ 242.048417] 0x228 Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... [ 384.001142] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [modprobe:215] [ 384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P OE 6.2.0-26-generic #26-Ubuntu [ 384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018 [ 384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4 [ 384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4 [ 384.006108] sp : 889a3a70 [ 384.006381] x29: 889a3a70 x28: 0003 x27: 00056d1fafa0 [ 384.006954]
[Kernel-packages] [Bug 2045919] Re: mlxbf-bootctl: fails to report info about cards using dev keys
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- 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/2045919 Title: mlxbf-bootctl: fails to report info about cards using dev keys Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] There is a gap in the mlxbf-bootctl driver logic, resulting in failure to report when a secure boot enabled card is using development keys. The program will instead report lifecycle state as "GA Secured" which is misleading. [Fix] Bring in the following upstream commit from linux-next: "mlxbf-bootctl: correctly identify secure boot with development keys" [Test Case] Enable secure boot on a BF3 card that is using development keys Login as root on BF3 Run the command "mlxbf-bootctl" Verify that the "lifecycle state" row shows "Secured (development)" [Regression Potential] Low risk change, cherry pick of upstream approved commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2045919/+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 1906067] Re: Boot from ISO - exFAT support missing
I don't know how Live ISO images are generated in Ubuntu. I thought it was the same as in Debian. -- 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/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+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 1906067] Re: Boot from ISO - exFAT support missing
You've filed a bug in debian against software which is not used in Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+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 1906067] Re: Boot from ISO - exFAT support missing
I have already submitted a patch, waiting for approval: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060346 ** Bug watch added: Debian Bug tracker #1060346 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060346 -- 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/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+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 2007055] Re: cifs/samba mount not preserving file timestamps
Awesome, thanks for the help. Could you run samba -V on the server to see the samba version running there? And then on the client, could you run: cat /proc/mounts and find the line with your share to see what version of the SMB protocol it ended up using? (It'll be a line like: //10.0.234.59/sambashare /media/ubuntu22btrfs_sambashare cifs rw,relatime,vers=3.1.1,cache=strict ) If you have the time and can run the same script but changing "cp -p" to "rsync -t" that would be really helpful too. This morning I started finding scenarios where one of "cp -p"/"rsync -t" would fail but not the other, depending on protocol. (Thought I was losing my mind this morning b/c one of my reliable reproducers had stopped - turned out I had changed the SMB protocol version on the client to see if it affected my other reproducer - it didn't, so I forgot I had changed it.) -- 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/2007055 Title: cifs/samba mount not preserving file timestamps Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Incomplete Bug description: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) the remote NAS is a synology appliance, running Samba version 4.10.18. SMB version 3 Steps to reproduce: 1. Similar setup, 1 device running 20.04, another running 22.04, otherwise up to date. 2. mount the NAS on both devices the exact same way $ sudo mount -t cifs -o vers=3.0,credentials=/etc/samba/smbcreds,iocharset=utf8,rw,uid=1000,gid=1000,dir_mode=0775,file_mode=0664 //nas/backup /media/scratch 3. on the 20.04 older desktop, create a test file and show the modify time $ fallocate -l 1M test1.txt $ stat test1.txt File: test1.txt Size: 1048576 Blocks: 2048 IO Block: 4096 regular file Device:
[Kernel-packages] [Bug 2007055] Re: cifs/samba mount not preserving file timestamps
OK, ran the script on my end, result was: Copy complete; sleeping 10 seconds before stat Source modtime: 2020-01-01 12:34:56.0 +0100 Target modtime: 2020-01-01 12:34:56.0 +0100 PASS: Modtime preserved Client: Kernel Linux 6.5.0-14-generic Operating System: Linux Mint 21.2 SAMBA: Version 4.15.13-Ubuntu And, as luck would have it: Surely enough I have full root ssh access to the NAS box. Sooo (after converting my priv key to something putty could digest): Server: Kernel: Linux 4.4.218.alpine.1 Operating System: ReadyNASOS 6.10.8 SAMBA: Samba version 4.8.0 (running protocol SMB3_11) Hope that helps your investigation. If there's anything I should post over there at https://community.netgear.com, just tell me. -- 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/2007055 Title: cifs/samba mount not preserving file timestamps Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Incomplete Bug description: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) the remote NAS is a synology appliance, running Samba version 4.10.18. SMB version 3 Steps to reproduce: 1. Similar setup, 1 device running 20.04, another running 22.04, otherwise up to date. 2. mount the NAS on both devices the exact same way $ sudo mount -t cifs -o vers=3.0,credentials=/etc/samba/smbcreds,iocharset=utf8,rw,uid=1000,gid=1000,dir_mode=0775,file_mode=0664 //nas/backup /media/scratch 3. on the 20.04 older desktop, create a test file and show the modify time $ fallocate -l 1M test1.txt $ stat test1.txt File: test1.txt Size: 1048576 Blocks: 2048 IO Block: 4096 regular file Device: 801h/2049d Inode: 13634663Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/desktop_user) Gid: ( 1000/desktop_user) Access:
[Kernel-packages] [Bug 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
I can reproduce the failure on mantic with both the DKMS and LRM drivers. Specifically what I'm doing to install these are: for DKMS: sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server for LRM: sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-headless-no-dkms-535-server linux-modules-nvidia-535-server-generic nvidia-utils-535-server I'm intentionally not using `ubuntu-drivers` to isolate this testing to just the installation and functioning of the drivers. -- 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/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic Status in linux-aws package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525-server package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Confirmed Bug description: Loading the nvidia driver dkms modules with "modprove nvidia" will result in the host hanging and being completely unusable. This was reproduced using both the linux generic and linux-aws kernels on lunar and mantic using an AWS g5g.xlarge instance. To reproduce using the generic kernel: # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge. # Install the linux generic kernel from lunar-updates: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o DPkg::Options::=--force-confold linux-generic # Boot to the linux-generic kernel (this can be accomplished by removing the existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel) $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws linux-image-aws linux-modules-6.2.0-1008-aws linux-headers-6.2.0-1008-aws linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws $ reboot # Install the Nvidia 535-server driver DKMS package: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server # Enable the driver $ sudo modprobe nvidia # At this point the system will hang and never return. # A reboot instead of a modprobe will result in a system that never boots up all the way. I was able to recover the console logs from such a system and found (the full captured log is attached): [1.964942] nvidia: loading out-of-tree module taints kernel. [1.965475] nvidia: module license 'NVIDIA' taints kernel. [1.965905] Disabling lock debugging due to kernel taint [1.980905] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 [2.012715] [ 62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 62.025807] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=3301 [ 62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4) [ 62.027018] Task dump for CPU 3: [ 62.027290] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000e [ 62.028066] Call trace: [ 62.028273] __switch_to+0xbc/0x100 [ 62.028567] 0x228 Timed out for waiting the udev queue being empty. Timed out for waiting the udev queue being empty. [ 242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 242.045655] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=12303 [ 242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4) [ 242.046874] Task dump for CPU 3: [ 242.047146] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000f [ 242.047922] Call trace: [ 242.048128] __switch_to+0xbc/0x100 [ 242.048417] 0x228 Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... [ 384.001142] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [modprobe:215] [ 384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P OE 6.2.0-26-generic #26-Ubuntu [ 384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018 [ 384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4 [ 384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4 [ 384.006108] sp :
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
** Changed in: linux (Ubuntu Mantic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+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 2051342] Re: Enable lowlatency settings in the generic kernel
** Description changed: [Impact] Ubuntu provides the "lowlatency" kernel: a kernel optimized for applications that have special "low latency" requirements. Currently, this kernel does not include any specific UBUNTU SAUCE patches to improve the extra "low latency" requirements, but the only difference is a small subset of .config options. Almost all these options are now configurable either at boot-time or even at run-time, with the only exception of CONFIG_HZ (250 in the generic kernel vs 1000 in the lowlatency kernel). Maintaining a separate kernel for a single config option seems a bit overkill and it is a significant cost of engineering hours, build time, regression testing time and resources. Not to mention the risk of the low-latency kernel falling behind and not being perfectly in sync with the latest generic kernel. Enabling the low-latency settings in the generic kernel has been evaluated before, but it has been never finalized due to the potential risk of performance regressions in CPU-intensive applications (increasing HZ from 250 to 1000 may introduce more kernel jitter in number crunching workloads). The outcome of the original proposal resulted in a re-classification of the lowlatency kernel as a desktop- oriented kernel, enabling additional low latency features (LP: #2023007). As we are approaching the release of the new Ubuntu 24.04 we may want to re-consider merging the low-latency settings in the generic kernel again. Following a detailed analisys of the specific low-latency features: - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown clock tick when possible across all the enabled CPUs if they are either idle or running 1 task - reduce kernel jitter of running tasks due to the periodic clock tick, must be enabled at boot time passing `nohz_full=`); this can actually help CPU-intensive workloads and it could provide much more benefits than the CONFIG_HZ difference (since it can potentially shutdown any kernel jitter on specific CPUs), this one should really be enabled anyway, considering that it is configurable at boot time - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to kthread context (reduce time spent in softirqs with preemption disabled to improve the overall system responsiveness, at the cost of introducing a potential performance penalty, because RCU callbacks are not processed by kernel threads); this should be enabled as well, since it is configurable at boot time (via the rcu_nocbs= parameter) - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a timed delay instead of executing them immediately (c'an provide 5~10% power-savings for idle or lightly-loaded systems, this is extremely useful for laptops / portable devices - https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/); this has the potential to introduce significant performance regressions, but in the Noble kernel we already have a SAUCE patch that allows to enable/disable this option at boot time (see LP: #2045492), and by default it will be disabled (CONFIG_RCU_LAZY_DEFAULT_OFF=y). - CONFIG_HZ=1000 last but not least, the only option that is *only* tunable at compile time. As already mentioned there is a potential risk of regressions for CPU-intensive applications, but they can be mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On the other hand, HZ=1000 can improve system responsiveness, that means most of the desktop and server applications will benefit from this (the largest part of the server workloads is I/O bound, more than CPU-bound, so they can benefit from having a kernel that can react faster at switching tasks), not to mention the benefit for the typical end users applications (gaming, live conferencing, multimedia, etc.). With all of that in place we can provide a kernel that has the flexibility to be more responsive, more performant and more power - efficient, simply by tuning run-time and boot-time options. + efficient (therefore more "generic"), simply by tuning run-time and + boot-time options. - Once these changes are applied we will be able to deprecate the - lowlatency kernel, saving engineering time and also reducing power + Moreover, once these changes are applied we will be able to deprecate + the lowlatency kernel, saving engineering time and also reducing power consumption (required to build the kernel and do all the testing). Optionally, we can also provide optimal "lowlatency" settings as a user- space package that would set the proper options in the kernel boot command line (GRUB, or similar). [Test case] There are plenty of benchmarks that can prove the validity of each one of the setting mentioned above, providing huge benefits in terms of system responsive. However, our main goal here is to
[Kernel-packages] [Bug 2046082] Re: zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
removing block, as that condition no longer applied due to reject.
** Tags removed: block-proposed-mantic
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2046082
Title:
zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[Impact]
* There's a typo in user-visible option (/etc/zfs/zed.d/zed.rc)
ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT introduced upstream
in 2.2.0-rc4 and SRU-ed to Mantic with 2.2.0-0ubuntu1~23.10.
* This could be fixed in Ubuntu before users start adopting it.
[Test Plan]
* Check whether /etc/zfs/zed.d/zed.rc ships the correct option.
* Actual:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
* Expected:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
[Regression Potential]
* Users of Mantic who upgraded to zfs-linux 2.2.0-0ubuntu1~23.10
(published to mantic-updates on 2023-12-08) _and_ enabled the
option (with typo) would have such functionality disabled.
[Other Info]
* This option (with typo) was introduced in commit d19304ffeec5
("zed: Add zedlet to power off slot when drive is faulted"),
and is present in:
- ZFS 2.2: zfs-2.2.0-rc4 (mantic-updates)
- ZFS 2.1: zfs-2.1.13
* It affects Ubuntu Noble and Mantic, but not Lunar or older.
* Fixed upstream with commit 3c7650491b9a ("zed: fix typo in
variable ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2046082/+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 1906067] Re: Boot from ISO - exFAT support missing
In grub2, the statement "insmod exfat" works fine for me. The problem comes from the fact that exfat module is NOT included by default in INITRAMFS file created by mkinitramfs program ( remember that the file named initrd is in fact an initramfs file ). This may considered as a bug by omission. Have a look at bug number 2038694. -- 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/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+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 2051342] Re: Enable lowlatency settings in the generic kernel
** Description changed: [Impact] Ubuntu provides the "lowlatency" kernel: a kernel optimized for applications that have special "low latency" requirements. Currently, this kernel does not include any specific UBUNTU SAUCE patches to improve the extra "low latency" requirements, but the only difference is a small subset of .config options. Almost all these options are now configurable either at boot-time or even at run-time, with the only exception of CONFIG_HZ (250 in the generic kernel vs 1000 in the lowlatency kernel). Maintaining a separate kernel for a single config option seems a bit overkill and it is a significant cost of engineering hours, build time, regression testing time and resources. Not to mention the risk of the low-latency kernel falling behind and not being perfectly in sync with the latest generic kernel. Enabling the low-latency settings in the generic kernel has been evaluated before, but it has been never finalized due to the potential risk of performance regressions in CPU-intensive applications (increasing HZ from 250 to 1000 may introduce more kernel jitter in number crunching workloads). The outcome of the original proposal resulted in a re-classification of the lowlatency kernel as a desktop- oriented kernel, enabling additional low latency features (LP: #2023007). As we are approaching the release of the new Ubuntu 24.04 we may want to re-consider merging the low-latency settings in the generic kernel again. Following a detailed analisys of the specific low-latency features: - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown clock tick when possible across all the enabled CPUs if they are either idle or running 1 task - reduce kernel jitter of running tasks due to the periodic clock tick, must be enabled at boot time passing `nohz_full=`); this can actually help CPU-intensive workloads and it could provide much more benefits than the CONFIG_HZ difference (since it can potentially shutdown any kernel jitter on specific CPUs), this one should really be enabled anyway, considering that it is configurable at boot time - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to kthread context (reduce time spent in softirqs with preemption disabled to improve the overall system responsiveness, at the cost of introducing a potential performance penalty, because RCU callbacks are not processed by kernel threads); this should be enabled as well, since it is configurable at boot time (via the rcu_nocbs= parameter) - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a timed delay instead of executing them immediately (c'an provide 5~10% power-savings for idle or lightly-loaded systems, this is extremely useful for laptops / portable devices - https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/); this has the potential to introduce significant performance regressions, but in the Noble kernel we already have a SAUCE patch that allows to enable/disable this option at boot time (see LP: #2045492), and by default it will be disabled (CONFIG_RCU_LAZY_DEFAULT_OFF=y). - CONFIG_HZ=1000 last but not least, the only option that is *only* tunable at compile time. As already mentioned there is a potential risk of regressions for CPU-intensive applications, but they can be mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On the other hand, HZ=1000 can improve system responsiveness, that means most of the desktop and server applications will benefit from this (the largest part of the server workloads is I/O bound, more than CPU-bound, so they can benefit from having a kernel that can react faster at switching tasks), not to mention the benefit for the typical end users applications (gaming, live conferencing, multimedia, etc.). + With all of that in place we can provide a kernel that has the + flexibility to be more responsive, more performant and more power + efficient, simply by tuning run-time and boot-time options. + + Once these changes are applied we will be able to deprecate the + lowlatency kernel, saving engineering time and also reducing power + consumption (required to build the kernel and do all the testing). + + Optionally, we can also provide optimal "lowlatency" settings as a user- + space package that would set the proper options in the kernel boot + command line (GRUB, or similar). + [Test case] - There are plenty of micro-benchmarks to prove the validity of each one - of the config mentioned above, in terms of system responsive. + There are plenty of benchmarks that can prove the validity of each one + of the setting mentioned above, providing huge benefits in terms of + system responsive. However, our main goal here is to mitigate as much as possible the risk - of regression for CPU-intensive applications, so the test case
[Kernel-packages] [Bug 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough
This is already Fix Released for L and M. It's not set in noble's 6.6.0-14.14, but in 6.8.0-2.2. Hence leaving it as Fix Committed for noble until we are on 6.8. ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Mantic) 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/2042853 Title: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] * Today no s390x-specific vfio-pci devices (zPCI) can be passed from a KVM host to a KVM guest (incl. secure execution guests in the context of confidential computing). * s390x PCI passthrough needs various changes in the s390x kernel zPCI code (incl. the new s390x-specific Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0 and got backported to 22.04/jammy as part of LP: #1853306. * Lunar an newer Ubuntu releases have the code already included from upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the config option is not set, hence zPCI pass-through is still not possible. [Fix] * To be able to make use of VFIO zPCI pass-through on s390x running newer Ubuntu releases (especially needed in the context of secure execution) the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs to be enabled and set to 'y'. [Test Case] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only available on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) [Regression Potential] * The regression potential is moderate, since the code is upstream for quite a while and already enabled in jammy. * The general way on using passthrough has not changed, with this change (config option) it's now just possible to passthrough zPCI on top. * CCW devices are not affected. * And this is s390x-specific anyway, so no other architectures are affected. [Other] * The enabling of the kernel config option is exactly the same for L, M and U/N, but I submitted separate patches due to slightly different context and offsets. __ === Description by mjros...@us.ibm.com === LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to enable enhanced interpretation of PCI passthrough on s390. It
[Kernel-packages] [Bug 2051342] Re: Enable lowlatency settings in the generic kernel
** Description changed: [Impact] Ubuntu provides the "lowlatency" kernel: a kernel optimized for applications that have special "low latency" requirements. Currently, this kernel does not include any specific UBUNTU SAUCE patches to improve the extra "low latency" requirements, but the only difference is a small subset of .config options. Almost all these options are now configurable either at boot-time or even at run-time, with the only exception of CONFIG_HZ (250 in the generic kernel vs 1000 in the lowlatency kernel). Maintaining a separate kernel for a single config option seems a bit overkill and it is a significant cost of engineering hours, build time, regression testing time and resources. Not to mention the risk of the low-latency kernel falling behind and not being perfectly in sync with the latest generic kernel. Enabling the low-latency settings in the generic kernel has been evaluated before, but it has been never finalized due to the potential risk of performance regressions in CPU-intensive applications (increasing HZ from 250 to 1000 may introduce more kernel jitter in number crunching workloads). The outcome of the original proposal resulted in a re-classification of the lowlatency kernel as a desktop- oriented kernel, enabling additional low latency features (LP: #2023007). As we are approaching the release of the new Ubuntu 24.04 we may want to re-consider merging the low-latency settings in the generic kernel again. Following a detailed analisys of the specific low-latency features: - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown clock tick when possible across all the enabled CPUs if they are either idle or running 1 task - reduce kernel jitter of running tasks due to the periodic clock tick, must be enabled at boot time passing `nohz_full=`); this can actually help CPU-intensive workloads and it could provide much more benefits than the CONFIG_HZ difference (since it can potentially shutdown any kernel jitter on specific CPUs), this one should really be enabled anyway, considering that it is configurable at boot time - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to kthread context (reduce time spent in softirqs with preemption disabled to improve the overall system responsiveness, at the cost of introducing a potential performance penalty, because RCU callbacks are not processed by kernel threads); this should be enabled as well, since it is configurable at boot time (via the rcu_nocbs= parameter) - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a - timed delay instead of executing them immediately (can provide 5~10% + timed delay instead of executing them immediately (c'an provide 5~10% power-savings for idle or lightly-loaded systems, this is extremely useful for laptops / portable devices - https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/); this has the potential to introduce significant performance regressions, but in the Noble kernel we already have a SAUCE patch that allows to - enable/disable this option at boot time (see LP: #2045492) + enable/disable this option at boot time (see LP: #2045492), and by + default it will be disabled (CONFIG_RCU_LAZY_DEFAULT_OFF=y). - CONFIG_HZ=1000 last but not least, the only option that is *only* tunable at compile time. As already mentioned there is a potential risk of regressions for CPU-intensive applications, but they can be mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On the other hand, HZ=1000 can improve system responsiveness, that means most of the desktop and server applications will benefit from this (the largest part of the server workloads is I/O bound, more than CPU-bound, so they can benefit from having a kernel that can react faster at switching tasks), not to mention the benefit for the typical end users applications (gaming, live conferencing, multimedia, etc.). - - Other latency-related options: - - - CONFIG_LATENCYTOP=y: we should definitely support latencytop in the - generic kernel, considering that we are shipping the user-space package [Test case] There are plenty of micro-benchmarks to prove the validity of each one of the config mentioned above, in terms of system responsive. However, our main goal here is to mitigate as much as possible the risk of regression for CPU-intensive applications, so the test case should be focused on this particular aspect. We also have the opportunity to test these changes using the lowlatency kernel, therefore a reasonable test plan could be defined as following. Test case (a CPU-intensive stress test) - stress-ng --matrix $(getconf _NPROCESSORS_ONLN) --timeout 5m --metrics-brief Metrics: - measure the bogo ops printed to stdout (not a great metric for real- world
[Kernel-packages] [Bug 2029917] Re: [Potential Regression] cpuhotplug related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
Similarly, the following tests also fail (crash the instance) on j/gcp-fips
with version 5.15.0-1048.56+fips1 during development cycle d2024.01.02 on the
n2d-standard-4.sev_snp instance:
- cpuhotplug:cpuhotplug02 in ubuntu_ltp and
- cpu-hotplug:cpu-on-off-test.sh in ubuntu_kernel_selftests
If necessary, another bug could be filed targeting GCP specifically.
--
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/2029917
Title:
[Potential Regression] cpuhotplug related tests triggers kernel bug
(arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Confirmed
Status in linux-aws source package in Focal:
Confirmed
Bug description:
Issue found with 5.4.0-1107.115~18.04.1 Bionic AWS and 5.4.0-1107.115
Focal AWS kernel, on c3.xlarge instance only.
cpu-hotplug related tests will crash the instance, they are:
* cpuset_hotplug in ubuntu_ltp_controllers
* cpuhotplug:cpuhotplug02 in ubuntu_ltp (comment #7 in this bug)
* cpu-hotplug:cpu-on-off-test.sh in ubuntu_kernel_selftests (comment #8 in
this bug)
Take cpuset_hotplug in ubuntu_ltp_controllers for example.
There is no output from the test itself (looks like it has crashed):
START ubuntu_ltp_controllers.cpuset_hotplug
ubuntu_ltp_controllers.cpuset_hotplug timestamp=1689920544timeout=4500
localtime=Jul 21 06:22:24
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.cpuset_hotplug',
'ubuntu_ltp_controllers.cpuset_hotplug')
Waiting for pid 925631 for 4500 seconds
System python is too old, crash handling disabled
(nothing after this point)
But from the console log you will see a kernel BUG and kernel panic:
[ 3451.829941] kernel BUG at
/build/linux-aws-5.4-I38rpz/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62!
[ 3451.833383] invalid opcode: [#1] SMP PTI
[ 3451.835146] CPU: 1 PID: 14 Comm: cpuhp/1 Tainted: G C
5.4.0-1107-aws #115~18.04.1-Ubuntu
[ 3451.838679] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006
[ 3451.840965] RIP: 0010:dummy_handler+0x4/0x10
[ 3451.842675] Code: 8b 75 e4 74 d6 44 89 e7 e8 39 89 61 00 eb d6 44 89 e7 e8
af ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66
2e 0f 1f 84 00 00 00 00 00 80 3d 69 d0 9f 01 00 75 02 f3
[ 3451.849042] RSP: :b54bee38 EFLAGS: 00010046
[ 3451.851021] RAX: 92c2e3d0 RBX: 003b RCX:
[ 3451.853509] RDX: 00400e00 RSI: RDI:
003b
[ 3451.855996] RBP: b54bee38 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.858435] R10: R11: 94664da8 R12:
[ 3451.860896] R13: R14: R15:
8a9de6583200
[ 3451.863313] FS: () GS:8a9de804()
knlGS:
[ 3451.899246] CS: 0010 DS: ES: CR0: 80050033
[ 3451.901338] CR2: CR3: 2040a001 CR4:
001606e0
[ 3451.903757] DR0: DR1: DR2:
[ 3451.906184] DR3: DR6: fffe0ff0 DR7:
0400
[ 3451.908623] Call Trace:
[ 3451.909869]
[ 3451.911014] __handle_irq_event_percpu+0x44/0x1a0
[ 3451.912818] handle_irq_event_percpu+0x32/0x80
[ 3451.914578] handle_percpu_irq+0x3d/0x60
[ 3451.916198] generic_handle_irq+0x28/0x40
[ 3451.917834] handle_irq_for_port+0x8f/0xe0
[ 3451.919493] evtchn_2l_handle_events+0x157/0x270
[ 3451.921298] __xen_evtchn_do_upcall+0x76/0xe0
[ 3451.923046] xen_evtchn_do_upcall+0x2b/0x40
[ 3451.924742] xen_hvm_callback_vector+0xf/0x20
[ 3451.926484]
[ 3451.927632] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20
[ 3451.929674] Code: e8 a0 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90
90 90 0f 1f 44 00 00 55 48 89 e5 e8 d6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44
00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07
[ 3451.935996] RSP: :b54b000fbcf8 EFLAGS: 0246 ORIG_RAX:
ff0c
[ 3451.939023] RAX: 0001 RBX: 8a9de6583200 RCX:
0002cc00
[ 3451.941475] RDX: 0001 RSI: 0246 RDI:
0246
[ 3451.943948] RBP: b54b000fbcf8 R08: 8a9de6c01240 R09:
8a9de6c01440
[ 3451.946382] R10: R11: 0246 R12:
003b
[ 3451.948849] R13: R14: 8a9d8e75c600 R15:
8a9d8e75c6a4
[ 3451.951297] __setup_irq+0x456/0x760
[ 3451.952850] ? kmem_cache_alloc_trace+0x170/0x230
[ 3451.954661] request_threaded_irq+0xfb/0x160
[ 3451.956376] bind_ipi_to_irqhandler+0xba/0x1c0
[
[Kernel-packages] [Bug 2034057] Re: function_graph tracer in ftrace related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
This is also been seen on j/gcp-fips with version 5.15.0-1048.56+fips1 during development cycle d2024.01.02 on the n2d-standard-4.sev_snp instance. If necessary, another bug could be filed targeting GCP specifically. -- 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/2034057 Title: function_graph tracer in ftrace related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-aws source package in Focal: New Status in linux-aws source package in Jammy: New Status in linux-aws source package in Lunar: Won't Fix Bug description: Test: * ftrace:test.d--00basic--basic2.tc from ubuntu_kselftests_ftrace * test_enable_all_tracers() and test_enable_all_tracers() from ubuntu_ftrace_smoke_test Will crash AWS instance c3.xlarge when testing the "function_graph" tracer. We have a similar issue filed against Azure (bug 1882669). Filing a new bug report because on AWS this is affecting 5.4 ~ 6.2 AWS kernel. However on Azure this is not affecting newer kernels. Take B-aws-5.4-1108 for example, with the ubuntu_kselftests_ftrace test the system will crash with the following error message and reboot (similar to bug 2029917): [ 211.675624] kernel BUG at /build/linux-aws-5.4-VHOhmt/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62! [ 211.678258] invalid opcode: [#1] SMP PTI [ 211.679596] CPU: 1 PID: 14 Comm: cpuhp/1 Not tainted 5.4.0-1108-aws #116~18.04.1-Ubuntu [ 211.681825] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006 [ 211.683728] RIP: 0010:dummy_handler+0x4/0x10 [ 211.685042] Code: 8b 75 e4 74 d6 44 89 e7 e8 f9 88 61 00 eb d6 44 89 e7 e8 6f ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 80 3d 59 d0 9f 01 00 75 02 f3 [ 211.690314] RSP: :aecd4000ee38 EFLAGS: 00010046 [ 211.691934] RAX: b462e3e0 RBX: 003b RCX: [ 211.694036] RDX: 00400e00 RSI: RDI: 003b [ 211.696159] RBP: aecd4000ee38 R08: 8aefa6c036c0 R09: 8aefa6c038c0 [ 211.698232] R10: R11: b6064da8 R12: [ 211.700365] R13: R14: R15: 8aefa34b8700 [ 211.702482] FS: () GS:8aefa804() knlGS: [ 211.704894] CS: 0010 DS: ES: CR0: 80050033 [ 211.706598] CR2: CR3: 0001b400a001 CR4: 001606e0 [ 211.708731] DR0: DR1: DR2: [ 211.710835] DR3: DR6: fffe0ff0 DR7: 0400 [ 211.713448] Call Trace: [ 211.714796] [ 211.715996] __handle_irq_event_percpu+0x44/0x1a0 [ 211.717907] handle_irq_event_percpu+0x32/0x80 [ 211.719759] handle_percpu_irq+0x3d/0x60 [ 211.721474] generic_handle_irq+0x28/0x40 [ 211.723184] handle_irq_for_port+0x8f/0xe0 [ 211.724988] evtchn_2l_handle_events+0x157/0x270 [ 211.726913] __xen_evtchn_do_upcall+0x76/0xe0 [ 211.728749] xen_evtchn_do_upcall+0x2b/0x40 [ 211.730520] xen_hvm_callback_vector+0xf/0x20 [ 211.732271] [ 211.733425] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20 [ 211.735470] Code: e8 70 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90 90 90 0f 1f 44 00 00 55 48 89 e5 e8 a6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07 [ 211.741920] RSP: :aecd400fbcf8 EFLAGS: 0246 ORIG_RAX: ff0c [ 211.744980] RAX: 0001 RBX: 8aefa34b8700 RCX: 0002cc00 [ 211.747420] RDX: 0001 RSI: 0246 RDI: 0246 [ 211.749882] RBP: aecd400fbcf8 R08: 8aefa6c036c0 R09: 8aefa6c038c0 [ 211.752340] R10: R11: 0246 R12: 003b [ 211.754785] R13: R14: 8aef95bdfa00 R15: 8aef95bdfaa4 [ 211.757249] __setup_irq+0x456/0x760 [ 211.758779] ? kmem_cache_alloc_trace+0x170/0x230 [ 211.760639] request_threaded_irq+0xfb/0x160 [ 211.762358] bind_ipi_to_irqhandler+0xba/0x1c0 [ 211.764124] ? xen_qlock_wait+0x90/0x90 [ 211.765734] ? snr_uncore_mmio_init+0x20/0x20 [ 211.767496] xen_init_lock_cpu+0x78/0xd0 [ 211.769135] ? snr_uncore_mmio_init+0x20/0x20 [ 211.770864] xen_cpu_up_online+0xe/0x20 [ 211.772500] cpuhp_invoke_callback+0x8a/0x580 [ 211.774233] cpuhp_thread_fun+0xb8/0x120 [ 211.775866] smpboot_thread_fn+0xfc/0x170 [ 211.777524] kthread+0x121/0x140 [ 211.778968] ? sort_range+0x30/0x30 [ 211.780508] ? kthread_park+0x90/0x90 [ 211.782073]
[Kernel-packages] [Bug 2051366] [NEW] Mantic update: upstream stable patchset 2024-01-26
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-01-26 Ported from the following upstream stable relases: v6.1.66, v6.6.5 from git://git.kernel.org/ cifs: Fix FALLOC_FL_ZERO_RANGE by setting i_size if EOF moved cifs: Fix FALLOC_FL_INSERT_RANGE by setting i_size after EOF moved smb: client: report correct st_size for SMB and NFS symlinks pinctrl: avoid reload of p state in list iteration firewire: core: fix possible memory leak in create_units() mmc: sdhci-pci-gli: Disable LPM during initialization mmc: cqhci: Increase recovery halt timeout mmc: cqhci: Warn of halt or task clear failure mmc: cqhci: Fix task clearing in CQE error recovery mmc: block: Retry commands in CQE error recovery mmc: block: Do not lose cache flush during CQE error recovery mmc: block: Be sure to wait while busy in CQE error recovery ALSA: hda: Disable power-save on KONTRON SinglePC ALSA: hda/realtek: Headset Mic VREF to 100% ALSA: hda/realtek: Add supported ALC257 for ChromeOS dm-verity: align struct dm_verity_fec_io properly scsi: Change SCSI device boolean fields to single bit flags scsi: sd: Fix system start for ATA devices drm/amd: Enable PCIe PME from D3 drm/amdgpu: Force order between a read and write to the same address drm/amd/display: Include udelay when waiting for INBOX0 ACK drm/amd/display: Remove min_dst_y_next_start check for Z8 drm/amd/display: Use DRAM speed from validation for dummy p-state drm/amd/display: Update min Z8 residency time to 2100 for DCN314 drm/amd/display: fix ABM disablement dm verity: initialize fec io before freeing it dm verity: don't perform FEC for failed readahead IO nvme: check for valid nvme_identify_ns() before using it powercap: DTPM: Fix unneeded conversions to micro-Watts cpufreq/amd-pstate: Fix the return value of amd_pstate_fast_switch() dma-buf: fix check in dma_resv_add_fence bcache: revert replacing IS_ERR_OR_NULL with IS_ERR iommu/vt-d: Add MTL to quirk list to skip TE disabling KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers powerpc: Don't clobber f0/vs0 during fp|altivec register save parisc: Mark ex_table entries 32-bit aligned in assembly.h parisc: Mark ex_table entries 32-bit aligned in uaccess.h parisc: Use natural CPU alignment for bug_table parisc: Mark lock_aligned variables 16-byte aligned on SMP parisc: Drop the HP-UX ENOSYM and EREMOTERELEASE error codes parisc: Mark jump_table naturally aligned parisc: Ensure 32-bit alignment on parisc unwind section parisc: Mark altinstructions read-only and 32-bit aligned btrfs: add dmesg output for first mount and last unmount of a filesystem btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod() btrfs: fix off-by-one when checking chunk map includes logical address btrfs: send: ensure send_fd is writable btrfs: make error messages more clear when getting a chunk map btrfs: fix 64bit compat send ioctl arguments not initializing version member auxdisplay: hd44780: move cursor home after clear display command serial: sc16is7xx: Put IOControl register into regmap_volatile serial: sc16is7xx: add missing support for rs485 devicetree properties dpaa2-eth: increase the needed headroom to account for alignment uapi: propagate __struct_group() attributes to the container union selftests/net: ipsec: fix constant out of range selftests/net: fix a char signedness issue selftests/net: unix: fix unused variable compiler warning selftests/net: mptcp: fix uninitialized variable warnings octeontx2-af: Fix possible buffer overflow net: stmmac: xgmac: Disable FPE MMC interrupts octeontx2-pf: Fix adding mbox work queue entry when num_vfs > 64 octeontx2-af: Install TC filter rules in hardware based on priority octeontx2-pf: Restore TC ingress police rules when interface is up r8169: prevent potential deadlock in rtl8169_close ravb: Fix races between ravb_tx_timeout_work() and net related ops net: ravb: Check return value of reset_control_deassert() net: ravb: Use pm_runtime_resume_and_get() net: ravb: Make write access to CXR35 first before accessing other EMAC registers net: ravb: Start TX queues after HW initialization succeeded net: ravb: Stop DMA in case of failures on ravb_open() net: ravb: Keep reverse order of operations in ravb_remove() octeontx2-af: Initialize 'cntr_val' to fix uninitialized symbol error spi: Fix null dereference on suspend cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily iommu/vt-d: Omit devTLB invalidation requests when TES=0 iommu/vt-d: Disable PCI ATS in legacy passthrough mode iommu/vt-d:
[Kernel-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
tested on my hw, works as planned -- 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/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2051342] Re: Enable lowlatency settings in the generic kernel
** Description changed: [Impact] Ubuntu provides the "lowlatency" kernel: a kernel optimized for applications that have special "low latency" requirements. Currently, this kernel does not include any specific UBUNTU SAUCE patches to improve the extra "low latency" requirements, but the only difference is a small subset of .config options. Almost all these options are now configurable either at boot-time or even at run-time, with the only exception of CONFIG_HZ (250 in the generic kernel vs 1000 in the lowlatency kernel). Maintaining a separate kernel for a single config option seems a bit overkill and it is a significant cost of engineering hours, build time, regression testing time and resources. Not to mention the risk of the low-latency kernel falling behind and not being perfectly in sync with the latest generic kernel. Enabling the low-latency settings in the generic kernel has been evaluated before, but it has been never finalized due to the potential risk of performance regressions in CPU-intensive applications (increasing HZ from 250 to 1000 may introduce more kernel jitter in number crunching workloads). The outcome of the original proposal resulted in a re-classification of the lowlatency kernel as a desktop- oriented kernel, enabling additional low latency features (LP: #2023007). As we are approaching the release of the new Ubuntu 24.04 we may want to re-consider merging the low-latency settings in the generic kernel again. Following a detailed analisys of the specific low-latency features: - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown clock tick when possible across all the enabled CPUs if they are either idle or running 1 task - reduce kernel jitter of running tasks due to the periodic clock tick, must be enabled at boot time passing `nohz_full=`); this can actually help CPU-intensive workloads and it could provide much more benefits than the CONFIG_HZ difference (since it can potentially shutdown any kernel jitter on specific CPUs), this one should really be enabled anyway, considering that it is configurable at boot time - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to kthread context (reduce time spent in softirqs with preemption disabled to improve the overall system responsiveness, at the cost of introducing a potential performance penalty, because RCU callbacks are not processed by kernel threads); this should be enabled as well, since it is configurable at boot time (via the rcu_nocbs= parameter) - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a timed delay instead of executing them immediately (can provide 5~10% power-savings for idle or lightly-loaded systems, this is extremely useful for laptops / portable devices - https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/); this has the potential to introduce significant performance regressions, but in the Noble kernel we already have a SAUCE patch that allows to enable/disable this option at boot time (see LP: #2045492) - CONFIG_HZ=1000 last but not least, the only option that is *only* tunable at compile time. As already mentioned there is a potential risk of regressions for CPU-intensive applications, but they can be mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On the other hand, HZ=1000 can improve system responsiveness, that means most of the desktop and server applications will benefit from this (the largest part of the server workloads is I/O bound, more than CPU-bound, so they can benefit from having a kernel that can react faster at switching tasks), not to mention the benefit for the typical end users applications - (gaming, live conferencing, multimedia, etc.). Moreover, it is worth - noticing that pretty much all the other major Linux distributions are - also using CONFIG_HZ0=1000. + (gaming, live conferencing, multimedia, etc.). + + Other latency-related options: + + - CONFIG_LATENCYTOP=y: we should definitely support latencytop in the + generic kernel, considering that we are shipping the user-space package [Test case] There are plenty of micro-benchmarks to prove the validity of each one of the config mentioned above, in terms of system responsive. However, our main goal here is to mitigate as much as possible the risk of regression for CPU-intensive applications, so the test case should be focused on this particular aspect. We also have the opportunity to test these changes using the lowlatency kernel, therefore a reasonable test plan could be defined as following. Test case (a CPU-intensive stress test) - stress-ng --matrix $(getconf _NPROCESSORS_ONLN) --timeout 5m --metrics-brief Metrics: - measure the bogo ops printed to stdout (not a great metric for real- world applications, but in this case they
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.15/5.15.0.1051.59~20.04.1)
All autopkgtests for the newly accepted linux-meta-gcp-5.15 (5.15.0.1051.59~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.15/5.15.0-1051.59~20.04.1 (arm64) systemd/245.4-4ubuntu3.23 (amd64) 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/focal/update_excuses.html#linux-meta-gcp-5.15 [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 2051266] Re: package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
You have unsupported DKMS modules installed that break the header package
installations. Please remove them:
$ dkms remove anbox-ashmem
$ dkms remove anbox-binder
Or something like that.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
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/2051266
Title:
package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
Status in linux package in Ubuntu:
Invalid
Bug description:
yazılım yüklenirken hata oluştu.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-generic-hwe-22.04 6.5.0.15.17
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: beyzanrsr 1396 F wireplumber
/dev/snd/controlC1: beyzanrsr 1396 F wireplumber
/dev/snd/seq:beyzanrsr 1390 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Jan 25 19:51:56 2024
ErrorMessage: bağımlılık sorunları - yapılandırılmadan bırakılıyor
InstallationDate: Installed on 2023-12-02 (55 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=50c847c3-ad3a-4f4a-847e-fc7c299a1a16 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V0.3306
dmi.board.name: JM50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenix:bvrV0.3306:bd08/24/2009:svnAcer:pnAspire5739G:pvrNotApplicable:rvnAcer:rnJM50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:sku:
dmi.product.name: Aspire 5739G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051266/+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 2051266] Re: package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
Building module:
Cleaning build area...
make -j2 KERNELRELEASE=6.5.0-15-generic all
KERNEL_SRC=/lib/modules/6.5.0-15-generic/build...(bad exit status: 2)
ERROR (dkms apport): binary package for anbox-ashmem: 1 not found
Error! Bad return status for module build on kernel: 6.5.0-15-generic (x86_64)
Consult /var/lib/dkms/anbox-ashmem/1/build/make.log for more information.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051266
Title:
package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
Status in linux package in Ubuntu:
Invalid
Bug description:
yazılım yüklenirken hata oluştu.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-generic-hwe-22.04 6.5.0.15.17
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: beyzanrsr 1396 F wireplumber
/dev/snd/controlC1: beyzanrsr 1396 F wireplumber
/dev/snd/seq:beyzanrsr 1390 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Jan 25 19:51:56 2024
ErrorMessage: bağımlılık sorunları - yapılandırılmadan bırakılıyor
InstallationDate: Installed on 2023-12-02 (55 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=50c847c3-ad3a-4f4a-847e-fc7c299a1a16 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V0.3306
dmi.board.name: JM50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenix:bvrV0.3306:bd08/24/2009:svnAcer:pnAspire5739G:pvrNotApplicable:rvnAcer:rnJM50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:sku:
dmi.product.name: Aspire 5739G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051266/+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 2051267] Re: package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
*** This bug is a duplicate of bug 2051266 ***
https://bugs.launchpad.net/bugs/2051266
** This bug has been marked a duplicate of bug 2051266
package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
--
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/2051267
Title:
package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
Status in linux package in Ubuntu:
New
Bug description:
yazılım yüklenirken hata oluştu.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-generic-hwe-22.04 6.5.0.15.17
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: beyzanrsr 1396 F wireplumber
/dev/snd/controlC1: beyzanrsr 1396 F wireplumber
/dev/snd/seq:beyzanrsr 1390 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Jan 25 19:51:56 2024
ErrorMessage: bağımlılık sorunları - yapılandırılmadan bırakılıyor
InstallationDate: Installed on 2023-12-02 (55 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=50c847c3-ad3a-4f4a-847e-fc7c299a1a16 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-generic-hwe-22.04 6.5.0.15.17 failed to
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V0.3306
dmi.board.name: JM50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenix:bvrV0.3306:bd08/24/2009:svnAcer:pnAspire5739G:pvrNotApplicable:rvnAcer:rnJM50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:sku:
dmi.product.name: Aspire 5739G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051267/+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 2050858] Re: Jammy update: v5.15.143 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2050858 Title: Jammy update: v5.15.143 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.143 upstream stable release from git://git.kernel.org/ vdpa/mlx5: preserve CVQ vringh index hrtimers: Push pending hrtimers away from outgoing CPU earlier i2c: designware: Fix corrupted memory seen in the ISR netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test tg3: Move the [rt]x_dropped counters to tg3_napi tg3: Increment tx_dropped in tg3_tso_bug() kconfig: fix memory leak from range properties drm/amdgpu: correct chunk_ptr to a pointer to chunk. platform/x86: asus-wmi: Adjust tablet/lidflip handling to use enum platform/x86: asus-wmi: Add support for ROG X13 tablet mode platform/x86: asus-wmi: Simplify tablet-mode-switch probing platform/x86: asus-wmi: Simplify tablet-mode-switch handling platform/x86: asus-wmi: Move i8042 filter install to shared asus-wmi code of: dynamic: Fix of_reconfig_get_state_change() return value documentation platform/x86: wmi: Allow duplicate GUIDs for drivers that use struct wmi_driver platform/x86: wmi: Skip blocks with zero instances ipv6: fix potential NULL deref in fib6_add() octeontx2-pf: Add missing mutex lock in otx2_get_pauseparam octeontx2-af: Check return value of nix_get_nixlf before using nixlf hv_netvsc: rndis_filter needs to select NLS r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE r8152: Add RTL8152_INACCESSIBLE checks to more loops r8152: Add RTL8152_INACCESSIBLE to r8156b_wait_loading_flash() r8152: Add RTL8152_INACCESSIBLE to r8153_pre_firmware_1() r8152: Add RTL8152_INACCESSIBLE to r8153_aldps_en() mlxbf-bootctl: correctly identify secure boot with development keys platform/mellanox: Add null pointer checks for devm_kasprintf() platform/mellanox: Check devm_hwmon_device_register_with_groups() return value arcnet: restoring support for multiple Sohard Arcnet cards net: stmmac: fix FPE events losing octeontx2-af: fix a use-after-free in rvu_npa_register_reporters i40e: Fix unexpected MFS warning message net: bnxt: fix a potential use-after-free in bnxt_init_tc ionic: fix snprintf format length warning ionic: Fix dim work handling in split interrupt mode ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() net: hns: fix fake link up on xge port octeontx2-af: Update Tx link register range netfilter: nf_tables: validate family when identifying table via handle netfilter: xt_owner: Fix for unsafe access of sk->sk_socket tcp: do not accept ACK of bytes we never sent bpf: sockmap, updating the sg structure should also update curr psample: Require 'CAP_NET_ADMIN' when joining "packets" group net: add missing kdoc for struct genl_multicast_group::flags drop_monitor: Require 'CAP_SYS_ADMIN' when joining "events" group tee: optee: Fix supplicant based device enumeration RDMA/hns: Fix unnecessary err return when using invalid congest control algorithm RDMA/irdma: Do not modify to SQD on error RDMA/irdma: Add wait for suspend on SQD arm64: dts: rockchip: Expand reg size of vdec node for RK3399 RDMA/rtrs-srv: Do not unconditionally enable irq RDMA/rtrs-clt: Start hb after path_up RDMA/rtrs-srv: Check return values while processing info request RDMA/rtrs-srv: Free srv_mr iu only when always_invalidate is true RDMA/rtrs-srv: Destroy path files after making sure no IOs in-flight RDMA/rtrs-clt: Fix the max_send_wr setting RDMA/rtrs-clt: Remove the warnings for req in_use check RDMA/bnxt_re: Correct module description string hwmon: (acpi_power_meter) Fix 4.29 MW bug hwmon: (nzxt-kraken2) Fix error handling path in kraken2_probe() ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate RDMA/core: Fix umem iterator when PAGE_SIZE is greater then HCA pgsz RDMA/irdma: Avoid free the non-cqp_request scratch arm64: dts: imx8mq: drop usb3-resume-missing-cas from usb arm64: dts: imx8mp: imx8mq: Add parkmode-disable-ss-quirk on DWC3 ARM: dts: imx6ul-pico: Describe the Ethernet PHY clock tracing: Fix a warning when allocating buffered events fails scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle() ARM:
[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
** Tags added: verification-failed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Won't Fix
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
In Progress
Bug description:
[SRU Justification]
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
* 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
* 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
update board-2.bin") to forfill git history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes
from suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
Jammy included this fix from stable update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Lunar is EOL
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => Won't Fix
--
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/1983357
Title:
test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Status in QA Regression Testing:
Invalid
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
New
Status in linux source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Won't Fix
Status in linux-oem-6.1 source package in Lunar:
New
Status in linux source package in Mantic:
Confirmed
Status in linux-oem-6.1 source package in Mantic:
New
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.1 source package in Noble:
Invalid
Bug description:
Issue found on 5.19.0-9.9 Kinetic AMD64 systems
Test log:
Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel:
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs ... (default libs native) (default libs native rekey) (default
libs COMPAT) FAIL
==
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1203, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: default libs COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0xf7c81790
0xf7c81790
0xf7c81790
FAIL: ASLR not functional (libs always at 0xf7c81790)
--
Ran 1 test in 0.144s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
GA kernel doesn't support DG2, oem-6.1 was the first one, hwe-6.2 does too and works more or less fine (doesn't suffer from this issue) -- 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/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
** Description changed: [Impact] + The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] + Mario points out the commit in 6.7 may help + 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] + 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. + 2. Boot OS, put SUT to suspend. + 3. Wake up the System from suspend. + 4. Right away reboot the system from Ubuntu OS. + 5. Put SUT to suspend and wake up the system. + 6. After wake up Suspend, SUT should not be black screen. + 7. Repetition Step 2~6 30 cycles [Where problems could occur] + Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2051342] [NEW] Enable lowlatency settings in the generic kernel
Public bug reported: [Impact] Ubuntu provides the "lowlatency" kernel: a kernel optimized for applications that have special "low latency" requirements. Currently, this kernel does not include any specific UBUNTU SAUCE patches to improve the extra "low latency" requirements, but the only difference is a small subset of .config options. Almost all these options are now configurable either at boot-time or even at run-time, with the only exception of CONFIG_HZ (250 in the generic kernel vs 1000 in the lowlatency kernel). Maintaining a separate kernel for a single config option seems a bit overkill and it is a significant cost of engineering hours, build time, regression testing time and resources. Not to mention the risk of the low-latency kernel falling behind and not being perfectly in sync with the latest generic kernel. Enabling the low-latency settings in the generic kernel has been evaluated before, but it has been never finalized due to the potential risk of performance regressions in CPU-intensive applications (increasing HZ from 250 to 1000 may introduce more kernel jitter in number crunching workloads). The outcome of the original proposal resulted in a re-classification of the lowlatency kernel as a desktop- oriented kernel, enabling additional low latency features (LP: #2023007). As we are approaching the release of the new Ubuntu 24.04 we may want to re-consider merging the low-latency settings in the generic kernel again. Following a detailed analisys of the specific low-latency features: - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown clock tick when possible across all the enabled CPUs if they are either idle or running 1 task - reduce kernel jitter of running tasks due to the periodic clock tick, must be enabled at boot time passing `nohz_full=`); this can actually help CPU-intensive workloads and it could provide much more benefits than the CONFIG_HZ difference (since it can potentially shutdown any kernel jitter on specific CPUs), this one should really be enabled anyway, considering that it is configurable at boot time - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to kthread context (reduce time spent in softirqs with preemption disabled to improve the overall system responsiveness, at the cost of introducing a potential performance penalty, because RCU callbacks are not processed by kernel threads); this should be enabled as well, since it is configurable at boot time (via the rcu_nocbs= parameter) - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a timed delay instead of executing them immediately (can provide 5~10% power-savings for idle or lightly-loaded systems, this is extremely useful for laptops / portable devices - https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/); this has the potential to introduce significant performance regressions, but in the Noble kernel we already have a SAUCE patch that allows to enable/disable this option at boot time (see LP: #2045492) - CONFIG_HZ=1000 last but not least, the only option that is *only* tunable at compile time. As already mentioned there is a potential risk of regressions for CPU-intensive applications, but they can be mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On the other hand, HZ=1000 can improve system responsiveness, that means most of the desktop and server applications will benefit from this (the largest part of the server workloads is I/O bound, more than CPU-bound, so they can benefit from having a kernel that can react faster at switching tasks), not to mention the benefit for the typical end users applications (gaming, live conferencing, multimedia, etc.). Moreover, it is worth noticing that pretty much all the other major Linux distributions are also using CONFIG_HZ0=1000. [Test case] There are plenty of micro-benchmarks to prove the validity of each one of the config mentioned above, in terms of system responsive. However, our main goal here is to mitigate as much as possible the risk of regression for CPU-intensive applications, so the test case should be focused on this particular aspect. We also have the opportunity to test these changes using the lowlatency kernel, therefore a reasonable test plan could be defined as following. Test case (a CPU-intensive stress test) - stress-ng --matrix $(getconf _NPROCESSORS_ONLN) --timeout 5m --metrics-brief Metrics: - measure the bogo ops printed to stdout (not a great metric for real- world applications, but in this case they can show the impact of the addditional kernel jitter introduced by the different CONFIG_HZ) Perform multiple runs of the stress test, both on amd64 and arm64. Repeat the test also with CONFIG_NO_HZ_FULL. If NO_HZ_FULL can provide better results than the CONFIG_HZ=250 case, we can safely switch to CONFIG_HZ=1000, since we have the possibility to provide a boot-time option to improve CPU-intensive workloads and get better
[Kernel-packages] [Bug 2051341] [NEW] black screen when wake up from s3 with AMD W7600 gfx
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2051251 somerville ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-2051251 somerville -- 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/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot
Noble on LXD works correctly too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046059 Title: kernel cannot find lz4hc and z3fold modules on boot Status in cloud-images: New Status in linux-signed-hwe-6.2 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: I've been using zswap without any issues for a while, but fairly recently (can't be certain when) the kernel became unable to find the modules for lz4hc compression and the z3fold zpool. $ egrep 'lz4hc|z3fold' /var/log/syslog Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'lz4hc' Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 'z3fold' Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 zswap.zpool=z3fold transparent_hugepage=always panic=-1 Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc not available, using default lzo Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not available, using default zbud But the modules are in the initrd (as they always have been): $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold' usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko I'm at a complete loss. If the modules are there, why can't the kernel find them? Both modules can be loaded (obviously from a different location – not the initrd) and the relevant parameters changed with startup scripts but this is a workaround not a solution. From: https://askubuntu.com/q/1234721/170177 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Sun Dec 10 11:22:41 2023 Ec2AMI: ami-0008be8e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-starter-1-2-20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2046059/+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 2045503] Re: apply sched-ext patch set to linux-unstable
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045503 Title: apply sched-ext patch set to linux-unstable Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [Impact] sched-ext is a new scheduling class introduced in the Linux kernel that provides a mechanism to implement scheduling policies as eBPF programs (https://lwn.net/Articles/922405/). Such programs can also be connected to user-space counterparts to defer scheduling decisions to regular user-space processes. The idea of "pluggable" schedulers is not new, it was initially proposed in 2004 (https://lwn.net/Articles/109458/), but at that time it was strongly rejected, to prioritize the creation of a single generic scheduler (one to rule them all), that ended up being the “completely fair scheduler” (CFS). However, with BPF and the sched-ext scheduling class, we now have the possibility to easily and quickly implement and test scheduling policies, making the “pluggable” approach an effective tool for easy experimentation. The ability to implement custom scheduling policies via BPF greatly lowers the difficulty of testing new scheduling ideas (much easier than changing CFS or replacing it with a different scheduler). With this feature researchers or developers can test their own scheduler in a safe way, without even needing to reboot the system. Shipping this feature in the Ubuntu kernel can provide a significant benefit to researchers and companies that want to experiment (or ship) their own scheduling policy, implemented as an eBPF/user-space program. Targeting linux-unstable only for now is probably a good compromise to allow users to start some experiments, collect feedbacks, help the upstream community to find and fix bugs and at the same time avoid to introduce too much maintenance burden on us. [Test case] Basic test cases for this feature are provided by the sched-ext patch set. Tests and custom scheduler implementations are available in tools/sched_ext or in https://github.com/sched-ext/scx. [Fix] Apply this patch set as SAUCE to linux-unstable: https://lore.kernel.org/bpf/zvpjtc5znenny...@slm.duckdns.org/T/ On top of the patch set we want to apply also the following patches (still as SAUCE): - UBUNTU: SAUCE: sched_ext: use proper atomic operator for scx.ops_state (extra fix to properly build sched-ext on armhf) - UBUNTU: SAUCE: sched-ext: taint kernel when a custom scheduler is loaded (set TAINT_OOT_MODULE in /proc/sys/kernel/tainted to easily determine when a custom scheduler has been used, that can be useful for bug reports: we can easily detect when a custom scheduler has been used and treat the bug report accordingly) - UBUNTU: [Config] enable sched_ext in annotations (enable sched-ext in the config across all the supported architectures) Soon there will be a branch against any kernel that we need here (we will only need 6.7 for now): https://github.com/sched-ext/sched_ext [Regression potential] This feature is not going to be merged upstream in the near future, some upstream maintainers are worried that giving the possibility to inject in the kernel a custom scheduler can introduce performance regressions that are hard to track down. For this reason we should apply this feature only to linux-unstable for now, making sure that the patch is unapplied or reverted when linux-unstable becomes linux. In the meantime we can also figure out a reasonable way to determine when a custom scheduler is used (i.e., taint the kernel?) to easily determine when any potential performance regression may have been introduced by a custom sched-ext scheduler. From a maintenance perspective, having this patch set applied may also be problematic (potential conflicts) when we apply new stable updates. However, the upstream maintainers of sched-ext have expressed interest to help us maintaining the patch set against the target kernel(s) that we need. And targeting linux-unstable only can definitely mitigate the maintenance problem a lot (since we won't have the urgency to apply critical security fixes to linux-unstable). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045503/+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
