[Kernel-packages] [Bug 2086749] Re: [SRU][N/O/P] Add BT firmware of Intel BlazarI core
** Tags added: jira-sutton-286 oem-priority -- 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/2086749 Title: [SRU][N/O/P] Add BT firmware of Intel BlazarI core Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Noble: In Progress Status in linux-firmware source package in Oracular: In Progress Status in linux-firmware source package in Plucky: In Progress Bug description: [Impact] Intel BE201 Bluetooth can't load firmware. Logs: Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0190-0291-iml.sfi (-2) [Fix] Add BT firmware of Intel BlazarI core which includes BE201 and AX211 [Test] Bluetooth works fine with connection of headphone. [Where problems could occur] It may break the bluetooth of Intel BE201. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2086749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085410] Re: Fix USB device suspend failure while HCD in S4 wakeup
** Changed in: linux-oem-6.11 (Ubuntu Oracular) Status: New => Invalid ** Changed in: linux-oem-6.11 (Ubuntu Plucky) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2085410 Title: Fix USB device suspend failure while HCD in S4 wakeup Status in linux package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: New Status in linux-oem-6.11 source package in Noble: Fix Committed Status in linux source package in Oracular: New Status in linux-oem-6.11 source package in Oracular: Invalid Status in linux source package in Plucky: New Status in linux-oem-6.11 source package in Plucky: Invalid Bug description: [SRU Justification] [Impact] More and more USB device suspend failure are caused by the un-expected HCD_FLAG_WAKEUP_PENDING on the USB host controller. It mostly happens on the USB devices connected to the high-speed root hub. It randomly happens when put the system into suspend [Fix] Fixed by the upstream fix https://lore.kernel.org/linux-usb/20241012094633.126736-1-duancheng...@kylinos.cn/. Set wakeup to false if suspend type is either PM_EVENT_FREEZE or PM_EVENT_QUIESCE [Test Case] 1. Power on machine and connect a USB device to the high-speed root hub. (Find your device in lsusb in the secondary root hub) 2. run checkbox-cli run com.canonical.certification::suspend-cycles-stress-test 3. observe the suspend/resume fail with the kernel message [Where problems could occur] Add more restriction on how the wakeup should be performed. Should be low risk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086818] Re: Null pointer dereference in wireguard module during shutdown
** Description changed: The bug is intermittent and happens during shutdown process, prevents computer from shutting down. May be reproducible more often on certain hardware and certain kernel versions. + + Pre-condition: main network connection should be enabled for all users + of the computer, even if there's just one. Reproduction steps: 1) start a wireguard connection, 2) proceed with shutting down the computer, 3) observe parts of the memory traces on the screen, 4) shutdown process is interrupted. Expected behavior: Normal shutdown without errors and interruptions. See also attached dmesg.txt file containing the kernel log. $ uname -a Linux elnath 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14 13:19:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -cr Release:24.10 Codename: oracular Previous release 24.04LTS Noble is also affected. In fact the issue can be observed even more often. ** Description changed: The bug is intermittent and happens during shutdown process, prevents computer from shutting down. May be reproducible more often on certain hardware and certain kernel versions. - Pre-condition: main network connection should be enabled for all users - of the computer, even if there's just one. + Pre-condition: + main network connection should be enabled for all users of the computer, even if there's just one. Reproduction steps: 1) start a wireguard connection, 2) proceed with shutting down the computer, 3) observe parts of the memory traces on the screen, 4) shutdown process is interrupted. Expected behavior: Normal shutdown without errors and interruptions. See also attached dmesg.txt file containing the kernel log. $ uname -a Linux elnath 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14 13:19:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -cr Release:24.10 Codename: oracular Previous release 24.04LTS Noble is also affected. In fact the issue can be observed even more often. -- 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/2086818 Title: Null pointer dereference in wireguard module during shutdown Status in linux package in Ubuntu: New Bug description: The bug is intermittent and happens during shutdown process, prevents computer from shutting down. May be reproducible more often on certain hardware and certain kernel versions. Pre-condition: main network connection should be enabled for all users of the computer, even if there's just one. Reproduction steps: 1) start a wireguard connection, 2) proceed with shutting down the computer, 3) observe parts of the memory traces on the screen, 4) shutdown process is interrupted. Expected behavior: Normal shutdown without errors and interruptions. See also attached dmesg.txt file containing the kernel log. $ uname -a Linux elnath 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14 13:19:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -cr Release:24.10 Codename: oracular Previous release 24.04LTS Noble is also affected. In fact the issue can be observed even more often. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086819] [NEW] scripts/insert-sys-cert does not insert a cert into kernel image
Public bug reported: [Impact] /usr/src/linux-headers-6.8.0-47-generic/scripts/insert-sys-cert fails to insert a certificate into vmlinuz [Test Case] 1. cp /boot/vmlinuz-6.8.0-47-generic ~/workdir/ 2. cp /boot/System.map-6.8.0-47-generic ~/workdir/ 3. cd ~/workdir 4. openssl req -x509 -newkey rsa:4096 -keyout snakeoil-key.der -out snakeoil-cert.der -sha256 -days 3650 -nodes -subj "/O=MyCert/OU=MyCert/CN=snakeoil" -outform DER 5. /usr/src/linux-headers-6.8.0-47-generic/scripts/insert-sys-cert -s System.map-6.8.0-47-generic -z vmlinuz-6.8.0-47-generic -c snakeoil-cert.der ERROR: Unable to determine the compression of vmlinux Recent kernels use zstd compression, which Ubuntu's insert-sys-cert does not know about. The scripts/extract-vmlinux could be used to extract the vmlinux since it knows about zstd. However, because it has been stripped, it tries to use the Systems.map file to find the symbol, but has trouble reading lines of the file. 1. /usr/src/linux-headers-6.8.0-47-generic/scripts/extract-vmlinux vmlinuz-6.8.0-47-generic > myvmlinux 2. file vmlinux vmlinux: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=90786183f0bb9cf3d745ac2a83e1b86d473d6594, stripped 3. /usr/src/linux-headers-6.8.0-47-generic/scripts/insert-sys-cert -s System.map-6.8.0-47-generic -b myvmlinux -c snakeoil-cert.der WARNING: Could not find the symbol table. ERROR: Missing line ending. ERROR: Missing line ending. ERROR: Missing line ending. [ Where Problem Occurred ] Package Name: # dpkg -l | grep linux-headers-6.8.0-47-generic ii linux-headers-6.8.0-47-generic 6.8.0-47.47 amd64Linux kernel headers for version 6.8.0 on 64 bit x86 SMP # cat /proc/version_signature Ubuntu 6.8.0-47.47-generic 6.8.12 # lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04.1 LTS Release:24.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2086819 Title: scripts/insert-sys-cert does not insert a cert into kernel image Status in linux package in Ubuntu: New Bug description: [Impact] /usr/src/linux-headers-6.8.0-47-generic/scripts/insert-sys-cert fails to insert a certificate into vmlinuz [Test Case] 1. cp /boot/vmlinuz-6.8.0-47-generic ~/workdir/ 2. cp /boot/System.map-6.8.0-47-generic ~/workdir/ 3. cd ~/workdir 4. openssl req -x509 -newkey rsa:4096 -keyout snakeoil-key.der -out snakeoil-cert.der -sha256 -days 3650 -nodes -subj "/O=MyCert/OU=MyCert/CN=snakeoil" -outform DER 5. /usr/src/linux-headers-6.8.0-47-generic/scripts/insert-sys-cert -s System.map-6.8.0-47-generic -z vmlinuz-6.8.0-47-generic -c snakeoil-cert.der ERROR: Unable to determine the compression of vmlinux Recent kernels use zstd compression, which Ubuntu's insert-sys-cert does not know about. The scripts/extract-vmlinux could be used to extract the vmlinux since it knows about zstd. However, because it has been stripped, it tries to use the Systems.map file to find the symbol, but has trouble reading lines of the file. 1. /usr/src/linux-headers-6.8.0-47-generic/scripts/extract-vmlinux vmlinuz-6.8.0-47-generic > myvmlinux 2. file vmlinux vmlinux: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=90786183f0bb9cf3d745ac2a83e1b86d473d6594, stripped 3. /usr/src/linux-headers-6.8.0-47-generic/scripts/insert-sys-cert -s System.map-6.8.0-47-generic -b myvmlinux -c snakeoil-cert.der WARNING: Could not find the symbol table. ERROR: Missing line ending. ERROR: Missing line ending. ERROR: Missing line ending. [ Where Problem Occurred ] Package Name: # dpkg -l | grep linux-headers-6.8.0-47-generic ii linux-headers-6.8.0-47-generic 6.8.0-47.47 amd64Linux kernel headers for version 6.8.0 on 64 bit x86 SMP # cat /proc/version_signature Ubuntu 6.8.0-47.47-generic 6.8.12 # lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.1 LTS Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086820] [NEW] package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess
Public bug reported: bug during update process ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-48-generic 6.8.0-48.48 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:hp15-ubu 1980 F pipewire /dev/snd/controlC0: hp15-ubu 1984 F wireplumber CasperMD5CheckResult: pass Date: Thu Nov 7 02:30:16 2024 ErrorMessage: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-10-25 (12 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=66b67246-2445-4a02-ab7a-aee6c9a70fa5 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2024 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.50 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.50 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd08/20/2024:br15.49:efr80.50:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.50:cvnHP:ct10:cvrChassisVersion:sku4TT07PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4TT07PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/2086820 Title: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 Status in linux package in Ubuntu: New Bug description: bug during update process ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-48-generic 6.8.0-48.48 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:hp15-ubu 1980 F pipewire /dev/snd/controlC0: hp15-ubu 1984 F wireplumber CasperMD5CheckResult: pass Date: Thu Nov 7 02:30:16 2024 ErrorMessage: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-10-25 (12 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=66b67246-2445-4a02-ab7a-aee6c9a70fa5 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2024 dmi.bios.relea
[Kernel-packages] [Bug 2086820] Re: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- 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/2086820 Title: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 Status in linux package in Ubuntu: New Bug description: bug during update process ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-48-generic 6.8.0-48.48 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:hp15-ubu 1980 F pipewire /dev/snd/controlC0: hp15-ubu 1984 F wireplumber CasperMD5CheckResult: pass Date: Thu Nov 7 02:30:16 2024 ErrorMessage: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-10-25 (12 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=66b67246-2445-4a02-ab7a-aee6c9a70fa5 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2024 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.50 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.50 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd08/20/2024:br15.49:efr80.50:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.50:cvnHP:ct10:cvrChassisVersion:sku4TT07PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4TT07PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086815] [NEW] i2c-mlxbf: SMBus Repeated Start Support
Public bug reported: SRU Justification: [Impact] Reading SMBus or I2C block data on Bluefield will fail if the target device requires repeated start conditions to be used. [Fix] * Add support for repeated start conditions to the Mellanox I2C driver. * Enable repeated start condition for I2C_FUNC_SMBUS_WRITE_I2C_BLOCK read implementation. * Update I2C bus timing settings based on latest HW testing results. Required for repeated start transactions with Bluefield 3 target devices. [Test Case] * Verified MLXBF I2C driver builds and loads without errors on Bluefield 2 and Bluefield 3. * Verified I2C block read of a device that requires repeated start conditions succeeds using the following command: "i2cget -yi ". * Verified IPMB communication with BMC to regression test general I2C behavior. Used to following command which will result in several I2C transactions: "ipmitool mc info". [Regression Potential] * I2C bus timing settings have been updated and will affect all I2C and SMBus transactions on Bluefield. * SMBus I2C block reads now include a repeated start condition which could cause a regression if this type of read is expected to be used with a target device that does not support repeated start conditions. * IPMB transactions that use I2C could fail due to a bug with this implementation. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2086815 Title: i2c-mlxbf: SMBus Repeated Start Support Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Reading SMBus or I2C block data on Bluefield will fail if the target device requires repeated start conditions to be used. [Fix] * Add support for repeated start conditions to the Mellanox I2C driver. * Enable repeated start condition for I2C_FUNC_SMBUS_WRITE_I2C_BLOCK read implementation. * Update I2C bus timing settings based on latest HW testing results. Required for repeated start transactions with Bluefield 3 target devices. [Test Case] * Verified MLXBF I2C driver builds and loads without errors on Bluefield 2 and Bluefield 3. * Verified I2C block read of a device that requires repeated start conditions succeeds using the following command: "i2cget -yi ". * Verified IPMB communication with BMC to regression test general I2C behavior. Used to following command which will result in several I2C transactions: "ipmitool mc info". [Regression Potential] * I2C bus timing settings have been updated and will affect all I2C and SMBus transactions on Bluefield. * SMBus I2C block reads now include a repeated start condition which could cause a regression if this type of read is expected to be used with a target device that does not support repeated start conditions. * IPMB transactions that use I2C could fail due to a bug with this implementation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2086815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062568] Re: nfsd gets unresponsive after some hours of operation
@mehmetbasaran: This issue is impacting one of the HPC clusters I manage. Are there any thoughts as to when this patch will get rolled out to a released 6.8.0 kernel? Also, does anyone know if this is a server bug or a client bug, i.e. for mitigation, do the servers need to be rolled back to a version that does not have the bug? Do the clients need to be rolled back? Both? Thanks, Omen -- 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/2062568 Title: nfsd gets unresponsive after some hours of operation Status in linux package in Ubuntu: In Progress Status in nfs-utils package in Ubuntu: Incomplete Status in linux source package in Noble: In Progress Status in nfs-utils source package in Noble: Incomplete Bug description: I installed the 24.04 Beta on two test machines that were running 22.04 without issues before. One of them exports two volumes that are mounted by the other machine, which primarily uses them as a secondary storage for ccache. After being up for a couple of hours (happened twice since yesterday evening) it seems that nfsd on the machine exporting the volumes hangs on something. From dmesg on the server (repeated a few times): [11183.290548] INFO: task nfsd:1419 blocked for more than 1228 seconds. [11183.290558] Not tainted 6.8.0-22-generic #22-Ubuntu [11183.290563] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [11183.290582] task:nfsdstate:D stack:0 pid:1419 tgid:1419 ppid:2 flags:0x4000 [11183.290587] Call Trace: [11183.290602] [11183.290606] __schedule+0x27c/0x6b0 [11183.290612] schedule+0x33/0x110 [11183.290615] schedule_timeout+0x157/0x170 [11183.290619] wait_for_completion+0x88/0x150 [11183.290623] __flush_workqueue+0x140/0x3e0 [11183.290629] nfsd4_probe_callback_sync+0x1a/0x30 [nfsd] [11183.290689] nfsd4_destroy_session+0x186/0x260 [nfsd] [11183.290744] nfsd4_proc_compound+0x3af/0x770 [nfsd] [11183.290798] nfsd_dispatch+0xd4/0x220 [nfsd] [11183.290851] svc_process_common+0x44d/0x710 [sunrpc] [11183.290924] ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd] [11183.290976] svc_process+0x132/0x1b0 [sunrpc] [11183.291041] svc_handle_xprt+0x4d3/0x5d0 [sunrpc] [11183.291105] svc_recv+0x18b/0x2e0 [sunrpc] [11183.291168] ? __pfx_nfsd+0x10/0x10 [nfsd] [11183.291220] nfsd+0x8b/0xe0 [nfsd] [11183.291270] kthread+0xef/0x120 [11183.291274] ? __pfx_kthread+0x10/0x10 [11183.291276] ret_from_fork+0x44/0x70 [11183.291279] ? __pfx_kthread+0x10/0x10 [11183.291281] ret_from_fork_asm+0x1b/0x30 [11183.291286] From dmesg on the client (repeated a number of times): [ 6596.911785] RPC: Could not send backchannel reply error: -110 [ 6596.972490] RPC: Could not send backchannel reply error: -110 [ 6837.281307] RPC: Could not send backchannel reply error: -110 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nfs-kernel-server 1:2.6.4-3ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 .etc.request-key.d.id_resolver.conf: create id_resolver * * /usr/sbin/nfsidmap -t 600 %k %d ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 19 14:10:25 2024 InstallationDate: Installed on 2024-04-16 (3 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1) NFSMounts: NFSv4Mounts: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086818] [NEW] Null pointer dereference in wireguard module during shutdown
Public bug reported: The bug is intermittent and happens during shutdown process, prevents computer from shutting down. May be reproducible more often on certain hardware and certain kernel versions. Reproduction steps: 1) start a wireguard connection, 2) proceed with shutting down the computer, 3) observe parts of the memory traces on the screen, 4) shutdown process is interrupted. Expected behavior: Normal shutdown without errors and interruptions. See also attached dmesg.txt file containing the kernel log. $ uname -a Linux elnath 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14 13:19:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -cr Release:24.10 Codename: oracular Previous release 24.04LTS Noble is also affected. In fact the issue can be observed even more often. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug wireguard ** Attachment added: "Kernel log taken from previous session" https://bugs.launchpad.net/bugs/2086818/+attachment/5835134/+files/dmesg.txt ** Description changed: The bug is intermittent and happens during shutdown process, prevents computer from shutting down. May be reproducible more often on certain hardware and certain kernel versions. Reproduction steps: - 1) proceed with shutting down the computer - 2) observe parts of the memory traces on the screen - 3) shutdown process is interrupted. + 1) start a wireguard connection, + 2) proceed with shutting down the computer, + 3) observe parts of the memory traces on the screen, + 4) shutdown process is interrupted. Expected behavior: Normal shutdown without errors and interruptions. See also attached dmesg.txt file containing the kernel log. $ uname -a Linux elnath 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14 13:19:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux - $ lsb_release -cr Release:24.10 Codename: oracular - - Previous release 24.04LTS Noble is also affected. In fact the issue can be observer even more often. + Previous release 24.04LTS Noble is also affected. In fact the issue can + be observer even more often. ** Description changed: The bug is intermittent and happens during shutdown process, prevents computer from shutting down. May be reproducible more often on certain hardware and certain kernel versions. Reproduction steps: 1) start a wireguard connection, 2) proceed with shutting down the computer, 3) observe parts of the memory traces on the screen, 4) shutdown process is interrupted. Expected behavior: Normal shutdown without errors and interruptions. See also attached dmesg.txt file containing the kernel log. $ uname -a Linux elnath 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14 13:19:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -cr Release:24.10 Codename: oracular Previous release 24.04LTS Noble is also affected. In fact the issue can - be observer even more often. + be observed even more often. -- 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/2086818 Title: Null pointer dereference in wireguard module during shutdown Status in linux package in Ubuntu: New Bug description: The bug is intermittent and happens during shutdown process, prevents computer from shutting down. May be reproducible more often on certain hardware and certain kernel versions. Reproduction steps: 1) start a wireguard connection, 2) proceed with shutting down the computer, 3) observe parts of the memory traces on the screen, 4) shutdown process is interrupted. Expected behavior: Normal shutdown without errors and interruptions. See also attached dmesg.txt file containing the kernel log. $ uname -a Linux elnath 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14 13:19:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -cr Release:24.10 Codename: oracular Previous release 24.04LTS Noble is also affected. In fact the issue can be observed even more often. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028891] Re: HTTP boot grub issue
It will be helpful to debug if the following information is provided: - bluefield model name (or SKU if that is possible for you) - firmware version - grub version - how and where did you get the grubaa64.efi? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2028891 Title: HTTP boot grub issue Status in linux-bluefield package in Ubuntu: Confirmed Bug description: SRU Justification: [Impact] We have tested PXE boot successfully on the BlueField using grubaa64.efi and grub.cfg but HTTP boot does not work. During HTTP boot, UEFI is able to load the grubaa64.efi but doesn’t load grub.cfg and goes instead into the grub rescue shell. From the grub shell, I try to load the grub.cfg file manually, but I get the error shown below. grub> set ?=0 cmdpath=(http,192.168.200.1) color_highlight=black/light-gray color_normal=light-gray/black feature_200_final=y feature_all_video_module=y feature_chainloader_bpb=y feature_default_font_path=y feature_menuentry_id=y feature_menuentry_options=y feature_nativedisk_cmd=y feature_ntldr=y feature_platform_search_hint=y feature_timeout_style=y grub_cpu=arm64 grub_netfs_type=efi grub_platform=efi lang= locale_dir= net_default_interface=efinet2 net_default_ip=192.168.200.2 net_default_mac= net_default_server=192.168.200.1 net_efinet2_ip=192.168.200.2 net_efinet2_mac= package_version=2.06-2ubuntu14.1 pager= prefix=(http,192.168.200.1)/grub pxe_default_server=192.168.200.1 root=http,192.168.200.1 secondary_locale_dir= configfile (http,192.168.200.1)/grub/grub.cfg this doesn't works: error: Fail to send a request! status=0x8002. However it works if I run: configfile (tftp,192.168.200.1)/grub/grub.cfg This forum discusses a similar issue which points to a grub issue: https://groups.google.com/g/linux.debian.bugs.dist/c/CqfwbhAd-Xg Could you please help investigate this? Or point me to the right person? [Fix] * Unknown yet. Investigate grub. [Test Case] * HTTP boot via OOB * HTTP boot via Connect X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086758] [NEW] [Driver Readiness] Intel BE201 Bluetooth
Public bug reported: [Impact] Update Ubuntu linux-firmware to support Intel BE201 BT. [Fix] Cherry-pick upstream commit: fe16af92ca833c linux-firmware: Update firmware file for Intel BlazarI core [Test Plan] 1. Boot into the Ubuntu kernel 2. Test the functionality of Bluetooth [Where problems could occur] May cause regression. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2086758 Title: [Driver Readiness] Intel BE201 Bluetooth Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux source package in Noble: New Status in linux-firmware source package in Noble: New Bug description: [Impact] Update Ubuntu linux-firmware to support Intel BE201 BT. [Fix] Cherry-pick upstream commit: fe16af92ca833c linux-firmware: Update firmware file for Intel BlazarI core [Test Plan] 1. Boot into the Ubuntu kernel 2. Test the functionality of Bluetooth [Where problems could occur] May cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047728] Re: nvme 0000:02:00.0: Unable to change power state from D3cold to D0, device inaccessible
Hi Waiting for a kernel patch (Reproduce in mainline up to Linux 6.10+), I recommend using the dirty workarround I write to "save" one of my production server while no patch are currently doing the job and issuing at kernel cmdline options "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" don't have any effect and not more effect than totally disabling PCIE ASPM in the UEFI BIOS, since Linux 6.1 sysfs is populated with 'd3cold_allowed=1" on NVME and PCIE downstream port where it should be 0 for NVME storage (Windows seems to let NVME in D0 state during PCIE ASPM) More complete explanations and the workaround script can be find here : https://bbs.archlinux.org/viewtopic.php?pid=2206758#p2206758 Kind regards nbanba -- 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/2047728 Title: nvme :02:00.0: Unable to change power state from D3cold to D0, device inaccessible Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu release: Ubuntu 22.04.3 LTS (ubuntu 23.10 also affected) Tested on kernal vesions:6.6.8, 6.2.0.39.40~22.04.16_22.04, 6.2.0-39.40~22.04.1, 6.2.0-26.26~22.04.1, 6.0 Hardware: Thunderobot zero, ssd: sumsung990pro, sumsung ssd MZVL2512HCJQ-00B00 bios version: TP117 05/11/2021 BUG discription: ubuntu can't detect one channel of SSD when installing or after installization. This bug is not related to the SSD product itsel but related to the location where it is mounted. Because i have switched these two SSDs, and only the SSD mounted at the same location can be detected. I list the grub log as following: kernel: ACPI: bus type thunderbolt registered kernel: thunderbolt :00:0d.2: enabling device ( -> 0002) kernel: nvme nvme1: pci function :03:00.0 kernel: nvme nvme0: pci function :02:00.0 kernel: nvme :02:00.0: Unable to change power state from D3cold to D0, device inaccessible -- This error remains when i change kernal versions as list above. This bug is quit similar to bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085162] Re: Bluetooth headphones connect erratically
Thanks to https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084963/comments/4 I've been able to manually rebuild the bluez debs with a patch of commit https://github.com/bluez/bluez/commit/366a8c522b648f47147de4852c5c030d69b916b3 and my headphone connection woes have been solved. I'll attach the patch here. ** Patch added: "bluez-fix-address.patch" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2085162/+attachment/5834952/+files/bluez-fix-address.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2085162 Title: Bluetooth headphones connect erratically Status in alsa-driver package in Ubuntu: Invalid Status in bluez package in Ubuntu: New Bug description: Description of the problem A pair of Sony Sony WH-H900N Bluetooth headphones often refuses to re-connect with a Lenovo V15 G2 ALC laptop. These headphones pair without trouble to a MacBook Pro and an Android phone. Step to reproduce: 1. Put the headphones into discovery mode. 2. Go to Settings -> Bluetooth and connect to the headphones. 3. Reboot the laptop. 4. Go to Settings -> Bluetooth 5. Click on the headphones. 6. Try to connect to the headphones. 7. If step 6. fails try to disconnect. 8. Go to step 6. Expected result: After step 6 for headphones to be connected and for headphones to announce "Bluetooth connected". Actual result: Sometimes the "connected" slider slides back to unconnected. Sometimes the slider remains "on" but the headphones don't announce that they are connected and no headphones appear in sound settings. How reproducible is the problem: Fairly reproducible. It can sometimes takes 30 or more connection attempts before a real connection is established. Version information: Ubuntu 24.10 ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:sitsofe8130 F pipewire /dev/snd/controlC0: sitsofe8136 F wireplumber /dev/snd/controlC1: sitsofe8136 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 21:34:28 2024 InstallationDate: Installed on 2024-10-14 (7 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: LENOVO 82KD PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN42WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15 G2 ALC dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrGLCN42WW:bd12/13/2021:br1.42:efr1.42:svnLENOVO:pn82KD:pvrLenovoV15G2ALC:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoV15G2ALC:skuLENOVO_MT_82KD_BU_idea_FM_V15G2ALC: dmi.product.family: V15 G2 ALC dmi.product.name: 82KD dmi.product.sku: LENOVO_MT_82KD_BU_idea_FM_V15 G2 ALC dmi.product.version: Lenovo V15 G2 ALC dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2085162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2081384] Re: bluetooth headphones need reconnect after every reboot
Does the patch mentioned in https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2085162/comments/5 help anyone else? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2081384 Title: bluetooth headphones need reconnect after every reboot Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in bluez source package in Oracular: Confirmed Status in linux source package in Oracular: Confirmed Bug description: This issue seems to be caused by a recent package update in oracular. Every time I reboot my desktop my bluetooth headset will fail to connect until I manually go through forget device -> new pairing. journalctl says: 23:13:44 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:45 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:47 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:00 desktop bluetoothd[3274]: No matching connection for device 23:14:04 desktop bluetoothd[3274]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Operation already in progress 23:14:04 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:27 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:15:46 desktop bluetoothd[3274]: /org/bluez/hci0/dev_80_C3_33_59_89_D6/sep7/fd0: fd(43) ready In dmesg I see lots of: [44738.102583] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.325565] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.496566] Bluetooth: hci0: ACL packet for unknown connection handle 3837 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2081384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [
[Kernel-packages] [Bug 2086727] Re: [24.04.02]: mpi3mr: Features and Bug Fixes
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- 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/2086727 Title: [24.04.02]: mpi3mr: Features and Bug Fixes Status in linux package in Ubuntu: New Bug description: Please include the latest mpi3mr upstream accepted patches in the upcoming ubuntu 24.04.02 point kernel. Below are the patch-set: b9e63d6c7c0e scsi: mpi3mr: Validate SAS port assignments e7d67f3f9f9c scsi: mpi3mr: Update driver version to 8.12.0.0.50 4616a4b3cb8a scsi: mpi3mr: Improve wait logic while controller transitions to READY state 6e4c825f267e scsi: mpi3mr: Update MPI Headers to revision 34 fc1ddda33094 scsi: mpi3mr: Use firmware-provided timestamp update interval 9634bb07083c scsi: mpi3mr: Enhance the Enable Controller retry logic 24d7071d9645 scsi: mpi3mr: A performance fix f856e57d6138 scsi: mpi3mr: Driver version update to 8.10.0.5.50 199510e33dea scsi: mpi3mr: Update consumer index of reply queues after every 100 replies 6dc7050d4671 scsi: mpi3mr: Return complete ioc_status for ioctl commands 8c6b808c8c2a scsi: mpi3mr: Avoid MAX_PAGE_ORDER WARNING for buffer allocations 6b9935da2a6b scsi: mpi3mr: Add missing spin_lock_init() for mrioc->trigger_lock a62193abae75 scsi: mpi3mr: struct mpi3_sas_io_unit_page1: Replace 1-element array with flexible array 41bb96296f9d scsi: mpi3mr: struct mpi3_sas_io_unit_page0: Replace 1-element array with flexible array 0e11f97bfddc scsi: mpi3mr: struct mpi3_event_data_pcie_topology_change_list: Replace 1-element array with flexible array ac5b7505de70 scsi: mpi3mr: struct mpi3_event_data_sas_topology_change_list: Replace 1-element array with flexible array 1abc900ddda8 scsi: mpi3mr: Avoid IOMMU page faults on REPORT ZONES cf82b9e866b6 scsi: mpi3mr: Driver version update 1c342b0548e3 scsi: mpi3mr: Prevent PCI writes from driver during PCI error recovery 30bafe1774f0 scsi: mpi3mr: Support PCI Error Recovery callback handlers de24085328c0 scsi: mpi3mr: Correct a test in mpi3mr_sas_port_add() 3f7e469987f8 scsi: mpi3mr: Update driver version to 8.9.1.0.50 78b506984ebe scsi: mpi3mr: Add ioctl support for HDB d8d08d1638ce scsi: mpi3mr: Trigger support fc941140 scsi: mpi3mr: HDB allocation and posting for hardware and firmware buffers 90e6f08915ec scsi: mpi3mr: Fix ATA NCQ priority support 9f365cb8bbd0 scsi: mpi3mr: Use proper format specifier in mpi3mr_sas_port_add() 3668651def2c scsi: mpi3mr: Sanitise num_phys d4309246cf6b scsi: mpi3mr: Avoid possible run-time warning with long manufacturer strings 30efd3823f2c scsi: mpi3mr: Switch to using ->device_configure 310887f688f7 scsi: mpi3mr: Switch to using ->device_configure 9042fb6d2c08 scsi: mpi3mr: Pass queue_limits to bsg_setup_queue() 4373d2ecca7f scsi: bsg: Pass queue_limits to bsg_setup_queue() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086210] Re: Backport some AppArmor complain-mode profile bugfixes from Oracular to Noble
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Noble)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2086210
Title:
Backport some AppArmor complain-mode profile bugfixes from Oracular to
Noble
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Confirmed
Bug description:
SRU Justification:
[Impact]
Backporting two AppArmor bugfixes (2de989ae726b "apparmor: allocate
xmatch for nullpdf inside aa_alloc_null" and 62bd5d5f2149 "apparmor:
properly handle cx/px lookup failure for complain") from the Ubuntu
Oracular kernel will fix incorrect behavior that occurs with the usage
of some complain mode profiles (a kernel oops and an actual denial
occurring in complain mode, respectively).
[Fix]
Apply the two patches 2de989ae726b and 62bd5d5f2149 from the Ubuntu
Oracular kernel, previously applied to the Oracular kernel via LP
#2028253 as #94/99 and #95/99 in the series.
[Test case]
Patch 62bd5d5f2149 can be tested by loading the following profile into
the kernel:
abi ,
include
profile ls_child flags=(complain) {
include
/dev/tty rw,
/usr/bin/ls cxr,
}
and exercising the profile's nonexistent transition with `aa-exec -p
ls_child sh -c ls`. With the patch applied, the ls command will
succeed instead of failing.
Patch 2de989ae726b is much harder to test, unfortunately. The
reproducer I have is (deterministically) finicky but goes through a
Docker indirection layer, although at least one other person has
encountered the same kernel oops without using Docker. I have attached
the files needed to construct a reproducer to the LP bug report.
With the patch applied, the run_reproducer.sh script will succeed
instead of generating a kernel oops.
[Regression potential]
This patch set fixes bugs in the handling of complain mode profiles,
and are both very small. A bug caused by patch 2de989ae726b would
cause, at most, a memory leak by preventing deallocation of a
reference-counted profile object. A bug introduced by patch
62bd5d5f2149 would show up in the handling of complain mode profiles
and would not affect enforcement of enforce mode profiles.
[Other Info]
This patchset backports some patches from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028253 which
were applied to Oracular but not to Noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086210/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086782] Re: [UBUNTU 24.04] Exception handling support is disabled in libc++/libc++abi
I think this (libc++1) applies to source package 'llvm-defaults'. ** Package changed: linux (Ubuntu) => llvm-defaults (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: llvm-defaults (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Also affects: llvm-defaults (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: llvm-defaults (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: llvm-defaults (Ubuntu Plucky) 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/2086782 Title: [UBUNTU 24.04] Exception handling support is disabled in libc++/libc++abi Status in Ubuntu on IBM z Systems: New Status in llvm-defaults package in Ubuntu: New Status in llvm-defaults source package in Noble: New Status in llvm-defaults source package in Oracular: New Status in llvm-defaults source package in Plucky: New Bug description: Currently the C++ exception handling support is disabled for s390x when building libc++/libc++abi packages: ifneq (,$(filter $(DEB_HOST_ARCH),s390x)) STAGE_ALL_CMAKE_EXTRA += -DLLVM_HOST_TRIPLE=s390x-linux-gnu LIBCXX_EXCEPTIONS := OFF However, this is supposed to work on s390x and has already been enabled in other distros. Please, remove the s390x special handling here. Be aware that we used to lack proper libunwind support for Z, what might have triggered this. But this has been solved some time ago. --- Ubuntu package: libc++abi1-18 1:18.1.3-1ubuntu1 --- libunwind could be enabled for s390x as well: # Enable libunwind (or not) LIBUNWIND_ENABLE=yes ifneq (,$(filter $(DEB_HOST_ARCH), s390x armel m68k mipsel mips64el hurd-i386 powerpc sparc sparc64 x32)) LIBUNWIND_ENABLE=no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2086782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2076396] [NEW] Linux, Ubuntu, 22.04, Run CheckBox "Suspend(S3) stress test" fail on Oasis14 MTL
You have been subscribed to a public bug: ● Summary Checkbox-Stress will show fail on Oasis 14/16 MTL ● Reproduce Steps 1.Install the Ubuntu 2.Install checkbox 3.0 3.Run checkbox-stress. 4.It could be found that checkbox will show fail on Suspend-->Issue ● Results ○ Expected Result Checkbox show pass. ○ Actual Result Checkbox show fail on Oasis 14 MTL,we could find below error: stress-tests/suspend-30-cycles-with-reboot-3-log-check failed I/O log High failures: s3: 1 failures Found 1 differences in device configuration during s2idle cycle. (x 1) ● Additional Information ○ Testcase ID：160331.011 ○ SKU：Oasis MTL (Latitude 7450/7650) ○ BIOS Version：1.5.0 ○ Image/Manifest： dell-bto-jammy-jellyfish-oddish-X122-20240717-11.iso ○ CPU：MTL ○ GPU：Intel ○ Failure rate：2/2 cycle ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Assignee: Viral Wang (viralwang) Status: New ** Tags: dm-reviewed jellyfish-oddish -- Linux, Ubuntu, 22.04, Run CheckBox "Suspend(S3) stress test" fail on Oasis14 MTL https://bugs.launchpad.net/bugs/2076396 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 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 2076396] Re: Linux, Ubuntu, 22.04, Run CheckBox "Suspend(S3) stress test" fail on Oasis14 MTL
** Project changed: kernel-sru-workflow => linux-oem-6.5 (Ubuntu) ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Viral Wang (viralwang) ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu) Assignee: Viral Wang (viralwang) => (unassigned) -- 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/2076396 Title: Linux, Ubuntu, 22.04, Run CheckBox "Suspend(S3) stress test" fail on Oasis14 MTL Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: New Bug description: ● Summary Checkbox-Stress will show fail on Oasis 14/16 MTL ● Reproduce Steps 1.Install the Ubuntu 2.Install checkbox 3.0 3.Run checkbox-stress. 4.It could be found that checkbox will show fail on Suspend-->Issue ● Results ○ Expected Result Checkbox show pass. ○ Actual Result Checkbox show fail on Oasis 14 MTL,we could find below error: stress-tests/suspend-30-cycles-with-reboot-3-log-checkfailed I/O log High failures: s3: 1 failures Found 1 differences in device configuration during s2idle cycle. (x 1) ● Additional Information ○ Testcase ID：160331.011 ○ SKU：Oasis MTL (Latitude 7450/7650) ○ BIOS Version：1.5.0 ○ Image/Manifest： dell-bto-jammy-jellyfish-oddish-X122-20240717-11.iso ○ CPU：MTL ○ GPU：Intel ○ Failure rate：2/2 cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2076396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2080495] Re: BCM57416 bnxt_re error during bootup and poweroff
@Kevin
This issue is related to old and unsupported firmware of BCM54716.
Could you update firmware?
Quoted from maintainer:
"
Thank you for providing additional information.
This is a BCM57416 device. I see that the FW version is quite old and this is
an expected failure after the commit "a9a457f338e7 ("RDMA/bnxt_re: Update HW
interface headers")".
Broadcom RoCE solution was not GAed for this FW version and to use RoCE in
production, you will have to update to a latest FW.
Are you okay to update the FW to the latest versions? You can find the
firmware location here:
https://www.broadcom.com/support/download-
search?pg=Ethernet+Connectivity,+Switching,+and+PHYs&pf=Ethernet+Connectivity,+Switching,+and+PHYs&pn=&pa=&po=&dk=&pl=&l=false
Regards,
Kalesh
"
--
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/2080495
Title:
BCM57416 bnxt_re error during bootup and poweroff
Status in linux package in Ubuntu:
Triaged
Bug description:
[Summary]
During the SRU testing, I found a Lenovo workstation has multiple NICs
installed that failed to wake up from cold-reboot by rtc event. After
some investigations, I found that it's because too many kernel message
appear and slow down the power off.
We don't have any connection on those impacted NIC, so we still can
access the machine, but I assume it should also be a regression for
6.8 kerenl.
Those error messages didn't be recorded by journalctl, so I just took
a photo and converted them to text.
[Expected result]
SRU test can continue after cold-reboot
[Actual result]
Cold-reboot takes too long to power off that exceed the wake up time
we set for rtc.
[Additional information]
Following are the DUTs that are impacted.
https://certification.canonical.com/hardware/202310-32275/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.8.0-44-generic 6.8.0-44.44~22.04.1
ProcVersionSignature: Ubuntu 6.8.0-44.44~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckMismatches: ./preseed/project.cfg
CasperMD5CheckResult: fail
Date: Thu Sep 12 16:44:46 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-20240129-711
InstallationDate: Installed on 2024-09-11 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
pc-sutton-jammy-amd64-20240129-711
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.8
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080495/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085162] Re: Bluetooth headphones connect erratically
The attachment "bluez-fix-address.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2085162 Title: Bluetooth headphones connect erratically Status in alsa-driver package in Ubuntu: Invalid Status in bluez package in Ubuntu: New Bug description: Description of the problem A pair of Sony Sony WH-H900N Bluetooth headphones often refuses to re-connect with a Lenovo V15 G2 ALC laptop. These headphones pair without trouble to a MacBook Pro and an Android phone. Step to reproduce: 1. Put the headphones into discovery mode. 2. Go to Settings -> Bluetooth and connect to the headphones. 3. Reboot the laptop. 4. Go to Settings -> Bluetooth 5. Click on the headphones. 6. Try to connect to the headphones. 7. If step 6. fails try to disconnect. 8. Go to step 6. Expected result: After step 6 for headphones to be connected and for headphones to announce "Bluetooth connected". Actual result: Sometimes the "connected" slider slides back to unconnected. Sometimes the slider remains "on" but the headphones don't announce that they are connected and no headphones appear in sound settings. How reproducible is the problem: Fairly reproducible. It can sometimes takes 30 or more connection attempts before a real connection is established. Version information: Ubuntu 24.10 ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:sitsofe8130 F pipewire /dev/snd/controlC0: sitsofe8136 F wireplumber /dev/snd/controlC1: sitsofe8136 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 21:34:28 2024 InstallationDate: Installed on 2024-10-14 (7 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: LENOVO 82KD PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN42WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15 G2 ALC dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrGLCN42WW:bd12/13/2021:br1.42:efr1.42:svnLENOVO:pn82KD:pvrLenovoV15G2ALC:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoV15G2ALC:skuLENOVO_MT_82KD_BU_idea_FM_V15G2ALC: dmi.product.family: V15 G2 ALC dmi.product.name: 82KD dmi.product.sku: LENOVO_MT_82KD_BU_idea_FM_V15 G2 ALC dmi.product.version: Lenovo V15 G2 ALC dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2085162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086789] [NEW] kexec results in kernel panics
Public bug reported: Howdy! We have noticed that when running 'kexec' on Azure VM's running the '6.8.0-1017.20~22.04.1' linux-azure kernel we will see kernel panics. Each panic doesn't have the exact same trace which is confusing to me. Here are a few I've collected: * https://paste.ubuntu.com/p/Vs2VsQvV33/ * https://paste.ubuntu.com/p/yXkN8w6Frh/ I attempted to downgrade to the linux-azure-lts-22.04 5.15.0.1074.72 kernel and to my surprise , the kexec also triggered another panic there: https://paste.ubuntu.com/p/6Xq89qD8VT//. I've been unable to reproduce this on the linux-aws and linux-gcp kernels. I've been able to easily reproduce this behavior on Standard_D8as_v5 and Standard_F32s_v2 instance types. It doesn't appear to matter what kernel args are passed into the kexec. My go to so far is a simple 'sudo kexec -l /boot/vmlinuz --command-line="$(cat /proc/cmdline) fake-new-kernel-arg=1" -f' command which triggers it. It does seem that one of the kernel args needs to change for this to happen, simply running 'sudo kexec -l /boot/vmlinuz --command-line="$(cat /proc/cmdline)" -f' doesn't appear to reproduce the panics. It looks like this wasn't a problem on the previous 6.5 linux-azure kernel (which makes the 5.15 repro particularly surprising...). For reference, we currently use these args: `BOOT_IMAGE=/boot/vmlinuz-6.8.0-1017-azure root=PARTUUID=uuid-here ro console=tty1 console=ttyS0 earlyprintk=ttyS0 nvme_core.io_timeout=240 apparmor=1 security=apparmor ipv6.disable=1 transparent_hugepage=madvise systemd.unified_cgroup_hierarchy=0 systemd.legacy_systemd_cgroup_controller=true panic=-1` >From my testing, eventually the systems will stabilize and stop panicking but it's been undetermined as to why. I've also noticed cases where a 'kexec' will happen and not trigger the panics but, that's seemingly rare. I'd appreciate any help trying to debug this and am more than happy to provide additional testing/repro info as needed. Thanks! ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/2086789 Title: kexec results in kernel panics Status in linux-azure package in Ubuntu: New Bug description: Howdy! We have noticed that when running 'kexec' on Azure VM's running the '6.8.0-1017.20~22.04.1' linux-azure kernel we will see kernel panics. Each panic doesn't have the exact same trace which is confusing to me. Here are a few I've collected: * https://paste.ubuntu.com/p/Vs2VsQvV33/ * https://paste.ubuntu.com/p/yXkN8w6Frh/ I attempted to downgrade to the linux-azure-lts-22.04 5.15.0.1074.72 kernel and to my surprise , the kexec also triggered another panic there: https://paste.ubuntu.com/p/6Xq89qD8VT//. I've been unable to reproduce this on the linux-aws and linux-gcp kernels. I've been able to easily reproduce this behavior on Standard_D8as_v5 and Standard_F32s_v2 instance types. It doesn't appear to matter what kernel args are passed into the kexec. My go to so far is a simple 'sudo kexec -l /boot/vmlinuz --command-line="$(cat /proc/cmdline) fake-new-kernel-arg=1" -f' command which triggers it. It does seem that one of the kernel args needs to change for this to happen, simply running 'sudo kexec -l /boot/vmlinuz --command-line="$(cat /proc/cmdline)" -f' doesn't appear to reproduce the panics. It looks like this wasn't a problem on the previous 6.5 linux-azure kernel (which makes the 5.15 repro particularly surprising...). For reference, we currently use these args: `BOOT_IMAGE=/boot/vmlinuz-6.8.0-1017-azure root=PARTUUID=uuid-here ro console=tty1 console=ttyS0 earlyprintk=ttyS0 nvme_core.io_timeout=240 apparmor=1 security=apparmor ipv6.disable=1 transparent_hugepage=madvise systemd.unified_cgroup_hierarchy=0 systemd.legacy_systemd_cgroup_controller=true panic=-1` From my testing, eventually the systems will stabilize and stop panicking but it's been undetermined as to why. I've also noticed cases where a 'kexec' will happen and not trigger the panics but, that's seemingly rare. I'd appreciate any help trying to debug this and am more than happy to provide additional testing/repro info as needed. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2086789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086791] [NEW] mlxbf-gige: Support workaround for MDIO GPIO degradation bug
Public bug reported: SRU Justification: [Impact] Once the BF3 MDIO clock is enabled by software it is expected and intended for it to keep toggling. BF3 has a hardware GPIO bug where constant toggling at "high frequencies" will lead to GPIO degradation. [Fix] * A workaround is to lower down the clock frequency. * That will increase the "life expectation" of the GPIO. * The lowest possible frequency we can achieve is 1.09Mhz by setting mdio_period = 0xFF. [Test Case] * Check if the gige driver is loaded * Check that the oob_net0 interface is up and operational * Check that the OOB gets an ip * Do SW reset and powercycle and check the oon_net0 interface again [Regression Potential] * Lowering the frequency shouldn't have any impact but it controls the access to the PHY registers. So do the usual OOB tests to verify that there is indeed no impact. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2086791 Title: mlxbf-gige: Support workaround for MDIO GPIO degradation bug Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Once the BF3 MDIO clock is enabled by software it is expected and intended for it to keep toggling. BF3 has a hardware GPIO bug where constant toggling at "high frequencies" will lead to GPIO degradation. [Fix] * A workaround is to lower down the clock frequency. * That will increase the "life expectation" of the GPIO. * The lowest possible frequency we can achieve is 1.09Mhz by setting mdio_period = 0xFF. [Test Case] * Check if the gige driver is loaded * Check that the oob_net0 interface is up and operational * Check that the OOB gets an ip * Do SW reset and powercycle and check the oon_net0 interface again [Regression Potential] * Lowering the frequency shouldn't have any impact but it controls the access to the PHY registers. So do the usual OOB tests to verify that there is indeed no impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2086791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086758] Re: [Driver Readiness] Intel BE201 Bluetooth
Sorry, I didn't notice that someone has already opened an SRU bug already. Please ignore this bug. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2086758 Title: [Driver Readiness] Intel BE201 Bluetooth Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Invalid Bug description: [Impact] Update Ubuntu linux-firmware to support Intel BE201 BT. [Fix] Cherry-pick upstream commit: fe16af92ca833c linux-firmware: Update firmware file for Intel BlazarI core [Test Plan] 1. Boot into the Ubuntu kernel 2. Test the functionality of Bluetooth [Where problems could occur] May cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086549] Re: Intel Iris Xe Graphics: System freeze with kernel 6.8.0-48 on TigerLake (Ubuntu 22.04.4 LTS)
I'm seeing similar issue for a user at our organisation. Same make/model of laptop. Same error message: i915 :00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)! Apparently shutting the lid (suspend) then wake seems to temporarily fix the problem. -- 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/2086549 Title: Intel Iris Xe Graphics: System freeze with kernel 6.8.0-48 on TigerLake (Ubuntu 22.04.4 LTS) Status in linux package in Ubuntu: Confirmed Bug description: Description: After upgrading to kernel 6.8.0-48-generic (version 6.8.0-48.48~22.04.1, via unattended upgrade on Nov 1st, 2024), my system experiences complete freezes requiring hard reboot. Expected behavior: - System should remain stable and responsive - Graphics should function normally Actual behavior: - System freezes completely within minutes of booting - Requires hard reboot (power button hold) - Logs show error: "i915 :00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!" System information: - Ubuntu version: 22.04.4 LTS (jammy) - Kernel package: linux-image-6.8.0-48-generic (6.8.0-48.48~22.04.1) - Hardware: Dell laptop with Intel TigerLake-LP GT2 [Iris Xe Graphics] - Previous kernel 6.8.0-47-generic worked correctly - Current workaround: Using kernel 5.15.0-124-generic which works properly Steps to reproduce: 1. Boot with kernel 6.8.0-48-generic 2. System freezes within minutes 3. No specific trigger action required - happens during normal use ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-124-generic 5.15.0-124.134 ProcVersionSignature: Ubuntu 5.15.0-124.134-generic 5.15.163 Uname: Linux 5.15.0-124-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 1785 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 20:48:18 2024 InstallationDate: Installed on 2022-10-24 (740 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Latitude 7420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-124-generic root=UUID=a56ad61f-f787-46ac-b830-f6797e3ffdf4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-124-generic N/A linux-backports-modules-5.15.0-124-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.30 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-24 (740 days ago) dmi.bios.date: 09/14/2022 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd09/14/2022:br1.20:svnDellInc.:pnLatitude7420:pvr:rvnDellInc.:rn07MHG4:rvrA00:cvnDellInc.:ct10:cvr:sku0A36: dmi.product.family: Latitude dmi.product.name: Latitude 7420 dmi.product.sku: 0A36 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2080498] Re: Default session type changed from Xorg to Wayland in some installs of 22.04 on Nvidia hybrids since kernel 6.8
** Description changed: - [Summary] - On HP ZBook Fury G11 platform preloaded with Ubuntu 22.04. The windowing system in "Settings -> About" is Xorg. After doing kernel upgrade from 6.5-oem to 6.8-hwe, windowing system become Wayland. + [ Impact ] + On some nvidia hybrid systems, like the HP ZBook Fury G11 platform + preloaded with Ubuntu 22.04, the windowing system in "Settings -> About" + used to be Xorg but after doing kernel upgrade from 6.5-oem to 6.8-hwe, + the windowing system become Wayland. - [Reproduce Steps] - 1. Update kernel by command "sudo apt install linux-image-oem-22.04d linux-modules-nvidia-535-oem-22.04d" - 2. Reboot system - 3. After enter desktop, check windowing system via "Settings -> About" + There is a race condition in udev rules that makes the default desktop + session either Xorg or Wayland depending on the ordering of hardware + discovery and modules loading. This would affect both jammy and noble, + but being a race condition it is unpredictable which hardware defaults + to which desktop session, and the same hardware may behave differently + in jammy vs in noble. - [Results] - Expected: Windowing system remain Xorg - Actual: Windowing system become Wayland + The intended default desktop session was meant to be Wayland, however + the vast majority of nvidia hybrid laptops defaulted to Xorg at launch, + including and particularly all Ubuntu Certified laptops. For this reason + we're considering this a bug and are taking measures to ensure that all + nvidia hybrid laptops keep defaulting to Xorg. + + The fix removes the udev logic that was trying to make nvidia hybrid + laptops specifically prefer Wayland, making that hardware use the same + udev rules as nvidia desktops which already default to Xorg. + + [ Test Plan ] + + 1. Set up a nvidia hybrid laptop with Ubuntu 22.04 or 24.04 + 2. Install the latest updates, particularly the latest kernel + 2. Install the gdm3 update from this bug + 3. Create a new a new User on the system + 3. Reboot + 4. At the log-in screen, select the new User + 5. Verify that there is a cogwheel icon at the bottom-right of the screen. + 6. Click on the cogwheel icon to open up the menu + 7. Verify that the selected option is "Ubuntu" + 8. Verify that the alternative option is "Ubuntu on Wayland" + 9. Close the menu without changing the selection + 10. Log-in + 11. Verify via "Settings -> About" that "Windowing System" is X11 + + [ Where problems could occur ] + + The patch only touches the gdm udev rules, only removing some broken udev rules that matched specific hardware configurations. + At worst, Wayland on nvidia laptops could end up completely hidden away rather than opt-in -- it is expected to do so only for nvidia driver versions < 470. + + There should be no regression potential for nvidia desktops or non- + nvidia hardware, because such hardware would not have matched the udev + rules that are being removed here. ** No longer affects: linux-hwe-6.8 (Ubuntu) ** Also affects: gdm3 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: [ Impact ] On some nvidia hybrid systems, like the HP ZBook Fury G11 platform preloaded with Ubuntu 22.04, the windowing system in "Settings -> About" used to be Xorg but after doing kernel upgrade from 6.5-oem to 6.8-hwe, the windowing system become Wayland. There is a race condition in udev rules that makes the default desktop session either Xorg or Wayland depending on the ordering of hardware discovery and modules loading. This would affect both jammy and noble, but being a race condition it is unpredictable which hardware defaults to which desktop session, and the same hardware may behave differently in jammy vs in noble. The intended default desktop session was meant to be Wayland, however the vast majority of nvidia hybrid laptops defaulted to Xorg at launch, including and particularly all Ubuntu Certified laptops. For this reason we're considering this a bug and are taking measures to ensure that all nvidia hybrid laptops keep defaulting to Xorg. The fix removes the udev logic that was trying to make nvidia hybrid laptops specifically prefer Wayland, making that hardware use the same udev rules as nvidia desktops which already default to Xorg. [ Test Plan ] 1. Set up a nvidia hybrid laptop with Ubuntu 22.04 or 24.04 2. Install the latest updates, particularly the latest kernel - 2. Install the gdm3 update from this bug + 2. Install the gdm3 update being tested 3. Create a new a new User on the system 3. Reboot 4. At the log-in screen, select the new User 5. Verify that there is a cogwheel icon at the bottom-right of the screen. 6. Click on the cogwheel icon to open up the menu 7. Verify that the selected option is "Ubuntu" 8. Verify that the alternative option is "Ubuntu on Wayland" 9. Close the
[Kernel-packages] [Bug 2086758] Re: [Driver Readiness] Intel BE201 Bluetooth
You should mark this bug as a duplicate of the other SRU bug: what's the bug number? -- 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/2086758 Title: [Driver Readiness] Intel BE201 Bluetooth Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Invalid Bug description: [Impact] Update Ubuntu linux-firmware to support Intel BE201 BT. [Fix] Cherry-pick upstream commit: fe16af92ca833c linux-firmware: Update firmware file for Intel BlazarI core [Test Plan] 1. Boot into the Ubuntu kernel 2. Test the functionality of Bluetooth [Where problems could occur] May cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086782] [NEW] [UBUNTU 24.04] Exception handling support is disabled in libc++/libc++abi
Public bug reported: Currently the C++ exception handling support is disabled for s390x when building libc++/libc++abi packages: ifneq (,$(filter $(DEB_HOST_ARCH),s390x)) STAGE_ALL_CMAKE_EXTRA += -DLLVM_HOST_TRIPLE=s390x-linux-gnu LIBCXX_EXCEPTIONS := OFF However, this is supposed to work on s390x and has already been enabled in other distros. Please, remove the s390x special handling here. Be aware that we used to lack proper libunwind support for Z, what might have triggered this. But this has been solved some time ago. --- Ubuntu package: libc++abi1-18 1:18.1.3-1ubuntu1 --- libunwind could be enabled for s390x as well: # Enable libunwind (or not) LIBUNWIND_ENABLE=yes ifneq (,$(filter $(DEB_HOST_ARCH), s390x armel m68k mipsel mips64el hurd-i386 powerpc sparc sparc64 x32)) LIBUNWIND_ENABLE=no ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-208925 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-208925 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/2086782 Title: [UBUNTU 24.04] Exception handling support is disabled in libc++/libc++abi Status in linux package in Ubuntu: New Bug description: Currently the C++ exception handling support is disabled for s390x when building libc++/libc++abi packages: ifneq (,$(filter $(DEB_HOST_ARCH),s390x)) STAGE_ALL_CMAKE_EXTRA += -DLLVM_HOST_TRIPLE=s390x-linux-gnu LIBCXX_EXCEPTIONS := OFF However, this is supposed to work on s390x and has already been enabled in other distros. Please, remove the s390x special handling here. Be aware that we used to lack proper libunwind support for Z, what might have triggered this. But this has been solved some time ago. --- Ubuntu package: libc++abi1-18 1:18.1.3-1ubuntu1 --- libunwind could be enabled for s390x as well: # Enable libunwind (or not) LIBUNWIND_ENABLE=yes ifneq (,$(filter $(DEB_HOST_ARCH), s390x armel m68k mipsel mips64el hurd-i386 powerpc sparc sparc64 x32)) LIBUNWIND_ENABLE=no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086741] Re: apt get update fails to download arm64 packages
non-x86 packages are hosted on ports, not archive. I.e., you need to use azure.ports.ubuntu.com. http://azure.ports.ubuntu.com/dists/noble/main/binary-arm64/ ** Changed in: linux-signed-azure (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/2086741 Title: apt get update fails to download arm64 packages Status in linux-signed-azure package in Ubuntu: Invalid Bug description: binary-arm64 packages are missing from azure.archive.ubuntu.com. Hence, apt-get update (in ubuntu 24.04) is failing with 404 error status while trying to down load the package via this URL (http://azure.archive.ubuntu.com/ubuntu/dists/noble/main/binary-arm64/Packages). Trying to reach the url from the browser also fails. It seems the folder (path) binary-arm64 are missing. Kindly add the binary-arm64 packages to the same. == Required details == Output of `lsb_release -a` Distributor ID: Ubuntu Description: Ubuntu 24.04.1 LTS Release: 24.04 Codename: noble =Steps to reproduce === In an Azure VM with Ubuntu 24.04 execute the below commands - sudo dpkg --add-architecture arm64 sudo apt update Expected output The arm64 packages should get installed successfully along with amd64 packages === Actual output The command fails with ` Fetched 97.4 MB in 9s (11.2 MB/s) Reading package lists... E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/noble/main/binary-arm64/Packages 404 Not Found [IP: 52.252.163.49 80] E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/noble-updates/main/binary-arm64/Packages 404 Not Found [IP: 52.252.163.49 80] E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/noble-backports/universe/binary-arm64/Packages 404 Not Found [IP: 52.252.163.49 80] E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/noble-security/main/binary-arm64/Packages 404 Not Found [IP: 52.252.163.49 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Error: Process completed with exit code 100. We have a complete Github Actions pipeline workflow log in the below URL with the error message - https://github.com/subir0071/Samples-ravengine/actions/runs/11692216732/job/32561072667 Kindly help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-azure/+bug/2086741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086549] Re: Intel Iris Xe Graphics: System freeze with kernel 6.8.0-48 on TigerLake (Ubuntu 22.04.4 LTS)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2086549 Title: Intel Iris Xe Graphics: System freeze with kernel 6.8.0-48 on TigerLake (Ubuntu 22.04.4 LTS) Status in linux package in Ubuntu: Confirmed Bug description: Description: After upgrading to kernel 6.8.0-48-generic (version 6.8.0-48.48~22.04.1, via unattended upgrade on Nov 1st, 2024), my system experiences complete freezes requiring hard reboot. Expected behavior: - System should remain stable and responsive - Graphics should function normally Actual behavior: - System freezes completely within minutes of booting - Requires hard reboot (power button hold) - Logs show error: "i915 :00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!" System information: - Ubuntu version: 22.04.4 LTS (jammy) - Kernel package: linux-image-6.8.0-48-generic (6.8.0-48.48~22.04.1) - Hardware: Dell laptop with Intel TigerLake-LP GT2 [Iris Xe Graphics] - Previous kernel 6.8.0-47-generic worked correctly - Current workaround: Using kernel 5.15.0-124-generic which works properly Steps to reproduce: 1. Boot with kernel 6.8.0-48-generic 2. System freezes within minutes 3. No specific trigger action required - happens during normal use ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-124-generic 5.15.0-124.134 ProcVersionSignature: Ubuntu 5.15.0-124.134-generic 5.15.163 Uname: Linux 5.15.0-124-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 1785 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 20:48:18 2024 InstallationDate: Installed on 2022-10-24 (740 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Latitude 7420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-124-generic root=UUID=a56ad61f-f787-46ac-b830-f6797e3ffdf4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-124-generic N/A linux-backports-modules-5.15.0-124-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.30 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-24 (740 days ago) dmi.bios.date: 09/14/2022 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd09/14/2022:br1.20:svnDellInc.:pnLatitude7420:pvr:rvnDellInc.:rn07MHG4:rvrA00:cvnDellInc.:ct10:cvr:sku0A36: dmi.product.family: Latitude dmi.product.name: Latitude 7420 dmi.product.sku: 0A36 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
Hi there, I had this flickering issue with Ubuntu 22.04 and recently I did a fresh installation of Ubuntu 24.04 with the big hope of getting rid of this flickering issue. However, to my big disappointment, it did not fix the issue and was even of worse kind. I followed some posts and tried out the proposed solution ``` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" sudo update-grub sudo reboot ``` It did help instantly to some extent however the problem remained. ``` Linux ThinkPad-L13-Yoga-Gen-4 6.8.0-1014-oem #14-Ubuntu SMP PREEMPT_DYNAMIC Wed Oct 9 13:16:31 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ``` In case, if there is any better fix for this issue, please do let me know. Thank you, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.8 package in Ubuntu: Confirmed Status in linux source package in Lunar: Won't Fix Status in linux-hwe-5.19 source package in Lunar: Invalid Status in linux-hwe-6.2 source package in Lunar: Invalid Status in linux-hwe-6.5 source package in Lunar: Won't Fix Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
sorry for the double message, I could not see my earlier posted message, so posted twice. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.8 package in Ubuntu: Confirmed Status in linux source package in Lunar: Won't Fix Status in linux-hwe-5.19 source package in Lunar: Invalid Status in linux-hwe-6.2 source package in Lunar: Invalid Status in linux-hwe-6.5 source package in Lunar: Won't Fix Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
Hi there, I had the same issue with Ubuntu 22.04, where I really could not fix it. Recently I did a fresh installation of Ubuntu 24.04 with the big hope of getting rid of this annoying flickering issue. However, no, it did persist and even in most worse form. I did follow few threads on this and did the proposed fix ``` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" sudo update-grub sudo reboot ``` It did make it bit better instantly, however did not fix it completely. here is my computer info: ``` uname -a Linux ThinkPad-L13-Yoga-Gen-4 6.8.0-1014-oem #14-Ubuntu SMP PREEMPT_DYNAMIC Wed Oct 9 13:16:31 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ``` I wonder if there is any other better fix for this problem? regards, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.8 package in Ubuntu: Confirmed Status in linux source package in Lunar: Won't Fix Status in linux-hwe-5.19 source package in Lunar: Invalid Status in linux-hwe-6.2 source package in Lunar: Invalid Status in linux-hwe-6.5 source package in Lunar: Won't Fix Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086782] [NEW] [UBUNTU 24.04] Exception handling support is disabled in libc++/libc++abi
You have been subscribed to a public bug: Currently the C++ exception handling support is disabled for s390x when building libc++/libc++abi packages: ifneq (,$(filter $(DEB_HOST_ARCH),s390x)) STAGE_ALL_CMAKE_EXTRA += -DLLVM_HOST_TRIPLE=s390x-linux-gnu LIBCXX_EXCEPTIONS := OFF However, this is supposed to work on s390x and has already been enabled in other distros. Please, remove the s390x special handling here. Be aware that we used to lack proper libunwind support for Z, what might have triggered this. But this has been solved some time ago. --- Ubuntu package: libc++abi1-18 1:18.1.3-1ubuntu1 --- libunwind could be enabled for s390x as well: # Enable libunwind (or not) LIBUNWIND_ENABLE=yes ifneq (,$(filter $(DEB_HOST_ARCH), s390x armel m68k mipsel mips64el hurd-i386 powerpc sparc sparc64 x32)) LIBUNWIND_ENABLE=no ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-208925 severity-high targetmilestone-inin--- -- [UBUNTU 24.04] Exception handling support is disabled in libc++/libc++abi https://bugs.launchpad.net/bugs/2086782 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 2074215] Re: [SRU] UBSAN warnings in bnx2x kernel driver
** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2074215 Title: [SRU] UBSAN warnings in bnx2x kernel driver Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Released Bug description: [impact] Currently in the bnx2x kernel driver there are reads/writes that occur out of bounds that have the possibility to cause kernel crashes. No meaningful impact has been observed yet other than UBSAN stack traces. I have posted a patch upstream to resolve this issue (134061163ee5 bnx2x: Fix multiple UBSAN array-index-out-of-bounds) and it has been accepted and merged. Although these traces appear only on linux version 6.5 and up, this bug also affects kernels 6.x and 5.x as well but no UBSAN warnings will be printed on these kernels since they were not enforced in these kernels. [Test Plan] There are multiple ways to reproduce the issue. But the most hands free way to reproduce it would be to utilize a Qlogic NIC that makes use of the E2 controller on a system with more than 32 cores. Below are both ways this can be reproduced. Please note that both will require a NIC that makes use of the bnx2x driver. * Normal Reproduction: 1. start a machine running kernel 6.5 or higher with a a number of cores above 32. Please note that these need to be physical cores not threads. The machine also needs to be using a NIC that utilizes an E2 controller. 2. In dmesg the following UBSAN warnings can be seen: UBSAN: array-index-out-of-bounds in drivers/net/ethernet/broadcom/bnx2x/bnx2x_stats.c:1529:11 index 20 is out of range for type 'stats_query_entry [19]' CPU: 12 PID: 858 Comm: systemd-network Not tainted 6.9.0-060900rc7-generic #202405052133 Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 10/21/2019 Call Trace: dump_stack_lvl+0x76/0xa0 dump_stack+0x10/0x20 __ubsan_handle_out_of_bounds+0xcb/0x110 bnx2x_prep_fw_stats_req+0x2e1/0x310 [bnx2x] bnx2x_stats_init+0x156/0x320 [bnx2x] bnx2x_post_irq_nic_init+0x81/0x1a0 [bnx2x] bnx2x_nic_load+0x8e8/0x19e0 [bnx2x] bnx2x_open+0x16b/0x290 [bnx2x] __dev_open+0x10e/0x1d0 RIP: 0033:0x736223927a0a Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89 RSP: 002b:7ffc0bb2ada8 EFLAGS: 0246 ORIG_RAX: 002c RAX: ffda RBX: 583df50f9c78 RCX: 736223927a0a RDX: 0020 RSI: 583df50ee510 RDI: 0003 RBP: 583df50d4940 R08: 7ffc0bb2adb0 R09: 0080 R10: R11: 0246 R12: 583df5103ae0 R13: 035a R14: 583df50f9c30 R15: 583ddf00 ---[ end trace ]--- [ cut here ] UBSAN: array-index-out-of-bounds in drivers/net/ethernet/broadcom/bnx2x/bnx2x_stats.c:1546:11 index 28 is out of range for type 'stats_query_entry [19]' CPU: 12 PID: 858 Comm: systemd-network Not tainted 6.9.0-060900rc7-generic #202405052133 Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 10/21/2019 Call Trace: dump_stack_lvl+0x76/0xa0 dump_stack+0x10/0x20 __ubsan_handle_out_of_bounds+0xcb/0x110 bnx2x_prep_fw_stats_req+0x2fd/0x310 [bnx2x] bnx2x_stats_init+0x156/0x320 [bnx2x] bnx2x_post_irq_nic_init+0x81/0x1a0 [bnx2x] bnx2x_nic_load+0x8e8/0x19e0 [bnx2x] bnx2x_open+0x16b/0x290 [bnx2x] __dev_open+0x10e/0x1d0 RIP: 0033:0x736223927a0a Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89 RSP: 002b:7ffc0bb2ada8 EFLAGS: 0246 ORIG_RAX: 002c RAX: ffda RBX: 583df50f9c78 RCX: 736223927a0a RDX: 0020 RSI: 583df50ee510 RDI: 0003 RBP: 583df50d4940 R08: 7ffc0bb2adb0 R09: 0080 R10: R11: 0246 R12: 583df5103ae0 R13: 035a R14: 583df50f9c30 R15: 583ddf00 ---[ end trace ]--- [ cut here ] UBSAN: array-index-out-of-bounds in drivers/net/ethernet/broadcom/bnx2x/bnx2x_sriov.c:1895:8 index 29 is out of range for type 'stats_query_entry [19]' CPU: 13 PID: 163 Comm: kworker/u96:1 Not tainted 6.9.0-060900rc7-generic #202405052133 Hardware name: HP ProLiant DL360 Gen9/ProLiant
[Kernel-packages] [Bug 2086137] Re: 24.10 hangs on lock screen upon wake up from hibernate
Reverting status to 'New' on behalf of reporter as requested in comment #2. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2086137 Title: 24.10 hangs on lock screen upon wake up from hibernate Status in linux package in Ubuntu: New Bug description: After upgrade to 24.10, the system hangs on lock screen upon wake up from hibernation. This happens with and without external monitor attached. It doesn't respond to any keystroke at all. --- ProblemType: Bug ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:khteh 4479 F pipewire /dev/snd/controlC0: khteh 4483 F wireplumber /dev/snd/controlC1: khteh 4479 F pipewire khteh 4483 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.10 InstallationDate: Installed on 2021-10-20 (1110 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YUCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-9-generic root=UUID=d1b988e4-bae6-4b16-a5e8-da58f44d75f4 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.11.0-9-generic N/A linux-backports-modules-6.11.0-9-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 Tags: oracular wayland-session Uname: Linux 6.11.0-9-generic x86_64 UpgradeStatus: Upgraded to oracular on 2024-10-25 (9 days ago) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev root sambashare sudo syslog _MarkForUpload: True dmi.bios.date: 07/09/2024 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: N37ET55W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20YUCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN37ET55W(1.36):bd07/09/2024:br1.36:efr1.8:svnLENOVO:pn20YUCTO1WW:pvrThinkPadP17Gen2i:rvnLENOVO:rn20YUCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YU_BU_Think_FM_ThinkPadP17Gen2i: dmi.product.family: ThinkPad P17 Gen 2i dmi.product.name: 20YUCTO1WW dmi.product.sku: LENOVO_MT_20YU_BU_Think_FM_ThinkPad P17 Gen 2i dmi.product.version: ThinkPad P17 Gen 2i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2082225] Re: Service LED will show 1A8W when unplug WD22TB4 with TBT3 HDD then resume from suspend
** Tags removed: verification-needed-noble-linux-oem-6.11 ** Tags added: verification-done-noble-linux-oem-6.11 -- 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/2082225 Title: Service LED will show 1A8W when unplug WD22TB4 with TBT3 HDD then resume from suspend Status in linux package in Ubuntu: In Progress Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: Fix Committed Status in linux source package in Oracular: In Progress Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [Reproduce Steps] 1. Clean Install Ubuntu 24.04 image with USB Key 2. Boot to Ubuntu OS 3. Plug WD22TB4 with TBT3 HDD. 4. Let system enter suspend. 5. Wait 1-min. 6. Unplug WD22TB4. 7. Press anykey wake system from suspend. <--Service LED will show 1A8W. [Results] Expected Result:System will normal resume from suspend. Actual Result:Service LED show 1A8W [Additional Information] This issue will VNP when WD22TB4 without TBT HDD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2082225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085437] Re: BT Switch cannot open under Ubuntu 24.04 on MT7920
** Tags removed: verification-needed-noble-linux-oem-6.11 ** Tags added: verification-done-noble-linux-oem-6.11 -- 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/2085437 Title: BT Switch cannot open under Ubuntu 24.04 on MT7920 Status in linux package in Ubuntu: Invalid Status in linux-oem-6.11 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: Fix Committed Bug description: [Impact] With MT7920 on certain DUT in Dell platform, bluetooth switch (in GNOME desktop settings) cannot be opened. [Fix] The upstream fix is still under review here: https://lore.kernel.org/lkml/20240822052310.25220-1-hao@mediatek.com/ We'd apply this patch as a sauce patch to Noble oem-6.11 out of urgency. [Test Plan] 1. Plug MT7920 to SUT. 2. Manually Install Ubuntu 24.04 OS. 3. Boot into Ubuntu OS. 4. Check MT7920 function. [Where problems could occur] May cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085410] Re: Fix USB device suspend failure while HCD in S4 wakeup
** Changed in: linux (Ubuntu Plucky) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux-oem-6.11 (Ubuntu Noble) Assignee: (unassigned) => Chris Chiu (mschiu77) -- 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/2085410 Title: Fix USB device suspend failure while HCD in S4 wakeup Status in linux package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: New Status in linux-oem-6.11 source package in Noble: Fix Committed Status in linux source package in Oracular: New Status in linux-oem-6.11 source package in Oracular: Invalid Status in linux source package in Plucky: New Status in linux-oem-6.11 source package in Plucky: Invalid Bug description: [SRU Justification] [Impact] More and more USB device suspend failure are caused by the un-expected HCD_FLAG_WAKEUP_PENDING on the USB host controller. It mostly happens on the USB devices connected to the high-speed root hub. It randomly happens when put the system into suspend [Fix] Fixed by the upstream fix https://lore.kernel.org/linux-usb/20241012094633.126736-1-duancheng...@kylinos.cn/. Set wakeup to false if suspend type is either PM_EVENT_FREEZE or PM_EVENT_QUIESCE [Test Case] 1. Power on machine and connect a USB device to the high-speed root hub. (Find your device in lsusb in the secondary root hub) 2. run checkbox-cli run com.canonical.certification::suspend-cycles-stress-test 3. observe the suspend/resume fail with the kernel message [Where problems could occur] Add more restriction on how the wakeup should be performed. Should be low risk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085065] Re: Fix spurious wakeup on HP ProOne 440
** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux-oem-6.11 (Ubuntu Noble) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux-oem-6.11 (Ubuntu Oracular) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2085065 Title: Fix spurious wakeup on HP ProOne 440 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux source package in Noble: In Progress Status in linux-oem-6.11 source package in Noble: New Status in linux source package in Oracular: New Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [SRU Justification] [Impact] The HP ProOne 440 AIO PC with particular LG touch panel connected via high-speed USB root hub will randomly fail to enter suspend. [Fix] Fixed by a quirk for the particular HP model with LG touch panel in https://lore.kernel.org/platform-driver-x86/20240906053047.459036-1-kai.heng.f...@canonical.com/T/#m1b1f48fea9626a4fb5f199ef2304d2f61ed43f52 [Test Case] 1. Power on the HP AIO PC 2. run checkbox-cli run com.canonical.certification::suspend-cycles-stress-test 3. observe the suspend fail with the kernel message (PM: Some devices failed to suspend, or early wake event detected) [Where problems could occur] Only affect the particular HP AIO PC. The risk is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2085065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
With tousled layers and a mullet-inspired silhouette, the wolf cut creates a daring style. zhttp://wolfcut.org/ -- 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in linux source package in Vivid: Fix Released Status in linux package in Fedora: Won't Fix Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad". This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
With tousled layers and a mullet-inspired silhouette, the wolf cut creates a daring style. https://wolfcut.org/ -- 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in linux source package in Vivid: Fix Released Status in linux package in Fedora: Won't Fix Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad". This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2081652] Re: Battery not charging after suspend on Galaxy Book 4
I had similar issue. In my case, the laptop (Galaxy Book 4, which has dual boot with original Windows OS provided by Samsung by default) stopped charging due to a setting in "Samsung Settings" app in Windows, which limited batery charge to 80% in order to preserve battery life. After disabling that feature in Windows, the laptop battery started to charge normally, as it should. I don't understand how "Samsung Settings" on Windows can affect power supply on (dual boot) Linux, but in my case it was the cause. -- 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/2081652 Title: Battery not charging after suspend on Galaxy Book 4 Status in linux package in Ubuntu: Incomplete Bug description: Description: I am experiencing an issue with my Galaxy Book 4 where, after disconnecting the notebook from the power supply (AC) and suspending it, using it on battery for a while, the battery does not start charging again when I reconnect the charger. This happens after any period of use without being plugged in. Steps to reproduce: Connect the notebook to the charger. Disconnect the charger and suspend the notebook. Use the notebook unplugged Reconnect the charger. Expected behavior: The battery should start charging as soon as the charger is reconnected. Observed behavior: The battery remains at the same percentage and does not charge. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-45-generic 6.8.0-45.45 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:felipe 1798 F pipewire /dev/snd/controlC0: felipe 1798 F pipewire felipe 1803 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Sep 22 15:58:19 2024 InstallationDate: Installed on 2024-08-16 (37 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: SAMSUNG ELECTRONICS CO., LTD. 750XGK ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=07d7e1fc-ff25-4e07-aed8-b4e8fd1703f0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-45-generic N/A linux-backports-modules-6.8.0-45-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P02CFP.015.240409.HQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP750XGJ-KG2BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLB701A0F-C01-G002-S0001+10.0.22631 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP02CFP.015.240409.HQ:bd04/09/2024:br5.27:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XGK:pvrP02CFP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XGJ-KG2BR:rvrSGLB701A0F-C01-G002-S0001+10.0.22631:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-RPLU-PCFP: dmi.product.family: Galaxy Book4 dmi.product.name: 750XGK dmi.product.sku: SCAI-A5A5-A5A5-RPLU-PCFP dmi.product.version: P02CFP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2081652] Re: Battery not charging after suspend on Galaxy Book 4
Other curious thing to add, is that while the above refered "Samsung Setting" on Windows was active, not only laptop battery stoped charging, but battery charge percentage stopped measuring, showing the last reading without lowering. -- 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/2081652 Title: Battery not charging after suspend on Galaxy Book 4 Status in linux package in Ubuntu: Incomplete Bug description: Description: I am experiencing an issue with my Galaxy Book 4 where, after disconnecting the notebook from the power supply (AC) and suspending it, using it on battery for a while, the battery does not start charging again when I reconnect the charger. This happens after any period of use without being plugged in. Steps to reproduce: Connect the notebook to the charger. Disconnect the charger and suspend the notebook. Use the notebook unplugged Reconnect the charger. Expected behavior: The battery should start charging as soon as the charger is reconnected. Observed behavior: The battery remains at the same percentage and does not charge. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-45-generic 6.8.0-45.45 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:felipe 1798 F pipewire /dev/snd/controlC0: felipe 1798 F pipewire felipe 1803 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Sep 22 15:58:19 2024 InstallationDate: Installed on 2024-08-16 (37 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: SAMSUNG ELECTRONICS CO., LTD. 750XGK ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=07d7e1fc-ff25-4e07-aed8-b4e8fd1703f0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-45-generic N/A linux-backports-modules-6.8.0-45-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P02CFP.015.240409.HQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP750XGJ-KG2BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLB701A0F-C01-G002-S0001+10.0.22631 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP02CFP.015.240409.HQ:bd04/09/2024:br5.27:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XGK:pvrP02CFP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XGJ-KG2BR:rvrSGLB701A0F-C01-G002-S0001+10.0.22631:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-RPLU-PCFP: dmi.product.family: Galaxy Book4 dmi.product.name: 750XGK dmi.product.sku: SCAI-A5A5-A5A5-RPLU-PCFP dmi.product.version: P02CFP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085410] Re: Fix USB device suspend failure while HCD in S4 wakeup
** Tags added: jira-somerville-1140 oem-priority -- 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/2085410 Title: Fix USB device suspend failure while HCD in S4 wakeup Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: New Status in linux-oem-6.11 source package in Noble: Fix Committed Status in linux source package in Oracular: New Status in linux-oem-6.11 source package in Oracular: Invalid Status in linux source package in Plucky: New Status in linux-oem-6.11 source package in Plucky: Invalid Bug description: [SRU Justification] [Impact] More and more USB device suspend failure are caused by the un-expected HCD_FLAG_WAKEUP_PENDING on the USB host controller. It mostly happens on the USB devices connected to the high-speed root hub. It randomly happens when put the system into suspend [Fix] Fixed by the upstream fix https://lore.kernel.org/linux-usb/20241012094633.126736-1-duancheng...@kylinos.cn/. Set wakeup to false if suspend type is either PM_EVENT_FREEZE or PM_EVENT_QUIESCE [Test Case] 1. Power on machine and connect a USB device to the high-speed root hub. (Find your device in lsusb in the secondary root hub) 2. run checkbox-cli run com.canonical.certification::suspend-cycles-stress-test 3. observe the suspend/resume fail with the kernel message [Where problems could occur] Add more restriction on how the wakeup should be performed. Should be low risk To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2085410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086741] Re: apt get update fails to download arm64 packages
It seems we have this url ((http://azure.archive.ubuntu.com/ubuntu/) preconfigured as the primary mirror site. Can we expect the path (foolder) "binary-arm64" added to this url? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/2086741 Title: apt get update fails to download arm64 packages Status in linux-signed-azure package in Ubuntu: Invalid Bug description: binary-arm64 packages are missing from azure.archive.ubuntu.com. Hence, apt-get update (in ubuntu 24.04) is failing with 404 error status while trying to down load the package via this URL (http://azure.archive.ubuntu.com/ubuntu/dists/noble/main/binary-arm64/Packages). Trying to reach the url from the browser also fails. It seems the folder (path) binary-arm64 are missing. Kindly add the binary-arm64 packages to the same. == Required details == Output of `lsb_release -a` Distributor ID: Ubuntu Description: Ubuntu 24.04.1 LTS Release: 24.04 Codename: noble =Steps to reproduce === In an Azure VM with Ubuntu 24.04 execute the below commands - sudo dpkg --add-architecture arm64 sudo apt update Expected output The arm64 packages should get installed successfully along with amd64 packages === Actual output The command fails with ` Fetched 97.4 MB in 9s (11.2 MB/s) Reading package lists... E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/noble/main/binary-arm64/Packages 404 Not Found [IP: 52.252.163.49 80] E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/noble-updates/main/binary-arm64/Packages 404 Not Found [IP: 52.252.163.49 80] E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/noble-backports/universe/binary-arm64/Packages 404 Not Found [IP: 52.252.163.49 80] E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/noble-security/main/binary-arm64/Packages 404 Not Found [IP: 52.252.163.49 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Error: Process completed with exit code 100. We have a complete Github Actions pipeline workflow log in the below URL with the error message - https://github.com/subir0071/Samples-ravengine/actions/runs/11692216732/job/32561072667 Kindly help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-azure/+bug/2086741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085437] Re: BT Switch cannot open under Ubuntu 24.04 on MT7920
** Tags added: jira-wtn-1 -- 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/2085437 Title: BT Switch cannot open under Ubuntu 24.04 on MT7920 Status in linux package in Ubuntu: Invalid Status in linux-oem-6.11 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: Fix Committed Bug description: [Impact] With MT7920 on certain DUT in Dell platform, bluetooth switch (in GNOME desktop settings) cannot be opened. [Fix] The upstream fix is still under review here: https://lore.kernel.org/lkml/20240822052310.25220-1-hao@mediatek.com/ We'd apply this patch as a sauce patch to Noble oem-6.11 out of urgency. [Test Plan] 1. Plug MT7920 to SUT. 2. Manually Install Ubuntu 24.04 OS. 3. Boot into Ubuntu OS. 4. Check MT7920 function. [Where problems could occur] May cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
** Changed in: linux-firmware (Ubuntu) Status: Confirmed => 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/1968604 Title: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 [Test Case] Connect to and use a bluetooth device connected to a RTL8761B base USB BT controller. [Fix] Use latest rtl8761bu firmware blobs updates from linux-firmware. [Where Problems Could Occur] These firmwares are specific for the rtl8671b chips. So users of USB or UART BT controllers based on that chip could see problems when trying to connect to and use bluetooth devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2078659] Re: Hold IOPOLL locks when triggering io_uring's deferred work
** Description changed: [Impact] io_commit_cqring() writes the CQ ring tail to make it visible and also triggers any deferred work. When a ring is set up with IOPOLL, it doesn't require locking around the CQ ring updates. However, if there is deferred work that needs processing, io_queue_deferred() assumes that the completion_lock is held. The io_uring subsystem does not properly handle locking for rings with IOPOLL, leading to a double-free vulnerability, which can be exploited as CVE-2023-21400. [Fix] There is a commit that fixed this issue. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fb348857e7b67eefe365052f1423427b66dedbf3 There is no direct upstream commit for this issue, and the patch needs to be reworked to apply to version 5.4. [Test Plan] - This is a timing issue that can be verified by testing the normal behavior. - The test should cover the exact call path and ensure that no deadlock occurs. - For the userspace program, you can implement it using the liburing library and choose the XFS filesystem, as it implements the iopoll function hook. - The io_uring_params flag should be set to (IORING_SETUP_SQPOLL | IORING_SETUP_IOPOLL) and use O_DIRECT to open the XFS file for reading operations. - The test should be executed multiple times to ensure that no deadlocks occur. + This is a timing issue that can be triggered by using the liburing library to implement a test program. + First, set the io_uring_params flag to IORING_SETUP_IOPOLL and open an XFS file with the O_RDWR | O_DIRECT flags, as the XFS filesystem implements the iopoll function hook. + After setting up io_uring, create two threads in the process: one thread will wait for completion queue events, and the other will continuously send readv and writev requests in sequence. + The writev requests should include the IOSQE_IO_DRAIN flag to ensure that previous submission queue events are completed first. + + The issue arises when writev requests add entries into the defer_list, + but the io_iopoll_complete function consumes entries from defer_list + without holding the appropriate lock. [Where problems could occur] The problematic call path can be triggered under specific usage scenarios and only affects io_uring functionality. If the patch contains any issues, it may lead to a deadlock. -- 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/2078659 Title: Hold IOPOLL locks when triggering io_uring's deferred work Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: [Impact] io_commit_cqring() writes the CQ ring tail to make it visible and also triggers any deferred work. When a ring is set up with IOPOLL, it doesn't require locking around the CQ ring updates. However, if there is deferred work that needs processing, io_queue_deferred() assumes that the completion_lock is held. The io_uring subsystem does not properly handle locking for rings with IOPOLL, leading to a double-free vulnerability, which can be exploited as CVE-2023-21400. [Fix] There is a commit that fixed this issue. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fb348857e7b67eefe365052f1423427b66dedbf3 There is no direct upstream commit for this issue, and the patch needs to be reworked to apply to version 5.4. [Test Plan] This is a timing issue that can be triggered by using the liburing library to implement a test program. First, set the io_uring_params flag to IORING_SETUP_IOPOLL and open an XFS file with the O_RDWR | O_DIRECT flags, as the XFS filesystem implements the iopoll function hook. After setting up io_uring, create two threads in the process: one thread will wait for completion queue events, and the other will continuously send readv and writev requests in sequence. The writev requests should include the IOSQE_IO_DRAIN flag to ensure that previous submission queue events are completed first. The issue arises when writev requests add entries into the defer_list, but the io_iopoll_complete function consumes entries from defer_list without holding the appropriate lock. [Where problems could occur] The problematic call path can be triggered under specific usage scenarios and only affects io_uring functionality. If the patch contains any issues, it may lead to a deadlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2076209] Re: Intel Lunar Lake / Battlemage enablement
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2076209 Title: Intel Lunar Lake / Battlemage enablement Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: Fix Released Status in linux source package in Oracular: Fix Released Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [Impact] Intel Lunar Lake & Battlemage GPU's don't work in 24.10. [Fix] Backport commits from 6.12 to 6.11 in two batches, the second one dropping xe.force_probe requirement. [Test case] Boot the new kernel, check from dmesg that the drm driver is initialized correctly. [Where problems could occur] The backport is mostly confined in drm/xe, which isn't used by default on any hardware before LNL/BMG, so chance of regressions should be limited. Also, this backport is validated by the vendor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086820] Re: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess r
*** This bug is a duplicate of bug 2068107 *** https://bugs.launchpad.net/bugs/2068107 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2068107, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2068107 package linux-headers- failed to install/upgrade: installed linux-headers- package post-installation script subprocess returned error exit status -- 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/2086820 Title: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 Status in linux package in Ubuntu: New Bug description: bug during update process ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-48-generic 6.8.0-48.48 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:hp15-ubu 1980 F pipewire /dev/snd/controlC0: hp15-ubu 1984 F wireplumber CasperMD5CheckResult: pass Date: Thu Nov 7 02:30:16 2024 ErrorMessage: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-10-25 (12 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=66b67246-2445-4a02-ab7a-aee6c9a70fa5 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2024 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.50 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.50 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd08/20/2024:br15.49:efr80.50:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.50:cvnHP:ct10:cvrChassisVersion:sku4TT07PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4TT07PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2086820] Re: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess r
*** This bug is a duplicate of bug 2068107 *** https://bugs.launchpad.net/bugs/2068107 ERROR (dkms apport): binary package for rtl8821CU: 5.4.1 not found Error! Bad return status for module build on kernel: 6.8.0-48-generic (x86_64) Consult /var/lib/dkms/rtl8821CU/5.4.1/build/make.log for more information. dkms autoinstall on 6.8.0-48-generic/x86_64 failed for rtl8192eu(10) rtl8821CU(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.8.0-48-generic ...fail! You have an unsupported DKMS installed that you need to remove. -- 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/2086820 Title: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 Status in linux package in Ubuntu: New Bug description: bug during update process ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-48-generic 6.8.0-48.48 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:hp15-ubu 1980 F pipewire /dev/snd/controlC0: hp15-ubu 1984 F wireplumber CasperMD5CheckResult: pass Date: Thu Nov 7 02:30:16 2024 ErrorMessage: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-10-25 (12 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=66b67246-2445-4a02-ab7a-aee6c9a70fa5 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-48-generic 6.8.0-48.48 failed to install/upgrade: installed linux-headers-6.8.0-48-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2024 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.50 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.50 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd08/20/2024:br15.49:efr80.50:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.50:cvnHP:ct10:cvrChassisVersion:sku4TT07PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4TT07PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2084766] Re: Most Meteor Lake machines fail to boot into desktop after upgrading to the -48 kernel.
Hi timo,
Do you have plan to move the linux-firmware into jammy-security?
Our customer met this issue when the unattended-upgrade upgraded the kernel
from linux-oem-22.04d to linux-generic-hwe-22.04 (6.8.0-48), I did boot from
the old oem kernel and upgraded linux-firmware by manual, then this issue is
gone.
So the linux-firmware should be upgraded with linux-generic-hwe-22.04 at the
same time.
--
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/2084766
Title:
Most Meteor Lake machines fail to boot into desktop after upgrading to
the -48 kernel.
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-hwe-6.8 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-hwe-6.8 source package in Jammy:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
Invalid
Status in linux-hwe-6.8 source package in Noble:
Invalid
Bug description:
[Impact]
During the SRU testing, I found many laptops displayed a black screen after
booting. Those machines are still alive and able to access via ssh, just
nothing displayed on the screen.
After a brief check, those affected machines that I inspected are all
Meteor Lake machine.
I just attached the journal.log from one of the affected machines.
[Test Case]
1. restore the system the initial state.
2. run dist-upgrade
3. enable proposed pocket.
4. apt install linux-generic-hwe-22.04
5. reboot
[Fail rate]
5/5
[Expected result]
Machines can boot into desktop environment.
[Actual result]
Nothing display.
[Additional information]
Affected machines that I inspected are listed below
https://certification.canonical.com/hardware/202312-33277/
https://certification.canonical.com/hardware/202312-33278/
https://certification.canonical.com/hardware/202312-33279/
https://certification.canonical.com/hardware/202312-33291/
https://certification.canonical.com/hardware/202312-33251/
https://certification.canonical.com/hardware/202312-33252/
https://certification.canonical.com/hardware/202312-33253/
https://certification.canonical.com/hardware/202312-33254/
https://certification.canonical.com/hardware/202312-33255/
https://certification.canonical.com/hardware/202403-33527/
https://certification.canonical.com/hardware/202403-33526/
https://certification.canonical.com/hardware/202403-33525/
https://certification.canonical.com/hardware/202401-33397/
https://certification.canonical.com/hardware/202401-33398/
https://certification.canonical.com/hardware/202401-33401/
https://certification.canonical.com/hardware/202312-33275/
https://certification.canonical.com/hardware/202312-33273/
https://certification.canonical.com/hardware/202312-33274/
https://certification.canonical.com/hardware/202312-33270/
https://certification.canonical.com/hardware/202312-33271/
https://certification.canonical.com/hardware/202310-32270/
https://certification.canonical.com/hardware/202310-32272/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.8.0-48-generic 6.8.0-48.48~22.04.1
ProcVersionSignature: Ubuntu 6.8.0-48.48~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Thu Oct 17 13:11:07 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-oricorio+X125
InstallationDate: Installed on 2024-10-17 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.8
UpgradeStatus: No upgrade log present (probably fresh install)
[Where Problems Could Occur]
No or broken display output for HW with i915 GPUs that use the updated
firmware. Kernel crashes, stack traces, ... if incompatible.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084766/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2080454] Re: NIC(r8169) didn't link up after resuming from suspend
commit 10ce0db787004875f4dba068ea952207d1d8abeb
Author: Heiner Kallweit
Date: Fri Oct 18 11:08:16 2024 +0200
r8169: avoid unsolicited interrupts
It was reported that after resume from suspend a PCI error is logged
and connectivity is broken. Error message is:
PCI error (cmd = 0x0407, status_errs = 0x)
The message seems to be a red herring as none of the error bits is set,
and the PCI command register value also is normal. Exception handling
for a PCI error includes a chip reset what apparently brakes connectivity
here. The interrupt status bit triggering the PCI error handling isn't
actually used on PCIe chip versions, so it's not clear why this bit is
set by the chip. Fix this by ignoring this bit on PCIe chip versions.
Fixes: 0e4851502f84 ("r8169: merge with version 8.001.00 of Realtek's r8168
driver")
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219388
Tested-by: Atlas Yu
Signed-off-by: Heiner Kallweit
Reviewed-by: Simon Horman
Link:
https://patch.msgid.link/78e2f535-438f-4212-ad94-a77637ac6...@gmail.com
Signed-off-by: Paolo Abeni
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2080454
Title:
NIC(r8169) didn't link up after resuming from suspend
Status in linux-signed-hwe-6.8 package in Ubuntu:
In Progress
Bug description:
[Summary]
During the SRU testing, I found a hp laptop always timeout after
suspend test, after checking I found that the NIC didn't link up.
Part of journal log as follows:
Sep 12 11:13:01 ubuntu kernel: PM: suspend entry (s2idle)
...
...
Sep 12 11:13:10 ubuntu kernel: PM: suspend exit
...
Sep 12 11:13:14 ubuntu kernel: r8169 :02:00.1 enp2s0f1: PCI error (cmd =
0x0407, status_errs = 0x)
[Expected result]
SRU test can continue after suspend test.
[Actual result]
SRU test times out and NIC is down.
[Additional information]
Following are the DUTs that are impacted.
https://certification.canonical.com/hardware/202304-31463/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.8.0-44-generic 6.8.0-44.44~22.04.1
ProcVersionSignature: Ubuntu 6.8.0-44.44~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckMismatches: ./preseed/project.cfg
CasperMD5CheckResult: fail
Date: Thu Sep 12 11:16:43 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-stella-jammy-amd64-20230920-537
InstallationDate: Installed on 2024-09-11 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
pc-stella-jammy-amd64-20230920-537
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.8
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2080454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077061] Re: Ubuntu 24.04 showed CXL related complaining messages when CXL capable root port did not attach CXL device
Hi Philip, FYI, we had some progress... Link to the patch: https://lore.kernel.org/all/671c1503b2702_203f412945a@iweiny- mobl.notmuch/T/#m4db285d8318895bc36e9b06417fb185b0a76dbf6 Could you please check when will Ubuntu integrate this patch? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2077061 Title: Ubuntu 24.04 showed CXL related complaining messages when CXL capable root port did not attach CXL device Status in linux package in Ubuntu: New Bug description: Ubuntu 24.04 showed CXL related complaining messages (when CXL root port did not attach CXL device) such as below messages (refer to attached dmesg file): Couldn't locate the CXL.cache and CXL.mem capability array header. HDM decoder capability not found For more details, Please refer to the attached dmesg file How reproducible: 100% Steps to reproduce 1. Install Ubuntu 24.04 on a Lenovo server which is CXL enabled by Intel CPU and Lenovo UEFI, but there is no CXL device attached in this server. 2. Check the dmesg. 3. The above error messages are seen in the dmesg file. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 28 03:14 seq crw-rw 1 root audio 116, 33 Aug 28 03:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-08-28 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 (20240423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Lenovo ThinkSystem SR650 V4,Processor board,BHS,2U,Renesas Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-41-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 RelatedPackageVersions: linux-restricted-modules-6.8.0-41-generic N/A linux-backports-modules-6.8.0-41-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: noble Uname: Linux 6.8.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/26/2024 dmi.bios.release: 0.60 dmi.bios.vendor: Lenovo dmi.bios.version: IHE105M-0.60 dmi.board.name: SB27B70050 dmi.board.vendor: Lenovo dmi.board.version: 2 dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.ec.firmware.release: 0.46 dmi.modalias: dmi:bvnLenovo:bvrIHE105M-0.60:bd08/26/2024:br0.60:efr0.46:svnLenovo:pnThinkSystemSR650V4,Processorboard,BHS,2U,Renesas:pvr2:rvnLenovo:rnSB27B70050:rvr2:cvnLenovo:ct23:cvrNone:sku7DGCCTO2WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V4,Processor board,BHS,2U,Renesas dmi.product.sku: 7DGCCTO2WW dmi.product.version: 2 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062972] Re: ntfs partition does not mount with linux 6.8 and CONFIG_BLK_DEV_WRITE_MOUNTED=n
It took me quite some time to find this page.
Morbius1/Nmax solution worked like a charm.
Thanks a million!!
History :
Instead of doing a fresh install I clicked the upgrade-button for the upgrade
from Kubuntu 22.04 to 24.04.
One of the several bugs I encountered was no longer being able to access my
external hard drives.
Using a Start up Disk to access the HDDs did not work either.
Error message in all cases : Error mounting /dev/sda1 at
/media/{username}/Seagate Expansion Drive: wrong fs type, bad option,
bad superblock on /dev/sda1, missing codepage or helper program, or
other error
These NTFS-HDDs were however still accessible on my laptop under Kubuntu
22.04. So 24.04 had to be the culprit.
FYI :
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-48-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2
Product Name: B550 Extreme4
--
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/2062972
Title:
ntfs partition does not mount with linux 6.8 and
CONFIG_BLK_DEV_WRITE_MOUNTED=n
Status in linux package in Ubuntu:
Confirmed
Status in ntfs-3g package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 24.04 Development Branch (Beta). I am dualbooting it
with Windows 11. When I try to mount my NTFS Windows partition via the
Ubuntu Dock, I get: "Error mounting /dev/nvme01np3 at /media/chris(my
username)/Windows:wrong fs type, bad option, bad superblock on
/dev/nvme01np3, missing codepageor helper program, or other error".
Output of sudo apt-cache policy ntfs-3g: ntfs-3g:
Installed: 1:2022.10.3-1.2ubuntu3
Candidate: 1:2022.10.3-1.2ubuntu3
Version table:
*** 1:2022.10.3-1.2ubuntu3 500
500 http://gr.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ntfs-3g 1:2022.10.3-1.2ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 20 18:25:55 2024
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: ntfs-3g
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062972/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077140] Re: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server
Hi Yuri, Any 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/2077140 Title: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Released Bug description: [Impact] Add Arrow Lake H support According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c and https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. [Fix] " commit 6a9b38cc68a03b948df1f3fcb907c7557cfc315c Author: Matt Roper Date: Tue Mar 5 16:40:49 2024 -0800 drm/xe/arl: Add Arrow Lake H support ARL-H uses the same media and display IP as MTL, and a version 12.74 graphics IP (referred to as Xe_LPG+). From a driver point of view, we should be able to just treat the whole platform as MTL and rely on GRAPHICS_VERx100 checks to handle any spots where ARL's Xe_LPG+ needs different handling from MTL's Xe_LPG (i.e., workarounds). v2: Resolve conflict and Reorder PCI ids in sorted order v3: Append signed-off-by commiter to this commit Bspec: 55420 Signed-off-by: Matt Roper Signed-off-by: Dnyaneshwar Bhadane Reviewed-by: Matt Atwood Link: https://patchwork.freedesktop.org/patch/msgid/20240229070806.3402641-4 -dnyaneshwar.bhad...@intel.com diff --git a/include/drm/xe_pciids.h b/include/drm/xe_pciids.h index de1a344737bc..bc7cbef6e9d8 100644 --- a/include/drm/xe_pciids.h +++ b/include/drm/xe_pciids.h @@ -176,10 +176,13 @@ /* MTL / ARL */ #define XE_MTL_IDS(MACRO__, ...) \ MACRO__(0x7D40, ## __VA_ARGS__),\ + MACRO__(0x7D41, ## __VA_ARGS__),\ MACRO__(0x7D45, ## __VA_ARGS__),\ + MACRO__(0x7D51, ## __VA_ARGS__),\ MACRO__(0x7D55, ## __VA_ARGS__),\ MACRO__(0x7D60, ## __VA_ARGS__),\ MACRO__(0x7D67, ## __VA_ARGS__),\ + MACRO__(0x7DD1, ## __VA_ARGS__),\ MACRO__(0x7DD5, ## __VA_ARGS__) #define XE_LNL_IDS(MACRO__, ...) \ " https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/tree/include/drm/xe_pciids.h [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077140_intel_arrowlake However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server version, which are using Linux kernel 6.8, due to this reason, can this feature be backport to these two version, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085437] Re: BT Switch cannot open under Ubuntu 24.04 on MT7920
After apply 6.11-1007 OEM kernel, BT can switch open on MT7920. ** Attachment added: "sosreport-next1024dl-2024-11-07-tlafkza.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.11/+bug/2085437/+attachment/5835203/+files/sosreport-next1024dl-2024-11-07-tlafkza.tar.xz -- 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/2085437 Title: BT Switch cannot open under Ubuntu 24.04 on MT7920 Status in linux package in Ubuntu: Invalid Status in linux-oem-6.11 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: Fix Committed Bug description: [Impact] With MT7920 on certain DUT in Dell platform, bluetooth switch (in GNOME desktop settings) cannot be opened. [Fix] The upstream fix is still under review here: https://lore.kernel.org/lkml/20240822052310.25220-1-hao@mediatek.com/ We'd apply this patch as a sauce patch to Noble oem-6.11 out of urgency. [Test Plan] 1. Plug MT7920 to SUT. 2. Manually Install Ubuntu 24.04 OS. 3. Boot into Ubuntu OS. 4. Check MT7920 function. [Where problems could occur] May cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
@nrjrasaxena Please provide the console command output: lspci -k | grep -EA3 'VGA|3D controller' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.8 package in Ubuntu: Confirmed Status in linux source package in Lunar: Won't Fix Status in linux-hwe-5.19 source package in Lunar: Invalid Status in linux-hwe-6.2 source package in Lunar: Invalid Status in linux-hwe-6.5 source package in Lunar: Won't Fix Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2081384] Re: bluetooth headphones need reconnect after every reboot
I would like to try your patch but I don't quite know what I'm doing -- I did manage to apply, build and install, but I also require bluedevil for KDE Plasma to access the stack, and apt doesn't know I already have bluez installed that way so I don't know what to do with that. I'll wait for a new update instead -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2081384 Title: bluetooth headphones need reconnect after every reboot Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in bluez source package in Oracular: Confirmed Status in linux source package in Oracular: Confirmed Bug description: This issue seems to be caused by a recent package update in oracular. Every time I reboot my desktop my bluetooth headset will fail to connect until I manually go through forget device -> new pairing. journalctl says: 23:13:44 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:45 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:47 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:00 desktop bluetoothd[3274]: No matching connection for device 23:14:04 desktop bluetoothd[3274]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Operation already in progress 23:14:04 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:27 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:15:46 desktop bluetoothd[3274]: /org/bluez/hci0/dev_80_C3_33_59_89_D6/sep7/fd0: fd(43) ready In dmesg I see lots of: [44738.102583] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.325565] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.496566] Bluetooth: hci0: ACL packet for unknown connection handle 3837 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2081384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
