[Kernel-packages] [Bug 2052763] Re: i cant able to use dual screen in i7 13th gen of hp pro tower
Your "13th Gen Intel(R) Core(TM) i7-13700" is too new for such an old Linux kernel to support the graphics outputs correctly. Please install a newer Ubuntu release such as 22.04.3: https://ubuntu.com/download/desktop ** Package changed: xorg (Ubuntu) => linux-hwe-5.15 (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Also affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2052763 Title: i cant able to use dual screen in i7 13th gen of hp pro tower Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: Fix Released Bug description: whenever I plugged dual screen in ubuntu it will consider DP port primary and whenever i remove the port it will show blank screen. I can't able to use dual screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 10:07:56 2024 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8ac7] InstallationDate: Installed on 2024-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) MachineType: HP HP Pro Tower 400 G9 PCI Desktop PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=c5c60b84-e143-44b9-adac-06e7cfc11a40 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2023 dmi.bios.release: 11.0 dmi.bios.vendor: HP dmi.bios.version: U03 Ver. 02.11.00 dmi.board.name: 8AC7 dmi.board.vendor: HP dmi.board.version: KBC Version 12.03.05 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 18.3 dmi.modalias: dmi:bvnHP:bvrU03Ver.02.11.00:bd07/25/2023:br11.0:efr18.3:svnHP:pnHPProTower400G9PCIDesktopPC:pvr:rvnHP:rn8AC7:rvrKBCVersion12.03.05:cvnHP:ct3:cvr:sku7E953AV: dmi.product.family: 103C_53307F HP ProDesk dmi.product.name: HP Pro Tower 400 G9 PCI Desktop PC dmi.product.sku: 7E953AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052763/+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 2052763] [NEW] i cant able to use dual screen in i7 13th gen of hp pro tower
You have been subscribed to a public bug: whenever I plugged dual screen in ubuntu it will consider DP port primary and whenever i remove the port it will show blank screen. I can't able to use dual screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 10:07:56 2024 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8ac7] InstallationDate: Installed on 2024-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) MachineType: HP HP Pro Tower 400 G9 PCI Desktop PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=c5c60b84-e143-44b9-adac-06e7cfc11a40 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2023 dmi.bios.release: 11.0 dmi.bios.vendor: HP dmi.bios.version: U03 Ver. 02.11.00 dmi.board.name: 8AC7 dmi.board.vendor: HP dmi.board.version: KBC Version 12.03.05 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 18.3 dmi.modalias: dmi:bvnHP:bvrU03Ver.02.11.00:bd07/25/2023:br11.0:efr18.3:svnHP:pnHPProTower400G9PCIDesktopPC:pvr:rvnHP:rn8AC7:rvrKBCVersion12.03.05:cvnHP:ct3:cvr:sku7E953AV: dmi.product.family: 103C_53307F HP ProDesk dmi.product.name: HP Pro Tower 400 G9 PCI Desktop PC dmi.product.sku: 7E953AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- i cant able to use dual screen in i7 13th gen of hp pro tower https://bugs.launchpad.net/bugs/2052763 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. -- 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 2045385] Re: Add ODM driver rtc-pcf85263
@Luca In your case, since you're using the generic kernel, you can ignore the messages for the others. -- 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/2045385 Title: Add ODM driver rtc-pcf85263 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:43:41 +0100 Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385 [ Impact ] rtc-pcf85263 driver needed for ODM partner [ Test Plan ] Load the driver setting the timestamp level to 0 (default to 1) : modprobe rtc-pcf85263 tsl=0 export the rtc device: echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device RTC device should act as a standard RTC, hwclock -r -f /dev/rtc1 #for reading hwclock -w -f /dev/rtc1 #for writing This driver has anti-tampering function. Get the current tamper timestamp: cat /sys/class/rtc/rtc1/device/timestamp1 unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the anti-tampering goes in open state. The timestamp should be updated to the current time. [ Where problems could occur ] Events could occur on the I2C bus communication. [ Other Info ] X-HWE-Bug: Bug #2046985 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2045386] Re: Add ODM driver gpio-m058ssan
@Luca In your case, since you're using the generic kernel, you can ignore the messages for the others. -- 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/2045386 Title: Add ODM driver gpio-m058ssan Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:45:07 +0100 Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386 [ Impact ] gpio-m058ssan driver needed for ODM partner [ Test Plan ] Connect the loopback GPIO connector to the ReliaCOR-40-13 system and connect the power supply of the GPIO connector. insert the "m058ssan" module: modprobe m058ssan create GPIOchip: echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs , the latter 8 are GPIs. Set and reset all of the GPOs one at a time and check that the corresponding GPI is set and reset accordingly. [ Where problems could occur ] Make sure that the power supply of the GPIO connector is correctly connected, otherwise the GPI will always report 0. Events could occur on the i2c bus communication that may cause miss-behavior of the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045386/+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 2045387] Re: Add ODM driver f81604 usb-can
@Luca In your case, since you're using the generic kernel, you can ignore the messages for the others. -- 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/2045387 Title: Add ODM driver f81604 usb-can Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Jammy: Fix Released Bug description: From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001 From: Filippo Copetti Date: Mon, 4 Dec 2023 14:46:08 +0100 Subject: [PATCH 3/3] Add f81604 usb-can kernel driver https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387 [ Impact ] f81604 driver needed for ODM partner [ Test Plan ] Install can-utils apt install can-utils insert the driver: modprobe f81604 two socket can interfaces will be created, can0 and can1 connect the DB9 cable and termination provided. Set up the two interfaces: ip link set can1 up type can bitrate 50 ip link set can1 up type can bitrate 50 candump can0 In another shell run: cansend can1 123#DEADBEEF The first shell should report the received frame. Switch the interfaces in the last commands to test the frame flow in the other way around. [ Where problems could occur ] USB bus miss-behavior could cause issues to the driver. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 2049242] Re: CIFS Mounts Keep Load Average at n+1
This issue is fixed in the mainline kernel, 6.5.10 and higher. Re Possible bug report kernel 6.5.06.5.1 high load when CIFS share is mounted (cifsd-cfid-laundromat inD state) https://lore.kernel.org/lkml/cao+kfxqgxosx6u+xlkgje0kdifsragstspnrwxjqf6udgz5...@mail.gmail.com/T/ The relevant patches: "smb3: allow controlling length of time directory entries are cached with dir leases" https://github.com/torvalds/linux/commit/238b351d0935 "smb3: allow controlling maximum number of cached directories" https://github.com/torvalds/linux/commit/6a50d71d0fff "smb3: do not start laundromat thread when dir leases disabled" https://github.com/torvalds/linux/commit/2da338ff752a "smb: client: make laundromat a delayed worker" https://github.com/torvalds/linux/commit/e95f3f744650 "smb: client: prevent new fids from being removed by laundromat" https://github.com/torvalds/linux/commit/81ba10959970 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049242 Title: CIFS Mounts Keep Load Average at n+1 Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Today I noticed that my two primary Ubuntu boxes were running at high load. After investigation, I discovered at that unmounting their CIFS shares alleviating the high load. I rebooted to the previous kernel, linux-modules-6.2.0-39-generic, and saw that the load was low after everything had settled after startup. I rebooted to the current kernel, linux-modules-6.5.0-14-generic, and again saw the high load. The load appears to be n+1, where n is the number of CIFS mounts. (Based on a sample of two boxes.) I confirmed that the default mount options (e.g. the ones not specified in fstab) are the same between the two kernels. This *might* also be slowing down external (USB disk access. I'm still investigating that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 19:47:25 2024 InstallationDate: Installed on 2020-10-01 (1198 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2023-01-01 (376 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049242/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Could someone who's manually upgraded the firmware, as described in
comments #3 and #4, give instructions for doing the upgrade and
confirming that the new firmware is running? I've been trying to use
this workaround, but nothing I do seems to change which version of the
firmware is running, as discussed here:
https://askubuntu.com/q/1502905
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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] Re: Firefox/brave browser causes GPU reset and Gnome-shell crash
** Tags added: amdgpu
** Summary changed:
- Firefox/brave browser causes GPU reset and Gnome-shell crash
+ [amdgpu] Firefox/brave browser causes GPU reset and Gnome-shell crash
--
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:
[amdgpu] Firefox/brave browser causes GPU reset and Gnome-shell crash
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 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+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 2050032] Re: mpt3sas causes kernel stack trace
I also have this issue on Ubuntu 22.04 with 6.5.0-18-generic. Sharing my dmesg.txt in case it's helpful. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050032/+attachment/5745323/+files/dmesg.txt -- 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/2050032 Title: mpt3sas causes kernel stack trace Status in linux-hwe-6.5 package in Ubuntu: Confirmed Bug description: [ 22.989826] [ 22.989831] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12 [ 22.989838] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]' [ 22.989843] CPU: 23 PID: 0 Comm: swapper/23 Not tainted 6.5.0-14-generic #14~22.04.1-Ubuntu [ 22.989850] Hardware name: Supermicro H8DG6/H8DGi/H8DG6/H8DGi, BIOS 2.0b 03/01/2012 [ 22.989854] Call Trace: [ 22.989858] [ 22.989862] dump_stack_lvl+0x48/0x70 [ 22.989877] dump_stack+0x10/0x20 [ 22.989883] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 22.989895] _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas] [ 22.989962] mpt3sas_scsih_event_callback+0x21f/0x630 [mpt3sas] [ 22.990022] _base_async_event.isra.0+0x73/0x190 [mpt3sas] [ 22.990078] _base_process_reply_queue+0x3a0/0x720 [mpt3sas] [ 22.990133] _base_interrupt+0x4e/0x70 [mpt3sas] [ 22.990188] __handle_irq_event_percpu+0x4f/0x1c0 [ 22.990197] handle_irq_event+0x39/0x80 [ 22.990202] handle_edge_irq+0x8c/0x250 [ 22.990208] __common_interrupt+0x56/0x110 [ 22.990217] common_interrupt+0x9f/0xb0 [ 22.990224] [ 22.990226] [ 22.990228] asm_common_interrupt+0x27/0x40 [ 22.990239] RIP: 0010:cpuidle_idle_call+0xa2/0x190 [ 22.990248] Code: 00 4c 89 e2 4c 89 ee 48 89 df e8 c9 98 c1 00 4c 89 ee 48 89 df 89 c2 e8 9c a7 ff ff 65 48 8b 04 25 80 28 03 00 f0 80 48 02 20 <9c> 58 0f 1f 40 00 f6 c4 02 0f 84 8b 00 00 00 48 8b 45 d8 65 48 2b [ 22.990253] RSP: 0018:b627443a7eb0 EFLAGS: 0202 [ 22.990259] RAX: 9edde8178000 RBX: a58e52e0 RCX: [ 22.990263] RDX: RSI: RDI: [ 22.990266] RBP: b627443a7ee0 R08: R09: [ 22.990269] R10: R11: R12: 0001 [ 22.990272] R13: 9ed9ea75cc00 R14: R15: [ 22.990279] do_idle+0x82/0xf0 [ 22.990285] cpu_startup_entry+0x1d/0x20 [ 22.990290] start_secondary+0x129/0x160 [ 22.990300] secondary_startup_64_no_verify+0x17e/0x18b [ 22.990311] [ 22.99031 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050032/+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 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
I have confirmed that with the 6.5.0-25.25 kernel in mantic-proposed,
shared libraries for 32bit binaries are loaded with some randoness;
specifically, we are back to 7 bits of randomness with this kernel
update:
$ cat /proc/version_signature
Ubuntu 6.5.0-25.25-generic 6.5.13
$ for ((i = 0 ; i < 5; i++ )) ; do ./aslr32 --report libs ; done
0xe8a86e80
0xf4a86e80
0xf2886e80
0xf2a86e80
0xf1686e80
# report the number of distinct values we get:
$ for ((i = 0 ; i < 1; i++ )) ; do ./aslr32 --report libs ; done | sort |
uniq -c | wc -l
129
For reference, on the 6.5.0-17.17 kernel, we had no randomness
whatsoever:
$ cat /proc/version_signature
Ubuntu 6.5.0-17.17-generic 6.5.8
$ for ((i = 0 ; i < 1; i++ )) ; do ./aslr32 --report libs ; done | sort |
uniq -c
1 0xf7c86e80
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Status in QA Regression Testing:
Invalid
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
New
Status in linux source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Won't Fix
Status in linux-oem-6.1 source package in Lunar:
New
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.1 source package in Mantic:
New
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.1 source package in Noble:
Invalid
Bug description:
Issue found on 5.19.0-9.9 Kinetic AMD64 systems
Test log:
Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel:
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs ... (default libs native) (default libs native rekey) (default
libs COMPAT) FAIL
==
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1203, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: default libs COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0xf7c81790
0xf7c81790
0xf7c81790
FAIL: ASLR not functional (libs always at 0xf7c81790)
--
Ran 1 test in 0.144s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052676] Re: Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC
** Description changed: IPv6 SLAAC using 6.5.0.17-generic does not work, running on Linux mint - 6.3 Edge. This problem was also seen on kernel 6.5.0.15 and 6.5.0.14 + 21.3 Edge. This problem was also seen on kernel 6.5.0.15 and 6.5.0.14 generic kernels. The same system running on 6.2.0.33-generic works without any issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052676 Title: Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: IPv6 SLAAC using 6.5.0.17-generic does not work, running on Linux mint 21.3 Edge. This problem was also seen on kernel 6.5.0.15 and 6.5.0.14 generic kernels. The same system running on 6.2.0.33-generic works without any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2052676/+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 2052744] Re: nouveau breaks 24.04 desktop
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052744/+attachment/5745301/+files/dmesg.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/2052744 Title: nouveau breaks 24.04 desktop Status in linux package in Ubuntu: New Bug description: nouveau: detected PR support, will not use DSM nouveau :01:00.0: NVIDIA GP107 (137000a1) usb 3-3: new high-speed USB device number 2 using xhci_hcd nouveau :01:00.0: bios: version 86.07.90.00.51 nouveau :01:00.0: pmu: firmware unavailable nouveau :01:00.0: fb: 2048 MiB GDDR5 nouveau :01:00.0: DRM: VRAM: 2048 MiB nouveau :01:00.0: DRM: GART: 536870912 MiB nouveau :01:00.0: DRM: BIT table 'A' not found nouveau :01:00.0: DRM: BIT table 'L' not found nouveau :01:00.0: DRM: Pointer to TMDS table not found nouveau :01:00.0: DRM: DCB version 4.1 nouveau :01:00.0: DRM: MM: using COPY for buffer copies [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 nouveau :01:00.0: [drm] No compatible format found nouveau :01:00.0: [drm] Cannot find any crtc or sizes nouveau :01:00.0: bus: MMIO read of FAULT at 6013d4 [ PRIVRING ] nouveau :01:00.0: bus: MMIO read of FAULT at 122124 [ PRIVRING ] # above two repeat a lot And also stuff like this nouveau :01:00.0: bus: MMIO read of FAULT at 6013d4 [ TIMEOUT ] [ cut here ] nouveau :01:00.0: timeout WARNING: CPU: 3 PID: 6419 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1792 gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer nft_masq vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock ccm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc overlay qrtr cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi x86_pkg_temp_thermal snd_hda_c odec intel_powerclamp snd_hda_core coretemp snd_hwdep snd_pcm uvcvideo kvm_intel snd_seq_midi iwlmvm btusb videobuf2_vmalloc snd_seq_midi_event btrtl uvc cmdlinepart kvm snd_rawmidi videobuf2_memops btintel dell_laptop spi_nor videobuf2_v4l2 mac80211 snd_seq irqbypass btbcm processor_thermal_device_pci_legacy dell_wmi mtd videodev snd_seq_device rapl btmtk processor_thermal_device pmt_telemetry dell_smbios libarc4 mei_hdcp mei_pxp bluetooth pmt_class intel_rapl_msr dell_smm_hwmon iwlwifi videobuf2_common dcdbas snd_timer i2c_i801 dell_wmi_sysman spi_intel_pci intel_cstate processor_thermal_rfim dell_wmi_ddv ecdh_generic mc ecc ledtrig_audio firmware_attributes_class dell_wmi_descriptor wmi_bmof snd i2c_smbus spi_intel mei_me cfg80211 processor_thermal_mbox soundcore essiv mei authenc processor_thermal_rapl intel_rapl_common intel_skl_int3472_tps68470 intel_soc_dts_iosf intel_vsec igen6_edac tps68470_regulator int3403_thermal clk_tps68470 int340x_thermal_zone int3400_thermal intel_hid intel_skl_int3472_ discrete input_leds acpi_thermal_rel sparse_keymap acpi_pad joydev acpi_tad serio_raw mac_hid nbd msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 dm_crypt zfs(PO) spl(O) raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_sensor_custom nvme hid_sensor_hub nvme_core nvme_common intel_ishtp_hid hid_multitouch ahci hid_generic libahci i915 nouveau crct10dif_pclmul crc32_pclmul polyval_clmulni mxm_wmi polyval_generic drm_exec ghash_clmulni_intel gpu_sched drm_buddy sha256_ssse3 drm_ttm_helper i2c_algo_bit sha1_ssse3 ttm aesni_intel drm_display_helper cec i2c_hid_acpi rc_core intel_lpss_pci crypto_simd i2c_hid ucsi_acpi intel_ish_ipc drm_kms_helper hid typec_ucsi xhci_pci cryptd intel_lpss psmouse thunderbolt video idma64 intel_ishtp vmd drm xhci_pci_renesas typec wmi pinctrl_tigerlake CPU: 3 PID: 6419 Comm: gnome-shell Tainted: P O 6.6.0-14-generic #14-Ubuntu Hardware name: Dell Inc. Inspiron 7400/072W08, BIOS 1.16.0 04/13/2022 RIP: 0010:gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau] Code: 8b 40 10 48
[Kernel-packages] [Bug 2052744] [NEW] nouveau breaks 24.04 desktop
Public bug reported: nouveau: detected PR support, will not use DSM nouveau :01:00.0: NVIDIA GP107 (137000a1) usb 3-3: new high-speed USB device number 2 using xhci_hcd nouveau :01:00.0: bios: version 86.07.90.00.51 nouveau :01:00.0: pmu: firmware unavailable nouveau :01:00.0: fb: 2048 MiB GDDR5 nouveau :01:00.0: DRM: VRAM: 2048 MiB nouveau :01:00.0: DRM: GART: 536870912 MiB nouveau :01:00.0: DRM: BIT table 'A' not found nouveau :01:00.0: DRM: BIT table 'L' not found nouveau :01:00.0: DRM: Pointer to TMDS table not found nouveau :01:00.0: DRM: DCB version 4.1 nouveau :01:00.0: DRM: MM: using COPY for buffer copies [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 nouveau :01:00.0: [drm] No compatible format found nouveau :01:00.0: [drm] Cannot find any crtc or sizes nouveau :01:00.0: bus: MMIO read of FAULT at 6013d4 [ PRIVRING ] nouveau :01:00.0: bus: MMIO read of FAULT at 122124 [ PRIVRING ] # above two repeat a lot And also stuff like this nouveau :01:00.0: bus: MMIO read of FAULT at 6013d4 [ TIMEOUT ] [ cut here ] nouveau :01:00.0: timeout WARNING: CPU: 3 PID: 6419 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1792 gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer nft_masq vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock ccm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc overlay qrtr cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi x86_pkg_temp_thermal snd_hda_cod ec intel_powerclamp snd_hda_core coretemp snd_hwdep snd_pcm uvcvideo kvm_intel snd_seq_midi iwlmvm btusb videobuf2_vmalloc snd_seq_midi_event btrtl uvc cmdlinepart kvm snd_rawmidi videobuf2_memops btintel dell_laptop spi_nor videobuf2_v4l2 mac80211 snd_seq irqbypass btbcm processor_thermal_device_pci_legacy dell_wmi mtd videodev snd_seq_device rapl btmtk processor_thermal_device pmt_telemetry dell_smbios libarc4 mei_hdcp mei_pxp bluetooth pmt_class intel_rapl_msr dell_smm_hwmon iwlwifi videobuf2_common dcdbas snd_timer i2c_i801 dell_wmi_sysman spi_intel_pci intel_cstate processor_thermal_rfim dell_wmi_ddv ecdh_generic mc ecc ledtrig_audio firmware_attributes_class dell_wmi_descriptor wmi_bmof snd i2c_smbus spi_intel mei_me cfg80211 processor_thermal_mbox soundcore essiv mei authenc processor_thermal_rapl intel_rapl_common intel_skl_int3472_tps68470 intel_soc_dts_iosf intel_vsec igen6_edac tps68470_regulator int3403_thermal clk_tps68470 int340x_thermal_zone int3400_thermal intel_hid intel_skl_int3472_di screte input_leds acpi_thermal_rel sparse_keymap acpi_pad joydev acpi_tad serio_raw mac_hid nbd msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 dm_crypt zfs(PO) spl(O) raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_sensor_custom nvme hid_sensor_hub nvme_core nvme_common intel_ishtp_hid hid_multitouch ahci hid_generic libahci i915 nouveau crct10dif_pclmul crc32_pclmul polyval_clmulni mxm_wmi polyval_generic drm_exec ghash_clmulni_intel gpu_sched drm_buddy sha256_ssse3 drm_ttm_helper i2c_algo_bit sha1_ssse3 ttm aesni_intel drm_display_helper cec i2c_hid_acpi rc_core intel_lpss_pci crypto_simd i2c_hid ucsi_acpi intel_ish_ipc drm_kms_helper hid typec_ucsi xhci_pci cryptd intel_lpss psmouse thunderbolt video idma64 intel_ishtp vmd drm xhci_pci_renesas typec wmi pinctrl_tigerlake CPU: 3 PID: 6419 Comm: gnome-shell Tainted: P O 6.6.0-14-generic #14-Ubuntu Hardware name: Dell Inc. Inspiron 7400/072W08, BIOS 1.16.0 04/13/2022 RIP: 0010:gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau] Code: 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 6f c0 b6 ed 48 89 da 48 c7 c7 f5 22 99 c0 48 89 c6 e8 0d 05 13 ed <0f> 0b b8 f0 ff ff ff e9 f7 fd ff ff e8 5c 97 18 ee 66 66 2e 0f 1f RSP: 0018:c9000e67bb50 EFLAGS: 00010246 RAX: RBX: 8881022dec30 RCX: RDX: RSI: RDI: RBP: c9000e67bba0 R08: R09: R10:
[Kernel-packages] [Bug 2019011] Re: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver
** Tags added: verification-needed-focal-linux-bluefield -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification: == [ Impact ] * The mlx5 driver is causing a Kernel panic with "refcount_t: underflow". * This issue occurs during a recovery when the PCI device is isolated and thus doesn't respond. [ Fix ] * This issue got solved upstream with aaf2e65cac7f aaf2e65cac7f2e1ae729c2fbc849091df9699f96 "net/mlx5: Fix handling of entry refcount when command is not issued to FW" (upstream since 6.1-rc1) * But to get aaf2e65cac7f a backport of b898ce7bccf1 b898ce7bccf13087719c021d829dab607c175246 "net/mlx5: cmdif, Avoid skipping reclaim pages if FW is not accessible" is required on top (upstream since 5.10) [ Test Plan ] * An Ubuntu Server for s390x 20.04 LPAR or z/VM installation is needed that has Mellanox cards (RoCE Express 2.1) assigned, configured and enabled and that runs a 5.4 kernel with mlx5 driver. * Create some network traffic on (one of the) RoCE device (interface ens???[d?]) for testing (e.g. with stress-ng). * Make sure the module/driver mlx5 is loaded and in use. * Trigger a recovery (via the Support Element) that will render the adapter (ports) unresponsive for a moment and should provoke a similar situation. * Alternatively the interface itself can be removed for a moment and re-added again (but this may break further things on top). * Due to the lack of RoCE Express 2.1 hardware, the verification is on IBM. [ Where problems could occur ] * The modifications are limited to the Mellanox mlx5 driver only - no other network driver is affected. * The pre-required commit (aaf2e65cac7f) can have a bad impact on (re-)claiming pages if FW is not accessible, which could cause page leaks in case done wrong. But this commit is pretty save since it's upstream since v5.10. * The fix itself (aaf2e65cac7f) mainly changes the cmd_work_handler and mlx5_cmd_comp_handler functions in a way that instead of pci_channel_offline mlx5_cmd_is_down (introiduced by b898ce7bccf1). * Actually b898ce7bccf1 started with changing from pci_channel_offline to mlx5_cmd_is_down, but looks like a few cases (in the area of refcount increate/decrease) were missed, that are now covered by aaf2e65cac7f. * It fixes now on top refcounts are now always properly increment and decrement to achieve a symmetric state for all flows. * These changes may have an impact on all cases where the mlx5 device is not responding, which can happen in case of an offline channel, interface down, reset or recovery. [ Other Info ] * Looking at the master-next git trees for jammy, kinetic and lunar showed that both fixes are already included, hence only focal is affected. __ ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023]
[Kernel-packages] [Bug 2013088] uaccess clear_user() fix
--- Comment on attachment From h.carst...@de.ibm.com 2023-04-03 14:32 EDT--- Attached patch applies to 18.04 and 20.04. ** Attachment added: "uaccess clear_user() fix" https://bugs.launchpad.net/bugs/2013088/+attachment/5745283/+files/s390-uaccess.patch -- 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/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: == [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [Fix] * For Kinetic and Jammy cherrypick of 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3 "s390/uaccess: add missing earlyclobber annotations to __clear_user()" * For Focal and Bionic a backport of the above commit is needed: https://launchpadlibrarian.net/659551648/s390-uaccess.patch [ Test Plan ] * A test program in C is needed and used for testing. * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 separately, and submit the SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+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 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
Could you please add DEP-3 headers to the patches you're adding? If you see the patch being removed, you're going to notice the headers there, so you can use them to guide you. I'm going to unsubscribe ubuntu-sponsors from the bug for now. Please resubscribe it once you've addressed the point above. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2051199 Title: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs. mt8370-evk (G510): https://github.com/alsa-project/alsa-ucm-conf/pull/380 https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97 mt8390-evk (G700): https://github.com/alsa-project/alsa-ucm-conf/pull/321 https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b mt8395-evk (G1200): https://github.com/alsa-project/alsa-ucm-conf/pull/322 https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0 Fix a file type issue: https://github.com/alsa-project/alsa-ucm-conf/pull/386 https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf mt8395-evk (G1200) HDMI RX: https://github.com/alsa-project/alsa-ucm-conf/pull/389 https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1 [Where problems could occur] 1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu archive was rejected by upstream. Replace them with new patches accepted by upstream. 2. Add initial support for mt8370-evk 3. Add mt8395-evk HDMI RX support [Test Case] Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. mt8395-evk: HDMI RX Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] 1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk. 2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream and new configs have been verified by MediaTek. It should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-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/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] * Issue is causing transmit hang on E810 ports with bonding enabled. * Based on the provided logs, TX hang can last for even a couple of minutes, but in most scenarios, the network will be recovered after the ice driver performs a PF reset (TX hang handler routine). * Originally, the issue was observed during Tempest tests on a newly created OpenStack cluster, resulting in a lack of certification. [Fix] * Initially, a workaround has been proposed by Intel engineers to disable LAG initialization [1]. This change has been tested in an environment where reproduction is easily achieved. After multiple iterations, no reproduction has been observed. * Shortly after, Intel proposed a patch [2] to disable LAG initialization if NVM does not expose proper capabilities. [Test Plan] * To reproduce the issue, over a 20-node cluster was used with Ceph-based storage. The problem could sometimes manifest while deploying a cluster or after the cluster was already deployed during the Tempest test run. * The issue could appear on a random node, making reproduction hard to achieve. * Multiple stress tests on single host with similar configuration did not trigger a reproduction. [Where problems could occur] * All ice drivers with ice_lag_event_handler registered can expose the issue. This handler is not implemented in 20.04 * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this capability will be released. Although potentialy issue is caused by using features without proper FW support [2], we want to take a closer look once NVMs with proper support are introduced. [1] - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40 [2] - https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html 4d50fcdc2476eef94c14c6761073af5667bb43b6 [Other Info] * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice driver backported from mainline kernel from before patch [2] was added. * Original description of the case below: 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
[Kernel-packages] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-linux'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Status in QA Regression Testing:
Invalid
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
New
Status in linux source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Won't Fix
Status in linux-oem-6.1 source package in Lunar:
New
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.1 source package in Mantic:
New
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.1 source package in Noble:
Invalid
Bug description:
Issue found on 5.19.0-9.9 Kinetic AMD64 systems
Test log:
Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel:
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs ... (default libs native) (default libs native rekey) (default
libs COMPAT) FAIL
==
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1203, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: default libs COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0xf7c81790
0xf7c81790
0xf7c81790
FAIL: ASLR not functional (libs always at 0xf7c81790)
--
Ran 1 test in 0.144s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044131] Re: i915 regression introduced with 5.5 kernel
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2044131 Title: i915 regression introduced with 5.5 kernel Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.15 source package in Focal: Triaged Status in linux source package in Jammy: Fix Committed Status in linux-hwe-5.15 source package in Jammy: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-hwe-5.15 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-hwe-5.15 source package in Noble: Invalid Bug description: [ Impact ] Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks which have been proven invalid for at least some hardware setups. A user trying to run Focal with HWE 5.15 kernel is not able to get any video output. After going through bisection between 5.4 and 5.5 this commit was identified. Reverting it on top of Focal HWE kernel fixes the issue. The issue has been addressed upstream in DRM tree (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d). dmesg and lspci from the affected configuration are attached to this bug. [ Test Plan ] 1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or higher. 2. Wait until boot finishes and see the blank screen. Actual result: there is no video output visible. Expected result: normal boot process should be visible (e.g. splash), then GUI should appear. [ Where problem could occur ] This bug was a result of assumptions in the checks that turned out to be not valid for some hardware. The checks were removed from global intel_mode_valid function and moved into connector specific .mode_valid() hooks, entirely skiping BXT/GLK DSI connectors. This should keep the checks where appropriate and skip for hardware that does not comply to them. [ Other info ] Original bug description: There is a regression preventing a user to upgrade from 5.4 kernel to anything that's higher than 5.5. When using such kernel the image orientation is wrong (rotated by 90°C). Also the kernel log contains: wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06 wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25 wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga console wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory information wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:o> wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v> wrz 15 09:19:49 desktop kernel: wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.> wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]' (full stack trace attached) The video hardware in use is: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) (...) Kernel driver in use: i915 Kernel modules: i915 The user wanted to upgrade from bionic to focal with HWE kernel (they needed it due to some networking hardware they wanted to have supported by the newer kernel). The user was testing mainline stable kernels and noticed that the last working kernel was the 5.4 series, while anything starting from 5.5 and above is BROKEN (symptoms as described in the first paragraph above). Together with the user we have run a bisection between v5.4 and v5.5 on the upstream stable kernel and we were able to identify the first broken commit to be:
[Kernel-packages] [Bug 2049689] Re: partproke is broken on empty loopback device
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-linux'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-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/2049689
Title:
partproke is broken on empty loopback device
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
SRU Justification:
[Impact]
* BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
but now returns EINVAL, breaking partprobe due to commit
"block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
introduced in mantic 6.5.0-17 and jammy 5.15.0-94.
[Fix]
* backport commit
"block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"
[Test Plan]
* dd if=/dev/zero of=/tmp/foo bs=1M count=50
* partprobe $(losetup --find --show /tmp/foo)
Before the fix this fails.
After the fix it should work.
[Where problems could occur]
* We may see issues on disk partitions operations.
Old description:
This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic
5.15.0-94.104).
Do this:
# dd if=/dev/zero of=/tmp/file bs=1M count=50
# partprobe "$(losetup --show --find /tmp/file)"
Notice this very odd error message:
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
/dev/loop2 have been written, but we have been unable to inform the
kernel of the change, probably because it/they are in use. As a
result, the old partition(s) will remain in use. You should reboot
now before making further changes.
That's a result of an ioctl changing its error code in an incompatible
way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
partprobe.
5.15.0.91.88:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or
address)
5.15.0.94.91:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
This is a userspace API break which impacts GNU parted and util-linux
(as confirmed by the util-linux maintainer).
This issue was discovered as part of Cockpit CI here:
https://github.com/cockpit-project/bots/pull/5793
This issue is being discussed on LKML here (with a patch likely to
land soon): https://lkml.org/lkml/2024/1/15/147
lsb_release -rd:
Description: Ubuntu 22.04.3 LTS
Release: 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+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 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-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/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. Status in linux package in Ubuntu: Invalid Status in linux-signed-hwe-6.5 package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-signed-hwe-6.5 source package in Mantic: Invalid Bug description: SRU Justification: [Impact] Multiple users have reported frozen displays when external HDMI device is connected on systems with intel graphics chipsets. [Fix] * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events" from 6.6.9 [Test Plan] * Tested on Intel TigerLake with iris Xe Graphics and no issues so far. It seems it affects mostly Alder Lake though, but at least it does not cause any issues on other models. * It has also been tested upstream https://gitlab.freedesktop.org/drm/intel/-/issues/8685 [Where problems could occur] * We could see issues on systems with Intel Graphics when HDMI devices are connected during power state changes. Old description: It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685 It was fixed with that kernel commit: commit 648d7be8ecf47b0556e32550145c70db153b16fb Author: Ville Syrjälä Date: Mon Dec 11 23:37:47 2023 +0200 drm/i915/dmc: Don't enable any pipe DMC events https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/ which was picked for 6.6.9. I'd like to ask whether it is possible to apply that patch to the current Ubuntu kernel? Best Sönke ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 13:11:59 2024 InstallationDate: Installed on 2023-03-01 (316 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051176] Re: Update Ubuntu.md
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-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/2051176 Title: Update Ubuntu.md Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: [ Impact ] * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md [ Other Info ] * I used the current kernel version of 6.5.10 since it didn't seem to make sense to use the old version we released with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
Ran AppArmor tests from the QA Regression Tests [1] and POSIX mqueue tests from the AppArmor test suite and they all passed as expected. georgia@sec-jammy-amd64:~$ uname -a Linux sec-jammy-amd64 5.15.0-1056-azure #64-Ubuntu SMP Tue Feb 6 19:23:34 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux georgia@sec-jammy-amd64:~/qrt-test-apparmor$ sudo ./test-apparmor.py . -- Ran 62 tests in 1061.185s OK (skipped=2) georgia@sec-jammy-amd64:~$ apt source apparmor georgia@sec-jammy-amd64:~$ cd apparmor-3.0.4/tests/regression/apparmor/ georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ USE_SYSTEM=1 make georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ sudo ./posix_mq.sh BAD PASSWORD: The password fails the dictionary check - it is based on a dictionary word xpass: POSIX MQUEUE (confined root - mqueue label 1) xpass: POSIX MQUEUE (confined root - mqueue label 1 : mq_notify) xpass: POSIX MQUEUE (confined root - mqueue label 1 : select) xpass: POSIX MQUEUE (confined root - mqueue label 1 : poll) xpass: POSIX MQUEUE (confined root - mqueue label 1 : epoll) xpass: POSIX MQUEUE (confined root - mqueue label 2) xpass: POSIX MQUEUE (confined root - mqueue label 2 : mq_notify) xpass: POSIX MQUEUE (confined root - mqueue label 2 : select) xpass: POSIX MQUEUE (confined root - mqueue label 2 : poll) xpass: POSIX MQUEUE (confined root - mqueue label 2 : epoll) xpass: POSIX MQUEUE (confined 1002 - mqueue label 1) xpass: POSIX MQUEUE (confined 1002 - mqueue label 1 : mq_notify) xpass: POSIX MQUEUE (confined 1002 - mqueue label 1 : select) xpass: POSIX MQUEUE (confined 1002 - mqueue label 1 : poll) xpass: POSIX MQUEUE (confined 1002 - mqueue label 1 : epoll) xpass: POSIX MQUEUE (confined 1002 - mqueue label 2) xpass: POSIX MQUEUE (confined 1002 - mqueue label 2 : mq_notify) xpass: POSIX MQUEUE (confined 1002 - mqueue label 2 : select) xpass: POSIX MQUEUE (confined 1002 - mqueue label 2 : poll) xpass: POSIX MQUEUE (confined 1002 - mqueue label 2 : epoll) [1] https://launchpad.net/qa-regression-testing ** Tags removed: verification-needed-jammy-linux-azure ** Tags added: verification-done-jammy-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/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough
This issue is s390-specific only, and does not affect azure at all. Hence adding tag verification-done again to potentially unblock the process. ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042853 Title: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] * Today no s390x-specific vfio-pci devices (zPCI) can be passed from a KVM host to a KVM guest (incl. secure execution guests in the context of confidential computing). * s390x PCI passthrough needs various changes in the s390x kernel zPCI code (incl. the new s390x-specific Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0 and got backported to 22.04/jammy as part of LP: #1853306. * Lunar an newer Ubuntu releases have the code already included from upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the config option is not set, hence zPCI pass-through is still not possible. [Fix] * To be able to make use of VFIO zPCI pass-through on s390x running newer Ubuntu releases (especially needed in the context of secure execution) the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs to be enabled and set to 'y'. [Test Case] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only available on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) [Regression Potential] * The regression potential is moderate, since the code is upstream for quite a while and already enabled in jammy. * The general way on using passthrough has not changed, with this change (config option) it's now just possible to passthrough zPCI on top. * CCW devices are not affected. * And this is s390x-specific anyway, so no other architectures are affected. [Other] * The enabling of the kernel config option is exactly the same for L, M and U/N, but I submitted separate patches due to slightly different context and offsets. __ === Description by mjros...@us.ibm.com === LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to enable enhanced interpretation of PCI passthrough on s390. It also included a kernel config update for CONFIG_VFIO_PCI_ZDEV_KVM=y which is necessary to activate this kernel feature. For lunar and mantic,
[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
This issue is s390x only, and not related to azure at all. Hence adding verification-done again to potentially unblock the process. ** Tags added: verification-done -- 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/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
https://lists.ubuntu.com/archives/kernel-team/2024-February/148724.html -- 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/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow
Please let me know if testing from the Canonical Kernel PPA is
sufficient or if I should test again using -proposed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2043841
Title:
kernel BUG: io_uring openat triggers audit reference count underflow
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Released
Bug description:
I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
occurs during io_uring openat audit processing. I have a kernel patch
that was accepted into the upstream kernel as well as the v6.6,
v6.5.9, and v6.1.60 releases. The bug was first introduced in the
upstream v5.16 kernel.
I do not see the change yet in:
* The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel
repository.
* The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.
Can this upstream commit be cherry picked?
The upstream commit is:
03adc61edad49e1bbecfb53f7ea5d78f398fe368
The upstream patch thread is:
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u
The maintainer pull request thread is:
https://lore.kernel.org/lkml/20231019-kampfsport-
metapher-e5211d7be247@brauner
The pre-patch discussion thread is:
https://lore.kernel.org/io-
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u
The commit log message is:
commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
Author: Dan Clash
Date: Thu Oct 12 14:55:18 2023 -0700
audit,io_uring: io_uring openat triggers audit reference count
underflow
An io_uring openat operation can update an audit reference count
from multiple threads resulting in the call trace below.
A call to io_uring_submit() with a single openat op with a flag of
IOSQE_ASYNC results in the following reference count updates.
These first part of the system call performs two increments that
do not race.
do_syscall_64()
__do_sys_io_uring_enter()
io_submit_sqes()
io_openat_prep()
__io_openat_prep()
getname()
getname_flags() /* update 1 (increment) */
__audit_getname() /* update 2 (increment) */
The openat op is queued to an io_uring worker thread which starts the
opportunity for a race. The system call exit performs one decrement.
do_syscall_64()
syscall_exit_to_user_mode()
syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
audit_reset_context()
putname() /* update 3 (decrement) */
The io_uring worker thread performs one increment and two decrements.
These updates can race with the system call decrement.
io_wqe_worker()
io_worker_handle_work()
io_wq_submit_work()
io_issue_sqe()
io_openat()
io_openat2()
do_filp_open()
path_openat()
__audit_inode() /* update 4 (increment) */
putname() /* update 5 (decrement) */
__audit_uring_exit()
audit_reset_context()
putname() /* update 6 (decrement) */
The fix is to change the refcnt member of struct audit_names
from int to atomic_t.
kernel BUG at fs/namei.c:262!
Call Trace:
...
? putname+0x68/0x70
audit_reset_context.part.0.constprop.0+0xe1/0x300
__audit_uring_exit+0xda/0x1c0
io_issue_sqe+0x1f3/0x450
? lock_timer_base+0x3b/0xd0
io_wq_submit_work+0x8d/0x2b0
? __try_to_del_timer_sync+0x67/0xa0
io_worker_handle_work+0x17c/0x2b0
io_wqe_worker+0x10a/0x350
Cc: sta...@vger.kernel.org
Link:
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support
to io_uring")
Signed-off-by: Dan Clash
Link:
https://lore.kernel.org/r/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
Reviewed-by: Jens Axboe
Signed-off-by: Christian Brauner
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043841/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow
I previously verified that the test program hangs when 6.5.0-1011-azure is installed. I have been testing with 6.5.0-1012-azure from the Canonical Kernel PPA for a while with no issues. I upgraded to 6.5.0-1013-azure just now and the test program still passes. devvm7 ~ $ uname -a Linux daclashlinux7 6.5.0-1013-azure #13~22.04.1-Ubuntu SMP Tue Feb 6 20:34:09 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux devvm7 ~ $ sudo dmesg --clear devvm7 ~ $ ./io_uring_open_close_audit_hang --directory /tmp/deleteme --count 1 i=0 i=100 i=200 ... i=9800 i=9900 devvm7 ~ $ sudo dmesg devvm7 ~ $ The test program does not hang when running with 6.5.0-1012-azure. daclash@daclashlinux4:~$ uname -a Linux daclashlinux4 6.5.0-1012-azure #12~22.04.1-Ubuntu SMP Tue Jan 16 21:24:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux daclash@daclashlinux4:~$ sudo dmesg --clear daclash@daclashlinux4:~$ ./io_uring_open_close_audit_hang --directory /tmp/deleteme --count 1 ... i=9900 daclash@daclashlinux4:~$ sudo dmesg daclash@daclashlinux4:~$ The test program does hang when running with 6.5.0-1011-azure. daclash@daclashlinux4:~$ uname -a Linux daclashlinux4 6.5.0-1011-azure #11~22.04.1-Ubuntu SMP Mon Jan 15 16:59:12 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux daclash@daclashlinux4:~$ sudo dmesg --clear daclash@daclashlinux4:~$ ./io_uring_open_close_audit_hang --directory /tmp/deleteme --count 1 i=0 ... i=5900 i=6000 ^C daclash@daclashlinux4:~$ sudo dmesg | grep "kernel BUG at fs/namei.c" [ 125.159601] kernel BUG at fs/namei.c:264! -- 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/2043841 Title: kernel BUG: io_uring openat triggers audit reference count underflow Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Released Bug description: I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that occurs during io_uring openat audit processing. I have a kernel patch that was accepted into the upstream kernel as well as the v6.6, v6.5.9, and v6.1.60 releases. The bug was first introduced in the upstream v5.16 kernel. I do not see the change yet in: * The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel repository. * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository. Can this upstream commit be cherry picked? The upstream commit is: 03adc61edad49e1bbecfb53f7ea5d78f398fe368 The upstream patch thread is: https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u The maintainer pull request thread is: https://lore.kernel.org/lkml/20231019-kampfsport- metapher-e5211d7be247@brauner The pre-patch discussion thread is: https://lore.kernel.org/io- uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u The commit log message is: commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368 Author: Dan Clash Date: Thu Oct 12 14:55:18 2023 -0700 audit,io_uring: io_uring openat triggers audit reference count underflow An io_uring openat operation can update an audit reference count from multiple threads resulting in the call trace below. A call to io_uring_submit() with a single openat op with a flag of IOSQE_ASYNC results in the following reference count updates. These first part of the system call performs two increments that do not race. do_syscall_64() __do_sys_io_uring_enter() io_submit_sqes() io_openat_prep() __io_openat_prep() getname() getname_flags() /* update 1 (increment) */ __audit_getname() /* update 2 (increment) */ The openat op is queued to an io_uring worker thread which starts the opportunity for a race. The system call exit performs one decrement. do_syscall_64() syscall_exit_to_user_mode() syscall_exit_to_user_mode_prepare() __audit_syscall_exit() audit_reset_context() putname() /* update 3 (decrement) */ The io_uring worker thread performs one increment and two decrements. These updates can race with the system call decrement. io_wqe_worker() io_worker_handle_work() io_wq_submit_work() io_issue_sqe() io_openat() io_openat2() do_filp_open() path_openat() __audit_inode() /* update 4 (increment) */ putname() /* update 5 (decrement) */ __audit_uring_exit() audit_reset_context() putname() /* update 6 (decrement) */ The fix is to change
[Kernel-packages] [Bug 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Changed in: linux-azure (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
Houston, we have a problem... This bug is notoriously difficult to reproduce. The only environment that presented it is now in production and will not be available for testing anymore. Which means that this cannot be tested, unless anyone can suggest a new way of reproducing 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/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] * Issue is causing transmit hang on E810 ports with bonding enabled. * Based on the provided logs, TX hang can last for even a couple of minutes, but in most scenarios, the network will be recovered after the ice driver performs a PF reset (TX hang handler routine). * Originally, the issue was observed during Tempest tests on a newly created OpenStack cluster, resulting in a lack of certification. [Fix] * Initially, a workaround has been proposed by Intel engineers to disable LAG initialization [1]. This change has been tested in an environment where reproduction is easily achieved. After multiple iterations, no reproduction has been observed. * Shortly after, Intel proposed a patch [2] to disable LAG initialization if NVM does not expose proper capabilities. [Test Plan] * To reproduce the issue, over a 20-node cluster was used with Ceph-based storage. The problem could sometimes manifest while deploying a cluster or after the cluster was already deployed during the Tempest test run. * The issue could appear on a random node, making reproduction hard to achieve. * Multiple stress tests on single host with similar configuration did not trigger a reproduction. [Where problems could occur] * All ice drivers with ice_lag_event_handler registered can expose the issue. This handler is not implemented in 20.04 * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this capability will be released. Although potentialy issue is caused by using features without proper FW support [2], we want to take a closer look once NVMs with proper support are introduced. [1] - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40 [2] - https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html 4d50fcdc2476eef94c14c6761073af5667bb43b6 [Other Info] * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice driver backported from mainline kernel from before patch [2] was added. * Original description of the case below: 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
[Kernel-packages] [Bug 2052723] [NEW] Azure: Enable CONFIG_TEST_LOCKUP
Public bug reported: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 ** Affects: linux-azure (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Mantic) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Noble) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux-azure (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Mantic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Noble) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Status in linux-azure source package in Noble: In Progress Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision
This bug is awaiting verification that the linux-azure/6.5.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If the problem still exists, change the tag
'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-
linux-azure'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-mantic-linux-azure-v2
verification-needed-mantic-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035971
Title:
linux tools packages for derived kernels refuse to install
simultaneously due to libcpupower name collision
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[ Impact ]
* Multiple kernel flavours are conflicting with each on .deb / file
level via their tools packages
* Resolve the conflicting private libcpupower.so by statically
linking it into the only C binary that uses said library in the linux-
tools
[ Test Plan ]
* co-install tools packages from multiple kernel flavours of the same
major version and abi, it should be successful
[ Where problems could occur ]
* If one tries really hard to find the private location of
libcpupower.so and dlopen it by ever changing abi name, that will not
be possible, until the separate bug report is fixed to introduce the
public stable libcpupower.so.1 which so far ubuntu has never yet
provided.
[ Other Info ]
* original bug report
Taking linux-kvm and linux-gcp for example:
$ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103384 2023-07-25 20:00
./usr/lib/libcpupower.so.6.2.0-1011
$ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103392 2023-08-16 15:08
./usr/lib/libcpupower.so.6.2.0-1011
linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
utilities, and yet files of the same full path cannot be installed
from two distinct debian packages, which follows we won't be able to
install two linux-tools packages of two different derived kernels on
the same system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
Uname: Linux 6.5.0-9004-generic x86_64
NonfreeKernelModules: zfs wl
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vicamo 6331 F wireplumber
/dev/snd/controlC0: vicamo 6331 F wireplumber
/dev/snd/seq:vicamo 6315 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Sep 14 23:31:16 2023
InstallationDate: Installed on 2022-04-10 (522 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9004-generic N/A
linux-backports-modules-6.5.0-9004-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 432.60.3.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias:
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
dmi.product.family: Mac
dmi.product.name: MacBookPro11,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To
[Kernel-packages] [Bug 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2039151 Title: Support speaker mute hotkey for Cirrus CS35L41 HDA codec Status in HWE Next: New Status in linux package in Ubuntu: Incomplete 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 Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Some systems use a special hotkey to mute speaker audio. On systems using CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI notifications to detect whether the hotkey is triggered to switch the mute state. [Fix] Backport the fix from Cirrus on linux-next https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t. [Test Case] 1. Power on the machine with CS35L41 HDA and the speaker mute hotkey. 2. Verify the audio functions 3. Verify if the speaker can be mute/unmute by the hotkey. [Where problems could occur] Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey on keyboard. The impact is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2039151/+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 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
This bug is awaiting verification that the linux/5.15.0-100.110 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' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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-v2 verification-needed-jammy-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/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] * Issue is causing transmit hang on E810 ports with bonding enabled. * Based on the provided logs, TX hang can last for even a couple of minutes, but in most scenarios, the network will be recovered after the ice driver performs a PF reset (TX hang handler routine). * Originally, the issue was observed during Tempest tests on a newly created OpenStack cluster, resulting in a lack of certification. [Fix] * Initially, a workaround has been proposed by Intel engineers to disable LAG initialization [1]. This change has been tested in an environment where reproduction is easily achieved. After multiple iterations, no reproduction has been observed. * Shortly after, Intel proposed a patch [2] to disable LAG initialization if NVM does not expose proper capabilities. [Test Plan] * To reproduce the issue, over a 20-node cluster was used with Ceph-based storage. The problem could sometimes manifest while deploying a cluster or after the cluster was already deployed during the Tempest test run. * The issue could appear on a random node, making reproduction hard to achieve. * Multiple stress tests on single host with similar configuration did not trigger a reproduction. [Where problems could occur] * All ice drivers with ice_lag_event_handler registered can expose the issue. This handler is not implemented in 20.04 * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this capability will be released. Although potentialy issue is caused by using features without proper FW support [2], we want to take a closer look once NVMs with proper support are introduced. [1] - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40 [2] - https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html 4d50fcdc2476eef94c14c6761073af5667bb43b6 [Other Info] * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice driver backported from mainline kernel from before patch [2] was added. * Original description of the case below: 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
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD 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-oem-6.5 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-oem-6.5 source package in Jammy: Fix Released 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 Released 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 can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ Lunar, $ git push l_cbd Enumerating objects: 9, done. Counting objects: 100% (9/9), done. Delta compression using up to 8 threads Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done. Total 5 (delta 4), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-915de03d6ecf-V1nm remote: * 9/9 workers busy, 0 builds queued remote: 2023-11-20 16:00:11
[Kernel-packages] [Bug 2027615] Re: Azure: MANA: Fix doorbell access for receives
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2027615 Title: Azure: MANA: Fix doorbell access for receives Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: Fix Released Status in linux-azure source package in Lunar: Fix Released Bug description: SRU Justification [Impact] It's inefficient to ring the doorbell page every time a WQE is posted to the received queue. Excessive MMIO writes result in CPU spending more time waiting on LOCK instructions (atomic operations), resulting in poor scaling performance. [Test Plan] MSFT tested. [Regression Potential] The MANA receive queue could stop. [Other Info] SF: #00363437 These 2 patches have been submitted for upstream inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2027615/+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 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038263 Title: Add SoF topology support on Intel RaptorLake DELL SKU 0C11 Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released 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 firmware-sof source package in Jammy: Fix Released 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 Released Status in firmware-sof source package in Lunar: Won't Fix Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Fix Released 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 Jusitification for firmware-sof [Impact] To support audio functions on RPL Dell SKU 0C11, it requires the topology file from sof-tplg-v2.2.7 [Fix] Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Test Case] Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the audio function. 1. Install the firmware-sof on platform(RPL) Dell SKU 0C11 2. Make sure the audio output/input devices are not dummy in audio settings. [Where problems could occur] New firmware is only for the RPL platforms which requires the specific topology file. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Impact] Audio play/capture are not functional on specific Dell machines of Intel RPL platforms [Fix] Backport the fix from Intel in https://github.com/thesofproject/linux [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy` shown on the Audio output/input option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038263/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Lunar: Fix Released Status in linux-gcp source package in Lunar: Fix Released Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042853 Title: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] * Today no s390x-specific vfio-pci devices (zPCI) can be passed from a KVM host to a KVM guest (incl. secure execution guests in the context of confidential computing). * s390x PCI passthrough needs various changes in the s390x kernel zPCI code (incl. the new s390x-specific Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0 and got backported to 22.04/jammy as part of LP: #1853306. * Lunar an newer Ubuntu releases have the code already included from upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the config option is not set, hence zPCI pass-through is still not possible. [Fix] * To be able to make use of VFIO zPCI pass-through on s390x running newer Ubuntu releases (especially needed in the context of secure execution) the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs to be enabled and set to 'y'. [Test Case] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only available on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) [Regression Potential] * The regression potential is moderate, since the code is upstream for quite a while and already enabled in jammy. * The general way on using passthrough has not changed, with this change (config option) it's now just possible to passthrough zPCI on top. * CCW devices are not
[Kernel-packages] [Bug 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042060 Title: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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 Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume from suspend. The audio play and capture functions are not working after resume from S3. [Fix] Backport the fix from Cirrus on linux-next https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/. [Test Case] 1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA . 2. Perform system suspend/resume at least 3 times. 3. Verify the audio functions, including playback and capture [Where problems could occur] Only affect specific laptops with the CS35L41 HDA. The impact is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042060/+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 2041613] Re: correct cephfs pull request for uidmap support
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041613 Title: correct cephfs pull request for uidmap support Status in linux package in Ubuntu: New Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: New Bug description: [ Impact ] * During mantic dev cycle, we pulled all of cephfs testing patches, rather than uidmapshift patches alone * We also pulled in debug patches that generate a lot of dmesg and delays in the cephfs module [ Test Plan ] * run ceph fs and experience less dmesg at info level [ Where problems could occur ] * Hopefully the reverts were done correctly, and none of the messages reference non-existing things, in all the code paths. [ Other Info ] * Story time how we got here: The following pull requests BugLink: https://bugs.launchpad.net/bugs/2038522 BugLink: https://bugs.launchpad.net/bugs/2032959 generated the following commit list 1: eddf9ed788 UBUNTU: [Config] disable shiftfs 72e8806959 UBUNTU: SAUCE: ceph: enable unsafe idmapped mounts by default 80b85e5d76 UBUNTU: SAUCE: ceph: allow idmapped mounts 9d341bb8aa UBUNTU: SAUCE: ceph/file: allow idmapped atomic_open inode op ddd1a8ee19 UBUNTU: SAUCE: ceph/acl: allow idmapped set_acl inode op 1b12f12987 UBUNTU: SAUCE: ceph: allow idmapped setattr inode op b1f695f0d1 UBUNTU: SAUCE: ceph: pass idmap to __ceph_setattr 8a9a3b9e88 UBUNTU: SAUCE: ceph: allow idmapped permission inode op e5471722b3 UBUNTU: SAUCE: ceph: allow idmapped getattr inode op f6b1d353fa UBUNTU: SAUCE: ceph: pass an idmapping to mknod/symlink/mkdir 5ecfa6f659 UBUNTU: SAUCE: ceph: add enable_unsafe_idmap module parameter 19724a984a UBUNTU: SAUCE: ceph: handle idmapped mounts in create_request_message() 6ec4e53238 UBUNTU: SAUCE: ceph: stash idmapping in mdsc request 8006617c5e UBUNTU: SAUCE: fs: export mnt_idmap_get/mnt_idmap_put 55f4f0afc5 UBUNTU: SAUCE: ceph: make num_fwd and num_retry to __u32 54e03068d6 UBUNTU: SAUCE: ceph: make the members in struct ceph_mds_request_args_ext an union f7ec09aaac UBUNTU: SAUCE: ceph: print the client global_id in all the debug logs b2831559c5 UBUNTU: SAUCE: ceph: add ceph_inode_to_client() helper support a0852434ee UBUNTU: SAUCE: ceph: move mdsmap.h to fs/ceph/ cfda2c4b70 UBUNTU: SAUCE: ceph: rename _to_client() to _to_fs_client() 42924fda3a UBUNTU: SAUCE: ceph: pass the mdsc to several helpers 9f6e6f9ce9 UBUNTU: SAUCE: ceph: add the *_client debug macros support 8f61639667 UBUNTU: SAUCE: ceph: BUG if MDS changed truncate_seq with client caps still outstanding a53dba9297 UBUNTU: SAUCE: ceph: make sure all the files successfully put before unmounting 17fcf5d75d UBUNTU: SAUCE: mm: BUG if filemap_alloc_folio gives us a folio with a non-NULL ->private 834ebb591f UBUNTU: SAUCE: ceph: dump info about cap flushes when we're waiting too long for them 498d08b9bd UBUNTU: SAUCE: rbd: bump RBD_MAX_PARENT_CHAIN_LEN to 128 3ae75e2438 UBUNTU: SAUCE: libceph: do not include crypto/algapi.h d984763988 UBUNTU: SAUCE: ceph: switch ceph_lookup/atomic_open() to use new fscrypt helper 8e298c72fb UBUNTU: SAUCE: ceph: fix updating i_truncate_pagecache_size for fscrypt 288f935219 UBUNTU: SAUCE: ceph: wait for OSD requests' callbacks to finish when unmounting 435fc54954 UBUNTU: SAUCE: ceph: drop messages from MDS when unmounting 862a1e3c2a UBUNTU: SAUCE: ceph: update documentation regarding snapshot naming limitations 904f39f283 UBUNTU: SAUCE: ceph: prevent snapshot creation in encrypted locked directories a47bdc0f8a UBUNTU: SAUCE: ceph: add support for encrypted snapshot names e4202a1c3e UBUNTU: SAUCE: ceph: invalidate pages when doing direct/sync writes 9f781cfb0d UBUNTU: SAUCE: ceph: plumb in decryption during reads e76383977f UBUNTU: SAUCE: ceph: add encryption support to writepage and writepages 0b571b2ac0 UBUNTU: SAUCE: ceph: add read/modify/write to ceph_sync_write a81bd5f1c8 UBUNTU: SAUCE: ceph: align data in pages in ceph_sync_write edbe3d2a62 UBUNTU: SAUCE: ceph: don't use special DIO path for
[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-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 OEM Priority Project: 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 Released Status in linux source package in Lunar: Won't Fix 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 Released 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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
This bug is awaiting verification that the linux-azure/6.5.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If the problem still exists, change the tag
'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-
linux-azure'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-mantic-linux-azure-v2
verification-needed-mantic-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2043730] Re: Update io_uring to 6.6
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043730 Title: Update io_uring to 6.6 Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] io_uring is a fast-developed subsystem in the Linux kernel. In order to keep up with the latest changes such that applying further fixes are possible, it should be updated to a more recent version. [Test case] Given the general update, there are no specific test cases. [Potential regression] io_uring users only would be affected given most changes are restricted to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043730/+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
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-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 Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released 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 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-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: Fix Released 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 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043786 Title: RTL8111EPP: Fix the network lost after resume with DASH 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released 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 Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] On the system installed RTL8111EPP with DASH, unable to get the network back upon system resume [Fix] handle DASH during system suspend and resume. [Test] Vendor tested on hardware, the ethernet is OK after resume. [Where problems could occur] It may break r8169 driver. No SRU for Jammy 5.15 kernel due to too many commits are needed to backport to support DASH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2044131] Re: i915 regression introduced with 5.5 kernel
This bug is awaiting verification that the linux/5.15.0-100.110 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' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2044131 Title: i915 regression introduced with 5.5 kernel Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.15 source package in Focal: Triaged Status in linux source package in Jammy: Fix Committed Status in linux-hwe-5.15 source package in Jammy: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-hwe-5.15 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-hwe-5.15 source package in Noble: Invalid Bug description: [ Impact ] Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks which have been proven invalid for at least some hardware setups. A user trying to run Focal with HWE 5.15 kernel is not able to get any video output. After going through bisection between 5.4 and 5.5 this commit was identified. Reverting it on top of Focal HWE kernel fixes the issue. The issue has been addressed upstream in DRM tree (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d). dmesg and lspci from the affected configuration are attached to this bug. [ Test Plan ] 1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or higher. 2. Wait until boot finishes and see the blank screen. Actual result: there is no video output visible. Expected result: normal boot process should be visible (e.g. splash), then GUI should appear. [ Where problem could occur ] This bug was a result of assumptions in the checks that turned out to be not valid for some hardware. The checks were removed from global intel_mode_valid function and moved into connector specific .mode_valid() hooks, entirely skiping BXT/GLK DSI connectors. This should keep the checks where appropriate and skip for hardware that does not comply to them. [ Other info ] Original bug description: There is a regression preventing a user to upgrade from 5.4 kernel to anything that's higher than 5.5. When using such kernel the image orientation is wrong (rotated by 90°C). Also the kernel log contains: wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06 wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25 wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga console wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory information wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:o> wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v> wrz 15 09:19:49 desktop kernel: wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.> wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]' (full stack trace attached) The video hardware in use is: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) (...) Kernel driver in use: i915 Kernel modules: i915 The user wanted to upgrade from bionic to focal with HWE kernel (they needed it due to some networking hardware they wanted to have supported by the newer kernel). The user was testing mainline stable kernels and noticed that the last working kernel was the 5.4 series, while anything starting from 5.5 and above is BROKEN (symptoms as described in the first paragraph above). Together with the user we have run a bisection between v5.4 and v5.5 on the upstream stable kernel and we were able to identify the first broken commit to be:
[Kernel-packages] [Bug 2045796] Re: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045796 Title: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Confirmed Bug description: [IMPACT] This is requested by one of our larger server hardware partners and Broadcom to to update the bnxt_en network driver code to add some bug fixes and support for the newer 5760X adapters into Mantic. The goal is to have these land in 22.04.4 HWE and the installer environment via the HWE kernel. Missing these patches will mean customers running this hardware will not be able to use it with Ubuntu Server 22.04 LTS until the much later 22.04.5 point release, setting up a months-long gap in support for these adapters. [FIXES] These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and pick cleanly with the exception of the two noted at the end of this section. For Mantic all are picked. For Noble, only the subset currently in linux-next will be picked, depending on what happens in our Noble tree during the cycle. d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions 8243345bfaec bnxt_en: Refactor RSS capability fields d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism on P7 chips d3c16475dc06 bnxt_en: Consolidate DB offset calculation a432a45bdba4 bnxt_en: Define basic P7 macros 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 08b386b132c6 bnxt_en: Fix backing store V2 logic 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters 5d4e1bf60664
[Kernel-packages] [Bug 2044512] Re: Build failure if run in a console
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2044512 Title: Build failure if run in a console Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Confirmed Bug description: [Impact] Build fails if run in a console: $ debian/rules binary ... # Compress kernel modules find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 -P 8 zstd -19 --quiet --rm stdout is a console, aborting make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123 [Test Case] See above. [Where Problems Could Occur] Build failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044512/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow
This bug is awaiting verification that the linux-azure/6.5.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If the problem still exists, change the tag
'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-
linux-azure'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-mantic-linux-azure-v2
verification-needed-mantic-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2043841
Title:
kernel BUG: io_uring openat triggers audit reference count underflow
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Released
Bug description:
I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
occurs during io_uring openat audit processing. I have a kernel patch
that was accepted into the upstream kernel as well as the v6.6,
v6.5.9, and v6.1.60 releases. The bug was first introduced in the
upstream v5.16 kernel.
I do not see the change yet in:
* The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel
repository.
* The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.
Can this upstream commit be cherry picked?
The upstream commit is:
03adc61edad49e1bbecfb53f7ea5d78f398fe368
The upstream patch thread is:
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u
The maintainer pull request thread is:
https://lore.kernel.org/lkml/20231019-kampfsport-
metapher-e5211d7be247@brauner
The pre-patch discussion thread is:
https://lore.kernel.org/io-
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u
The commit log message is:
commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
Author: Dan Clash
Date: Thu Oct 12 14:55:18 2023 -0700
audit,io_uring: io_uring openat triggers audit reference count
underflow
An io_uring openat operation can update an audit reference count
from multiple threads resulting in the call trace below.
A call to io_uring_submit() with a single openat op with a flag of
IOSQE_ASYNC results in the following reference count updates.
These first part of the system call performs two increments that
do not race.
do_syscall_64()
__do_sys_io_uring_enter()
io_submit_sqes()
io_openat_prep()
__io_openat_prep()
getname()
getname_flags() /* update 1 (increment) */
__audit_getname() /* update 2 (increment) */
The openat op is queued to an io_uring worker thread which starts the
opportunity for a race. The system call exit performs one decrement.
do_syscall_64()
syscall_exit_to_user_mode()
syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
audit_reset_context()
putname() /* update 3 (decrement) */
The io_uring worker thread performs one increment and two decrements.
These updates can race with the system call decrement.
io_wqe_worker()
io_worker_handle_work()
io_wq_submit_work()
io_issue_sqe()
io_openat()
io_openat2()
do_filp_open()
path_openat()
__audit_inode() /* update 4 (increment) */
putname() /* update 5 (decrement) */
__audit_uring_exit()
audit_reset_context()
putname() /* update 6 (decrement) */
The fix is to change the refcnt member of struct audit_names
from int to atomic_t.
kernel BUG at fs/namei.c:262!
Call Trace:
...
? putname+0x68/0x70
audit_reset_context.part.0.constprop.0+0xe1/0x300
__audit_uring_exit+0xda/0x1c0
io_issue_sqe+0x1f3/0x450
? lock_timer_base+0x3b/0xd0
io_wq_submit_work+0x8d/0x2b0
? __try_to_del_timer_sync+0x67/0xa0
io_worker_handle_work+0x17c/0x2b0
io_wqe_worker+0x10a/0x350
Cc: sta...@vger.kernel.org
Link:
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support
to io_uring")
Signed-off-by: Dan Clash
[Kernel-packages] [Bug 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed 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 2046105] Re: Sound: Add rtl quirk of M90-Gen5
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046105 Title: Sound: Add rtl quirk of M90-Gen5 Status in HWE Next: Fix Committed 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: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix 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 Released 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] When plugin the headset jack, only speaker is identified. [Fix] Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work. [Test] Vendor tested on hardware, headset mic works fine. [Where problems could occur] It may break audio. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046105/+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 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2045958 Title: Avoid using damage rectangle under hardware rotation mode when PSR is enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released 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 Released 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: Confirmed 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] When hardware rotation feature is used by compositor, the clip damage on cursor plane causes screen glitches on AMD platforms with PSR panel. [Fix] Disable clip damage when hardware rotation is used. [Test] With the patch applied, the issue can't be observed when the screen is rotated 180 degree. 90 and 270 degrees are unaffected since no compositor is using hardware rotation for those two angles. [Where problems could occur] The power consumption in theory will higher for 180 degree rotation because now the full screen may need to be redrawn when cursor moves. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045958/+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 2046217] Re: Some machines can't pass the pm-graph test
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046217 Title: Some machines can't pass the pm-graph test Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: New Status in linux-signed-hwe-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux-hwe-6.5 source package in Jammy: Fix Released Status in linux-signed-hwe-6.5 source package in Jammy: Confirmed Status in linux source package in Mantic: Fix Released Status in linux-hwe-6.5 source package in Mantic: New Status in linux-signed-hwe-6.5 source package in Mantic: New Status in linux source package in Noble: Confirmed Status in linux-hwe-6.5 source package in Noble: New Status in linux-signed-hwe-6.5 source package in Noble: In Progress Bug description: == SRU Justification == [Impact] When iwlwifi firmware causes the WiFi NIC dropped off PCI bus on system resume, NULL pointer dereference occurs and the system stops working. [Fix] Rescan the bus in order to reprobe the device to avoid mac80211 layer gets messed up. [Test] With the fix in place, system keeps working after firmware issue occurs. Verified with thousand times of suspend. [Where problems could occur] If the firmware/hardware is really dead and beyond recoverable, the same process can be triggered again and again. == Original bug report == During the jammy-hwe migration test, I found some machines failed to run the pm-graph. test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604) One of machine when I rerun it locally, it passed, but others are still failed. Following are the machines failed to run pm-graph. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201702-25401/ https://certification.canonical.com/hardware/202002-27718/ https://certification.canonical.com/hardware/201711-25989/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Tue Dec 12 02:48:24 2023 InstallationDate: Installed on 2023-02-22 (293 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046217/+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 2047382] Re: Hotplugging SCSI disk in QEMU VM fails
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047382 Title: Hotplugging SCSI disk in QEMU VM fails Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: In Progress Bug description: [Impact] Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest kernels >= 6.5 might be broken. The inconsistency suggests a potential race condition. [Fix] Reverting the two specified commits appears to restore reliability. == cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only for non-root bus 40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary == Upstream has resolved the issue by reverting both commits through a commit placed below. == 5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary == [Test Plan] 1. Create a VM virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0 2. Prepare two XMLs for adding two disk devices # cat disk_X.xml 3. Hotplug disks and check for success virsh attach-device scsi_test disk_X.xml [Where problems could occur] The patch reverts two commits that previously addressed long-standing issues related to hotplugging devices with large BARs. While this reversion may reintroduce legacy issues, it does not introduce new problems. The associated risks are deemed low, making it worthwhile to address timing issues during the hotplugging of SCSI disks in QEMU VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047382/+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 2047389] Re: Fix AMDGPU crash on 6.5 kernel
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047389 Title: Fix AMDGPU crash on 6.5 kernel Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] AMD GPU crash with a message: " cp queue preemption timeout". [Fix] Disable MCBP(mid command buffer preemption) by default as old Mesa hangs with it. [Test] Tested on hardware, play web video for more than 1 hour OK. [Where problems could occur] It may break AMD GPU. This issue is only reproduced on v6.5+ kernel versions and fixes in v6.6, so SRU for oem-6.5, mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047389/+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 2047398] Re: Add missing RPL P/U CPU IDs
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs 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: Fix Released Status in linux source package in Mantic: Fix Released 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] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+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 2047461] Re: drm: Update file owner during use
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047461 Title: drm: Update file owner during use Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients' 2. runs glxgears(specify the GPU if needed) 3. check the precesses again and there should be a 'glxgears' process [Where problems could occur] This commit added some protections on read/write and only changes the process' pid, the worst case is that the process got the wrong pid as its owner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047461/+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 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux/5.15.0-100.110 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' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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-v2 verification-needed-jammy-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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2047518] Re: Fix BCM57416 lost after resume
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047518 Title: Fix BCM57416 lost after resume Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released 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] BCM57416 is lost after resume. Error log: [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 0x125d error 0x4 [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 failed. rc:ffe4 err:4 [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure rc: fffb [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb [Fix] Clear the reservations in driver after reset the ethernet card. [Test] Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works fine. [Where problems could occur] It may break broadcom bnxt driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047518/+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 2048078] Re: Add support of MTL audio of Lenovo
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048078 Title: Add support of MTL audio of Lenovo Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released 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] On Lenovo ThinkPad MTL platform, the audio and mic are not working. Error Logs: [ 22.098899] sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA path [ 22.107925] sof-audio-pci-intel-mtl :00:1f.3: no matching blob for sample rate: 48000 sample width: 32 channels: 2 [ 22.107931] sof-audio-pci-intel-mtl :00:1f.3: failed to prepare widget dai-copier.DMIC.dmic01.capture [ 22.107933] sof-audio-pci-intel-mtl :00:1f.3: Failed to prepare connected widgets [ 22.107935] sof-audio-pci-intel-mtl :00:1f.3: error: failed widget list set up for pcm 6 dir 1 [ 22.107937] sof-audio-pci-intel-mtl :00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on :00:1f.3: -22 [Fix] Commit: "ALSA: hda: intel-nhlt: Ignore vbps when looking for DMIC 32 bps format" Add support of both 24 bit and 32 bit of DMIC hardware. [Test] Tested on hardware, sound ouput and DMIC input work fine. [Where problems could occur] It may break sound driver. MTL is not supported by 5.15 and 6.2 kernel, SRU for oem-6.5, 6.5 and 6.6. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2048078/+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 2048404] Re: Don't WARN_ON_ONCE() for a broken discovery table
This bug is awaiting verification that the linux/5.15.0-100.110 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' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.
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-v2 verification-needed-jammy-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/2048404
Title:
Don't WARN_ON_ONCE() for a broken discovery table
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Won't Fix
Bug description:
SRU Justification
[Impact]
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] [ cut here ]
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/x86/events/intel/uncore_discovery.c:184
intel_uncore_has_discovery_tables+0x4c0/0x65c
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.17-2136.313.1-X10-2c+ #4
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 ('perf/x86/uncore:
Don't WARN_ON_ONCE() for a broken discovery table')
[Test]
AWS tested
[Regression potential]
Low regression potential. Only the code that prints the warning has
been changed.
[Other Info]
SF: #00347830
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048404/+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 2052453] Re: Azure: Fix regression introduced in LP: #2045069
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052453 Title: Azure: Fix regression introduced in LP: #2045069 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] Microsoft requested the addition of 3 patches in LP: #2045069. A regression was discovered in Focal. [Fix] hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove [Test Case] Microsoft tested [Regression Potential] hv_netvsc could still have a modprobe race. [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052453/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
This bug is awaiting verification that the linux/5.15.0-100.110 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' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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-v2 verification-needed-jammy-linux -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2049689] Re: partproke is broken on empty loopback device
This bug is awaiting verification that the linux/5.15.0-100.110 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' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.
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-v2 verification-needed-jammy-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/2049689
Title:
partproke is broken on empty loopback device
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
SRU Justification:
[Impact]
* BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
but now returns EINVAL, breaking partprobe due to commit
"block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
introduced in mantic 6.5.0-17 and jammy 5.15.0-94.
[Fix]
* backport commit
"block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"
[Test Plan]
* dd if=/dev/zero of=/tmp/foo bs=1M count=50
* partprobe $(losetup --find --show /tmp/foo)
Before the fix this fails.
After the fix it should work.
[Where problems could occur]
* We may see issues on disk partitions operations.
Old description:
This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic
5.15.0-94.104).
Do this:
# dd if=/dev/zero of=/tmp/file bs=1M count=50
# partprobe "$(losetup --show --find /tmp/file)"
Notice this very odd error message:
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
/dev/loop2 have been written, but we have been unable to inform the
kernel of the change, probably because it/they are in use. As a
result, the old partition(s) will remain in use. You should reboot
now before making further changes.
That's a result of an ioctl changing its error code in an incompatible
way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
partprobe.
5.15.0.91.88:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or
address)
5.15.0.94.91:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
This is a userspace API break which impacts GNU parted and util-linux
(as confirmed by the util-linux maintainer).
This issue was discovered as part of Cockpit CI here:
https://github.com/cockpit-project/bots/pull/5793
This issue is being discussed on LKML here (with a patch likely to
land soon): https://lkml.org/lkml/2024/1/15/147
lsb_release -rd:
Description: Ubuntu 22.04.3 LTS
Release: 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+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 2052519] Re: Azure: Fix TDX regressions in Azure 6.5
This bug is awaiting verification that the linux-azure/6.5.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052519 Title: Azure: Fix TDX regressions in Azure 6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] TDX support in Microsoft Azure kernels based on 6.5 has regressed from 6.2. Microsoft has provided a backport that brings TDX functionality back to that of Azure 6.2. [Test Case] Microsoft tested [Regression Potential] TDX support has been backported from Linux v6.6, so there could be some lingering issues. [Other Information] SF: #00378027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052519/+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 2052696] Re: [UBUNTU 24.04] Haskell LLVM Backend: Objects of data section are missing alignment
Hi Simon, no, it's of course not. The LP bug is pretty new (came in today) and I didn't had a chance to properly triage it. Will do it right now ... ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ghc (Ubuntu) Status: New => Triaged ** Tags added: noble -- 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/2052696 Title: [UBUNTU 24.04] Haskell LLVM Backend: Objects of data section are missing alignment Status in Ubuntu on IBM z Systems: Triaged Status in ghc package in Ubuntu: Triaged Bug description: Description: Objects of the data section may be accessed through tagged pointers. Thus, those objects require a minimal alignment of 8 byte on a 64-bit architecture. Otherwise, this may lead to undefined behavior. Solution: commit https://gitlab.haskell.org/ghc/ghc/-/commit/dfe1c3540e4b519b62b862b5966dfec5cae9ece1 This patch resolves the alignment issue for all targets utilizing the LLVM backend. The fix was backported by upstream for ghc release 9.6 and 9.8 but not for 9.4.x which has landed in Noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2052696/+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 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot
Hello. Any updates on this? -- 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/2008157 Title: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: SRU Justification: [Impact] When booted into Ubuntu 22.04.1 OS after installation, observed "Array Index out of bounds" Call Trace multiple times in dmesg. Call Trace is as follow: [ 6.125704] UBSAN: array-index-out-of-bounds in /build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32 [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic #59-Ubuntu [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022 [ 6.125710] Workqueue: events work_for_cpu_fn [ 6.125716] Call Trace: [ 6.125718] [ 6.125720] show_stack+0x52/0x5c [ 6.125725] dump_stack_lvl+0x4a/0x63 [ 6.125731] dump_stack+0x10/0x16 [ 6.125732] ubsan_epilogue+0x9/0x49 [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas] [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas] [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas] [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas] [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas] [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas] [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas] [ 6.125779] local_pci_probe+0x48/0x90 [ 6.125783] work_for_cpu_fn+0x17/0x30 [ 6.125785] process_one_work+0x228/0x3d0 [ 6.125786] worker_thread+0x223/0x420 [ 6.125787] ? process_one_work+0x3d0/0x3d0 [ 6.125788] kthread+0x127/0x150 [ 6.125790] ? set_kthread_struct+0x50/0x50 [ 6.125791] ret_from_fork+0x1f/0x30 [ 6.125796] [ 6.125796] Steps to reproduce: 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation 5. Multiple Call Traces of "array-index-out-of-bounds" are seen Expected Behavior: OS should boot without this Call Trace [Fix] [PATCH v3 0/6] Replace one-element arrays with flexible-array members https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/ 48658213 scsi: megaraid_sas: Use struct_size() in code related to struct MR_PD_CFG_SEQ_NUM_SYNC 41e83026 scsi: megaraid_sas: Use struct_size() in code related to struct MR_FW_RAID_MAP ee92366a scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_PD_CFG_SEQ_NUM_SYNC eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_DRV_RAID_MAP 204a29a1 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP_DYNAMIC ac23b92b scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP [Test Plan] 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation OS should boot without the Call Trace listed in the Impact field [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157/+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 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
Kernel source tree is here, but note that if it's there, it does not say when it's gonna be released. https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/log/?h=hwe-6.5-next -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
Hi everyone! Could you verify the kernel in proposed, see above message? So that we can release this kernel to -updates? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052710] Re: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subp
** Tags removed: need-duplicate-check -- 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/2052710 Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-6.5 package in Ubuntu: New Bug description: I do not know any other details about the issue. I was away from my computer. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 8 06:44:58 2024 ErrorMessage: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-04 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-hwe-6.5 Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2052710/+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 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
Confirmed the fix has been applied to 24.04 Noble linux 6.8 repository: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?h=master- next=04be82f0a7b12d0064afc919098f831ce79ba24f As soon as the kernel is promoted to the noble-release pocket the bug report will be updated automatically. -- 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/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 2052696] Re: [UBUNTU 24.04] Haskell LLVM Backend: Objects of data section are missing alignment
I might be missing something, but I don't think that's related to the kernel? ** Also affects: ghc (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/2052696 Title: [UBUNTU 24.04] Haskell LLVM Backend: Objects of data section are missing alignment Status in ghc package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Description: Objects of the data section may be accessed through tagged pointers. Thus, those objects require a minimal alignment of 8 byte on a 64-bit architecture. Otherwise, this may lead to undefined behavior. Solution: commit https://gitlab.haskell.org/ghc/ghc/-/commit/dfe1c3540e4b519b62b862b5966dfec5cae9ece1 This patch resolves the alignment issue for all targets utilizing the LLVM backend. The fix was backported by upstream for ghc release 9.6 and 9.8 but not for 9.4.x which has landed in Noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghc/+bug/2052696/+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 2052710] [NEW] package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script su
Public bug reported: I do not know any other details about the issue. I was away from my computer. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 8 06:44:58 2024 ErrorMessage: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-04 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-hwe-6.5 Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052710 Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-6.5 package in Ubuntu: New Bug description: I do not know any other details about the issue. I was away from my computer. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 8 06:44:58 2024 ErrorMessage: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-04 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-hwe-6.5 Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2052710/+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 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
** Changed in: linux-firmware (Ubuntu Noble)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2051636
Title:
AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress
loading
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
within a few minutes or sometimes even quicker
[Fix]
Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and
other prerequisites:
* amdgpu/gc_11_0_1_* up to commit 56c0e7e ("amdgpu: update GC 11.0.1
firmware")
* amdgpu/psp_13_0_4_ta.bin up to commit ed7ddfb ("amdgpu: update PSP 13.0.4
firmware")
* amdgpu/vcn_4_0_2.bin up to commit 34ccb75 ("amdgpu: update VCN 4.0.2
firmware")
* amdgpu/gc_11_0_4_* up to commit 680d98c ("amdgpu: update GC 11.0.4
firmware")
* amdgpu/psp_13_0_11_ta.bin up to commit 72227fe ("amdgpu: update PSP 13.0.11
firmware")
[Test Case]
Run stress tool like 3DMark or GravityMark.
[Where problems could occur]
Binary firmware update recommended by chip vendor. No known issue so
far.
[Other Info]
Phoenix is supported in linux-oem-6.5/jammy, so linux-firmware/jammy
is also nominated for fix.
== original bug report ==
With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
within a few minutes or sometimes even quicker. Also using mantic +
v6.7 hit the hang, so need to update new FWs to fix this issue.
PHX series
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=680d98c62b13bd441949280c77ca31efb021b68a
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=72227fe463af85648523300543287a68e6c6de5f
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=56c0e7e688427270729fce6e85ecd98f1fe2a6e1
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ed7ddfb5d136c3b9b1eeb48f7568550c0e5d99da
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=34ccb7502e075607682f0f0984a83022bfa0da85
[ 415.782623] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0
timeout, signaled seq=27035, emitted seq=27037
[ 415.782833] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process gnome-shell pid 1361 thread gnome-shel:cs0 pid 1421
[ 415.783004] amdgpu :0d:00.0: amdgpu: GPU reset begin!
[ 415.944129] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 415.944317] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.074161] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.074327] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.204184] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.204356] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.334204] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.334377] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.464226] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.464398] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.594247] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.594418] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.724265] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.724432] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.854275] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.854437] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.984284] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.984456] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.996743] amdgpu :0d:00.0: amdgpu: MODE2 reset
[ 417.026498] amdgpu :0d:00.0: amdgpu: GPU reset succeeded,
[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Won't Fix
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
In Progress
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2048977
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
'hot reset' assert
2nd PCIe reset' assert
Asmedia 'hot reset' deassert
PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
5217b76bed90 ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37")
324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0:
update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") to forfill git
history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes
from suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2024427 Title: S3 stress issue for amdgpu Navi 31/Navi33 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware 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: Won't Fix Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2024427 [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. [Fix] kernel patches: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 firmware patches: * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to be fixed. For the firmware parts, they have been included in linux-firmware/mantic, leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2024470] Re: Mantic update: v6.3.7 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2024470 Title: Mantic update: v6.3.7 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.3.7 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024470/+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 2024469] Re: Mantic update: v6.3.6 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2024469 Title: Mantic update: v6.3.6 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.3.6 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024469/+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 2028251] Re: Mantic update: v6.4.4 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2028251 Title: Mantic update: v6.4.4 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.4 upstream stable release from git://git.kernel.org/ Linux 6.4.4 sh: hd64461: Handle virq offset for offchip IRQ base and HD64461 IRQ sh: mach-dreamcast: Handle virq offset in cascaded IRQ demux sh: mach-highlander: Handle virq offset in cascaded IRL demux sh: mach-r2d: Handle virq offset in cascaded IRL demux block/partition: fix signedness issue for Amiga partitions io_uring: Use io_schedule* in cqring wait tty: serial: fsl_lpuart: add earlycon for imx8ulp platform wireguard: netlink: send staged packets when setting initial private key wireguard: queueing: use saner cpu selection wrapping netfilter: nf_tables: prevent OOB access in nft_byteorder_eval netfilter: nf_tables: do not ignore genmask when looking up chain by id netfilter: conntrack: Avoid nf_ct_helper_hash uses after free drm/amdgpu: check RAS irq existence for VCN/JPEG drm/amd/pm: add abnormal fan detection for smu 13.0.0 drm/amdgpu/sdma4: set align mask to 255 drm/amd/pm: revise the ASPM settings for thunderbolt attached scenario drm/amdgpu: Skip mark offset for high priority rings drm/amdgpu: make sure that BOs have a backing store drm/amdgpu: make sure BOs are locked in amdgpu_vm_get_memory LoongArch: Include KBUILD_CPPFLAGS in CHECKFLAGS invocation ovl: fix null pointer dereference in ovl_get_acl_rcu() ovl: let helper ovl_i_path_real() return the realinode ovl: fix null pointer dereference in ovl_permission() kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS kbuild: Add KBUILD_CPPFLAGS to as-option invocation kbuild: Add CLANG_FLAGS to as-instr powerpc/vdso: Include CLANG_FLAGS explicitly in ldflags-y mips: Include KBUILD_CPPFLAGS in CHECKFLAGS invocation Input: ads7846 - fix pointer cast warning fs: no need to check source md/raid1-10: fix casting from randomized structure in raid1_submit_write() Input: ads7846 - Fix usage of match data blktrace: use inline function for blk_trace_remove() while blktrace is disabled leds: trigger: netdev: Recheck NETDEV_LED_MODE_LINKUP on dev rename ARM: orion5x: fix d2net gpio initialization ARM: dts: qcom: ipq4019: fix broken NAND controller properties override ARM: dts: qcom: msm8660: Fix regulator node names regulator: tps65219: Fix matching interrupts for their regulators ASoC: mediatek: mt8173: Fix snd_soc_component_initialize error path ASoC: mediatek: mt8173: Fix irq error path btrfs: do not BUG_ON() on tree mod log failure at __btrfs_cow_block() btrfs: fix extent buffer leak after tree mod log failure at split_node() btrfs: add missing error handling when logging operation while COWing extent buffer btrfs: fix race when deleting quota root from the dirty cow roots list btrfs: reinsert BGs failed to reclaim btrfs: add block-group tree to lockdep classes btrfs: bail out reclaim process if filesystem is read-only btrfs: delete unused BGs while reclaiming BGs btrfs: warn on invalid slot in tree mod log rewind btrfs: insert tree mod log move in push_node_left btrfs: fix dirty_metadata_bytes for redirtied buffers btrfs: add handling for RAID1C23/DUP to btrfs_reduce_alloc_profile ipvs: increase ip_vs_conn_tab_bits range for 64BIT usb: typec: ucsi: Mark dGPUs as DEVICE scope fs: Lock moved directories fs: Establish locking order for unrelated directories Revert "udf: Protect rename against modification of moved directory" Revert "f2fs: fix potential corruption when moving a directory" ext4: Remove ext4 locking of moved directory fs: avoid empty option when generating legacy mount string jffs2: reduce stack usage in jffs2_build_xattr_subsystem() nfsd: use vfs setgid helper shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs mm/damon/ops-common: atomically test and clear young on ptes and pmds autofs: use flexible array in ioctl structure integrity: Fix possible multiple allocation in integrity_inode_get() um: Use HOST_DIR for mrproper watch_queue: prevent dangling pipe pointer bcache:
[Kernel-packages] [Bug 2024471] Re: Mantic update: v6.3.8 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2024471 Title: Mantic update: v6.3.8 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.3.8 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024471/+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 2028791] Re: Mantic update: v6.4.6 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2028791 Title: Mantic update: v6.4.6 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.6 upstream stable release from git://git.kernel.org/ Linux 6.4.6 x86/cpu/amd: Add a Zenbleed fix x86/cpu/amd: Move the errata checking functionality up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028791/+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 2028790] Re: Mantic update: v6.4.5 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2028790 Title: Mantic update: v6.4.5 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.5 upstream stable release from git://git.kernel.org/ Linux 6.4.5 net/ncsi: change from ndo_set_mac_address to dev_set_mac_address net/ncsi: make one oem_gma function for all mfr id drm/atomic: Fix potential use-after-free in nonblocking commits Revert "drm/amd: Disable PSR-SU on Parade 0803 TCON" MIPS: kvm: Fix build error with KVM_MIPS_DEBUG_COP0_COUNTERS enabled net: dsa: ocelot: unlock on error in vsc9959_qos_port_tas_set() scsi: qla2xxx: Fix end of loop test scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue scsi: qla2xxx: Pointer may be dereferenced scsi: qla2xxx: Correct the index of array scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport() scsi: qla2xxx: Fix potential NULL pointer dereference scsi: qla2xxx: Fix buffer overrun scsi: qla2xxx: Avoid fcport pointer dereference scsi: qla2xxx: Array index may go out of bound scsi: qla2xxx: Fix mem access after free scsi: qla2xxx: Wait for io return on terminate rport scsi: qla2xxx: Fix hang in task management scsi: qla2xxx: Fix task management cmd fail due to unavailable resource scsi: qla2xxx: Fix task management cmd failure scsi: qla2xxx: Multi-que support for TMF tracing/user_events: Fix struct arg size match check tracing/probes: Fix to record 0-length data_loc in fetch_store_string*() if fails Revert "tracing: Add "(fault)" name injection to kernel probes" tracing/probes: Fix to update dynamic data counter if fetcharg uses it tracing/probes: Fix not to count error code to total length tracing/probes: Fix to avoid double count of the string length on the array smb: client: Fix -Wstringop-overflow issues selftests: mptcp: pm_nl_ctl: fix 32-bit support selftests: mptcp: depend on SYN_COOKIES selftests: mptcp: userspace_pm: report errors with 'remove' tests selftests: mptcp: userspace_pm: use correct server port selftests: mptcp: sockopt: return error if wrong mark selftests: mptcp: connect: fail if nft supposed to work selftests: mptcp: sockopt: use 'iptables-legacy' if available mptcp: ensure subflow is unhashed before cleaning the backlog mptcp: do not rely on implicit state check in mptcp_listen() tracing: Fix null pointer dereference in tracing_err_log_open() fprobe: Ensure running fprobe_exit_handler() finished before calling rethook_free() fprobe: Release rethook after the ftrace_ops is unregistered accel/ivpu: Clear specific interrupt status bits on C0 accel/ivpu: Fix VPU register access in irq disable pwm: meson: fix handling of period/duty if greater than UINT_MAX pwm: meson: modify and simplify calculation in meson_pwm_get_state PM: QoS: Restore support for default value on frequency QoS perf/x86: Fix lockdep warning in for_each_sibling_event() on SPR xtensa: ISS: fix call to split_if_spec cifs: if deferred close is disabled then close files immediately drm/amd/pm: conditionally disable pcie lane/speed switching for SMU13 drm/amd/pm: share the code around SMU13 pcie parameters update ftrace: Fix possible warning on checking all pages used in ftrace_process_locs() ring-buffer: Fix deadloop issue on reading trace_pipe net: ena: fix shift-out-of-bounds in exponential backoff regmap-irq: Fix out-of-bounds access when allocating config buffers perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start() samples: ftrace: Save required argument registers in sample trampolines nvme: don't reject probe due to duplicate IDs for single-ported PCIe devices tracing: Fix memory leak of iter->temp when reading trace_pipe tracing/histograms: Add histograms to hist_vars if they have referenced variables dm: verity-loadpin: Add NULL pointer check for 'bdev' parameter s390/decompressor: fix misaligned symbol build error bus: ixp4xx: fix IXP4XX_EXP_T1_MASK Revert "8250: add support for ASIX devices with a FIFO bug" media: uapi: Fix [GS]_ROUTING ACTIVE flag value soundwire: qcom: fix storing port config out-of-bounds opp: Fix
[Kernel-packages] [Bug 2028249] Re: Mantic update: v6.4.2 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2028249 Title: Mantic update: v6.4.2 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.2 upstream stable release from git://git.kernel.org/ Linux 6.4.2 arch/arm64/mm/fault: Fix undeclared variable error in do_page_fault() drm/amdgpu: Validate VM ioctl flags. dm ioctl: Avoid double-fetch of version docs: Set minimal gtags / GNU GLOBAL version to 6.6.5 scripts/tags.sh: Resolve gtags empty index generation hugetlb: revert use of page_cache_next_miss() nubus: Partially revert proc_create_single_data() conversion Revert "cxl/port: Enable the HDM decoder capability for switch ports" nfs: don't report STATX_BTIME in ->getattr execve: always mark stack as growing down during early stack setup PCI/ACPI: Call _REG when transitioning D-states PCI/ACPI: Validate acpi_pci_set_power_state() parameter tools/nolibc: x86_64: disable stack protector for _start xtensa: fix lock_mm_and_find_vma in case VMA not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028249/+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 2028250] Re: Mantic update: v6.4.3 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2028250 Title: Mantic update: v6.4.3 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.3 upstream stable release from git://git.kernel.org/ Linux 6.4.3 fork: lock VMAs of the parent process when forking bootmem: remove the vmemmap pages from kmemleak in free_bootmem_page mm: call arch_swap_restore() from do_swap_page() mm: lock newly mapped VMA with corrected ordering mm: lock newly mapped VMA which can be modified after it becomes visible mm: lock a vma before stack expansion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028250/+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 2028247] Re: Mantic update: v6.4.1 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => 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/2028247 Title: Mantic update: v6.4.1 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.4.1 upstream stable release from git://git.kernel.org/ x86/microcode/AMD: Load late on both threads too x86/smp: Make stop_other_cpus() more robust x86/smp: Dont access non-existing CPUID leaf x86/smp: Remove pointless wmb()s from native_stop_other_cpus() x86/smp: Use dedicated cache-line for mwait_play_dead() x86/smp: Cure kexec() vs. mwait_play_dead() breakage cpufreq: amd-pstate: Make amd-pstate EPP driver name hyphenated can: isotp: isotp_sendmsg(): fix return error fix on TX path maple_tree: fix potential out-of-bounds access in mas_wr_end_piv() mm: introduce new 'lock_mm_and_find_vma()' page fault helper mm: make the page fault mmap locking killable arm64/mm: Convert to using lock_mm_and_find_vma() powerpc/mm: Convert to using lock_mm_and_find_vma() mips/mm: Convert to using lock_mm_and_find_vma() riscv/mm: Convert to using lock_mm_and_find_vma() arm/mm: Convert to using lock_mm_and_find_vma() mm/fault: convert remaining simple cases to lock_mm_and_find_vma() powerpc/mm: convert coprocessor fault to lock_mm_and_find_vma() mm: make find_extend_vma() fail if write lock not held execve: expand new process stack manually ahead of time mm: always expand the stack with the mmap write lock held HID: wacom: Use ktime_t rather than int when dealing with timestamps gup: add warning if some caller would seem to want stack expansion mm/khugepaged: fix regression in collapse_file() fbdev: fix potential OOB read in fast_imageblit() HID: hidraw: fix data race on device refcount HID: logitech-hidpp: add HIDPP_QUIRK_DELAYED_INIT for the T651. Revert "thermal/drivers/mediatek: Use devm_of_iomap to avoid resource leak in mtk_thermal_probe" sparc32: fix lock_mm_and_find_vma() conversion parisc: fix expand_stack() conversion csky: fix up lock_mm_and_find_vma() conversion xtensa: fix NOMMU build with lock_mm_and_find_vma() conversion Linux 6.4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028247/+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 2052599] Re: Jammy update: v6.1.74 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- 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/2052599 Title: Jammy update: v6.1.74 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.74 upstream stable release from git://git.kernel.org/ Linux 6.1.74 scripts/decode_stacktrace.sh: optionally use LLVM utilities coresight: etm4x: Fix width of CCITMIN field PCI: Add ACS quirk for more Zhaoxin Root Ports leds: ledtrig-tty: Free allocated ttyname buffer on deactivate parport: parport_serial: Add Brainboxes device IDs and geometry parport: parport_serial: Add Brainboxes BAR details uio: Fix use-after-free in uio_open binder: fix comment on binder_alloc_new_buf() return value binder: fix trivial typo of binder_free_buf_locked() binder: fix use-after-free in shinker's callback binder: use EPOLLERR from eventpoll.h Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d" ksmbd: free ppace array on error in parse_dacl ksmbd: don't allow O_TRUNC open on read-only share bpf: Add --skip_encoding_btf_inconsistent_proto, --btf_gen_optimized to pahole flags for v1.25 btf, scripts: Exclude Rust CUs with pahole ASoC: SOF: Intel: hda-codec: Delay the codec device registration ACPI: resource: Add another DMI match for the TongFang GMxXGxx ALSA: hda/realtek: Fix mute and mic-mute LEDs for HP Envy X360 13-ay0xxx drm/crtc: fix uninitialized variable use ARM: sun9i: smp: fix return code check of of_property_match_string net: qrtr: ns: Return 0 if server port is not present virtio_blk: fix snprintf truncation compiler warning ida: Fix crash in ida_free when the bitmap is empty pinctrl: cy8c95x0: Fix get_pincfg pinctrl: cy8c95x0: Fix typo drm/amd/display: get dprefclk ss info from integration info table i2c: rk3x: fix potential spinlock recursion on poll smb: client: fix potential OOB in smb2_dump_detail() HID: nintendo: Prevent divide-by-zero on code dm audit: fix Kconfig so DM_AUDIT depends on BLK_DEV_DM ALSA: hda/realtek: Add quirks for ASUS Zenbook 2022 Models ASoC: Intel: bytcr_rt5640: Add new swapped-speakers quirk ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346 platform/x86: thinkpad_acpi: fix for incorrect fan reporting on some ThinkPad systems HID: nintendo: fix initializer element is not constant error kselftest: alsa: fixed a print formatting warning Input: xpad - add Razer Wolverine V2 support wifi: iwlwifi: pcie: avoid a NULL pointer dereference ARC: fix spare error s390/scm: fix virtual vs physical address confusion Input: i8042 - add nomux quirk for Acer P459-G2-M Input: atkbd - skip ATKBD_CMD_GETID in translated mode reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning Input: psmouse - enable Synaptics InterTouch for ThinkPad L14 G1 ring-buffer: Do not record in NMI if the arch does not support cmpxchg in NMI tracing: Fix uaf issue when open the hist or hist_debug file MIPS: dts: loongson: drop incorrect dwmac fallback compatible stmmac: dwmac-loongson: drop useless check for compatible fallback tracing: Add size check when printing trace_marker output tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing jbd2: fix soft lockup in journal_finish_inode_data_buffers() platform/x86: intel-vbtn: Fix missing tablet-mode-switch events neighbour: Don't let neigh_forced_gc() disable preemption for long drm/crtc: Fix uninit-value bug in drm_mode_setcrtc jbd2: increase the journal IO's priority jbd2: correct the printing of write_flags in jbd2_write_superblock() clk: rockchip: rk3128: Fix HCLK_OTG gate register clk: rockchip: rk3568: Add PLL rate for 292.5MHz LoongArch: Preserve syscall nr across execve() hwmon: (corsair-psu) Fix probe when built-in drm/exynos: fix a wrong error checking drm/exynos: fix a potential error pointer dereference drm/amdgpu: Add NULL checks for function pointers arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru nvme: prevent potential spectre v1 gadget nvme: introduce helper function to get ctrl state ASoC: ops: add correct range check for limiting volume ASoC: da7219:
[Kernel-packages] [Bug 2052622] Re: Jammy update: v6.1.75 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- 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/2052622 Title: Jammy update: v6.1.75 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.75 upstream stable release from git://git.kernel.org/ Linux 6.1.75 Revert "Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d"" arm64: dts: armada-3720-turris-mox: set irq type for RTC Revert "KEYS: encrypted: Add check for strsep" riscv: Fix wrong usage of lm_alias() when splitting a huge linear mapping block: Remove special-casing of compound pages i2c: s3c24xx: fix transferring more than one message in polling mode i2c: s3c24xx: fix read transfers in polling mode ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work selftests: mlxsw: qos_pfc: Adjust the test to support 8 lanes mlxsw: spectrum_acl_erp: Fix error flow of pool allocation failure loop: fix the the direct I/O support check when used on top of block devices ethtool: netlink: Add missing ethnl_ops_begin/complete kdb: Fix a potential buffer overflow in kdb_local() ipvs: avoid stat macros calls from preemptible context netfilter: nf_tables: reject NFT_SET_CONCAT with not field length description netfilter: nf_tables: skip dead set elements in netlink dump netfilter: nf_tables: do not allow mismatch field size and set key length netfilter: bridge: replace physindev with physinif in nf_bridge_info netfilter: propagate net to nf_bridge_get_physindev netfilter: nf_queue: remove excess nf_bridge variable netfilter: nfnetlink_log: use proper helper for fetching physinif netfilter: nft_limit: do not ignore unsupported flags netfilter: nf_tables: reject invalid set policy mptcp: relax check on MPC passive fallback LoongArch: BPF: Prevent out-of-bounds memory access net: dsa: vsc73xx: Add null pointer check to vsc73xx_gpio_probe bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS net: stmmac: ethtool: Fixed calltrace caused by unbalanced disable_irq_wake calls drm/amdkfd: fixes for HMM mem allocation drm/amdkfd: Use resource_size() helper function dt-bindings: gpio: xilinx: Fix node address in gpio net: ravb: Fix dma_addr_t truncation in error case udp: annotate data-races around up->pending block: ensure we hold a queue reference when using queue limits mptcp: refine opt_mp_capable determination mptcp: use OPTION_MPTCP_MPJ_SYN in subflow_check_req() mptcp: use OPTION_MPTCP_MPJ_SYNACK in subflow_finish_connect() mptcp: strict validation before using mp_opt->hmac mptcp: mptcp_parse_option() fix for MPTCPOPT_MP_JOIN net: phy: micrel: populate .soft_reset for KSZ9131 amt: do not use overwrapped cb area net: ethernet: ti: am65-cpsw: Fix max mtu to fit ethernet frames net: qualcomm: rmnet: fix global oob in rmnet_policy s390/pci: fix max size calculation in zpci_memcpy_toio() ASoC: mediatek: sof-common: Add NULL check for normal_link string PCI: mediatek-gen3: Fix translation window size calculation PCI: keystone: Fix race condition when initializing PHYs nvmet-tcp: Fix the H2C expected PDU len calculation nvme: trace: avoid memcpy overflow warning nvmet: re-fix tracing strncpy() warning serial: imx: Correct clock error message in function probe() usb: xhci-mtk: fix a short packet issue of gen1 isoc-in transfer apparmor: avoid crash when parsed profile name is empty cxl/region: fix x9 interleave typo perf env: Avoid recursively taking env->bpf_progs.lock nvmet-tcp: fix a crash in nvmet_req_complete() nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length vdpa: Fix an error handling path in eni_vdpa_probe() spmi: mtk-pmif: Serialize PMIF status check and command submission usb: cdc-acm: return correct error code on unsupported break tty: use 'if' in send_break() instead of 'goto' tty: don't check for signal_pending() in send_break() tty: early return from send_break() on TTY_DRIVER_HARDWARE_BREAK tty: change tty_write_lock()'s ndelay parameter to bool perf genelf: Set ELF program header addresses properly perf hisi-ptt: Fix one memory leakage in hisi_ptt_process_auxtrace_event() perf
[Kernel-packages] [Bug 2052631] Re: Jammy update: v6.1.77 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Fix Committed => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- 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/2052631 Title: Jammy update: v6.1.77 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.77 upstream stable release from git://git.kernel.org/ Linux 6.1.77 drm/amdgpu: Fix missing error code in 'gmc_v6/7/8/9_0_hw_init()' ASoC: codecs: wsa883x: fix PA volume control ASoC: codecs: lpass-wsa-macro: fix compander volume hack bonding: remove print in bond_verify_device_path gve: Fix use-after-free vulnerability LoongArch/smp: Call rcutree_report_cpu_starting() at tlb_init() drm/msm/dsi: Enable runtime PM Revert "drm/amd/display: Disable PSR-SU on Parade 0803 TCON again" mm, kmsan: fix infinite recursion due to RCU critical section arm64: irq: set the correct node for shadow call stack selftests: bonding: Check initial state selftests: team: Add missing config options net: sysfs: Fix /sys/class/net/ path selftests: net: fix available tunnels detection af_unix: fix lockdep positive in sk_diag_dump_icons() net: ipv4: fix a memleak in ip_setup_cork netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations netfilter: nf_log: replace BUG_ON by WARN_ON_ONCE when putting logger netfilter: nf_tables: restrict tunnel object to NFPROTO_NETDEV netfilter: conntrack: correct window scaling with retransmitted SYN selftests: net: add missing config for GENEVE bridge: mcast: fix disabled snooping after long uptime llc: call sock_orphan() at release time ipv6: Ensure natural alignment of const ipv6 loopback and router addresses net: dsa: qca8k: fix illegal usage of GPIO ixgbe: Fix an error handling path in ixgbe_read_iosf_sb_reg_x550() ixgbe: Refactor overtemp event handling ixgbe: Refactor returning internal error codes tcp: add sanity checks to rx zerocopy net: lan966x: Fix port configuration when using SGMII interface ipmr: fix kernel panic when forwarding mcast packets ipv4: raw: add drop reasons ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() selftests: net: give more time for GRO aggregation HID: hidraw: fix a problem of memory leak in hidraw_release() scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler regulator: ti-abb: don't use devm_platform_ioremap_resource_byname for shared interrupt register scsi: isci: Fix an error code problem in isci_io_request_build() drm: using mul_u32_u32() requires linux/math64.h wifi: cfg80211: fix RCU dereference in __cfg80211_bss_update perf: Fix the nr_addr_filters fix drm/amdkfd: Fix 'node' NULL check in 'svm_range_get_range_boundaries()' drm/amdgpu: Release 'adev->pm.fw' before return in 'amdgpu_device_need_post()' drm/amdgpu: Fix with right return code '-EIO' in 'amdgpu_gmc_vram_checking()' drm/amd/powerplay: Fix kzalloc parameter 'ATOM_Tonga_PPM_Table' in 'get_platform_power_management_table()' ceph: fix invalid pointer access if get_quota_realm return ERR_PTR ceph: fix deadlock or deadcode of misusing dget() ceph: reinitialize mds feature bit even when session in open blk-mq: fix IO hang from sbitmap wakeup race virtio_net: Fix "‘%d’ directive writing between 1 and 11 bytes into a region of size 10" warnings drm/amdkfd: Fix lock dependency warning with srcu drm/amdkfd: Fix lock dependency warning libsubcmd: Fix memory leak in uniq() misc: lis3lv02d_i2c: Add missing setting of the reg_ctrl callback 9p: Fix initialisation of netfs_inode for 9p PCI/AER: Decode Requester ID when no error info found PCI: Fix 64GT/s effective data rate calculation spmi: mediatek: Fix UAF on device remove fs/kernfs/dir: obey S_ISGID tty: allow TIOCSLCKTRMIOS with CAP_CHECKPOINT_RESTORE selftests/sgx: Fix linker script asserts usb: hub: Add quirk to decrease IN-ep poll interval for Microchip USB491x hub usb: hub: Replace hardcoded quirk value with BIT() macro perf cs-etm: Bump minimum OpenCSD version to ensure a bugfix is present PCI: switchtec: Fix stdev_release() crash after surprise hot remove PCI: Only
[Kernel-packages] [Bug 2052623] Re: Jammy update: v6.1.76 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- 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/2052623 Title: Jammy update: v6.1.76 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.76 upstream stable release from git://git.kernel.org/ Linux 6.1.76 net/mlx5e: Handle hardware IPsec limits events serial: core: fix kernel-doc for uart_port_unlock_irqrestore() x86/entry/ia32: Ensure s32 is sign extended to s64 tick/sched: Preserve number of idle sleeps across CPU hotplug events mips: Call lose_fpu(0) before initializing fcr31 in mips_set_personality_nan cxl/region：Fix overflow issue in alloc_hpa() MIPS: lantiq: register smp_ops on non-smp platforms spi: fix finalize message on error return spi: bcm-qspi: fix SFDP BFPT read by usig mspi read drm/bridge: anx7625: Ensure bridge is suspended in disable() block: Move checking GENHD_FL_NO_PART to bdev_add_partition() gpio: eic-sprd: Clear interrupt after set the interrupt type drm/exynos: gsc: minor fix for loop iteration in gsc_runtime_resume drm/exynos: fix accidental on-stack copy of exynos_drm_plane drm/bridge: parade-ps8640: Make sure we drop the AUX mutex in the error case drm/bridge: parade-ps8640: Ensure bridge is suspended in .post_disable() drm/bridge: sii902x: Fix audio codec unregistration drm/bridge: sii902x: Fix probing race issue drm/bridge: sii902x: Use devm_regulator_bulk_get_enable() drm: panel-simple: add missing bus flags for Tianma tm070jvhg[30/33] drm/bridge: parade-ps8640: Wait for HPD when doing an AUX transfer Revert "powerpc/64s: Increase default stack size to 32KB" drm/panel-edp: drm/panel-edp: Fix AUO B116XAK01 name and timing btrfs: zoned: optimize hint byte for zoned allocator btrfs: zoned: factor out prepare_allocation_zoned() serial: sc16is7xx: fix unconditional activation of THRI interrupt serial: sc16is7xx: Use port lock wrappers serial: core: Provide port lock wrappers dlm: use kernel_connect() and kernel_bind() ARM: dts: qcom: sdx55: fix USB SS wakeup ARM: dts: qcom: sdx55: fix USB DP/DM HS PHY interrupts ARM: dts: qcom: sdx55: fix pdc '#interrupt-cells' ARM: dts: samsung: exynos4210-i9100: Unconditionally enable LDO12 ARM: dts: qcom: sdx55: fix USB wakeup interrupt types pipe: wakeup wr_wait after setting max_usage fs/pipe: move check to pipe_has_watch_queue() thermal: intel: hfi: Add syscore callbacks for system-wide PM thermal: intel: hfi: Disable an HFI instance when all its CPUs go offline thermal: intel: hfi: Refactor enabling code into helper functions PM: sleep: Fix possible deadlocks in core system-wide PM code PM: core: Remove unnecessary (void *) conversions bus: mhi: ep: Do not allocate event ring element on stack media: ov13b10: Enable runtime PM before registering async sub-device media: ov13b10: Support device probe in non-zero ACPI D state erofs: fix lz4 inplace decompression erofs: get rid of the remaining kmap_atomic() drm/amdgpu/pm: Fix the power source flag error drm/amd/display: Port DENTIST hang and TDR fixes to OTG disable W/A drm/bridge: nxp-ptn3460: simplify some error checking platform/x86: intel-uncore-freq: Fix types in sysfs callbacks drm/amd/display: Disable PSR-SU on Parade 0803 TCON again drm/tidss: Fix atomic_flush check drm/bridge: nxp-ptn3460: fix i2c_master_send() error checking drm: Don't unref the same fb many times by mistake due to deadlock handling cpufreq: intel_pstate: Refine computation of P-state for given frequency gpiolib: acpi: Ignore touchpad wakeup on GPD G1619-04 xfs: read only mounts with fsopen mount API are busted firmware: arm_scmi: Check mailbox/SMT channel for consistency ksmbd: fix global oob in ksmbd_nl_policy platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe netfilter: nf_tables: reject QUEUE/DROP verdict parameters netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain hv_netvsc: Calculate correct ring size when PAGE_SIZE is not 4 Kbytes wifi: iwlwifi: fix a memory corruption exec: Fix error handling in begin_new_exec() rbd: don't move requests to the running list
[Kernel-packages] [Bug 2052696] [NEW] [UBUNTU 24.04] Haskell LLVM Backend: Objects of data section are missing alignment
Public bug reported: Description: Objects of the data section may be accessed through tagged pointers. Thus, those objects require a minimal alignment of 8 byte on a 64-bit architecture. Otherwise, this may lead to undefined behavior. Solution: commit https://gitlab.haskell.org/ghc/ghc/-/commit/dfe1c3540e4b519b62b862b5966dfec5cae9ece1 This patch resolves the alignment issue for all targets utilizing the LLVM backend. The fix was backported by upstream for ghc release 9.6 and 9.8 but not for 9.4.x which has landed in Noble. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-205159 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-205159 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052696 Title: [UBUNTU 24.04] Haskell LLVM Backend: Objects of data section are missing alignment Status in linux package in Ubuntu: New Bug description: Description: Objects of the data section may be accessed through tagged pointers. Thus, those objects require a minimal alignment of 8 byte on a 64-bit architecture. Otherwise, this may lead to undefined behavior. Solution: commit https://gitlab.haskell.org/ghc/ghc/-/commit/dfe1c3540e4b519b62b862b5966dfec5cae9ece1 This patch resolves the alignment issue for all targets utilizing the LLVM backend. The fix was backported by upstream for ghc release 9.6 and 9.8 but not for 9.4.x which has landed in Noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052696/+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 2052696] [NEW] [UBUNTU 24.04] Haskell LLVM Backend: Objects of data section are missing alignment
You have been subscribed to a public bug: Description: Objects of the data section may be accessed through tagged pointers. Thus, those objects require a minimal alignment of 8 byte on a 64-bit architecture. Otherwise, this may lead to undefined behavior. Solution: commit https://gitlab.haskell.org/ghc/ghc/-/commit/dfe1c3540e4b519b62b862b5966dfec5cae9ece1 This patch resolves the alignment issue for all targets utilizing the LLVM backend. The fix was backported by upstream for ghc release 9.6 and 9.8 but not for 9.4.x which has landed in Noble. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-205159 severity-high targetmilestone-inin--- -- [UBUNTU 24.04] Haskell LLVM Backend: Objects of data section are missing alignment https://bugs.launchpad.net/bugs/2052696 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 2052587] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/cpupower', which is also in package linux-laptop-tools-common 6.
*** This bug is a duplicate of bug 2048183 ***
https://bugs.launchpad.net/bugs/2048183
Doing uninstall did help getting those tools installed but still perf
counters do not work:
jan@jan-ThinkPad-P1-Gen-6:~/work/mariadb/10.11/mysql-test$ perf stat -e r5111c4
true
WARNING: event 'N/A' not valid (bits 16,20,22 of config '5111c4' not supported
by kernel)!
Performance counter stats for 'true':
131.341 cpu_core/r5111c4/
0,002273140 seconds time elapsed
0,002294000 seconds user
0,0 seconds sys
--
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/2052587
Title:
package linux-tools-common (not installed) failed to install/upgrade:
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
Status in linux package in Ubuntu:
New
Bug description:
jan@jan-ThinkPad-P1-Gen-6:~/work/mariadb/10.11/mysql-test$ sudo apt-get
install linux-tools-6.5.0-14-generic linux-cloud-tools-6.5.0-14-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-cloud-tools-6.5.0-14-generic is already the newest version
(6.5.0-14.14).
The following additional packages will be installed:
hwdata linux-tools-6.5.0-14 linux-tools-common
The following NEW packages will be installed:
hwdata linux-tools-6.5.0-14 linux-tools-6.5.0-14-generic linux-tools-common
0 upgraded, 4 newly installed, 0 to remove and 1 not upgraded.
Need to get 452 kB/8.591 kB of archives.
After this operation, 28,6 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ly.archive.ubuntu.com/ubuntu mantic-updates/main amd64
linux-tools-common all 6.5.0-15.15 [452 kB]
Fetched 452 kB in 1s (859 kB/s)
Selecting previously unselected package hwdata.
(Reading database ... 536450 files and directories currently installed.)
Preparing to unpack .../hwdata_0.374-1_all.deb ...
Unpacking hwdata (0.374-1) ...
Preparing to unpack .../linux-tools-common_6.5.0-15.15_all.deb ...
Unpacking linux-tools-common (6.5.0-15.15) ...
dpkg: error processing archive
/var/cache/apt/archives/linux-tools-common_6.5.0-15.15_all.deb (--unpack):
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package linux-tools-6.5.0-14.
Preparing to unpack .../linux-tools-6.5.0-14_6.5.0-14.14_amd64.deb ...
Unpacking linux-tools-6.5.0-14 (6.5.0-14.14) ...
Selecting previously unselected package linux-tools-6.5.0-14-generic.
Preparing to unpack .../linux-tools-6.5.0-14-generic_6.5.0-14.14_amd64.deb ...
Unpacking linux-tools-6.5.0-14-generic (6.5.0-14.14) ...
Errors were encountered while processing:
/var/cache/apt/archives/linux-tools-common_6.5.0-15.15_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
jan@jan-ThinkPad-P1-Gen-6:~/work/mariadb/10.11/mysql-test$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-tools-common (not installed)
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
hwdata:amd64: Install
linux-tools-common:amd64: Install
linux-tools-6.5.0-14:amd64: Install
linux-tools-6.5.0-14-generic:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CRDA: N/A
CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img
./boot/grub/grub.cfg ./casper/initrd
CasperMD5CheckResult: fail
Date: Wed Feb 7 08:46:38 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-sutton-jammy-amd64-20230811-498
DuplicateSignature:
package:linux-tools-common:(not installed)
Unpacking linux-tools-common (6.5.0-15.15) ...
dpkg: error processing archive
/var/cache/apt/archives/linux-tools-common_6.5.0-15.15_all.deb (--unpack):
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
ErrorMessage: trying to overwrite '/usr/bin/cpupower', which is also in
package linux-laptop-tools-common 6.5.0-1006.9
InstallationDate: Installed on 2023-08-11 (180 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
pc-sutton-jammy-amd64-20230811-498
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
