[Kernel-packages] [Bug 2060037] Re: nfs logging causes unstable system: kernel: xs_tcp_setup_socket: connect returned unhandled error -1
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2060037 Title: nfs logging causes unstable system: kernel: xs_tcp_setup_socket: connect returned unhandled error -1 Status in linux package in Ubuntu: New Bug description: We hit an issue when a nfs server is unreachable and clients keep reconnecting to it causes syslog and kern.log files to be flooded with errors like: kernel: xs_tcp_setup_socket: connect returned unhandled error -1 Approx 30.000 errors / second. This causes disk space to grow rapidly and fill the disk in a matter of minutes. Only solution appears to be to reboot the nfs servers. Nfs server is running longhorn 1.5.3 and client mounts options look like: ... type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,softerr,softreval,noresvport,proto=tcp,timeo=600,retrans=5,sec=sys,clientaddr=10.125.92.24,local_lock=none,addr=10.43.81.150) We did not experience this issue before longhorn introduced "soft" nfs options. We have a SUSE/Longhorn support ticket (01053865) for this and they suggested us to report this here. References/Possibly related to: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=98f930fb6b46b128b72f5635925ec97f2f875d72 *** # cat /proc/version_signature Ubuntu 5.15.0-101.111-generic 5.15.143 # lsb_release -rd Description:Ubuntu 22.04.4 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060037/+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 2060004] Re: Fail to enable workqueue via accel-config under ubuntu server 24.04
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2060004 Title: Fail to enable workqueue via accel-config under ubuntu server 24.04 Status in linux package in Ubuntu: New Bug description: 1. Fresh install Ubuntu server 24.04 on the thinksystem server; 2. Add boot parameter "intel_iommu=on,sm_on" and restart 3. Verify Intel Data Streaming Accelerator (DSA) functionality via accel-config command, it fail to enable workqueue: root@test:/# accel-config list [] root@test:/# accel-config config-wq dsa0/wq0.0 --group-id=0 root@test:/# accel-config config-wq dsa0/wq0.0 --priority=5 root@test:/# accel-config config-wq dsa0/wq0.0 --wq-size=8 root@test:/# accel-config config-engine dsa0/engine0.0 --group-id=0 root@test:/# accel-config config-wq dsa0/wq0.0 --type=user root@test:/# accel-config config-wq dsa0/wq0.0 --name="dsa-test" root@test:/# accel-config config-wq dsa0/wq0.0 --mode=dedicated root@test:/# accel-config enable-device dsa0 enabled 1 device(s) out of 1 root@test:/# root@test:/# accel-config enable-wq dsa0/wq0.0 failed in dsa0/wq0.0 enabled 0 wq(s) out of 1 Error[0x8020] dsa0/wq0.0: Unknown error root@test:/# After comparing the kernel source, the issue comes from 7af1e0aceeb321cbc90fcf6fa0bec8870290377f, please fix it, thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060004/+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 2060060] Re: Lenovo laptop wakes from suspend on closing the lid
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060060 Title: Lenovo laptop wakes from suspend on closing the lid Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: OS: Ubuntu 22.04.4 LTS Kernel: 6.5.0-26-generic Whenever I close the lid on my Lenovo Yoga (Yoga-Slim-7-ProX) laptop while it is in suspend, it immediately wakes up. It must be an issue with the kernel, because while looking this up, I found a similar problem reported with a 5.x kernel for a Thinkpad where it was suggested to use the following kernel parameter as a workaround: modprobe.blacklist=intel_ish_ipc For me, adding this parameter does not solve the problem, however, it does change something: if I manually suspend the computer, and then close the lid it will wake up for a second, and then go back in suspend (based on the indicator LED). However, if the computer goes into suspend automatically because of inactivity, and I then close the lid, it wakes up just as reported. Although I don't think it makes a difference, I observed this exact behaviour on X, as well as Wayland, and also on 6.2.x Ubuntu kernels. Older kernels are not supported on my machine. I used the ubuntu-bug command, I hope all the relevant logs are attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 20:26:01 2024 InstallationDate: Installed on 2024-04-02 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2060060/+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 2058321] Re: Unsupported platform 'ZynqMP KV260 revB
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058321 Title: Unsupported platform 'ZynqMP KV260 revB Status in linux-xilinx-zynqmp package in Ubuntu: Fix Committed Bug description: [ Impact ] * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks older versions of flash-kernel. [ Test Plan ] * Kernel regression testing uses flash-kernel and will test this change * certification testing uses flash-kernel and will test this change [ Where problems could occur ] * This will cause flash-kernel to be updated automatically when the kernel is updated . This may introduce other issues caused by previous flash-kernel changes that users were not running [ Other info ] * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- kernel/+bug/2054556 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058321/+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 2051720]
Can you guys try with the following change: https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201-1-luiz.de...@gmail.com/ -- 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/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: ``` kernel: Bluetooth: hci0: command 0xfc05 tx timeout ``` This issue started with kernel 6.5. Bluetooth has been broken ever since. The issue was not present in earlier versions of the kernel. ``` $ uname -a Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsusb | grep -i bluetooth Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth ``` ``` $ journalctl -b | egrep -i bluetooth Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth. Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support. Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110) ``` ``` linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all [installed,automatic] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+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 2051720]
I also get: ~$ dmesg | grep -i blue [ 13.838221] Bluetooth: Core ver 2.22 [ 13.838236] NET: Registered PF_BLUETOOTH protocol family [ 13.838237] Bluetooth: HCI device and connection manager initialized [ 13.838240] Bluetooth: HCI socket layer initialized [ 13.838241] Bluetooth: L2CAP socket layer initialized [ 13.838244] Bluetooth: SCO socket layer initialized [ 14.329584] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 14.329588] Bluetooth: BNEP filters: protocol multicast [ 14.329590] Bluetooth: BNEP socket layer initialized [ 16.032582] Bluetooth: hci0: Reading Intel version command failed (-110) [ 16.032583] Bluetooth: hci0: command 0xfc05 tx timeout ~$ modinfo btintel filename: /lib/modules/6.5.0-26-generic/kernel/drivers/bluetooth/btintel.ko firmware: intel/ibt-12-16.ddc firmware: intel/ibt-12-16.sfi firmware: intel/ibt-11-5.ddc firmware: intel/ibt-11-5.sfi license:GPL version:0.1 description:Bluetooth support for Intel devices ver 0.1 author: Marcel Holtmann srcversion: FDF2221B8ED4B01F8EADF85 depends:bluetooth retpoline: Y intree: Y name: btintel vermagic: 6.5.0-26-generic SMP preempt mod_unload modversions ~$ lsusb | grep -i bluetooth Bus 001 Device 005: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter -- 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/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: ``` kernel: Bluetooth: hci0: command 0xfc05 tx timeout ``` This issue started with kernel 6.5. Bluetooth has been broken ever since. The issue was not present in earlier versions of the kernel. ``` $ uname -a Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsusb | grep -i bluetooth Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth ``` ``` $ journalctl -b | egrep -i bluetooth Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth. Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support. Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110) ``` ``` linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all [installed,automatic] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+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 2058226] Re: iwlwifi repeatedly logging microcode crashes
I'm not sure what happened but I did the following: - Disabled Bluetooth - Switched to another access point - Used the PC for some time - Noticed I wasn't getting these errors any more, and decided I want to reproduce the issue - Re-enabled Bluetooth - Switched back to original access point -> Still not observing a microcode crash with the same signature. I do get microcode crashes but those are a different story. Firmware is still the same version and access point is still using the same firmware version as well. Another nearby access point has been updated to a new firmware version but that shouldn't matter here as when the failures occurred the computer wasn't connected to that AP. Until I figure out how to reproduce the same failure it's probably impossible to find and fix this. -- 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/2058226 Title: iwlwifi repeatedly logging microcode crashes Status in linux-firmware package in Ubuntu: New Bug description: The iwlwifi driver is logging microcode crashes on a daily basis. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. Crash log is different from what I've found by googling, and for similar errors the firmware version is much more recent. Here's the log output from crash (leaving some extra lines there as well to show the chip and firmware version): Mar 15 12:03:14 waplinuc kernel: [1203239.253200] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Mar 15 12:03:14 waplinuc kernel: [1203239.253293] iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 15 12:03:14 waplinuc kernel: [1203239.253295] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Mar 15 12:03:14 waplinuc kernel: [1203239.253298] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Mar 15 12:03:14 waplinuc kernel: [1203239.253300] iwlwifi :00:14.3: 0x003F | ADVANCED_SYSASSERT Mar 15 12:03:14 waplinuc kernel: [1203239.253303] iwlwifi :00:14.3: 0x00A022F0 | trm_hw_status0 Mar 15 12:03:14 waplinuc kernel: [1203239.253305] iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 15 12:03:14 waplinuc kernel: [1203239.253307] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Mar 15 12:03:14 waplinuc kernel: [1203239.253308] iwlwifi :00:14.3: 0x1820 | interruptlink1 Mar 15 12:03:14 waplinuc kernel: [1203239.253310] iwlwifi :00:14.3: 0x0001C346 | interruptlink2 Mar 15 12:03:14 waplinuc kernel: [1203239.253312] iwlwifi :00:14.3: 0x000601FF | data1 Mar 15 12:03:14 waplinuc kernel: [1203239.253313] iwlwifi :00:14.3: 0x00812C80 | data2 Mar 15 12:03:14 waplinuc kernel: [1203239.253315] iwlwifi :00:14.3: 0x0001C346 | data3 Mar 15 12:03:14 waplinuc kernel: [1203239.253316] iwlwifi :00:14.3: 0xB743 | beacon time Mar 15 12:03:14 waplinuc kernel: [1203239.253318] iwlwifi :00:14.3: 0x9AB048FC | tsf low Mar 15 12:03:14 waplinuc kernel: [1203239.253320] iwlwifi :00:14.3: 0x038D | tsf hi Mar 15 12:03:14 waplinuc kernel: [1203239.253321] iwlwifi :00:14.3: 0x | time gp1 Mar 15 12:03:14 waplinuc kernel: [1203239.253323] iwlwifi :00:14.3: 0xFF3E816F | time gp2 Mar 15 12:03:14 waplinuc kernel: [1203239.253324] iwlwifi :00:14.3: 0x0001 | uCode revision type Mar 15 12:03:14 waplinuc kernel: [1203239.253326] iwlwifi :00:14.3: 0x004D | uCode version major Mar 15 12:03:14 waplinuc kernel: [1203239.253327] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Mar 15 12:03:14 waplinuc kernel: [1203239.253329] iwlwifi :00:14.3: 0x0351 | hw version Mar 15 12:03:14 waplinuc kernel: [1203239.253330] iwlwifi :00:14.3: 0x00489001 | board version Mar 15 12:03:14 waplinuc kernel: [1203239.253332] iwlwifi :00:14.3: 0x80D2FD25 | hcmd Mar 15 12:03:14 waplinuc kernel: [1203239.25] iwlwifi :00:14.3: 0x00021000 | isr0 Mar 15 12:03:14 waplinuc kernel: [1203239.253335] iwlwifi :00:14.3: 0x0004 | isr1 Mar 15 12:03:14 waplinuc kernel: [1203239.253336] iwlwifi :00:14.3: 0x08F2 | isr2 Mar 15 12:03:14 waplinuc kernel: [1203239.253337] iwlwifi :00:14.3: 0x04C3428D | isr3 Mar 15 12:03:14 waplinuc kernel: [1203239.253339] iwlwifi :00:14.3: 0x | isr4 Mar 15 12:03:14 waplinuc kernel: [1203239.253340] iwlwifi :00:14.3: 0x0502001C | last cmd Id Mar 15 12:03:14 waplinuc kernel: [1203239.253342] iwlwifi :00:14.3: 0x0001191E | wait_event Mar 15 12:03:14 waplinuc kernel: [1203239.253343] iwlwifi :00:14.3: 0x00D4 | l2p_control Mar 15 12:03:14 waplinuc kernel: [1203239.253345] iwlwifi :00:14.3: 0x0020 | l2p_duration Mar 15 12:03:14 waplinuc kernel: [1203239.253346] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid Mar 15 12:03:14 waplinuc kernel:
[Kernel-packages] [Bug 2046636] Re: Mouse is erratic moving even i am not using it
I had a similar problem. Flip the mouse over and look for a hair in the sensor. If that isn't it, try replacing the mouse, it might be a bad cable or similar. (That worked for me.) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046636 Title: Mouse is erratic moving even i am not using it Status in linux package in Ubuntu: Incomplete Bug description: I cannot focus in the button to be clicked ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 10:35:46 2023 DistUpgraded: 2023-06-17 09:34:51,040 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:179b] MachineType: Hewlett-Packard HP EliteBook 8470p ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic root=UUID=23e707c5-d92f-40fa-83c4-b498438a2545 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2023-06-17 (183 days ago) dmi.bios.date: 01/31/2013 dmi.bios.release: 15.64 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.40 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.32 dmi.chassis.asset.tag: CNU324CNB2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 66.50 dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.40:bd01/31/2013:br15.64:efr66.50:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1103:rvnHewlett-Packard:rn179B:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr:skuH5E19ET#ABU: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470p dmi.product.sku: H5E19ET#ABU dmi.product.version: A1029D1103 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046636/+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 2060130] Re: [SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel cmdline/initrd sections from EFI stub
** Description changed: This is a public version of https://bugs.launchpad.net/bugs/2058835 [Description] - When a TD is created, during the boot process, steps like loading the firmware, bootloader, kernel image, etc are measured and stored in RTMR registers to support the trusted boot model. After boot, this measured value is used to validate the integrity of the boot process. + When a TD is created, during the boot process, steps like loading the firmware, bootloader, kernel image, etc are measured and stored in RTMR registers to support the trusted boot model. After boot, this measured value is used to validate the integrity of the boot process. - During the direct boot process, bootloader is responsible for + During the direct boot process, bootloader is responsible for measuring the kernel image before loading the kernel. But if the kernel is loaded from EFI bootstub, the related measurements needs to be owned by the EFI bootstub. This support needs to be added to Linux EFI boot stub code. - Also, as per the following discussion, the kernel command line or + Also, as per the following discussion, the kernel command line or initrd section measurements also needs be owned by the EFI bootsub. - https://edk2.groups.io/g/devel/topic/93737108?p=Created%2C%2C%2C20%2C2%2C0%2C0%3A%3A%2C%2C%2C0%2C0%2C0%2C93737108 + https://edk2.groups.io/g/devel/topic/93737108?p=Created%2C%2C%2C20%2C2%2C0%2C0%3A%3A%2C%2C%2C0%2C0%2C0%2C93737108 [Fix] Cherry pick cleanly: - d228814b1913 efi/libstub: Add get_event_log() support for CC platforms - ac93cbfc2a2c efi/libstub: Measure into CC protocol if TCG2 protocol is absent - 0bbe5b0ea97a efi/libstub: Add Confidential Computing (CC) measurement typedefs - 7a1381e8313f efi/tpm: Use symbolic GUID name from spec for final events table - 3e0b0f880e9e efi/libstub: Use TPM event typedefs from the TCG PC Client spec + d228814b1913 efi/libstub: Add get_event_log() support for CC platforms + ac93cbfc2a2c efi/libstub: Measure into CC protocol if TCG2 protocol is absent + 0bbe5b0ea97a efi/libstub: Add Confidential Computing (CC) measurement typedefs + 7a1381e8313f efi/tpm: Use symbolic GUID name from spec for final events table + 3e0b0f880e9e efi/libstub: Use TPM event typedefs from the TCG PC Client spec + + External Links: + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=70ef654469b371d0a71bcf967fa3dcbca05d4b25 Those are all merged into upstream. + [Test Plan] Build/sign/boot with secure boot enabled. [Where problems could occur] At boot time, as this is modifying the efi libstub. Could be impacting secure boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060130 Title: [SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel cmdline/initrd sections from EFI stub Status in linux package in Ubuntu: New Bug description: This is a public version of https://bugs.launchpad.net/bugs/2058835 [Description] When a TD is created, during the boot process, steps like loading the firmware, bootloader, kernel image, etc are measured and stored in RTMR registers to support the trusted boot model. After boot, this measured value is used to validate the integrity of the boot process. During the direct boot process, bootloader is responsible for measuring the kernel image before loading the kernel. But if the kernel is loaded from EFI bootstub, the related measurements needs to be owned by the EFI bootstub. This support needs to be added to Linux EFI boot stub code. Also, as per the following discussion, the kernel command line or initrd section measurements also needs be owned by the EFI bootsub. https://edk2.groups.io/g/devel/topic/93737108?p=Created%2C%2C%2C20%2C2%2C0%2C0%3A%3A%2C%2C%2C0%2C0%2C0%2C93737108 [Fix] Cherry pick cleanly: d228814b1913 efi/libstub: Add get_event_log() support for CC platforms ac93cbfc2a2c efi/libstub: Measure into CC protocol if TCG2 protocol is absent 0bbe5b0ea97a efi/libstub: Add Confidential Computing (CC) measurement typedefs 7a1381e8313f efi/tpm: Use symbolic GUID name from spec for final events table 3e0b0f880e9e efi/libstub: Use TPM event typedefs from the TCG PC Client spec External Links: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=70ef654469b371d0a71bcf967fa3dcbca05d4b25 Those are all merged into upstream. [Test Plan] Build/sign/boot with secure boot enabled. [Where problems could occur] At boot time, as this is modifying the efi libstub. Could be impacting secure boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060130/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2053101] Re: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules
The following commit changed the name of that variable: 99a4e9bce56b block: rename GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART That commit was applied to the gcp kernel via stable updates from Jammy (22.04) version: 5.15.0-93.103 Jammy received it from upstream stable updates via: c6ce1c5dd327 block: rename GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART That commit was applied to upstream stable in version: v5.15.132 I'll report this to upstream and see what the suggested fix may be. ** Changed in: linux-signed-gcp-5.15 (Ubuntu) Importance: Undecided => High ** Changed in: linux-signed-gcp-5.15 (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux-signed-gcp-5.15 (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Package changed: linux-signed-gcp-5.15 (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Tags added: kernel-key ** Also affects: linux-realtime (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-realtime (Ubuntu Jammy) ** Changed in: linux-realtime (Ubuntu) Importance: Undecided => High ** Changed in: linux-realtime (Ubuntu) Status: New => In Progress ** Changed in: linux-realtime (Ubuntu) Status: In Progress => Triaged ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu) Status: New => Triaged ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-gcp-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2053101 Title: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Triaged Status in linux-realtime package in Ubuntu: Triaged Status in linux source package in Jammy: In Progress Bug description: 3rd party kernel modules for Ubuntu 20.04 break due to the recently backported change of renaming GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART linux-gcp-5.15-headers-5.15.0-1049 still uses GENHD_FL_NO_PART_SCAN which the 3rd party kernel modules use, while linux- gcp-5.15-headers-5.15.0-1051 has brought the rename to GENHD_FL_NO_PART in. This is a breaking change and should not have been backported. The 3rd party modules have been updated for newer kernels on 22.04, but can't be updated on 20.04 with this breaking change. $ grep GENHD_FL_NO_PART /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: * ``GENHD_FL_NO_PART_SCAN`` (0x0200): partition scanning is disabled. /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: * ``GENHD_FL_NO_PART_SCAN``. /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h:#define GENHD_FL_NO_PART_SCAN 0x0200 /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: !(disk->flags & GENHD_FL_NO_PART_SCAN); /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: * ``GENHD_FL_NO_PART`` (0x0200): partition support is disabled. /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: * ``GENHD_FL_NO_PART``. /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h:#define GENHD_FL_NO_PART 0x0200 /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: return disk_max_parts(disk) > 1 && !(disk->flags & GENHD_FL_NO_PART); $ lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 $ apt policy linux-image-5.15.0-1051-gcp linux-image-5.15.0-1051-gcp: Installed: 5.15.0-1051.59~20.04.1 Candidate: 5.15.0-1051.59~20.04.1 Version table: *** 5.15.0-1051.59~20.04.1 500 500 http://australia-southeast1.gce.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 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-1051-gcp 5.15.0-1051.59~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-1051.59~20.04.1-gcp 5.15.136 Uname: Linux 5.15.0-1051-gcp x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 14 12:07:11 2024 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-gcp-5.15 UpgradeStatus: Upgraded to
[Kernel-packages] [Bug 2051672] Re: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
Hello, I was quickly checking if I could help preparing the upgrade of IPRoute2 packages for Noble (before the final freeze). In short, IPRoute2 has Ubuntu specific modifications. The merge was not difficult, the code is there: https://code.launchpad.net/~matttbe/ubuntu/+source/iproute2/+git/iproute2/+ref/merge- lp2051672-noble But then, I realised that the 6.8 Linux kernel in Noble no longer includes Ubuntu FAN support. We could then drop these Ubuntu specific patches and sync with Debian. Andrea Righi mentioned this on IRC: > ubuntu-fan has been temporarily dropped from the noble kernel (see the discourse post https://discourse.ubuntu.com/t/introducing- kernel-6-8-for-the-24-04-noble-numbat-release), we're still trying to figure out if there are still some users that rely on this feature, if not we can definitely sync with Debian & upgrade Because the situation is still unknown, it might be good to continue to merge IPRoute2 with the version from Debian. In this case, please use the version I shared here above. I understand that we might be short on time, but it might be good if someone from the Kernel Packages team could have a look at this :) That would help to support networking features added in Kernel >6.1! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/2051672 Title: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) Status in iproute2 package in Ubuntu: Confirmed Bug description: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 Upstream ChangeLog: - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/ (Previous changelog: https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 ) ChangeLog from Debian: iproute2 (6.8.0-1) unstable; urgency=medium [ Ceppo ] * Update Italian po-debconf translation (Closes: #1063002) [ Luca Boccassi ] * Add build dependency on libnsl-dev (Closes: #1065214) * Switch to pkgconf * Update upstream source from tag 'upstream/6.8.0' * Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged upstream * Drop iproute2-doc package * Drop tc/m_xt.so and tc/m_ipt.so, removed upstream -- Luca Boccassi <> Tue, 12 Mar 2024 14:02:38 + iproute2 (6.7.0-2) unstable; urgency=medium * Backport fix for 'ss' output -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium * Add Italian debconf translation (Closes: #1056582) * Update upstream source from tag 'upstream/6.7.0' * Bump copyright year ranges in d/copyright * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, merged upstream * Default config files moved from /usr/lib to /usr/share -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium * Update upstream source from tag 'upstream/6.6.0' * Backport patch to fix configuration installation * Remove handling of qt_atm.so, dropped upstream -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium * Use dh-sequence-movetousr -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium * Remove further leftovers as part of upstream's move of config to /usr
[Kernel-packages] [Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)
This bug was fixed in the package linux-raspi - 6.8.0-1002.2 --- linux-raspi (6.8.0-1002.2) noble; urgency=medium * noble/linux-raspi: 6.8.0-1002.2 -proposed tracker (LP: #2057941) * Wifi wlan0 device not present on Raspberry Pi 3A+ (LP: #2056635) - [Config] raspi: Set MMC_BCM2835_SDHOST=y * Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives) (LP: #2038582) - [Config] raspi: Set COMPAT_32BIT_TIME=n * Miscellaneous Ubuntu changes - [Config] raspi: updateconfigs after update to raspberrypi rpi-6.8.y (2024-03-14) * Miscellaneous upstream changes - dtoverlays: Correct width/height on Waveshare 2.8" panel - dtoverlays: rotate override needs to update "rotation" for drm mode - configs: Disable process/register dumps via SysRq - ASOc: Add HiFiBerry DAC8X to the simple card driver - Overlays: Add definitions for HiFiBerry 8 channel DAC8X - drm: Add DRM_MODE_TV_MODE_MONOCHROME - drm/vc4: Add monochrome mode to the VEC. - media: i2c: imx296: Updated register setting to fix Fast Trigger - dt-bindings: add additional RP1 PLL output channels - drivers: clk: rp1: add GPCLK source muxes and additional PLL dividers - DT: rp1: add general-purpose clock source definitions - drivers: clk: rp1: constrain clock divider outputs to design maximums - vc4: Add jack detection to HDMI audio driver - fixup! ASoC: dwc: Defer bclk_ratio handling to hw_params - ASoC: bcm: Use the correct sample width value - clk: rp1: Reserve pll_audio* for clk_i2s - clk: rp1: Allow clk_i2s to change the audio PLLs - regulator: Add a regulator for the new LCD panels - dt-bindings: ili9881c: add compatible string for new panels - drm/panel: ilitek-ili9881c: Allow configuration of the number of lanes - drm/panel: ili9881: Add configuration for the new panels - defconfigs: Add panel regulator to all the Pi defconfigs - dtoverlays: Add overlays for 5" and 7" ILI9881 panels - ARM: dts: bcm2712-rpi: Add i2c_pins labels - ASoC: dwc: Correct channel count reporting - Driver:add waveshare 4inch dsi lcd (C) driver - Dtoverlay:add waveshare 4inch dsi lcd (C) dtoverlay - Dtoverlay:fix waveshare 11.9inch touch orientation error - Dtoverlay:Add waveshare 4inch dsi lcd (C) parameters to the README [ Ubuntu: 6.8.0-20.20 ] * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y [ Ubuntu: 6.8.0-19.19 ] * noble/linux: 6.8.0-19.19 -proposed tracker (LP: #2057910) * Miscellaneous Ubuntu changes - [Packaging] re-introduce linux-doc as an empty package [ Ubuntu: 6.8.0-18.18 ] * noble/linux: 6.8.0-18.18 -proposed tracker (LP: #2057456) * Miscellaneous Ubuntu changes - [Packaging] drop dependency on libclang-17 [ Ubuntu: 6.8.0-17.17 ] * noble/linux: 6.8.0-17.17 -proposed tracker (LP: #2056745) * Miscellaneous upstream changes - Revert "UBUNTU: [Packaging] Add debian/control sanity check" [ Ubuntu: 6.8.0-16.16 ] * noble/linux: 6.8.0-16.16 -proposed tracker (LP: #2056738) * left-over ceph debugging printks (LP: #2056616) - Revert "UBUNTU: SAUCE: ceph: make sure all the files successfully put before unmounting" * qat: Improve error recovery flows (LP: #2056354) - crypto: qat - add heartbeat error simulator - crypto: qat - disable arbitration before reset - crypto: qat - update PFVF protocol for recovery - crypto: qat - re-enable sriov after pf reset - crypto: qat - add fatal error notification - crypto: qat - add auto reset on error - crypto: qat - limit heartbeat notifications - crypto: qat - improve aer error reset handling - crypto: qat - change SLAs cleanup flow at shutdown - crypto: qat - resolve race condition during AER recovery - Documentation: qat: fix auto_reset section * update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate ima_filter_rule from security_audit_rule - SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure management of the sock security - SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data structure. - SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label collisions with stacked LSMs - SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use
[Kernel-packages] [Bug 2056635] Re: Wifi wlan0 device not present on Raspberry Pi 3A+
This bug was fixed in the package linux-raspi - 6.8.0-1002.2 --- linux-raspi (6.8.0-1002.2) noble; urgency=medium * noble/linux-raspi: 6.8.0-1002.2 -proposed tracker (LP: #2057941) * Wifi wlan0 device not present on Raspberry Pi 3A+ (LP: #2056635) - [Config] raspi: Set MMC_BCM2835_SDHOST=y * Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives) (LP: #2038582) - [Config] raspi: Set COMPAT_32BIT_TIME=n * Miscellaneous Ubuntu changes - [Config] raspi: updateconfigs after update to raspberrypi rpi-6.8.y (2024-03-14) * Miscellaneous upstream changes - dtoverlays: Correct width/height on Waveshare 2.8" panel - dtoverlays: rotate override needs to update "rotation" for drm mode - configs: Disable process/register dumps via SysRq - ASOc: Add HiFiBerry DAC8X to the simple card driver - Overlays: Add definitions for HiFiBerry 8 channel DAC8X - drm: Add DRM_MODE_TV_MODE_MONOCHROME - drm/vc4: Add monochrome mode to the VEC. - media: i2c: imx296: Updated register setting to fix Fast Trigger - dt-bindings: add additional RP1 PLL output channels - drivers: clk: rp1: add GPCLK source muxes and additional PLL dividers - DT: rp1: add general-purpose clock source definitions - drivers: clk: rp1: constrain clock divider outputs to design maximums - vc4: Add jack detection to HDMI audio driver - fixup! ASoC: dwc: Defer bclk_ratio handling to hw_params - ASoC: bcm: Use the correct sample width value - clk: rp1: Reserve pll_audio* for clk_i2s - clk: rp1: Allow clk_i2s to change the audio PLLs - regulator: Add a regulator for the new LCD panels - dt-bindings: ili9881c: add compatible string for new panels - drm/panel: ilitek-ili9881c: Allow configuration of the number of lanes - drm/panel: ili9881: Add configuration for the new panels - defconfigs: Add panel regulator to all the Pi defconfigs - dtoverlays: Add overlays for 5" and 7" ILI9881 panels - ARM: dts: bcm2712-rpi: Add i2c_pins labels - ASoC: dwc: Correct channel count reporting - Driver:add waveshare 4inch dsi lcd (C) driver - Dtoverlay:add waveshare 4inch dsi lcd (C) dtoverlay - Dtoverlay:fix waveshare 11.9inch touch orientation error - Dtoverlay:Add waveshare 4inch dsi lcd (C) parameters to the README [ Ubuntu: 6.8.0-20.20 ] * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221) * Noble update: v6.8.1 upstream stable release (LP: #2058224) - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set - Documentation/hw-vuln: Add documentation for RFDS - x86/rfds: Mitigate Register File Data Sampling (RFDS) - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests - Linux 6.8.1 * Autopkgtest failures on amd64 (LP: #2048768) - [Packaging] update to clang-18 * Miscellaneous Ubuntu changes - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with CONFIG_SECURITY=n - [Config] amd64: MITIGATION_RFDS=y [ Ubuntu: 6.8.0-19.19 ] * noble/linux: 6.8.0-19.19 -proposed tracker (LP: #2057910) * Miscellaneous Ubuntu changes - [Packaging] re-introduce linux-doc as an empty package [ Ubuntu: 6.8.0-18.18 ] * noble/linux: 6.8.0-18.18 -proposed tracker (LP: #2057456) * Miscellaneous Ubuntu changes - [Packaging] drop dependency on libclang-17 [ Ubuntu: 6.8.0-17.17 ] * noble/linux: 6.8.0-17.17 -proposed tracker (LP: #2056745) * Miscellaneous upstream changes - Revert "UBUNTU: [Packaging] Add debian/control sanity check" [ Ubuntu: 6.8.0-16.16 ] * noble/linux: 6.8.0-16.16 -proposed tracker (LP: #2056738) * left-over ceph debugging printks (LP: #2056616) - Revert "UBUNTU: SAUCE: ceph: make sure all the files successfully put before unmounting" * qat: Improve error recovery flows (LP: #2056354) - crypto: qat - add heartbeat error simulator - crypto: qat - disable arbitration before reset - crypto: qat - update PFVF protocol for recovery - crypto: qat - re-enable sriov after pf reset - crypto: qat - add fatal error notification - crypto: qat - add auto reset on error - crypto: qat - limit heartbeat notifications - crypto: qat - improve aer error reset handling - crypto: qat - change SLAs cleanup flow at shutdown - crypto: qat - resolve race condition during AER recovery - Documentation: qat: fix auto_reset section * update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate ima_filter_rule from security_audit_rule - SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure management of the sock security - SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data structure. - SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label collisions with stacked LSMs - SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use
[Kernel-packages] [Bug 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
** Patch added: "nvidia-drm-take-modeset-ownership-earlier.patch" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2052420/+attachment/5761484/+files/nvidia-drm-take-modeset-ownership-earlier.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
Hi, I have question, Is possible to add this patches: PATCH[0]="disable_fstack-clash-protection_fcf-protection.patch" PATCH[1]="buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch" PATCH[2]="buildfix_kernel_6.8-gpl-pfn_valid.patch" PATCH[3]="nvidia-drm-hotplug-workqueue.patch" PATCH[4]="nvidia-drm-take-modeset-ownership-earlier.patch" At 0 to 2 exist now, but 3 and 4 not in 545. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
** Patch added: "nvidia-drm-hotplug-workqueue.patch" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2052420/+attachment/5761485/+files/nvidia-drm-hotplug-workqueue.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2060142] [NEW] Jammy update: v5.15.150 upstream stable release
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: v5.15.150 upstream stable release from git://git.kernel.org/ net/sched: Retire CBQ qdisc UBUNTU: [Config] updateconfigs for NET_SCH_CBQ net/sched: Retire ATM qdisc UBUNTU: [Config] updateconfigs for NET_SCH_ATM net/sched: Retire dsmark qdisc UBUNTU: [Config] updateconfigs for NET_SCH_DSMARK smb: client: fix potential OOBs in smb2_parse_contexts() smb: client: fix parsing of SMB3.1.1 POSIX create context sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset PCI: dwc: Fix a 64bit bug in dw_pcie_ep_raise_msix_irq() bpf: Merge printk and seq_printf VARARG max macros bpf: Add struct for bin_args arg in bpf_bprintf_prepare bpf: Do cleanup in bpf_bprintf_cleanup only when needed bpf: Remove trace_printk_lock userfaultfd: fix mmap_changing checking in mfill_atomic_hugetlb zonefs: Improve error handling x86/fpu: Stop relying on userspace for info to fault in xsave buffer sched/rt: Fix sysctl_sched_rr_timeslice intial value sched/rt: Disallow writing invalid values to sched_rt_period_us scsi: target: core: Add TMF to tmr_list handling dmaengine: shdma: increase size of 'dev_id' dmaengine: fsl-qdma: increase size of 'irq_name' wifi: cfg80211: fix missing interfaces when dumping wifi: mac80211: fix race condition on enabling fast-xmit fbdev: savage: Error out if pixclock equals zero fbdev: sis: Error out if pixclock equals zero spi: hisi-sfc-v3xx: Return IRQ_NONE if no interrupts were detected ahci: asm1166: correct count of reported ports ahci: add 43-bit DMA address quirk for ASMedia ASM1061 controllers MIPS: reserve exception vector space ONLY ONCE platform/x86: touchscreen_dmi: Add info for the TECLAST X16 Plus tablet ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found() ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal() dmaengine: ti: edma: Add some null pointer checks to the edma_probe regulator: pwm-regulator: Add validity checks in continuous .get_voltage nvmet-tcp: fix nvme tcp ida memory leak ALSA: usb-audio: Check presence of valid altsetting control ASoC: sunxi: sun4i-spdif: Add support for Allwinner H616 spi: sh-msiof: avoid integer overflow in constants Input: xpad - add Lenovo Legion Go controllers netfilter: conntrack: check SCTP_CID_SHUTDOWN_ACK for vtag setting in sctp_new ALSA: usb-audio: Ignore clock selector errors for single connection nvme-fc: do not wait in vain when unloading module nvmet-fcloop: swap the list_add_tail arguments nvmet-fc: release reference on target port nvmet-fc: defer cleanup using RCU properly nvmet-fc: hold reference on hostport match nvmet-fc: abort command when there is no binding nvmet-fc: avoid deadlock on delete association path nvmet-fc: take ref count on tgtport before delete assoc ext4: correct the hole length returned by ext4_map_blocks() Input: i8042 - add Fujitsu Lifebook U728 to i8042 quirk table fs/ntfs3: Modified fix directory element type detection fs/ntfs3: Improve ntfs_dir_count fs/ntfs3: Correct hard links updating when dealing with DOS names fs/ntfs3: Print warning while fixing hard links count fs/ntfs3: Fix detected field-spanning write (size 8) of single field "le->name" fs/ntfs3: Add NULL ptr dereference checking at the end of attr_allocate_frame() fs/ntfs3: Disable ATTR_LIST_ENTRY size check fs/ntfs3: use non-movable memory for ntfs3 MFT buffer cache fs/ntfs3: Prevent generic message "attempt to access beyond end of device" fs/ntfs3: Correct function is_rst_area_valid fs/ntfs3: Update inode->i_size after success write into compressed file fs/ntfs3: Fix oob in ntfs_listxattr wifi: mac80211: adding missing drv_mgd_complete_tx() call efi: runtime: Fix potential overflow of soft-reserved region size efi: Don't add memblocks for soft-reserved memory hwmon: (coretemp) Enlarge per package core count limit scsi: lpfc: Use unsigned type for num_sge firewire: core: send bus reset promptly on gap count error drm/amdgpu: skip to program GFXDEC registers for suspend abort drm/amdgpu: reset gpu for s3 suspend abort case virtio-blk: Ensure no requests in virtqueues before deleting vqs. pmdomain: mediatek: fix race conditions with genpd ksmbd: free aux buffer if ksmbd_iov_pin_rsp_read fails pmdomain: renesas: r8a77980-sysc: CR7 must be always on erofs: fix lz4 inplace decompression IB/hfi1: Fix sdma.h tx->num_descs off-by-one error drm/ttm: Fix an invalid freeing on already freed page in error path dm-crypt: don't modify the data when
[Kernel-packages] [Bug 1999589] Re: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / J-hwe-6.5
** Tags added: mantic -- 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/1999589 Title: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / J-hwe-6.5 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Confirmed Bug description: All of the sm4* ciper testcases are failing in net:tls for kinetic linux 5.19.0-27.28 These seem like new testcases that have not been run before. and this has only been seen as far as I am aware of on s390x - 21:31:48 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendfile ... 21:31:48 DEBUG| [stdout] # # tls.c:314:sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # not ok 197 tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.send_then_sendfile ... 21:31:49 DEBUG| [stdout] # # tls.c:314:send_then_sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # send_then_sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # not ok 198 tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_max ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_max:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_max: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # not ok 199 tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_small ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_small:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_small: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # not ok 200 tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # not ok 201 tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more_unsent ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more_unsent:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more_unsent: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # not ok 202 tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_single ... 21:31:49 DEBUG| [stdout] # # tls.c:314:sendmsg_single:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_single: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # not ok 203 tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_fragmented ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_fragmented:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_fragmented: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # not ok 204 tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_large ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_large:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_large: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # not ok 205 tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_multiple ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_multiple: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_multiple 21:31:50 DEBUG| [stdout] # not ok 206 tls.13_sm4_gcm.sendmsg_multiple 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_multiple_stress ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple_stress:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_multiple_stress: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_multiple_stress 21:31:50 DEBUG| [stdout] # not ok 207 tls.13_sm4_gcm.sendmsg_multiple_stress 21:31:50 DEBUG| [stdout] # # RUN
[Kernel-packages] [Bug 2060130] [NEW] [SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel cmdline/initrd sections from EFI stub
Public bug reported: This is a public version of https://bugs.launchpad.net/bugs/2058835 [Description] When a TD is created, during the boot process, steps like loading the firmware, bootloader, kernel image, etc are measured and stored in RTMR registers to support the trusted boot model. After boot, this measured value is used to validate the integrity of the boot process. During the direct boot process, bootloader is responsible for measuring the kernel image before loading the kernel. But if the kernel is loaded from EFI bootstub, the related measurements needs to be owned by the EFI bootstub. This support needs to be added to Linux EFI boot stub code. Also, as per the following discussion, the kernel command line or initrd section measurements also needs be owned by the EFI bootsub. https://edk2.groups.io/g/devel/topic/93737108?p=Created%2C%2C%2C20%2C2%2C0%2C0%3A%3A%2C%2C%2C0%2C0%2C0%2C93737108 [Fix] Cherry pick cleanly: d228814b1913 efi/libstub: Add get_event_log() support for CC platforms ac93cbfc2a2c efi/libstub: Measure into CC protocol if TCG2 protocol is absent 0bbe5b0ea97a efi/libstub: Add Confidential Computing (CC) measurement typedefs 7a1381e8313f efi/tpm: Use symbolic GUID name from spec for final events table 3e0b0f880e9e efi/libstub: Use TPM event typedefs from the TCG PC Client spec Those are all merged into upstream. [Test Plan] Build/sign/boot with secure boot enabled. [Where problems could occur] At boot time, as this is modifying the efi libstub. Could be impacting secure boot. ** Affects: linux (Ubuntu) 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/2060130 Title: [SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel cmdline/initrd sections from EFI stub Status in linux package in Ubuntu: New Bug description: This is a public version of https://bugs.launchpad.net/bugs/2058835 [Description] When a TD is created, during the boot process, steps like loading the firmware, bootloader, kernel image, etc are measured and stored in RTMR registers to support the trusted boot model. After boot, this measured value is used to validate the integrity of the boot process. During the direct boot process, bootloader is responsible for measuring the kernel image before loading the kernel. But if the kernel is loaded from EFI bootstub, the related measurements needs to be owned by the EFI bootstub. This support needs to be added to Linux EFI boot stub code. Also, as per the following discussion, the kernel command line or initrd section measurements also needs be owned by the EFI bootsub. https://edk2.groups.io/g/devel/topic/93737108?p=Created%2C%2C%2C20%2C2%2C0%2C0%3A%3A%2C%2C%2C0%2C0%2C0%2C93737108 [Fix] Cherry pick cleanly: d228814b1913 efi/libstub: Add get_event_log() support for CC platforms ac93cbfc2a2c efi/libstub: Measure into CC protocol if TCG2 protocol is absent 0bbe5b0ea97a efi/libstub: Add Confidential Computing (CC) measurement typedefs 7a1381e8313f efi/tpm: Use symbolic GUID name from spec for final events table 3e0b0f880e9e efi/libstub: Use TPM event typedefs from the TCG PC Client spec Those are all merged into upstream. [Test Plan] Build/sign/boot with secure boot enabled. [Where problems could occur] At boot time, as this is modifying the efi libstub. Could be impacting secure boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060130/+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 2058808] Re: iwlwifi disconnect and crash - intel wifi7
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058808 Title: iwlwifi disconnect and crash - intel wifi7 Status in HWE Next: In Progress 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: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: iwlwifi disconnecting and crashing when I using Wifi 2.4GHz. [ cut here ] Invalid rxb from HW 0 WARNING: CPU: 14 PID: 896 at drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc rapl nvidia_uvm(PO) nfnetlink binfmt_misc n xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW OE 6.5.0-26-generic #26~22.04.1-Ubuntu Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023 RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9 RSP: 0018:b91d803e0e18 EFLAGS: 00010246 RAX: RBX: 956747353c30 RCX: RDX: RSI: RDI: RBP: b91d803e0e78 R08: R09: R10: R11: R12: 1007 R13: 0015 R14: R15: 956746a30028 FS: () GS:95768f38() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? free_unref_page+0x30/0x180 iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi] ? skb_free_head+0xa8/0xd0 __napi_poll+0x30/0x1f0 net_rx_action+0x181/0x2e0 ? __irq_wake_thread+0x42/0x50 __do_softirq+0xd9/0x349 ? __pfx_irq_thread_fn+0x10/0x10 do_softirq.part.0+0x41/0x80 __local_bh_enable_ip+0x72/0x80 iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi] irq_thread_fn+0x21/0x70 irq_thread+0xf8/0x1c0 ? __pfx_irq_thread_dtor+0x10/0x10 ? __pfx_irq_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 ---[ end trace ]--- iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0. iwlwifi :05:00.0: Start IWL Error Log Dump: iwlwifi :05:00.0: Transport status: 0x004A, valid: 6 iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 gl-c0-fm-c0-83.ucode iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN iwlwifi :05:00.0: 0x0003 | trm_hw_status0 iwlwifi :05:00.0: 0x | trm_hw_status1 iwlwifi :05:00.0: 0x002C280A | branchlink2 iwlwifi :05:00.0: 0x9328 | interruptlink1 iwlwifi :05:00.0: 0x9328 | interruptlink2 iwlwifi :05:00.0: 0xF46C | data1 iwlwifi :05:00.0: 0x0100 | data2 iwlwifi :05:00.0: 0x | data3 iwlwifi :05:00.0: 0xA0005E44 | beacon time iwlwifi :05:00.0: 0x2806818F | tsf low iwlwifi :05:00.0: 0x | tsf hi iwlwifi :05:00.0: 0x | time gp1 iwlwifi :05:00.0: 0x0BB840A7 | time gp2 iwlwifi :05:00.0: 0x0001 | uCode revision type iwlwifi :05:00.0: 0x0053 | uCode version major iwlwifi :05:00.0: 0xEC13314B | uCode version minor iwlwifi :05:00.0: 0x0472 | hw version iwlwifi :05:00.0: 0x00C80002 | board version iwlwifi :05:00.0: 0x03B7001C | hcmd iwlwifi :05:00.0:
[Kernel-packages] [Bug 2058452] Re: Support USB serial port for Dell DW5826e WWAN
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2058452
Title:
Support USB serial port for Dell DW5826e WWAN
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.8
[Test Case]
1. check system with USB\VID_413C_8217 or USB\VID_413C_8218
creates corresponding tty port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream commit:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
The tty port will be utilized by the userspace fcc unlock program.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2058452/+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 2038584] Re: Turning COMPAT_32BIT_TIME off on riscv64
This bug was fixed in the package linux-riscv - 6.8.0-20.20.1 --- linux-riscv (6.8.0-20.20.1) noble; urgency=medium * noble/linux-riscv: 6.8.0-20.20.1 -proposed tracker (LP: #2058921) * Packaging resync (LP: #1786013) - debian.riscv/dkms-versions -- update from kernel-versions (main/d2024.02.29) * Enable StarFive VisionFive 2 board (LP: #2013232) - dt-bindings: pwm: Add bindings for OpenCores PWM Controller - riscv: dts: starfive: jh7110: Add PWM node and pins configuration - SAUCE: pwm: opencores: Add PWM driver support - SAUCE: dt-bindings: PCI: Add PLDA XpressRICH PCIe host common properties - SAUCE: PCI: microchip: Move pcie-microchip-host.c to plda directory - SAUCE: PCI: microchip: Move PLDA IP register macros to pcie-plda.h - SAUCE: PCI: microchip: Add bridge_addr field to struct mc_pcie - SAUCE: PCI: microchip: Rename two PCIe data structures - SAUCE: PCI: microchip: Move PCIe host data structures to plda-pcie.h - SAUCE: PCI: microchip: Rename two setup functions - SAUCE: PCI: microchip: Change the argument of plda_pcie_setup_iomems() - SAUCE: PCI: microchip: Move setup functions to pcie-plda-host.c - SAUCE: PCI: microchip: Rename interrupt related functions - SAUCE: PCI: microchip: Add num_events field to struct plda_pcie_rp - SAUCE: PCI: microchip: Add request_event_irq() callback function - SAUCE: PCI: microchip: Add INTx and MSI event num to struct plda_event - SAUCE: PCI: microchip: Add get_events() callback and add PLDA get_event() - SAUCE: PCI: microchip: Add event irqchip field to host port and add PLDA irqchip - SAUCE: PCI: microchip: Move IRQ functions to pcie-plda-host.c - SAUCE: PCI: plda: Add event bitmap field to struct plda_pcie_rp - SAUCE: PCI: plda: Add host init/deinit and map bus functions - SAUCE: dt-bindings: PCI: Add StarFive JH7110 PCIe controller - SAUCE: PCI: Add PCIE_RESET_CONFIG_DEVICE_WAIT_MS waiting time value - SAUCE: PCI: starfive: Add JH7110 PCIe controller - SAUCE: PCI: starfive: Offload the NVMe timeout workaround to host drivers. - SAUCE: riscv: dts: starfive: add PCIe dts configuration for JH7110 - SAUCE: clk: starfive: jh7110-sys: Fix lower rate of CPUfreq by setting PLL0 rate to 1.5GHz - SAUCE: [HACK] riscv: dts: starfive: Add VisionFive 2 reserved memory node - SAUCE: riscv: dts: starfive: Disable JH7110 crypto peripheral - [Config] riscv: updateconfigs for VisionFive 2 patches * Enable Nezha board (LP: #1975592) - [Config] Enable CONFIG_REGULATOR_FIXED_VOLTAGE on riscv64 - SAUCE: dt-bindings: pwm: Add binding for Allwinner D1/T113-S3/R329 PWM controller - SAUCE: pwm: Add Allwinner's D1/T113-S3/R329 SoCs PWM support - SAUCE: riscv: dts: allwinner: d1: Add pwm node - SAUCE: riscv: dts: allwinner: d1: Add PWM pins - SAUCE: mmc: sunxi-mmc: Correct the maximum segment size - SAUCE: riscv: dts: allwinner: d1: Add misc nodes - SAUCE: riscv: dts: allwinner: Keep aldo regulator on - SAUCE: riscv: dts: allwinner: Add button on the Nezha board - SAUCE: riscv: dts: allwinner: Add button on the Lichee RV Dock - SAUCE: dt-bindings: nvmem: Allow bit offsets greater than a byte - SAUCE: nvmem: core: Support reading cells with >= 8 bit offsets - SAUCE: regulator: dt-bindings: Add Allwinner D1 LDOs - SAUCE: regulator: sun20i: Add support for Allwinner D1 LDOs - SAUCE: regulator: sun20i: Use device_node_to_regmap() - SAUCE: dt-bindings: sram: sunxi-sram: Add optional regulators child - SAUCE: dt-bindings: thermal: sun8i: Add compatible for D1 - SAUCE: thermal: sun8i: Document the unknown field - SAUCE: thermal: sun8i: Set the event type for new samples - SAUCE: thermal: sun8i: Ensure vref is powered - SAUCE: riscv: dts: allwinner: d1: Add thermal sensor and zone - SAUCE: riscv: dts: allwinner: d1: Hook up PWM-controlled CPU voltage regulators - SAUCE: drm/sun4i: dsi: Allow panel attach before card registration - SAUCE: drm/sun4i: mixer: Remove unused CMA headers - SAUCE: drm/sun4i: tcon: Always protect the LCD dotclock rate - SAUCE: drm/sun4i: tcon_top: Register reset, clock gates in probe - SAUCE: riscv: dts: allwinner: lichee-rv-86-panel-480p: Add panel - SAUCE: riscv: dts: allwinner: d1: Add HDMI pipeline - SAUCE: riscv: dts: allwinner: d1: Enable HDMI on supported boards - SAUCE: dt-bindings: display: sun4i-tcon: Add external LVDS PHY - SAUCE: riscv: dts: allwinner: d1: Add LVDS0 PHY - SAUCE: riscv: dts: allwinner: d1: Add LED controller node - SAUCE: riscv: dts: allwinner: d1: Add RGB LEDs to boards - SAUCE: ASoC: sun20i-codec: New driver for D1 internal codec - SAUCE: [WIP] ASoC: sun20i-codec: What is this ramp thing? - SAUCE: riscv: dts: allwinner: d1: Add sound cards to boards - SAUCE: dt-bindings: display: sun8i-a83t-dw-hdmi: Remove #phy-cells -
[Kernel-packages] [Bug 2057960] Re: Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4
Hello Anderson, Thank you for reporting the issue. We have a new kernel for 22.04 (version 5.15.0-102.112) that is about to be released in the next few days. Could you please test it again with this kernel and report the results? You can either enable -proposed in your system and update the kernel, or wait until it gets promoted to -updates and a simple dist- upgrate will update the kernel. -- 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/2057960 Title: Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4 Status in linux package in Ubuntu: New Bug description: Since I've upgraded my server's to Ubuntu 22.04.4 I'm facing problems to make my fcoe setup to work correctly. Firstly, some context. We have a HPE Synergy appliance with a bunch of Synergy 480 Gen10 servers still running Ubuntu 20.04. Each 480 server has 4 QLogic BCM57840 NetXtreme II Ethernet Multi Function network adapters with two of them dedicated to storage communication through FCoE. Recently, I've upgraded one of them to Ubuntu 22.04 and realized that after the upgrade, all the Fibre Channel LUNs have disappeared. During the diagnostic process I noticed that both network (bnx2x) and fcoe (fcoe, bnx2fc) kernel drivers have been loaded properly, FCoE vlans were correctly detected by fcoe-utils, but there was no connection between the server and the storage and the server could not detect any LUN. I also noticed that fcoeadm was reporting the following status: # fcoeadm -i Description: BCM57840 NetXtreme II Ethernet Multi Function Revision: 11 Manufacturer: Broadcom Inc. and subsidiaries Serial Number:9440C953B7F0 Driver: bnx2x Unknown Number of Ports: 1 Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over ens3f2.4093-fco OS Device Name:host2 Node Name: 0x1a3d2725 Port Name: 0x1a3d2724 Fabric Name: 0x0 Speed: 20 Gbit Supported Speed: 1 Gbit, 10 Gbit MaxFrameSize: 2048 bytes FC-ID (Port ID): 0x State: Offline Description: BCM57840 NetXtreme II Ethernet Multi Function Revision: 11 Manufacturer: Broadcom Inc. and subsidiaries Serial Number:9440C953B7F0 Driver: bnx2x Unknown Number of Ports: 1 Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over ens3f3.4094-fco OS Device Name:host3 Node Name: 0x1a3d2727 Port Name: 0x1a3d2726 Fabric Name: 0x0 Speed: 20 Gbit Supported Speed: 1 Gbit, 10 Gbit MaxFrameSize: 2048 bytes FC-ID (Port ID): 0x State: Offline Although most of information displayed was correct, the port state was always offline (what explains no storage connectivity) and the FC-ID reported was 0x for both interfaces. Supposing that something went wrong during the upgrade process, I decided to make a fresh install of the server and, for my surprise, the fcoe ports went online and all luns were detected correctly. Unfortunately, the ports went offline again after a dist-upgrade. Trying to understand what was happening I performed another fresh install of the Ubuntu 22.04, but this time collecting some information about kernel and packages versions from before and after dist-upgrade. What I discovered was that all packages related (fcoe-utils, lldpad) had the same versions before and after, the only exception was the kernel itself. Before the dist-upgrade the kernel in use was 5.15.0-25-generic and after dist-upgrade the kernel was 5.15.0-100-generic. Suspecting a kernel problem I installed and booted different kernel versions from 5.15.0-25 and 5.15.0-100 and discovered that the problem probably was introduced with kernel 5.15.0-94, since it is the first version showing the describe behavior. Looking at the changelog of linux-modules package, I noticed some changes on fcoe and other scsi modules, right after the 5.15.0-91 version. Could those changes be the cause of the behavior observed on my server or just a coincidence? Is there any fix to it? Thanks in advance. Anderson ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-94-generic 5.15.0-94.104 ProcVersionSignature: Ubuntu 5.15.0-94.104-generic 5.15.136 Uname: Linux 5.15.0-94-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 14 11:03 seq crw-rw 1 root audio 116, 33 Mar 14 11:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64
[Kernel-packages] [Bug 2055002] Re: Mantic update: upstream stable patchset 2024-02-27
this change seems to break copying files within a CIFS mount (cp is getting killed, and dmesg contains a BUG entry pointing to cifs_flush_folio - see the attached dmesg.log). Reproduced with 2 different Samba-shares with the current 6.5.0-32-generic linux-image. Not present in linux-image-6.5.0-26-generic Reverting "cifs: fix flushing folio regression for 6.1 backport" makes the issue disappear in my tests. (Which seems sensible, since, at a very quick glance, `66dabbb65d673aef40dd17bf62c042be8f6d4a4b` probably introduced the change in 6.4, and is part of the mantic source, while it is not in the 6.1 tree) ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055002/+attachment/5761425/+files/dmesg.log -- 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/2055002 Title: Mantic update: upstream stable patchset 2024-02-27 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: 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: upstream stable patchset 2024-02-27 Ported from the following upstream stable releases: v6.1.73, v6.6.12 from git://git.kernel.org/ Revert "nfsd: call nfsd_last_thread() before final nfsd_put()" cifs: fix flushing folio regression for 6.1 backport UBUNTU: Upstream stable to v6.1.73, v6.6.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055002/+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 2055083] Re: Drop fips-checks script from trees
** Changed in: linux (Ubuntu Noble) 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/2055083 Title: Drop fips-checks script from trees Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: [Impact] When producing a new version of some kernels, we need to check for changes that might affect FIPS certs and justify why a commit was kept. For that, we have a fips-checks script that lives under debian/ in Focal, Jammy, Mantic and Noble. This script has been moved to `cranky`[1], so now there is no need to have this script in the kernel Git trees as well. [1] https://git.launchpad.net/~canonical-kernel/+git/kteam- tools/commit/?id=2ab9364d4b4c18bee7d835787d7dd11990103bca [Fix] Remove the fips-checks script and its calls. [Test Plan] Prepare a kernel and ensure that the `cranky close` step runs without any errors. [Where problems could occur] This only affects the preparation of FIPS kernels and not the kernel final binary. Moreover, I've prepared some FIPS kernels from the 2024.03.04 cycle relying on `cranky check-fips` to ensure that we have it working well on the cranky side too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055083/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
Sorry, but I don't believe that for a second. The fix is not difficult or time-consuming, and they already had a patched version. "Eventually 6.5+ based jammy kernels will not have it in lrm either. And we will only keep it against older kernels in bionic..jammy (ga only)" Unless they reverse ^that decision, it means Won't Fix. I'll believe otherwise when I see it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-450-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-470 source package in Jammy: Invalid Status in nvidia-graphics-drivers-470-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-525 source package in Jammy: Invalid Status in nvidia-graphics-drivers-525-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 1971699] Re: disable Intel DMA remapping by default
With no test case, I'll mark this as verified ** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux verification-needed-jammy-linux-aws-fips verification-needed-jammy-linux-nvidia-tegra ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra -- 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/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+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 1988018] Re: [mlx5] Intermittent VF-LAG activation failure
This should be fixed as of Netplan v1.0: https://github.com/canonical/netplan/pull/439 Please re-open if you think this is still an issue. ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Fix Committed ** Also affects: netplan.io (Ubuntu Noble) Importance: Medium Status: Triaged ** Changed in: netplan.io (Ubuntu Noble) Status: Triaged => Fix Released ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Mantic) 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/1988018 Title: [mlx5] Intermittent VF-LAG activation failure Status in linux package in Ubuntu: Fix Committed Status in netplan.io package in Ubuntu: Fix Released Status in linux source package in Jammy: New Status in netplan.io source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Status in netplan.io source package in Kinetic: Won't Fix Status in linux source package in Mantic: New Status in netplan.io source package in Mantic: New Status in linux source package in Noble: Fix Committed Status in netplan.io source package in Noble: Fix Released Bug description: During system initialization there is a specific sequence that must be followed to enable the use of hardware offload and VF-LAG. Intermittently one may see that VF-LAG initialization fails: [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 shared_fdb:1 [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x7d49cb) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 9): Failed to create LAG (-22) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 9): Failed to activate VF LAG Make sure all VFs are unbound prior to VF LAG activation or deactivation This is caused by rebinding the driver prior to the VF lag being ready. A sysfs knob has recently been added to the driver [0] and we should monitor it before attempting to rebind the driver: $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state The kernel feature is available in the upcoming Kinetic 5.19 kernel and we should probably backport it to the Jammy 5.15 kernel. 0: https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988018/+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 1756997] Re: plasmashell leaks memory uncontrollably
** No longer affects: nvidia-graphics-drivers-384 (Ubuntu) ** Changed in: plasma-workspace (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1756997 Title: plasmashell leaks memory uncontrollably Status in plasma-workspace package in Ubuntu: Fix Released Bug description: I'm not sure if this is a problem with the plasmashell executable itself, or the the nvidia libraries, or perhaps plasmashell not interacting with the nvidia libraries correctly, but for the past several months I've noticed that the memory usage of plasmashell creeps slowly and consistently upward the longer it is running. This is at the level for me that within a day or two after (re)starting it, it is taking up all of my 12 gigs of ram and my my swap space engages and my system starts thrashing to the point that it takes minutes to get to a console to killall plasmashell. If I'm not sure if I'll even get to that point, I do SysRq+F (Sometimes it locks up completely -- presumably due to a kernel panic -- if I don't catch the extensive thrashing before too long, but that's a secondary issue.) This problem began several months ago (I was sort of expecting someone would quickly patch it, so I lived with it for a bit) so unfortunately I can't point to a specific version number. I did run apport-valgrind on plasmashell (output to be attached), which is what implicates the nvidia drivers. Happy to provide any additional information requested or to try other versions of these applications. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: plasma-workspace 4:5.10.5-0ubuntu1 [modified: usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml] ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Mon Mar 19 15:48:15 2018 InstallationDate: Installed on 2012-01-06 (2264 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: plasma-workspace UpgradeStatus: Upgraded to artful on 2014-12-03 (1202 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1756997/+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 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Noble) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Noble: In Progress Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+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 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Information type changed from Private to Public ** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Noble: In Progress Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+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 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Also affects: intel-gpu-tools (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Noble: In Progress Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+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 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-aws-fips verification-needed-jammy-linux-nvidia-tegra ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra -- 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/2052005 Title: Validate connection interval to pass Bluetooth Test Suite Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified. [Fix] Validate max connection interval to pass test case "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid Parameters Central Responder'" [Test] Run the test suite. With the patch applied the case is passed. [Where problems could occur] If any device requires setting a wrong interval to function properly, this might affect those devices in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+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 2055685] Re: Cranky update-dkms-versions rollout
** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-aws-fips verification-needed-jammy-linux-nvidia-tegra verification-needed-xenial-linux ** Tags added: verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra verification-done-xenial-linux ** Tags removed: verification-needed-bionic-linux verification-needed-focal-linux-aws-5.15 ** Tags added: verification-done-bionic-linux verification-done-focal-linux-aws-5.15 -- 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/2055685 Title: Cranky update-dkms-versions rollout Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Having a common file for dkms-versions between main kernels and derivatives causes a lot of conflicts during rebase. Solution is to have a dkms-versions per kernels, under debian./dkms-version. While at it, instead of running ./update-dkms-version script, cranky update-dkms-versions was introduced. This is not used in xenial, therefore for xenial we only replaced debian/dkms-versions with debian./dkms-versions [Fix] This is needed only in the main kernels. 1. remove update-dkms-version script (where needed), in xenial:linux we don't have it 2. rename debian/dkms-version with debian.master/dkms-versions 3. Replace debian/dkms-versions references in debian scripts and rules with $(DEBIAN)/dkms-versions Note for derivatives: These changes will be inherited from the parent during cranky rebase. The only change to the cranky process is: instead of using ./update-dkms-versions script, cranky-update-dkms-versions should be used [Test] Build test on cbd. No issue found. [Regression pottential] Owners have tried this last cycle in derivatives and no issues were found. We may see build failures due to wrong dkms versions, but it will be fixed along the way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055685/+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 2056143] Re: block/loop: No longer allows to create partitions
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-aws-fips verification-needed-jammy-linux-nvidia-tegra ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra -- 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/2056143 Title: block/loop: No longer allows to create partitions Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == -- Impact -- In 22.04/Jammy with the GA 5.15 kernel there was an upstream change preventing partition table operations when GENHD_FL_NO_PART is set. 1a721de8489f "block: don't add or resize partition on the disk with GENHD_FL_NO_PART" Beside of changing return codes and breaking some user-space that way this also causes loop block devices to no longer be able to have partitions manually created. This is because the loop block driver uses GENHD_FL_NO_PART to prevent active partition scans. -- Fix -- This was changed in 5.19 (and thus Mantic is not affected) by introducing a separate flag to prevent those scans: b9684a71fca7 "block, loop: support partitions without scanning" The fix depends on a larger rewrite so it cannot be simply picked. The biggest change from the original is moving the check for the new flag into a helper function in genhd.h which checks whether a disk should be scanned for partitions. That function was dropped with the upstream rewrite and checking moved into the loop driver directly. But it felt like adjusting the helper was the better approach. Note: The upstream patch has a follow-up change submitted: 748008e1da92 "block: don't add partitions if GD_SUPPRESS_PART_SCAN is set" We do _NOT_ need that in Jammy/5.15 because block/partitions/core.c: blk_add_partitions() checks disk_part_scan_enabled() which was where we added the check for the backport instead of modifying disk_scan_partitions() directly. -- Testcase -- $ fallocate -l 1G /tmp/blob $ LOOPDEV=$(sudo losetup --find --show /tmp/blob) $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100% -- Regression Potential -- If things go wrong it might be other devices which no longer get scanned automatically or other issues with the loop block driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056143/+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 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold
** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-nvidia-tegra ** Tags added: verification-passed-focal-linux-nvidia-tegra-5.15 verification-passed-jammy-linux-nvidia-tegra ** Tags removed: verification-passed-focal-linux-aws-5.15 verification-passed-focal-linux-nvidia-tegra-5.15 verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips verification-passed-jammy-linux-nvidia-tegra ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra -- 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/2052827 Title: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034981 Backport upstream commit: 873f64b791a2 mm/memcontrol.c: remove the redundant updating of stats_flush_threshold to jammy. [Impact] Remove the redundant updating of stats_flush_threshold. If the global var stats_flush_threshold has exceeded the trigger value for __mem_cgroup_flush_stats, further increment is unnecessary. This is targeting Sapphire Rapids platforms. [Fix] Upstream commit 873f64b791a2 fixes this issue. The fix involves not updating the status after a certain threshold has been hit as it is unnecessary. [Test Plan] I have tested the changes, and hit no regressions. [Where problems could occur] As the change has been upstream since 6.0-rc1, and is reducing a stats update which isn't needed, the change for regressions should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052827/+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 2051727] Re: tcp: Add memory barrier to tcp_push()
** Tags removed: verification-passed-focal-linux-aws
verification-passed-focal-linux-aws-5.15
verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux-aws
** Tags added: verification-done-focal-linux-aws
verification-done-focal-linux-aws-5.15 verification-done-jammy-linux-aws-fips
verification-done-mantic-linux-aws
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2051727
Title:
tcp: Add memory barrier to tcp_push()
Status in linux package in Ubuntu:
Invalid
Status in linux-aws package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-aws source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-aws source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
Invalid
Status in linux-aws source package in Mantic:
Fix Committed
Bug description:
Recently a patch has been accepted on the Linux Kernel regarding the
TCP stack which fix an additional +40ms latency on ARM64 CPU
architecture without impacting other CPU types.
More information can be find in here:
https://lore.kernel.org/netdev/20240119190133.43698-1-dipi...@amazon.com/
Would be possible to include the following patch as part of Linux
image on the most recent and LTS maintained Ubuntu versions?
Patch:
```
---
net/ipv4/tcp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
index ff6838ca2e58..7bce79beca2b 100644
--- a/net/ipv4/tcp.c
+++ b/net/ipv4/tcp.c
@@ -722,6 +722,7 @@ void tcp_push(struct sock *sk, int flags, int mss_now,
if (!test_bit(TSQ_THROTTLED, >sk_tsq_flags)) {
NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPAUTOCORKING);
set_bit(TSQ_THROTTLED, >sk_tsq_flags);
+ smp_mb__after_atomic();
}
/* It is possible TX completion already happened
* before we set TSQ_THROTTLED.
--
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051727/+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 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers
** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-nvidia-tegra ** Tags added: verification-passed-focal-linux-nvidia-tegra-5.15 verification-passed-jammy-linux-nvidia-tegra ** Tags removed: verification-passed-focal-linux-aws-5.15 verification-passed-focal-linux-nvidia-tegra-5.15 verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips verification-passed-jammy-linux-nvidia-tegra ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra -- 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/2052817 Title: cpufreq: intel_pstate: Enable HWP IO boost for all servers Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2009321 Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to jammy. [Impact] Currently there is a CPU model check for Skylake desktop and server along with the ACPI PM profile for performance and enterprise servers to enable IO boost. Patch removes the CPU model check, so that all current server models enable HWP IO boost by default. The HWP IO boost results in improvements for IO performance on both Ice Lake and Sapphire Rapid servers. Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf- Boost Upstream review Link: https://lore.kernel.org/linux- pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/ [Fix] Upstream patch: cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 was merged to fix this. This will be back porting it to jammy. [Test Plan] I have tested this code, as has Intel. [Where problems could occur] The risk for regression is low. The change is fairly narrow, and has been upstreamed for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052817/+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 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing
** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-nvidia-tegra verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra -- 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/2053069 Title: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034983 [Description] When running UnixBench/shell1 cases, we observed high false sharing for accessing i_mmap against i_mmap_rwsem. The patch places the i_mmap and i_mmap_rwsem in separate cache lines to avoid this false sharing problem. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): DNP Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: TBD Commit IDs: aee79d4e5271 fs/address_space: add alignment padding for i_map and i_mmap_rwsem to mitigate a false sharing. External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5159 Here's the commit ID: aee79d4e5271cee4ffa89ed830189929a6272eb8 https://github.com/torvalds/linux/commit/aee79d4e5271cee4ffa89ed830189929a6272eb8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053069/+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 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
** Tags removed: verification-needed-jammy-linux-nvidia-tegra verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-jammy-linux verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra verification-done-mantic-linux ** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 ** Tags added: verification-done-focal-linux-nvidia-tegra-5.15 -- 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/2054699 Title: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2044822 SRU Justification: [Impact] Fix tsc clocksource on 4 sockets x86 servers was wrongly judged as 'unstable' by 'jiffies' and other watchdogs, and disabled [Fix] cherry-pick 233756a640be x86/tsc: Extend watchdog check exemption to 4-Sockets platform from upstream fixes this [Test Plan] This has been tested by intel, and has been upstreamed for a while. [Where problems could occur] This is a fairly narrow change, and extends a behaviour correction to cover up to 4-socket machines, rather than just 2 socket machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054699/+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 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
** Tags removed: verification-passed-focal-linux-aws verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux-aws ** Tags added: verification-done-focal-linux-aws verification-done-focal-linux-aws-5.15 verification-done-jammy-linux-aws-fips verification-done-mantic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2056475 Title: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Mantic: Fix Committed Status in linux-aws source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our latest generation instances with networking heavy workloads is up to a 25% performance regression (i.e. NGINX in a load-balancing configuration). [Fix] The mainline Linux kernel will now support IRQ moderation by default for ENA in the 6.9 kernel release via this patch: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/amazon/ena?id=50d7a2660579889fba28b7e4543d4ce85aa2311b [Test Plan] AWS tested [Where problems could occur] By enabling adaptive coalescing, the default interrupt behaviour will by changed to be more adaptive, which shows improvements on heavy network workloads, but my change the behaviour and performance on other network workloads differently. Rather than handling the interrupts based off of a fixed amount of time elapsed, it will change to an adaptive based approach. There should be no negative impact on light workloads, and a positive impact on heavy work loads. If there is an impact though, this option can be disabled via the ethtool command. [Other Info] SF: 00380449 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2056475/+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 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux ** Also affects: auto-package-testing 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/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package Status in Auto Package Testing: New Status in linux package in Ubuntu: New Bug description: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux- aws-5.15--modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+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 2051727] Re: tcp: Add memory barrier to tcp_push()
This was added to linux-aws, not linux and it messed up the verification
process
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Invalid
** Changed in: linux (Ubuntu Mantic)
Status: Fix Committed => Invalid
** Changed in: linux-aws (Ubuntu)
Status: New => Invalid
** Changed in: linux-aws (Ubuntu Focal)
Assignee: (unassigned) => Philip Cox (philcox)
** Changed in: linux-aws (Ubuntu Jammy)
Assignee: (unassigned) => Philip Cox (philcox)
** Changed in: linux-aws (Ubuntu Mantic)
Assignee: (unassigned) => Philip Cox (philcox)
** Changed in: linux-aws (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-aws (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-aws (Ubuntu Mantic)
Status: New => Fix Committed
--
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/2051727
Title:
tcp: Add memory barrier to tcp_push()
Status in linux package in Ubuntu:
Invalid
Status in linux-aws package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-aws source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-aws source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
Invalid
Status in linux-aws source package in Mantic:
Fix Committed
Bug description:
Recently a patch has been accepted on the Linux Kernel regarding the
TCP stack which fix an additional +40ms latency on ARM64 CPU
architecture without impacting other CPU types.
More information can be find in here:
https://lore.kernel.org/netdev/20240119190133.43698-1-dipi...@amazon.com/
Would be possible to include the following patch as part of Linux
image on the most recent and LTS maintained Ubuntu versions?
Patch:
```
---
net/ipv4/tcp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
index ff6838ca2e58..7bce79beca2b 100644
--- a/net/ipv4/tcp.c
+++ b/net/ipv4/tcp.c
@@ -722,6 +722,7 @@ void tcp_push(struct sock *sk, int flags, int mss_now,
if (!test_bit(TSQ_THROTTLED, >sk_tsq_flags)) {
NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPAUTOCORKING);
set_bit(TSQ_THROTTLED, >sk_tsq_flags);
+ smp_mb__after_atomic();
}
/* It is possible TX completion already happened
* before we set TSQ_THROTTLED.
--
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051727/+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 2060101] Re: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
** Tags added: oem-priority originate-from-2044254 sutton -- 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/2060101 Title: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060101/+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 2007759] Re: Spotify freezes my entire system
I have also facing the same issue on my client's website... Check my client website: https://www.spotifyhub.app/ -- 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/2007759 Title: Spotify freezes my entire system Status in linux package in Ubuntu: Confirmed Bug description: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 The main error that I always get aren't included in any txt files but here is the one error I copy paste from askubuntu: retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) -- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1576 F wireplumber /dev/snd/controlC0: adrian 1576 F wireplumber /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version: IdeaPad 3 15ADA05
[Kernel-packages] [Bug 2060101] [NEW] Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
Public bug reported: TBD. ** Affects: linux (Ubuntu) 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/2060101 Title: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera Status in linux package in Ubuntu: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060101/+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 2060097] [NEW] Noble update: v6.8.2 upstream stable release
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: v6.8.2 upstream stable release from git://git.kernel.org/ Linux 6.8.2 printk: Use prb_first_seq() as base for 32bit seq macros printk: Adjust mapping for 32bit seq macros x86/efistub: Don't clear BSS twice in mixed mode x86/efistub: Clear decompressor BSS in native EFI entrypoint dm-integrity: align the outgoing bio in integrity_recheck dm io: Support IO priority selftests: forwarding: Fix ping failure due to short timeout spi: spi-mt65xx: Fix NULL pointer access in interrupt handler netfilter: nf_tables: Fix a memory leak in nf_tables_updchain net: dsa: mt7530: fix handling of all link-local frames net: dsa: mt7530: fix link-local frames that ingress vlan filtering ports bpf: report RCU QS in cpumap kthread net: report RCU QS on threaded NAPI repolling rcu: add a helper to report consolidated flavor QS netfilter: nf_tables: do not compare internal table flags on updates netfilter: nft_set_pipapo: release elements in clone only from destroy path drm/amdgpu: drop setting buffer funcs in sdma442 drm/amdgpu: fix mmhub client id out-of-bounds access drm/amdgpu: add MMHUB 3.3.1 support octeontx2-af: Use separate handlers for interrupts octeontx2-pf: Send UP messages to VF only when VF is up. octeontx2-pf: Use default max_active works instead of one octeontx2-pf: Wait till detach_resources msg is complete octeontx2: Detect the mbox up or down message via register devlink: fix port new reply cmd type net/bnx2x: Prevent access to a freed page in page_pool dm-integrity: fix a memory leak when rechecking the data net: phy: fix phy_read_poll_timeout argument type in genphy_loopback ceph: stop copying to iter at EOF on sync reads nouveau/gsp: don't check devinit disable on GSP. ipv4: raw: Fix sending packets from raw sockets via IPsec tunnels hsr: Handle failures in module init rds: introduce acquire/release ordering in acquire/release_in_xmit() wireguard: receive: annotate data-race around receiving_counter.counter net: move dev->state into net_device_read_txrx group virtio: packed: fix unmap leak for indirect desc table vdpa/mlx5: Allow CVQ size changes vdpa_sim: reset must not run virtio: uapi: Drop __packed attribute in linux/virtio_pci.h drm: Fix drm_fixp2int_round() making it add 0.5 spi: spi-imx: fix off-by-one in mx51 CPU mode burst length net: dsa: mt7530: prevent possible incorrect XTAL frequency selection net: veth: do not manipulate GRO when using XDP xfrm: Allow UDP encapsulation only in offload modes packet: annotate data-races around ignore_outgoing xen/events: increment refcnt only if event channel is refcounted xen/evtchn: avoid WARN() when unbinding an event channel riscv: Fix compilation error with FAST_GUP and rv32 ASoC: SOF: amd: Skip IRAM/DRAM size modification for Steam Deck OLED ASoC: SOF: amd: Move signed_fw_image to struct acp_quirk_entry io_uring: fix poll_remove stalled req completion net: ethernet: mtk_eth_soc: fix PPE hanging issue net: mediatek: mtk_eth_soc: clear MAC_MCR_FORCE_LINK only when MAC is up drm/xe: Skip VMAs pin when requesting signal to the last XE_EXEC drm/xe: Invalidate userptr VMA on page pin fault nvme: fix reconnection fail due to reserved tag allocation spi: Fix error code checking in spi_mem_exec_op() spi: spi-mem: add statistics support to ->exec_op() calls net: txgbe: fix clk_name exceed MAX_DEV_ID limits hsr: Fix uninit-value access in hsr_get_node() vmxnet3: Fix missing reserved tailroom tcp: Fix refcnt handling in __inet_hash_connect(). io_uring: Fix release of pinned pages when __io_uaddr_map fails cpufreq: Fix per-policy boost behavior on SoCs using cpufreq_boost_set_sw() soc: fsl: dpio: fix kcalloc() argument order riscv: Only check online cpus for emulated accesses devlink: Fix devlink parallel commands processing net/sched: taprio: proper TCA_TAPRIO_TC_ENTRY_INDEX check s390/vtime: fix average steal time calculation octeontx2-af: Use matching wake_up API variant in CGX command interface rds: tcp: Fix use-after-free of net in reqsk_timer_handler(). tcp: Fix NEW_SYN_RECV handling in inet_twsk_purge() nouveau: reset the bo resource bus info after an eviction ASoC: rockchip: i2s-tdm: Fix inaccurate sampling rates spi: Restore delays for non-GPIO chip select spi: lpspi: Avoid potential use-after-free in probe() io_uring: don't save/restore iowait state thermal/drivers/qoriq: Fix getting tmu range thermal/drivers/mediatek/lvts_thermal: Fix a memory leak in an error handling path ASoC: tlv320adc3xxx: Don't strip remove function when driver is builtin x86/hyperv: Use per
[Kernel-packages] [Bug 2060004] Re: Fail to enable workqueue via accel-config under ubuntu server 24.04
** Description changed: 1. Fresh install Ubuntu server 24.04 on the thinksystem server; 2. Add boot parameter "intel_iommu=on,sm_on" and restart 3. Verify Intel Data Streaming Accelerator (DSA) functionality via accel-config command, it fail to enable workqueue: root@test:/# accel-config list [] root@test:/# accel-config config-wq dsa0/wq0.0 --group-id=0 root@test:/# accel-config config-wq dsa0/wq0.0 --priority=5 root@test:/# accel-config config-wq dsa0/wq0.0 --wq-size=8 root@test:/# accel-config config-engine dsa0/engine0.0 --group-id=0 root@test:/# accel-config config-wq dsa0/wq0.0 --type=user root@test:/# accel-config config-wq dsa0/wq0.0 --name="dsa-test" root@test:/# accel-config config-wq dsa0/wq0.0 --mode=dedicated root@test:/# accel-config enable-device dsa0 enabled 1 device(s) out of 1 - root@test:/# + root@test:/# root@test:/# accel-config enable-wq dsa0/wq0.0 failed in dsa0/wq0.0 enabled 0 wq(s) out of 1 Error[0x8020] dsa0/wq0.0: Unknown error - root@test:/# + root@test:/# After comparing the kernel source, the issue comes from - c9d01179e185f72b20af7e37aa4308f4c7ca7eeb, please fix it, thanks. + 7af1e0aceeb321cbc90fcf6fa0bec8870290377f, please fix it, thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060004 Title: Fail to enable workqueue via accel-config under ubuntu server 24.04 Status in linux package in Ubuntu: New Bug description: 1. Fresh install Ubuntu server 24.04 on the thinksystem server; 2. Add boot parameter "intel_iommu=on,sm_on" and restart 3. Verify Intel Data Streaming Accelerator (DSA) functionality via accel-config command, it fail to enable workqueue: root@test:/# accel-config list [] root@test:/# accel-config config-wq dsa0/wq0.0 --group-id=0 root@test:/# accel-config config-wq dsa0/wq0.0 --priority=5 root@test:/# accel-config config-wq dsa0/wq0.0 --wq-size=8 root@test:/# accel-config config-engine dsa0/engine0.0 --group-id=0 root@test:/# accel-config config-wq dsa0/wq0.0 --type=user root@test:/# accel-config config-wq dsa0/wq0.0 --name="dsa-test" root@test:/# accel-config config-wq dsa0/wq0.0 --mode=dedicated root@test:/# accel-config enable-device dsa0 enabled 1 device(s) out of 1 root@test:/# root@test:/# accel-config enable-wq dsa0/wq0.0 failed in dsa0/wq0.0 enabled 0 wq(s) out of 1 Error[0x8020] dsa0/wq0.0: Unknown error root@test:/# After comparing the kernel source, the issue comes from 7af1e0aceeb321cbc90fcf6fa0bec8870290377f, please fix it, thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060004/+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
