[Kernel-packages] [Bug 2044091] Re: Long resume on surprise dock unplug
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- 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/2044091 Title: Long resume on surprise dock unplug Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] In OEM-6.5 testing it was found long resume when doing surprise unplug for TBT4 dock while system is in s0i3. The resume takes 2+ minutes when this issue happens. This issue is caused by this commit which got picked up in 6.4 kernel. https://github.com/torvalds/linux/commit/e8b908146d44310473e43b3382eca126e12d279c [Fix] It has been fixed upstream by https://github.com/torvalds/linux/commit/c82458101d5490230d735caecce14c9c27b1010c Which is backported to 6.5.7 kernel. [Test case] Unplug the dock when in s0i3. [Where problems could happen] hard to think how this would break anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2044091/+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 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
** Description changed: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] + Run `iw list` should see something like below + + Frequencies: + * 5955 MHz [1] (22.0 dBm) (no IR) + * 5975 MHz [5] (22.0 dBm) (no IR) + * 5995 MHz [9] (22.0 dBm) (no IR) + * 6015 MHz [13] (22.0 dBm) (no IR) + * 6035 MHz [17] (22.0 dBm) (no IR) + * 6055 MHz [21] (22.0 dBm) (no IR) + * 6075 MHz [25] (22.0 dBm) (no IR) + * 6095 MHz [29] (22.0 dBm) (no IR) + * 6115 MHz [33] (22.0 dBm) (no IR) + * 6135 MHz [37] (22.0 dBm) (no IR) + * 6155 MHz [41] (22.0 dBm) (no IR) + * 6175 MHz [45] (22.0 dBm) (no IR) + * 6195 MHz [49] (22.0 dBm) (no IR) + * 6215 MHz [53] (22.0 dBm) (no IR) + + And `iw reg get` shows the contry code read from BIOS [Where problems could occur] ** Description changed: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] Run `iw list` should see something like below Frequencies: - * 5955 MHz [1] (22.0 dBm) (no IR) - * 5975 MHz [5] (22.0 dBm) (no IR) - * 5995 MHz [9] (22.0 dBm) (no IR) - * 6015 MHz [13] (22.0 dBm) (no IR) - * 6035 MHz [17] (22.0 dBm) (no IR) - * 6055 MHz [21] (22.0 dBm) (no IR) - * 6075 MHz [25] (22.0 dBm) (no IR) - * 6095 MHz [29] (22.0 dBm) (no IR) - * 6115 MHz [33] (22.0 dBm) (no IR) - * 6135 MHz [37] (22.0 dBm) (no IR) - * 6155 MHz [41] (22.0 dBm) (no IR) - * 6175 MHz [45] (22.0 dBm) (no IR) - * 6195 MHz [49] (22.0 dBm) (no IR) - * 6215 MHz [53] (22.0 dBm) (no IR) + * 5955 MHz [1] (22.0 dBm) (no IR) + * 5975 MHz [5] (22.0 dBm) (no IR) + * 5995 MHz [9] (22.0 dBm) (no IR) + * 6015 MHz [13] (22.0 dBm) (no IR) + * 6035 MHz [17] (22.0 dBm) (no IR) + * 6055 MHz [21] (22.0 dBm) (no IR) + * 6075 MHz [25] (22.0 dBm) (no IR) + * 6095 MHz [29] (22.0 dBm) (no IR) + * 6115 MHz [33] (22.0 dBm) (no IR) + * 6135 MHz [37] (22.0 dBm) (no IR) + * 6155 MHz [41] (22.0 dBm) (no IR) + * 6175 MHz [45] (22.0 dBm) (no IR) + * 6195 MHz [49] (22.0 dBm) (no IR) + * 6215 MHz [53] (22.0 dBm) (no IR) - And `iw reg get` shows the contry code read from BIOS + And `iw reg get` shows the contry code read from BIOS and supported + freq, too + + phy#0 (self-managed) + country TW: DFS-UNSET + (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ + (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ + (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ + [Where problems could occur] -- 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/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble:
[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
@toekneefan I know the workforce is always limited and I don't want to blame anyone. After all, I'm not paying for support. However, silent data corruption in a file system that is supposed to first and foremost prevent silent data corruption is a serious defect, and I understand that people are worried about the apparent inactivity on this bug. I'm also using ZFS on FreeBSD and there the patch was rushed out as soon as it was available. So it would be great to get some kind of indication if this is being worked on (such as triaging the bug). If we know that shipping the patch is going to take very long, then at least affected users can make an informed decision if they are just going to live with the bug or start looking for alternative solutions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
I have the same issue. Kubuntu 22.04, after sleep/screen lock my usb-c -> display port connected monitor goes from 5120x1440 down to 3840x2160. -- 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/1978980 Title: [amdgpu] Wrong external screen resolution after wake up from sleep Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04, running KDE) I started experiencing a problem with external screen resolution after the wake up from sleep. The monitor resolution is small (1280x768) and doesn't respect the setting prior the sleep (1920x1200). After the wake up from sleep: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1280x768 59.94* # a list of lower resolutions ``` There is an error when trying to change the setting to the highest resolution supported by the monitor (which is not included in the above list). ``` > xrandr --output DisplayPort-1 --mode 1920x1200 xrandr: cannot find mode 1920x1200 ``` After the turn off and turn on of the external monitor, the resolution is somehow added to the xrandr list: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95 + # a list of resolutions 1280x768 59.94* # a list of lower resolutions ``` Now it is possible to change the resolution: ``` > xrandr --output DisplayPort-1 --mode 1920x1200 # no output, the resolution was successfully changed ``` After the change, the resolution is successfully changed and xrandr gives proper output: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95*+ # a list of lower resolutions ``` The problem is not present on fresh start. However, it is consistently present after the wake up from sleep. What can cause the problem and how may I fix it? Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the external monitor is connected via USB-C. There are no problems with laptop screen resolution, only external monitor is affected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jun 16 18:12:05 2022 DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2019-08-21 (1030 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20NE000BMC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET44W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000BMC dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495: dmi.product.family: ThinkPad E495 dmi.product.name: 20NE000BMC dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
[Kernel-packages] [Bug 2045560] Re: Possible TCP memory leak
affects 6.2.0-1011-aws -> 6.2.0-1016-aws, 6.2.0-1011-azure -> 6.2.0-1016-azure kernels, did not affect 5.19 and prior kernels in 22.04.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: Possible TCP memory leak Status in linux-signed-aws-6.2 package in Ubuntu: Confirmed Bug description: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+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 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
** Description changed: [Impact] + WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] + Realtek provides a patchset to enable this feature + https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t + + The patchset has been included in linux-next/master + c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 + b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS + 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] [Where problems could occur] -- 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/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting. [Fix] Realtek provides a patchset to enable this feature https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t The patchset has been included in linux-next/master c212abfbd19f wifi: rtw89: regd: update regulatory map to R65-R44 b2774a916ab9 wifi: rtw89: regd: handle policy of 6 GHz according to BIOS 665ecff7dd14 wifi: rtw89: acpi: process 6 GHz band policy from DSM [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045622/+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 2045622] Re: RTL8852CE WIFI read country list supporting 6 GHz from BIOS
** Tags added: oem-priority originate-from-2044087 somerville -- 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/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045622/+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 2045622] [NEW] RTL8852CE WIFI read country list supporting 6 GHz from BIOS
Public bug reported: [Impact] [Fix] [Test case] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2044087 somerville ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/2045622 Title: RTL8852CE WIFI read country list supporting 6 GHz from BIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045622/+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 2038544] Re: MINT 21.2
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038544 Title: MINT 21.2 Status in linux package in Ubuntu: Expired Bug description: Kernel 5.15.06.0-86 Mint 21.2 Asus Vivobook 17 amd graphics. After login black screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038544/+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 2038528] Re: testing bot states
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038528 Title: testing bot states Status in linux package in Ubuntu: Expired Bug description: new bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038528/+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 2038531] Re: '-' has bad syntax: revision number is empty
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038531 Title: '-' has bad syntax: revision number is empty Status in linux package in Ubuntu: Expired Bug description: when install nvidia-340 this occurs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038531/+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 2038589] Re: Backport DMABUF support from Upstream to Ubuntu Jammy
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038589 Title: Backport DMABUF support from Upstream to Ubuntu Jammy Status in linux package in Ubuntu: Expired Bug description: DAMBUF is backported using the two series of patches: First, we need the series of 3 patches at: https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ - dma-buf: Fix pin callback comment - RDMA/umem: Allow pinned dmabuf umem usage - RDMA/efa: Add support for dmabuf memory regions Second, we need series of 4 patches at: https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ Note: The changes made by first patch in series "net/mlx5: Add IFC bits for mkey ATS" had already been there in Ubuntu jammy "master- next" - (Already there in jammy ) net/mlx5: Add IFC bits for mkey ATS - RDMA/core: Add UVERBS_ATTR_RAW_FD - RDMA/mlx5: Add support for dmabuf to devx umem - RDMA/mlx5: Enable ATS support for MRs and umems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038589/+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 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops
** Tags added: originate-from-2042412 -- 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/2044096 Title: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux source package in Mantic: In Progress Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops [Fix] Need to backport https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f0d9da19d7de9e845e7a93a901c4b9658df6b492 to support dual speaker configuration on Dell Oasis series [Test Case] 1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA. 2. Verify the audio functions, including playback and capture [Where problems could occur] Add CS35L41 support on specific Dell laptops. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2044096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
@mafoelffen I'm sure the developers are hard at work with this and other issues. Ubuntu LTS, I believe, does not yet have coreutils v9, so it is unlikely to be affected. This bug is actually extremely old (possibly going back almost two decades), but recent changes, such as a change to zfs_dmu_offset_next_sync and use of SEEK_HOLE in cp of coreutils increased the likelihood of this bug manifesting. According to recent comments by OpenZFS contributors, this bug actually seems unrelated to block cloning, though they are keeping it off by default to be safe (https://gist.github.com/rincebrain/e23b4a39aba3fadc04db18574d30dc73) in case there are other unknown bugs/interactions. So 2.2.1 is actually a false patch, and 2.2.2 is the real one, grounded in more evidence and investigation of the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- 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/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html which is included in v6.7-rc1 7f3e6b840fa8 drm/amd/pm: Fix error of MACO flag setting code [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] The patch make sure MACO is supported only if BACO is supported. It creates a stricter rule for MACO to avoid MACO is enabled with BACO supports. It should be safe to apply stricter rules to enable features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042912/+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 2045593] [NEW] back-out zstd module compression automatic for backports
Public bug reported: back-out zstd module compression automatic for backports we decided to have kernel modules zstd compressed in mantic+, and keep them uncompressed in jammy backports. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - back zstd module compression automatic for backports + back-out zstd module compression automatic for backports ** Description changed: - back zstd module compression automatic for backports + back-out zstd module compression automatic for backports we decided to have kernel modules zstd compressed in mantic+, and keep them uncompressed in jammy backports. -- 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/2045593 Title: back-out zstd module compression automatic for backports Status in linux package in Ubuntu: New Bug description: back-out zstd module compression automatic for backports we decided to have kernel modules zstd compressed in mantic+, and keep them uncompressed in jammy backports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045593/+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 2042546] Re: Include cifs.ko in linux-modules package
** Tags removed: verification-needed-lunar-linux-kvm ** Tags added: verification-done-lunar-linux-kvm -- 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/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
Failing build had kernel Kernel version: Linux bos03-riscv64-014 5.19.0-1021-generic #23~22.04.1-Ubuntu SMP Thu Jun 22 12:49:35 UTC 2023 riscv64 The build immediately before the first failure had kernel Kernel version: Linux riscv64-qemu-lgw01-069 5.13.0-1019-generic #21~20.04.1-Ubuntu SMP Thu Mar 24 22:36:01 UTC 2022 riscv64 So maybe this is a kernel regression? -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
November 16 was 2 days after livecd-rootfs 24.04.4 landed in the noble release pocket, superseding 24.04.2. The code delta between 24.04.2 and 24.04.4 includes removal of support for "legacy" images (SUBPROJECT=legacy) which doesn't apply here; and some reorganization of code related to "preinstalled" images which could affect the riscv64+generic image, that is a preinstalled image using the cpc project, but there were no code changes touching any of the image partitioning code so it's unclear how those code changes could have introduced this bug. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2045586] [NEW] livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
Public bug reported: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Also 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0 nodelay 0 sendpage 0 splice 0 urgent data 0 * Instead of including the payload in the wrong >512 KB buckets, the output should be to have 19 reqs in the 8 KB buckets for TX stats and 9 reqs in the 8 KB bucket for RX stats. [Where problems could occur] * The changes are in common code /net/smc/smc_stats.h hence any potential negativ impact is not limited to a specific platform. but limited to statistics for shared memory communication (SMC) hardware statistics. * But limited to the functions SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB. * The bucket (aka pos) calculation is not that trivial, issues here
[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
I wondered why my old bug report has not gotten any attention. Being a duplicate of this bug didn't help, but at least someone from the security team marked it as a duplicate of this bug. BUT... On Bug Reports filed against zfs-linux, there are 55 bugs, with not one single person assigned, that are either marked as new, or confirmed, just because there were multiple users affected... Has anyone else, besides me, wondered why they are not even getting triaged? We do our due diligence to report these issues. I do my research, testing try to find answers, and work-around's... That we "can" get past what is wrong. I keep trying to keep faith in this support system. We try to make a difference, and do things for the betterment of Ubuntu. It does not seem sometimes like we are being taken seriously, or being heard. What other choices do we have? Compile it ourselves or add it to our own PPA"s? For actively supported versions, this seems like it should just be dealt with right? Especially for LTS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045584] [NEW] Firefox/brave browser causes GPU reset
Public bug reported:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image on
the screen, kind of like static with both firefox and brave broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95 successfully
on both windows and ubuntu now for 5-6 hours as well just to stress the
system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug 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/2045584
Title:
Firefox/brave browser causes GPU reset
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon
[Kernel-packages] [Bug 2045560] Re: Possible TCP memory leak
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-aws-6.2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: Possible TCP memory leak Status in linux-signed-aws-6.2 package in Ubuntu: Confirmed Bug description: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+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 2045573] Re: AMDGPU: cp queue preemption timeout
@AMD, any idea about the above? -- 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/2045573 Title: AMDGPU: cp queue preemption timeout Status in linux package in Ubuntu: New Bug description: Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic Under load, GPU crashed resulting in a weird behavior. Screen froze, blinked a few times and the laptop suspended. After wakeup a normal login screen showed up but after logging in, it crashed to black screen with a message: " cp queue preemption timeout". Eventually I was able to log in to a clean session. Log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573/+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 2045573] Re: AMDGPU: cp queue preemption timeout
This will be fixed by this patch: https://lore.kernel.org/amd- gfx/20231201005751.4194154-1-jiadong@amd.com/ Until Canonical pulls it in for now you can use amdgpu.mcbp=0 on kernel command line to avoid it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045573 Title: AMDGPU: cp queue preemption timeout Status in linux package in Ubuntu: New Bug description: Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic Under load, GPU crashed resulting in a weird behavior. Screen froze, blinked a few times and the laptop suspended. After wakeup a normal login screen showed up but after logging in, it crashed to black screen with a message: " cp queue preemption timeout". Eventually I was able to log in to a clean session. Log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573/+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 2036675] Re: 5.15.0-85 live migration regression
I'm not sure if this has been really fixed in Jammy default kernel. I've hit specifically this issue during this week while running 5.15.0-89. Upgrading to HWE kernel or 5.19.0-50 does fix live migrations. -- 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/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption
This is my merge fo a Bug Report marked as a duplicate of this one: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969 In the OpenZFS patch thread, they had said that feature@block_cloning, because of the underlying bug, OpenZFS had said they turned that feature off by default in 2.2.1. (They actually didn't.) 2.2.1 is in Noble Proposed. Rick S. and I have been testing it (in DEV Noble) ever since I reported my Bug Report which recently has been marked as a duplicate of this Bug... (Noted above) In my tests, in version 2.2.1, that package does not turn off that feature by default. Noble (with zfsutils 2.2.1) creates the rpool with feature@block_cloning=Active, as a default. I debugged the install activity for noble during the ZFS install, and it is passing features=defaults... That is not something that was injected i the code of ubuntu-desktop-installer, so it still set as a default. Just to test that, I confirmed it. If you create a new pool by defaults, that feature gets set to enabled, unless you explicitly give it: -o feature@block_cloning=disabled My previous proposal was for 2.2.1 to get pushed out of Noble Proposed to Noble Main. But that was before we found out that was was said about 2.2.1 was wrong. Now my proposal is to build 2.2.2, move it to Noble proposed, so Rick S. and I can test and verify it... The move it to Noble Main. Those go along with backporting the patch back through Focal. Yes that feature@block_cloning uncovered the Bug, and increases the likelihood that it occurs, but... The underlying bug in the code goes back to code from 2012. Focal is still in support. Ubuntu Pro ESM is another matter, which 14.04 is still in ESM, and still has 4 months left... But is also affected by this Bug/CVE. We had also started a thread on this in the Noble Dev section: https://ubuntuforums.org/showthread.php?t=2492927=14167819 OpenZFS did release zfs-linux 2.2.2 last week. But I do not see any zfs- linux builds yet of that there. Yes we know if only happens during a cp (does nto affect rsync), but the OpenZFs patches seem to work on the ZFS end of things... This summarizes what we had there in that bug report, into this one... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045573] [NEW] AMDGPU: cp queue preemption timeout
Public bug reported: Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic Under load, GPU crashed resulting in a weird behavior. Screen froze, blinked a few times and the laptop suspended. After wakeup a normal login screen showed up but after logging in, it crashed to black screen with a message: " cp queue preemption timeout". Eventually I was able to log in to a clean session. Log attached ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "amdgpu.txt" https://bugs.launchpad.net/bugs/2045573/+attachment/5726251/+files/amdgpu.txt -- 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/2045573 Title: AMDGPU: cp queue preemption timeout Status in linux package in Ubuntu: New Bug description: Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic Under load, GPU crashed resulting in a weird behavior. Screen froze, blinked a few times and the laptop suspended. After wakeup a normal login screen showed up but after logging in, it crashed to black screen with a message: " cp queue preemption timeout". Eventually I was able to log in to a clean session. Log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573/+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 2007286] Re: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed
Same here...none of these commands remove the old /lib/modules/ kernel dirs: sudo apt-get clean sudo apt-get autoclean sudo apt-get autoremove sudo apt-get purge -- 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/2007286 Title: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed Status in linux package in Ubuntu: Expired Bug description: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007286/+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 2034479] Re: Fix suspend hang on Lenovo workstation
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1 and merged by stable update in oem-6.1, SRU for Jammy and Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2035116] Re: allow io_uring to be disabled in runtime
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) Actually also tried setting kernel.io_uring_disabled=2 and checking that neither (privileged or unprivileged worked). Then testing setting it back to 0. Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and that it worked for group 1000, then set it to 1001 and verified that it didn't work anymore for group 1000. [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+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 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+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 2035163] Re: Avoid address overwrite in kernel_connect
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux-gkeop package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Status in linux-gkeop source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035163/+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 2036450] Re: Azure: Update CIFS to v6.5
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036450 Title: Azure: Update CIFS to v6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested this patch set to update CIFS and smbfs to the Linux kernel version 6.5. [Test Plan] Microsoft has tested with positive results. [Regression Potential] This is a huge patch set. The potential exists for corruption, connection instabilities, or other cifs related maladies. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036450/+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 2035123] Re: scripts/pahole-flags.sh change return to exit 0
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-azure-fips-v2
verification-needed-jammy-linux-azure-fips
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2035123
Title:
scripts/pahole-flags.sh change return to exit 0
Status in linux package in Ubuntu:
Fix Released
Status in linux-bluefield package in Ubuntu:
Triaged
Status in linux source package in Jammy:
Fix Committed
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2035123
[Impact]
When building the Jammy linux-bluefield kernel tree on a system
without pahole installed, the following warning is emitted:
./scripts/pahole-flags.sh: line 7: return: can only `return' from a
function or sourced script
scripts/pahole-flags.sh attempts to return from an if statement that
is not within a function, and generates a warning.
The fix is straightforward, changing return to an exit 0.
--- a/scripts/pahole-flags.sh
+++ b/scripts/pahole-flags.sh
@@ -4,7 +4,7 @@
extra_paholeopt=
if ! [ -x "$(command -v ${PAHOLE})" ]; then
- return
+ exit 0
fi
[Testcase]
Clone the linux-bluefield kernel tree and build it on a arm64 system without
pahole installed.
A test kernel is available with the fix applied in:
https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test
Both linux-bluefield and ubuntu-jammy build correctly.
[Fix]
This was fixed by Linus Torvalds in the following merge commit:
commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Merge: bfc484fe6abb 84882cf72cd7
Author: Linus Torvalds
Date: Tue Nov 2 06:20:58 2021 -0700
Subject: Merge tag 'net-next-for-5.16' of
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Note, the original commit does not have the fix included:
commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
Author: Jiri Olsa
Date: Fri Oct 29 14:57:29 2021 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8
The Ubuntu kernel cherry-picked the original commit and did not pick up the
silent fix made in the merge commit. Submitting the silent fix as a SAUCE
patch
with changelog describing the change.
Note: I know SAUCE patches are bad, but in this scenario, to revert
the initial commit and re-apply the fixed version would require us to
revert two additional dependency commits, making six patches to
review, vs, a one line change in a SAUCE commit that has a real
changelog entry.
[Where problems could occur]
The Ubuntu kernel is built with pahole enabled, and requires pahole to
be installed as a build dependency. It is extremely unlikely that any
users are disabling pahole at build time, apart from linux-bluefield
engineers.
If a regression were to occur, engineers would see errors during build
time about scripts/pahole-flags.sh not executing properly.
[Other info]
Linus remarked about the issue in the following lkml discussion:
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/
This was silently Incorporated into the linux-stable commit:
commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
From: Jiri Olsa
Date: Sun, 4 Sep 2022 15:19:00 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035123/+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 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2037513 Title: HP ProBook 450 G8 Notebook fail to wifi test Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-signed-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Bug description: I'm reviewing the SRU test result on this machine. I found that this machine always fails to wifi test and also pop out a lot of error message in dmesg. It's not a regression, since according to previous test run it has failed already. Just because we missed reviewing it for a while. The journal log is attach, please check further hardware informations at https://certification.canonical.com/hardware/202106-29176/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 27 15:47:37 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00 InstallationDate: Installed on 2023-09-25 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220621-04:14 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037513/+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 2035166] Re: NULL Pointer Dereference During KVM MMU Page Invalidation
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- 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/2035166 Title: NULL Pointer Dereference During KVM MMU Page Invalidation Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the cause. It's
[Kernel-packages] [Bug 2037403] Re: PCI BARs larger than 128GB are disabled
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2037403 Title: PCI BARs larger than 128GB are disabled Status in linux package in Ubuntu: Incomplete Status in linux-bluefield package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in linux-bluefield source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] Current linux-bluefield kernel reports that PCI BARs larger than 128GB are disabled. Increase the maximum PCI BAR size from 128GB to 8TB for future expansion. [Test Plan] Use updated kernel with PCI device with PCI BARs larger than 128GB. [Where problems could occur] No potential problems are expected. [Other Info] Testing has been provided by the customer. This patch is a cherry-pick from the upstream 5.18 kernel. It is intended for linux-bluefield kernel re-spin but it may be also suitable for the generic kernel (separate submission). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037403/+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 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+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 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras
[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2040300] Re: Azure: Improve SQL DB latency
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2040300 Title: Azure: Improve SQL DB latency Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] TCP pingpong threshold is 1 by default. But some applications, like SQL DB may prefer a higher pingpong threshold to activate delayed acks in quick ack mode for better performance. There is no single value that fits all applications. Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for optimal performance based on the application needs. [Test Case] Microsoft tested [Regression Potential] Should be zero since default behavior is unchanged. [Other Info] SF: #00357415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2040300/+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 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-done-jammy-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-azure-fips' to
'verification-failed-jammy-linux-azure-fips'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-azure-fips-v2
verification-needed-jammy-linux-azure-fips
--
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/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal
This bug is awaiting verification that the linux-azure- fips/5.15.0-1053.61+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar, jammy and focal Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware
[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
I have tried this (patches suggested in comment #40) and the problem seems to have gone away. It may be too soon to say but my test scenario (which never gave me a false negative before) finished without issues. Of course this is not a 'fix', so I'm curious to see what the OP has to say about this result. -- 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/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out Status in linux package in Ubuntu: Confirmed Bug description: I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu Jammy. Details: - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results. - using a bond over the two ports of the same card, at 25Gbps to two different switches, bond is using LACP with hash layer3+4 and fast timeout. But I believe the bug is not directly related to bonding as the problem seems to be in the interface. - machine installed by maas. No issues during installation, but at that time bond is not formed yet, later when linux is booted, the bond is formed and works without issues for a while - it works for about 2 to 3 hours fine, then the issue starts (may or may not be related to network load, but it seems that it is triggered by some tests that I run after openstack finishes installing) - one of the legs of the bond freezes and everything that would go to that lag is discarded, in and out, ping to random external hosts start losing every second packet - after some time you can see on the kernel log messages about "NETDEV WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack trace - the switch does log that the bond is flapping --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 12 20:05 seq crw-rw 1 root audio 116, 33 Sep 12 20:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7515 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116 RelatedPackageVersions: linux-restricted-modules-5.15.0-83-generic N/A linux-backports-modules-5.15.0-83-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-83-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/27/2023 dmi.bios.release: 2.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.4 dmi.board.name: 0J91V2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.4:bd07/27/2023:br2.12:svnDellInc.:pnPowerEdgeR7515:pvr:rvnDellInc.:rn0J91V2:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FD;ModelName=PowerEdgeR7515: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7515 dmi.product.sku: SKU=08FD;ModelName=PowerEdge R7515 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 03:13 seq crw-rw 1 root audio 116, 33 Sep 15 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Cannot stat file /proc/215602/fd/10: Permission denied Cannot stat file /proc/323635/fd/10: Permission denied CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.3.4.7:5248/MAAS/metadata/) DistroRelease: Ubuntu 22.04
[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
I don't believe so, I'm on one of the affected laptops on
6.2.0-37-generic / 23.04 with no issues. It's 23.10's kernel 6.5 that
triggers the issue for me. The bug is also about 23.10, which wouldn't
have kernel 6.2 anyway.
--
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/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files
** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045562 Title: [Debian] autoreconstruct - Do not generate chmod -x for deleted files Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: SRU Justification: [Impact] Debian source format 1.0 cannot remove files, create symlinks and change permission in the .diff.gz tarball. Therefore any changes in these 3 categories cannot be represented without any tricks. To solve this, the `reconstruct` script is used every time we build the source package. The script is generated by `gen-auto-reconstruct` script during `cranky close`. It checks if there has been any changes in the 3 categories mentioned above between the upstream version (i.e v6.5) and the current one. The problem with the script is that in case a file A was removed since the upstream version was released, the `reconstruct` script will contains these commands in this exact order: rm -f A chmod -x A The second command will fail because file A does not exist anymore. This is solved by generating the `chmod +/-x` commands before `rm`. Which results in: chmod -x A rm -f A But because the reconstruct script is used during `clean` rule which is triggered pretty much during every cranky step which is run in the source repo, the first command will always file because file A is not present anymore in the tree. To solved this, any `chmod` change is added only if the file has not been deleted. Therefore if file A has been deleted, the `reconstruct` script will contain only this: rm -f A [Fix] Generate chmod commands first. And when generating chmod -x command, first check if the file has been deleted. If yes, no need for a chmod command. [Test Plan] It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and it reconstruct script looked correct. [Other Info] An example of this is #lp2038611 where `script/is_rust_module.sh` was removed, but we keep seeing "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory" because `rm -f` and `chmod -x` command were generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562/+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 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
@copong
> I'm not sure why kernel 6.2 keeps getting suggested by the ubuntu bot, it's
> never been affected by this bug, at least not on any kernel packaged for
> ubuntu 23.04.
Maybe the bug had been backported?
--
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/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-riscv' to 'verification-done-lunar- linux-riscv'. If the problem still exists, change the tag 'verification- needed-lunar-linux-riscv' to 'verification-failed-lunar-linux-riscv'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-riscv-v2 verification-needed-lunar-linux-riscv -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-riscv' to 'verification-done-lunar- linux-riscv'. If the problem still exists, change the tag 'verification- needed-lunar-linux-riscv' to 'verification-failed-lunar-linux-riscv'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-riscv-v2 verification-needed-lunar-linux-riscv -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2039542] Re: Remove duplication of devm_pwmchip_add function definition
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-riscv' to 'verification-done-lunar- linux-riscv'. If the problem still exists, change the tag 'verification- needed-lunar-linux-riscv' to 'verification-failed-lunar-linux-riscv'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-riscv-v2 verification-needed-lunar-linux-riscv -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+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 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-riscv' to 'verification-done-lunar- linux-riscv'. If the problem still exists, change the tag 'verification- needed-lunar-linux-riscv' to 'verification-failed-lunar-linux-riscv'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-riscv-v2 verification-needed-lunar-linux-riscv -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0
[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If the problem still exists, change the tag 'verification-
needed-lunar-linux-riscv' to 'verification-failed-lunar-linux-riscv'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-lunar-linux-riscv-v2
verification-needed-lunar-linux-riscv
--
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/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-riscv' to 'verification-done-lunar- linux-riscv'. If the problem still exists, change the tag 'verification- needed-lunar-linux-riscv' to 'verification-failed-lunar-linux-riscv'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-riscv-v2 verification-needed-lunar-linux-riscv -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar, jammy and focal Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware
[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- 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/2041495 Title: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2041495 [Impact] NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: ``` kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 ``` [Fix] Proposed fix in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5=6cc834ba62998c65c42d0c63499bdd35067151ec "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well as stable kernels v6.1.55 and v6.5.5. [Test Case] Apply to kernel and boot with the nvme module installed. Now the device should be probed with success. ``` kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0 kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer. kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues kernel: [2.136735] nvme0n1: p1 p2 p3 ``` [Where problems could occur] This patch tries to set an appropriate CRTO (Controller Ready Timeouts) that may be reported incorrectly by some devices. There should be little (a bit longer CRTO) to no effect on devices performing normally before hands. [Other Info] While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1 will be nominated. == original bug report == NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2041495/+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 2042697] Re: Pull request to address thermal core issues
** Changed in: linux-nvidia-6.2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2042697 Title: Pull request to address thermal core issues Status in linux-nvidia-6.2 package in Ubuntu: Fix Released Bug description: The Grace development team has not been testing the 6.2 Ubuntu kernel but instead a newer kernel. When they run their thermal tests on a 6.2 kernel they are running into failures. Investigations have turned up several missing kernel patches. These patches are clean cherry-picks and have been tested and confirmed to fix the thermal issues we are seeing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2042697/+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 2045382] Re: AMD Lexa PRO graphic card can't work
That was already CC to stable, so I suggest checking the latest 5.15.y. If that's still not working, you probably need https://github.com/torvalds/linux/commit/2757a848cb0f184850d3e0a33b4a69e8014fdc5d backported too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2045382 Title: AMD Lexa PRO graphic card can't work Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: [Summary] When I racked the one dell device, and do the trail run, I found that the checkbox process is stuck when it got the graphic information. I want to debug with the monitor, plug the DP cable to AMD card. After doing the power cycle, it entered to the BIOS, observe through the screen that the kernel has been started, but it immediately turned into a black screen. Fortunately, it can ssh-able, it can work normally by using the onboard graphic card. After checking, AMD graphic card is broken after upgrading to 5.15.0-89-generic, it still have same issue in "5.15.0-91-generic" kernel version, but everything is good in the "5.15.0-88-generic" kernel version. [Information] Problematic DUT CID: 202101-28622 Platform name: Caribou Launchpad Tag: fossa-cubone-rkl Project name: Optiplex 5090 Used GM image: dell-bto-focal-fossa-release-X120-20210625-7_fossa-cubone-rkl_A02.iso GPU: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 1 14:39:55 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-release+X120 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2045382/+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 2045382] Re: AMD Lexa PRO graphic card can't work
It's probably a duplicate of the same patches missing for bug 2036742. https://github.com/torvalds/linux/commit/64ffd2f1d00c6235dabe9704bbb0d9ce3e28147f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2045382 Title: AMD Lexa PRO graphic card can't work Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: [Summary] When I racked the one dell device, and do the trail run, I found that the checkbox process is stuck when it got the graphic information. I want to debug with the monitor, plug the DP cable to AMD card. After doing the power cycle, it entered to the BIOS, observe through the screen that the kernel has been started, but it immediately turned into a black screen. Fortunately, it can ssh-able, it can work normally by using the onboard graphic card. After checking, AMD graphic card is broken after upgrading to 5.15.0-89-generic, it still have same issue in "5.15.0-91-generic" kernel version, but everything is good in the "5.15.0-88-generic" kernel version. [Information] Problematic DUT CID: 202101-28622 Platform name: Caribou Launchpad Tag: fossa-cubone-rkl Project name: Optiplex 5090 Used GM image: dell-bto-focal-fossa-release-X120-20210625-7_fossa-cubone-rkl_A02.iso GPU: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 1 14:39:55 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-release+X120 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2045382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-6.2/6.2.0.39.40~22.04.16)
All autopkgtests for the newly accepted linux-meta-hwe-6.2 (6.2.0.39.40~22.04.16) for jammy have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/9858-0ubuntu3.4 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-hwe-6.2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files
** Description changed: + SRU Justification: + + [Impact] + Debian source format 1.0 cannot remove files, create symlinks and change permission in the .diff.gz tarball. Therefore any changes in these 3 categories cannot be represented without any tricks. To solve this, the `reconstruct` script is used every time we build the source package. The script is generated by `gen-auto-reconstruct` script during `cranky close`. It checks if there has been any changes in the 3 categories mentioned above between the upstream version (i.e v6.5) and the current one. The problem with the script is that in case a file A was removed since the upstream version was released, the `reconstruct` script will contains these commands in this exact order: rm -f A chmod -x A The second command will fail because file A does not exist anymore. This is solved by generating the `chmod +/-x` commands before `rm`. Which results in: chmod -x A rm -f A But because the reconstruct script is used during `clean` rule which is triggered pretty much during every cranky step which is run in the source repo, the first command will always file because file A is not present anymore in the tree. To solved this, any `chmod` change is added only if the file has not been deleted. Therefore if file A has been deleted, the `reconstruct` script will contain only this: rm -f A - Note: an example of this is #lp2038611 where `script/is_rust_module.sh` was removed, but we keep seeing + [Fix] + Generate chmod commands first. + And when generating chmod -x command, first check if the file has been deleted. If yes, no need for a chmod command. + + [Test Plan] + It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and it reconstruct script looked correct. + + [Other Info] + An example of this is #lp2038611 where `script/is_rust_module.sh` was removed, but we keep seeing "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory" because `rm -f` and `chmod -x` command were generated. -- 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/2045562 Title: [Debian] autoreconstruct - Do not generate chmod -x for deleted files Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: SRU Justification: [Impact] Debian source format 1.0 cannot remove files, create symlinks and change permission in the .diff.gz tarball. Therefore any changes in these 3 categories cannot be represented without any tricks. To solve this, the `reconstruct` script is used every time we build the source package. The script is generated by `gen-auto-reconstruct` script during `cranky close`. It checks if there has been any changes in the 3 categories mentioned above between the upstream version (i.e v6.5) and the current one. The problem with the script is that in case a file A was removed since the upstream version was released, the `reconstruct` script will contains these commands in this exact order: rm -f A chmod -x A The second command will fail because file A does not exist anymore. This is solved by generating the `chmod +/-x` commands before `rm`. Which results in: chmod -x A rm -f A But because the reconstruct script is used during `clean` rule which is triggered pretty much during every cranky step which is run in the source repo, the first command will always file because file A is not present anymore in the tree. To solved this, any `chmod` change is added only if the file has not been deleted. Therefore if file A has been deleted, the `reconstruct` script will contain only this: rm -f A [Fix] Generate chmod commands first. And when generating chmod -x command, first check if the file has been deleted. If yes, no need for a chmod command. [Test Plan] It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and it reconstruct script looked correct. [Other Info] An example of this is #lp2038611 where `script/is_rust_module.sh` was removed, but we keep seeing "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory" because `rm -f` and `chmod -x` command were generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562/+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 2042546] Re: Include cifs.ko in linux-modules package
** Tags removed: verification-needed-lunar-linux-aws verification-needed-lunar-linux-azure ** Tags added: verification-done-lunar-linux-aws verification-done-lunar-linux-azure -- 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/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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 2042850] Re: Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC
** Tags removed: verification-done-mantic ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042850 Title: Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2042423 Subject: [mantic:linux] drm/ast: Add BMC virtual connector SRU Justification: [Impact] On systems with Aspeed 2600 revision 52 GPUs, the display fails to progress to the login prompt. With the commit (added in 6.5.0-6.6) commit: 916ae609a033cbb55661905d310ba2358b7621ea Author: Jocelyn Falempe Date:Thu Jul 13 15:41:31 2023 +0200 Subject: drm/ast: report connection status on Display Port. the Aspeed 2600 rev 52 GPUs have issues. They need the commit: This change was dependant on the upstream change commit e329cb53b45da475966c4b2e49f6a4a430f307fa Author: Jocelyn Falempe Date: Thu Jul 13 15:41:30 2023 +0200 Subject: drm/ast: Add BMC virtual connector https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e329cb53b45da475966c4b2e49f6a4a430f307fa in order to have the display work correctly on the rev52 GPUs. [Fix] With cherry-picking this change, the functionality of BMCs using Aspeed 2600 rev52 GPUs work as expected, as they did prior to the regression in 6.5.0-6.6. [Test Plan] I have tested this on multiple versions of Aspeed 2600 GPU enabled BMCs, and the revision 52 systems that required the nomodeset option to boot to the prompt, now boot fine and display the login prompt, and there is no regression on the other systems. I have tested this on different Aspeed GPUs, and have not seen any regressions, or unexpected behaviour. [Where problems could occur] As this fixes a regression of functionality for the mantic kernel's Aspeed GPU driver on a very specific version of some BMCs to the state it was was in the mantic 6.5.0-5.5 kernel, I think there is little room for regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042850/+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 2045562] [NEW] [Debian] autoreconstruct - Do not generate chmod -x for deleted files
Public bug reported: Debian source format 1.0 cannot remove files, create symlinks and change permission in the .diff.gz tarball. Therefore any changes in these 3 categories cannot be represented without any tricks. To solve this, the `reconstruct` script is used every time we build the source package. The script is generated by `gen-auto-reconstruct` script during `cranky close`. It checks if there has been any changes in the 3 categories mentioned above between the upstream version (i.e v6.5) and the current one. The problem with the script is that in case a file A was removed since the upstream version was released, the `reconstruct` script will contains these commands in this exact order: rm -f A chmod -x A The second command will fail because file A does not exist anymore. This is solved by generating the `chmod +/-x` commands before `rm`. Which results in: chmod -x A rm -f A But because the reconstruct script is used during `clean` rule which is triggered pretty much during every cranky step which is run in the source repo, the first command will always file because file A is not present anymore in the tree. To solved this, any `chmod` change is added only if the file has not been deleted. Therefore if file A has been deleted, the `reconstruct` script will contain only this: rm -f A Note: an example of this is #lp2038611 where `script/is_rust_module.sh` was removed, but we keep seeing "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory" because `rm -f` and `chmod -x` command were generated. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Roxana Nicolescu (roxanan) Status: New ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Roxana Nicolescu (roxanan) Status: New ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Roxana Nicolescu (roxanan) Status: New ** Affects: linux (Ubuntu Lunar) Importance: Medium Assignee: Roxana Nicolescu (roxanan) Status: New ** Affects: linux (Ubuntu Mantic) Importance: Medium Assignee: Roxana Nicolescu (roxanan) Status: New ** Affects: linux (Ubuntu Noble) Importance: Medium Assignee: Roxana Nicolescu (roxanan) Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Description changed: - Debian source format 1.0 cannot remove files, create symlinks and change permission in the .diff.gz tarball. Therefore any changes in these 3 categories cannot be represented without any tricks. To solve this, the `reconstruct` script is used every time we build the source package. The script is generated by `gen-auto-reconstruct` script during `cranky close`. It checks if there has been any changes in the 3 categories mentioned above between the upstream version (i.e v6.5) and the current one. The problem with the script is that in case a file A was removed since the upstream version was released, the `reconstruct` script will contains these commands in this exact order: - rm -f A - chmod -x A + rm -f A + chmod -x A The second command will fail because file A does not exist anymore. This is solved by generating the `chmod +/-x` commands before `rm`. Which results in: - chmod -x A - rm -f A + chmod -x A + rm -f A But because the reconstruct script is used during `clean` rule which is triggered pretty much during every cranky step which is run in the source repo, the first command will always file because file A is not present anymore in the tree. To solved this, any `chmod` change is added only if the file has not been deleted. Therefore if file A has been deleted, the `reconstruct` script will contain only this: - rm -f A + rm -f A - Note: an example of this is #lp + Note: an example of this is #lp2038611 where `script/is_rust_module.sh` was removed, but we keep seeing + "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory" + because `rm -f` and `chmod -x` command were generated. ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Roxana Nicolescu (roxanan) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Roxana Nicolescu (roxanan) ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Roxana Nicolescu (roxanan) ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Roxana Nicolescu (roxanan) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Roxana Nicolescu (roxanan) **
[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
I'm not sure why kernel 6.2 keeps getting suggested by the ubuntu bot,
it's never been affected by this bug, at least not on any kernel
packaged for ubuntu 23.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2038611] Re: drop all references to is_rust_module.sh in kernels >= 6.5
@arighi I created another bug for this because it is a general issue, not only
for this `is_rust_module.sh` script.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562
The command `rm -f` should stay because in v6.5 the script is still there, and
in debian 1.0 we don't properly represent removed files in .diff.gz tarball.
The problem is with the `chmod -x` command.
First, chmod commands should be generated in the reconstruct script before any
rm command.
And second, if a file has been deleted, rm -f is more than enough, no need for
chmod command.
--
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/2038611
Title:
drop all references to is_rust_module.sh in kernels >= 6.5
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Mantic:
Fix Committed
Bug description:
[Impact]
The script tools/is_rust_module.sh has been dropped by this commit:
079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
is_rust_module.sh")
And upstream as well (in 6.6):
41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")
But we still have a reference of it in debian.master/reconstruct and
that generates the following warning during the build:
chmod: cannot access 'scripts/is_rust_module.sh': No such file or
directory
[Fix]
Drop the reference to is_rust_module.sh from reconstruct to prevent
unnecessary warnings during the build.
[Test case]
The following command ran from the kernel source directory is enough
to trigger the warning:
$ fakeroot debian/rules clean
[Regression potential]
This change is affecting only our packaging. The change is trivial but
it might affect our kernel build process in case of regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038611/+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 2007286] Re: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed
AFAIU by default it's unattended-upgrades that takes care of removing old kernel (and kernel module packages). Apparently it doesn't pass --purge when it removes the old kernel packages. Should it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007286 Title: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed Status in linux package in Ubuntu: Expired Bug description: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007286/+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 2045561] [NEW] linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support
Public bug reported: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2045561 Title: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Jammy: New Status in linux-kvm source package in Mantic: New Status in linux-kvm source package in Noble: New Bug description: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2045561/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-gcp' to 'verification-done-lunar- linux-gcp'. If the problem still exists, change the tag 'verification- needed-lunar-linux-gcp' to 'verification-failed-lunar-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-gcp-v2 verification-needed-lunar-linux-gcp -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2045560] [NEW] Possible TCP memory leak
Public bug reported: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-aws-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 ec2-images jammy kernel-net ** Attachment added: "Screenshot 2023-12-04 at 14.27.09.png" https://bugs.launchpad.net/bugs/2045560/+attachment/5726215/+files/Screenshot%202023-12-04%20at%2014.27.09.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: Possible TCP memory leak Status in linux-signed-aws-6.2 package in Ubuntu: New Bug description: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions --
[Kernel-packages] [Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-aws/6.2.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-aws' to 'verification-done-lunar- linux-aws'. If the problem still exists, change the tag 'verification- needed-lunar-linux-aws' to 'verification-failed-lunar-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-aws-v2 verification-needed-lunar-linux-aws -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-lowlatency- hwe-6.2/6.2.0-1018.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.2' to 'verification-done-jammy-linux-lowlatency- hwe-6.2'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.2' to 'verification-failed-jammy- linux-lowlatency-hwe-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.2-v2 verification-needed-jammy-linux-lowlatency-hwe-6.2 -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux- hwe-6.2/6.2.0-39.40~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.2' to 'verification-done-jammy-linux-hwe-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.2' to 'verification-failed-jammy-linux-hwe-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.2-v2 verification-needed-jammy-linux-hwe-6.2 -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-azure/6.2.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar- linux-azure'. If the problem still exists, change the tag 'verification- needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-kvm' to 'verification-done-lunar- linux-kvm'. If the problem still exists, change the tag 'verification- needed-lunar-linux-kvm' to 'verification-failed-lunar-linux-kvm'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-kvm-v2 verification-needed-lunar-linux-kvm -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux- hwe-6.2/6.2.0-39.40~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.2' to 'verification-done-jammy-linux-hwe-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.2' to 'verification-failed-jammy-linux-hwe-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.2-v2 verification-needed-jammy-linux-hwe-6.2 -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-gcp' to 'verification-done-lunar- linux-gcp'. If the problem still exists, change the tag 'verification- needed-lunar-linux-gcp' to 'verification-failed-lunar-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-gcp-v2 verification-needed-lunar-linux-gcp -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-gcp' to 'verification-done-lunar- linux-gcp'. If the problem still exists, change the tag 'verification- needed-lunar-linux-gcp' to 'verification-failed-lunar-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-azure/6.2.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar- linux-azure'. If the problem still exists, change the tag 'verification- needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039542] Re: Remove duplication of devm_pwmchip_add function definition
This bug is awaiting verification that the linux- hwe-6.2/6.2.0-39.40~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.2' to 'verification-done-jammy-linux-hwe-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.2' to 'verification-failed-jammy-linux-hwe-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.2-v2 verification-needed-jammy-linux-hwe-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-aws/6.2.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-aws' to 'verification-done-lunar- linux-aws'. If the problem still exists, change the tag 'verification- needed-lunar-linux-aws' to 'verification-failed-lunar-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-aws-v2 verification-needed-lunar-linux-aws -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux- hwe-6.2/6.2.0-39.40~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.2' to 'verification-done-jammy-linux-hwe-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.2' to 'verification-failed-jammy-linux-hwe-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-hwe-6.2-v2 verification-needed-jammy-linux-hwe-6.2 -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0
[Kernel-packages] [Bug 2039542] Re: Remove duplication of devm_pwmchip_add function definition
This bug is awaiting verification that the linux-aws/6.2.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-aws' to 'verification-done-lunar- linux-aws'. If the problem still exists, change the tag 'verification- needed-lunar-linux-aws' to 'verification-failed-lunar-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-aws-v2 verification-needed-lunar-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-kvm' to 'verification-done-lunar- linux-kvm'. If the problem still exists, change the tag 'verification- needed-lunar-linux-kvm' to 'verification-failed-lunar-linux-kvm'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-kvm-v2 verification-needed-lunar-linux-kvm -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-lowlatency- hwe-6.2/6.2.0-1018.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.2' to 'verification-done-jammy-linux-lowlatency- hwe-6.2'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.2' to 'verification-failed-jammy- linux-lowlatency-hwe-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.2-v2 verification-needed-jammy-linux-lowlatency-hwe-6.2 -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039542] Re: Remove duplication of devm_pwmchip_add function definition
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-gcp' to 'verification-done-lunar- linux-gcp'. If the problem still exists, change the tag 'verification- needed-lunar-linux-gcp' to 'verification-failed-lunar-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-gcp-v2 verification-needed-lunar-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+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 2039542] Re: Remove duplication of devm_pwmchip_add function definition
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-starfive-v2 verification-needed-lunar-linux-starfive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+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 2039542] Re: Remove duplication of devm_pwmchip_add function definition
This bug is awaiting verification that the linux-azure/6.2.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar- linux-azure'. If the problem still exists, change the tag 'verification- needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+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 2039542] Re: Remove duplication of devm_pwmchip_add function definition
This bug is awaiting verification that the linux-lowlatency- hwe-6.2/6.2.0-1018.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.2' to 'verification-done-jammy-linux-lowlatency- hwe-6.2'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.2' to 'verification-failed-jammy- linux-lowlatency-hwe-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.2-v2 verification-needed-jammy-linux-lowlatency-hwe-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+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 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-done- lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed- lunar-linux-starfive'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-starfive-v2 verification-needed-lunar-linux-starfive -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls
[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-aws/6.2.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-aws' to 'verification-done-lunar- linux-aws'. If the problem still exists, change the tag 'verification- needed-lunar-linux-aws' to 'verification-failed-lunar-linux-aws'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-aws-v2 verification-needed-lunar-linux-aws -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0 nodelay
[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-azure/6.2.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar- linux-azure'. If the problem still exists, change the tag 'verification- needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0
[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-gcp' to 'verification-done-lunar- linux-gcp'. If the problem still exists, change the tag 'verification- needed-lunar-linux-gcp' to 'verification-failed-lunar-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-gcp-v2 verification-needed-lunar-linux-gcp -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0 nodelay
[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-kvm' to 'verification-done-lunar- linux-kvm'. If the problem still exists, change the tag 'verification- needed-lunar-linux-kvm' to 'verification-failed-lunar-linux-kvm'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-kvm-v2 verification-needed-lunar-linux-kvm -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0 nodelay
[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
hwe-6.2' to 'verification-done-jammy-linux-hwe-6.2'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-hwe-6.2'
to 'verification-failed-jammy-linux-hwe-6.2'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-hwe-6.2-v2
verification-needed-jammy-linux-hwe-6.2
--
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/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-lowlatency- hwe-6.2/6.2.0-1018.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.2' to 'verification-done-jammy-linux-lowlatency- hwe-6.2'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.2' to 'verification-failed-jammy- linux-lowlatency-hwe-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-6.2-v2 verification-needed-jammy-linux-lowlatency-hwe-6.2 -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2
[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar-linux-starfive' to 'verification-done-
lunar-linux-starfive'. If the problem still exists, change the tag
'verification-needed-lunar-linux-starfive' to 'verification-failed-
lunar-linux-starfive'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-lunar-linux-starfive-v2
verification-needed-lunar-linux-starfive
--
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/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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
