[Kernel-packages] [Bug 2052842] Re: Regression in partition table management in kernel 5.15.0-94.104
*** This bug is a duplicate of bug 2049689 *** https://bugs.launchpad.net/bugs/2049689 ** This bug has been marked a duplicate of bug 2049689 partproke is broken on empty loopback device -- 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/2052842 Title: Regression in partition table management in kernel 5.15.0-94.104 Status in linux package in Ubuntu: Confirmed Bug description: There is a regression in partition table management in the latest jammy kernel which can be reproduced with this simple script: fallocate -l 32M /tmp/blob LOOPDEV=$(losetup -f) sudo losetup $LOOPDEV /tmp/blob sudo /usr/sbin/parted -s -m $LOOPDEV -- "mklabel gpt" Expected result: Partition table is created successfully, exit code is 0, no output. Actual result: Partition table is created successfully, but exit code is 1 and output is: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128 on /dev/loop3 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. Packaging information: Description: Ubuntu 22.04.3 LTS Release: 22.04 Affected kernel version: Ubuntu 5.15.0-94.104-generic 5.15.136 Last working kernel version: Ubuntu 5.15.0-92.102-generic 5.15.131 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053130] [NEW] Realtek bluetooth controller malfunctions after upgrading from the 5.15.0-94-generic non-HWE kernel
Public bug reported: In a troubleshooting thread[1] I assisted within the local Ubuntu community a user encountered an issue where Bluetooth devices(e.g. HID mouse) no longer function after a certain update on a Xubuntu 22.04 system that uses an HWE kernel. bluetoothd logs appear to have some error messages like: ``` Bluetooth management interface 1.22 initialized src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv monitors: Failed (0x03) Failed to clear UUIDs: Failed (0x03) Failed to add UUID: Failed (0x03) Failed to add UUID: Failed (0x03) Failed to add UUID: Failed (0x03) Endpoint registered: sender=1.32 path=/MediaEndpoint/A2DPSource/ldac ``` ``` Endpoint registered: sender=1.46 path=/MediaEndpoint/A2DPSource/sbc_xq_552 src/device.c:load_gatt_db() no cache for D1:2B:38:RE:DA:CT src/service.c:service_accept() input-hog profile accept failed for D1:2B:38:RE:DA:CT src/device.c:load_gatt_db() no cache for D1:2B:38:RE:DA:CT src/service.c:service_accept() input-hog profile accept failed for D1:2B:38:RE:DA:CT src/device.c:load_gatt_db() no cache for D1:2B:38:RE:DA:CT src/service.c:service_accept() input-hog profile accept failed for D1:2B:38:RE:DA:CT ``` ``` Bluetooth: hci0: unexpected cc 0x0c7c length: 1 < 3 Bluetooth: hci0: unexpected SMP command 0x06 from D1:2B:38:RE:DA:CT Bluetooth: hci0: unexpected SMP command 0x07 from D1:2B:38:RE:DA:CT Bluetooth: hci0: unexpected SMP command 0x08 from D1:2B:38:RE:DA:CT Bluetooth: hci0: unexpected SMP command 0x09 from D1:2B:38:RE:DA:CT ``` The Bluetooth controller seems to be manufactured by Realtek(VendorID=0bda), however I am unable to find the exact model number of the hardware(ProductID=b00a). Downgrade the linux-firmware package to 20220329.git681281e4-0ubuntu3.14 doesn't fix the issue, however, when the kernel is downgraded from 6.5.0-17-generic to 5.15.0-94-generic the issue is no longer reproduced, which appears to be a regression in the kernel and/or the Bluetooth stack instead of the device firmware. As I'm not the one who reproduces this issue I can only document the gathered information here, though there are users in other distros who encountered similar problems on the 6.x kernel: Bluetoothd errors since kernel 6.x : archlinux https://www.reddit.com/r/archlinux/comments/16e9aks/bluetoothd_errors_since_kernel_6x/ [1] https://t.me/x_ubuntu_taiwan_community/111326 ** Affects: linux-meta-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: btrtl realtek regression ** Tags added: regression ** Description changed: - In a troubleshooting thread[1] I assisted with in the local Ubuntu - community a user encountered an issue where bluetooth devices(e.g. HID + In a troubleshooting thread[1] I assisted within the local Ubuntu + community a user encountered an issue where Bluetooth devices(e.g. HID mouse) no longer function after a certain update on a Xubuntu 22.04 - system that uses a HWE kernel. + system that uses an HWE kernel. bluetoothd logs appear to have some error messages like: ``` - Bluetooth management interfae 1.22 initialized + Bluetooth management interface 1.22 initialized src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv monitors: Failed (0x03) Failed to clear UUIDs: Failed (0x03) Failed to add UUID: Failed (0x03) Failed to add UUID: Failed (0x03) Failed to add UUID: Failed (0x03) Endpoint registered: sender=1.32 path=/MediaEndpoint/A2DPSource/ldac ``` ``` Endpoint registered: sender=1.46 path=/MediaEndpoint/A2DPSource/sbc_xq_552 src/device.c:load_gatt_db() no cache for D1:2B:38:RE:DA:CT src/service.c:service_accept() input-hog profile accept failed for D1:2B:38:RE:DA:CT src/device.c:load_gatt_db() no cache for D1:2B:38:RE:DA:CT src/service.c:service_accept() input-hog profile accept failed for D1:2B:38:RE:DA:CT src/device.c:load_gatt_db() no cache for D1:2B:38:RE:DA:CT src/service.c:service_accept() input-hog profile accept failed for D1:2B:38:RE:DA:CT ``` ``` Bluetooth: hci0: unexpected cc 0x0c7c length: 1 < 3 Bluetooth: hci0: unexpected SMP command 0x06 from D1:2B:38:RE:DA:CT Bluetooth: hci0: unexpected SMP command 0x07 from D1:2B:38:RE:DA:CT Bluetooth: hci0: unexpected SMP command 0x08 from D1:2B:38:RE:DA:CT Bluetooth: hci0: unexpected SMP command 0x09 from D1:2B:38:RE:DA:CT ``` The Bluetooth controller seems to be manufactured by - Realtek(VendorID=0bda), however I unable to find the exact model number - of the hardware(ProductID=b00a). + Realtek(VendorID=0bda), however I am unable to find the exact model + number of the hardware(ProductID=b00a). Downgrade the linux-firmware package to 20220329.git681281e4-0ubuntu3.14 - doesn't fix the issue, however when the kernel is downgraded from + doesn't fix the issue, however, when the kernel is downgraded from 6.5.0-17-generic to 5.15.0-94-generic the issue is no longer reproduced, which appears to be a regression in the kernel and/or the Bluetooth stack i
[Kernel-packages] [Bug 2051176] Re: Update Ubuntu.md
No functional change, no test needed ** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051176 Title: Update Ubuntu.md Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: [ Impact ] * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md [ Other Info ] * I used the current kernel version of 6.5.10 since it didn't seem to make sense to use the old version we released with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052453] Re: Azure: Fix regression introduced in LP: #2045069
** Tags removed: verification-needed-jammy-linux-azure verification-needed-mantic-linux-azure ** Tags added: verification-done-jammy-linux-azure verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052453 Title: Azure: Fix regression introduced in LP: #2045069 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] Microsoft requested the addition of 3 patches in LP: #2045069. A regression was discovered in Focal. [Fix] hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove [Test Case] Microsoft tested [Regression Potential] hv_netvsc could still have a modprobe race. [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
** Tags removed: verification-needed-jammy-linux-aws-6.5
** Tags added: verification-done-jammy-linux-aws-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Status in linux-aws package in Ubuntu:
Fix Committed
Status in linux-aws source package in Lunar:
Fix Committed
Status in linux-aws source package in Mantic:
Fix Released
Status in linux-aws source package in Noble:
Fix Committed
Bug description:
SRU Justification
[Impact]
An update from LP: #1853180 was carried forward to the Lunar 6.2 and
Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036600] Re: Azure: Fix Azure vendor ID
** Tags removed: verification-needed-jammy-linux-aws-6.5
verification-needed-jammy-linux-gcp-6.5
** Tags added: verification-done-jammy-linux-aws-6.5
verification-done-jammy-linux-gcp-6.5
--
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/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Fix Released
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
VMs could be misclassified.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052519] Re: Azure: Fix TDX regressions in Azure 6.5
** Tags removed: verification-needed-mantic-linux-azure ** Tags added: verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052519 Title: Azure: Fix TDX regressions in Azure 6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] TDX support in Microsoft Azure kernels based on 6.5 has regressed from 6.2. Microsoft has provided a backport that brings TDX functionality back to that of Azure 6.2. [Test Case] Microsoft tested [Regression Potential] TDX support has been backported from Linux v6.6, so there could be some lingering issues. [Other Information] SF: #00378027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027615] Re: Azure: MANA: Fix doorbell access for receives
** Tags removed: verification-needed-mantic-linux-azure ** Tags added: verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2027615 Title: Azure: MANA: Fix doorbell access for receives Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: Fix Released Status in linux-azure source package in Lunar: Fix Released Bug description: SRU Justification [Impact] It's inefficient to ring the doorbell page every time a WQE is posted to the received queue. Excessive MMIO writes result in CPU spending more time waiting on LOCK instructions (atomic operations), resulting in poor scaling performance. [Test Plan] MSFT tested. [Regression Potential] The MANA receive queue could stop. [Other Info] SF: #00363437 These 2 patches have been submitted for upstream inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2027615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053135] [NEW] Touchpad not working, device not detected
Public bug reported: Laptop model: Dell Precision 3560 Touchpad Manufacturer: can't find it First symptoms: today 14th February Description:Ubuntu 22.04.3 LTS Release:22.04 Touchpad doesn't work and isn't detected as a device. Not sure if the issue started after boot or after the apt-upgrade I did right after boot. I've followed the DebuggingTouchpadDetection guide until here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 15:21:51 2024 InstallationDate: Installed on 2023-09-19 (148 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Detected devices via "cat /proc/bus/input/devices"" https://bugs.launchpad.net/bugs/2053135/+attachment/5746296/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053135 Title: Touchpad not working, device not detected Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Laptop model: Dell Precision 3560 Touchpad Manufacturer: can't find it First symptoms: today 14th February Description: Ubuntu 22.04.3 LTS Release: 22.04 Touchpad doesn't work and isn't detected as a device. Not sure if the issue started after boot or after the apt-upgrade I did right after boot. I've followed the DebuggingTouchpadDetection guide until here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 15:21:51 2024 InstallationDate: Installed on 2023-09-19 (148 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2053135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053135] Re: Touchpad not working, device not detected
Attaching apt log since yesterday, February 13th. Tried rebooting more than once but the issue persists. First bug report so thank you for the assistance! ** Attachment added: "apt log since yesterday, February 13th" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2053135/+attachment/5746302/+files/apt-upgrades -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053135 Title: Touchpad not working, device not detected Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Laptop model: Dell Precision 3560 Touchpad Manufacturer: can't find it First symptoms: today 14th February Description: Ubuntu 22.04.3 LTS Release: 22.04 Touchpad doesn't work and isn't detected as a device. Not sure if the issue started after boot or after the apt-upgrade I did right after boot. I've followed the DebuggingTouchpadDetection guide until here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 15:21:51 2024 InstallationDate: Installed on 2023-09-19 (148 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2053135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053147] [NEW] CONFIG_EFI_STUB support disabled since 6.5.0-1002.2
Public bug reported: Looks like since commmit 0d02ca7853f4e487ff8b912b0d1d43ceb31a528b (https://git.launchpad.net/ubuntu/+source/linux- raspi/commit/?h=applied/ubuntu/devel&id=0d02ca7853f4e487ff8b912b0d1d43ceb31a528b) The support for EFI in the kernel config was disabled with no mention of why: """ - [Config] raspi: Set EFI=n """ This disables support for CONFIG_EFI_STUB which means that the kernel cannot be loaded via EFI directly. Any reasons for this? We are booting RPI by setting u-boot to launch in EFI mode, which runs grub.efi and then we load our entries from there, but this totally breaks support for that. This worked until the previous kernel version with no issues that we could find. Is there anything we can do to revert this and re-enable this option int he kernel? ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2053147 Title: CONFIG_EFI_STUB support disabled since 6.5.0-1002.2 Status in linux-raspi package in Ubuntu: New Bug description: Looks like since commmit 0d02ca7853f4e487ff8b912b0d1d43ceb31a528b (https://git.launchpad.net/ubuntu/+source/linux- raspi/commit/?h=applied/ubuntu/devel&id=0d02ca7853f4e487ff8b912b0d1d43ceb31a528b) The support for EFI in the kernel config was disabled with no mention of why: """ - [Config] raspi: Set EFI=n """ This disables support for CONFIG_EFI_STUB which means that the kernel cannot be loaded via EFI directly. Any reasons for this? We are booting RPI by setting u-boot to launch in EFI mode, which runs grub.efi and then we load our entries from there, but this totally breaks support for that. This worked until the previous kernel version with no issues that we could find. Is there anything we can do to revert this and re-enable this option int he kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2053147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053148] [NEW] Pull request: address GPIO initialization regression on Grace systems
Public bug reported: The tegra186_gpio_is_accessible() function incorrectly declares GPIO lines that have only one of TEGRA186_GPIO_SCR_SEC_REN _or_ TEGRA186_GPIO_SCR_SEC_WEN set as being inaccessible. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053148 Title: Pull request: address GPIO initialization regression on Grace systems Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: The tegra186_gpio_is_accessible() function incorrectly declares GPIO lines that have only one of TEGRA186_GPIO_SCR_SEC_REN _or_ TEGRA186_GPIO_SCR_SEC_WEN set as being inaccessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2053148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053152] [NEW] performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing
Public bug reported: This is a public version of https://bugs.launchpad.net/bugs/2034984 [Description] When running UnixBench/Execl throughput case, false sharing is observed due to frequent read on base_addr and write on free_bytes, chunk_md. UnixBench/Execl represents a class of workload where bash scripts are spawned frequently to do some short jobs. It will do system call on execl frequently, and execl will call mm_init to initialize mm_struct of the process. mm_init will call __percpu_counter_init for percpu_counters initialization. Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory from a specified chunk. This function will update "free_bytes" and "chunk_md" to record the rest free bytes and other meta data for this chunk. Correspondingly, pcpu_free_area will also update these 2 members when free memory. In current pcpu_chunk layout, `base_addr' is in the same cache line with `free_bytes' and `chunk_md', and `base_addr' is at the last 8 bytes. This patch moves `bound_map' up to `base_addr', to let `base_addr' locate in a new cacheline. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Platform-Independent Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: 6.5 Commit IDs: 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5160 The following requested patch has been applied upstream for v6.5-rc1: - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Philip Cox (philcox) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Philip Cox (philcox) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053152 Title: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034984 [Description] When running UnixBench/Execl throughput case, false sharing is observed due to frequent read on base_addr and write on free_bytes, chunk_md. UnixBench/Execl represents a class of workload where bash scripts are spawned frequently to do some short jobs. It will do system call on execl frequently, and execl will call mm_init to initialize mm_struct of the process. mm_init will call __percpu_counter_init for percpu_counters initialization. Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory from a specified chunk. This function will update "free_bytes" and "chunk_md" to record the rest free bytes and other meta data for this chunk. Correspondingly, pcpu_free_area will also update these 2 members when free memory. In current pcpu_chunk layout, `base_addr' is in the same cache line with `free_bytes' and `chunk_md', and `base_addr' is at the last 8 bytes. This patch moves `bound_map' up to `base_addr', to let `base_addr' locate in a new cacheline. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Platform-Independent Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: 6.5 Commit IDs: 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5160 The following requested patch has been applied upstream for v6.5-rc1: - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packag
[Kernel-packages] [Bug 2049195] Re: Wifi missing after upgrade to 6.5 kernel
I installed the 6.5.0-18-generic kernel from jammy-proposed. iwlwifi module worked without problems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049195 Title: Wifi missing after upgrade to 6.5 kernel Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is missing. Hardware: Framework Laptop $ lspci | grep Network aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) With 6.2: $ sudo ethtool -i wlp170s0 driver: iwlwifi version: 6.2.0-39-generic firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc Messages from journalctl that seem relevant: Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer destination and then some backtraces, result of journalctl -b-1 | grep "kernel: " > kernel-log.txt attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 12:32:19 2024 InstallationDate: Installed on 2022-06-29 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2049195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053155] [NEW] Add DPLL and syncE support
Public bug reported: * intro Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking that facilitates the transference of clock signals over the Ethernet physical layer. It is used to pass timing from node to node and is particularly important for mobile networks. The DPLL subsystem in the Linux kernel provides a general interface for configuring devices that use any kind of Digital PLL. This subsystem is designed to manage the clock signal synchronization of a device with an external clock signal. * Explain the bug(s) We need to support mlx5 SyncE feature. The following patches are needed. [net-next,v8,0/9] Create common DPLL configuration API [net-next,v8,1/9] dpll: documentation on DPLL subsystem interface [net-next,v8,2/9] dpll: spec: Add Netlink spec in YAML [net-next,v8,3/9] dpll: core: Add DPLL framework base functions [net-next,v8,4/9] dpll: netlink: Add DPLL framework base functions [net-next,v8,5/9] netdev: expose DPLL pin handle for netdevice [net-next,v8,6/9] ice: add admin commands to access cgu configuration [net-next,v8,7/9] ice: implement dpll interface to control cgu [net-next,v8,8/9] ptp_ocp: implement DPLL ops [net-next,v8,9/9] mlx5: Implement SyncE support using DPLL infrastructure https://lore.kernel.org/netdev/20230913204943.1051233-1-vadim.fedore...@linux.dev/ * Brief explanation of fixes We identify several dependent patches, especially related to netlink gap between current master-next. We cherry-pick/backport series of patches related to netlink. * How to test $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --dump device-get (mlx5 device should show up) $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --do pin-get * list of patches applied to 5.15 jammy based on 911f816f4c04 mlxbf_gige: fix receive packet race condition we applied the following 83a11d94c436 UBUNTU: SAUCE: fix build error after resv_start_op 036b2fecd315 genetlink: allow families to use split ops directly 9f40a82f73ea genetlink: inline old iteration helpers d8ae137b98fc genetlink: use iterator in the op to policy map dumping 095792a3a723 genetlink: add iterator for walking family ops 764747ba0085 genetlink: limit the use of validation workarounds to old ops 35b95f016392 genetlink: inline genl_get_cmd() c448680485e6 genetlink: support split policies in ctrl_dumppolicy_put_op() a17efffb8ce8 genetlink: add policies for both doit and dumpit in ctrl_dumppolicy_start() 82af441de2fa genetlink: check for callback type at op load time dc17c9675d6d genetlink: load policy based on validation flags d867b1e130d3 genetlink: move the private fields in struct genl_family b515a3664ef5 genetlink: piggy back on resv_op to default to a reject policy 1fa6e0ec60a4 genetlink: refactor the cmd <> policy mapping dump c8ba54011c1d netlink: add helpers for extack attr presence checking 3d9c79882136 netlink: add support for ext_ack missing attributes a0edd1e6e99c netlink: factor out extack composition 181e77073d7c genetlink: introduce split op representation 58077e5acc95 genetlink: reject use of nlmsg_flags for new commands 199935182e01 genetlink: start to validate reserved header bytes 137d6fb11693 kernel: make taskstats available from all net namespaces 75acbd978295 genetlink: fix kdoc warnings 05670bbfb561 dpll: remove leftover mode_supported() op and use mode_get() instead e878653f5370 dpll: netlink/core: change pin frequency set behavior d483a8e43651 dpll: netlink/core: add support for pin-dpll signal phase offset/adjust 71574fa963d0 dpll: spec: add support for pin-dpll signal phase offset/adjust 2b004af8572d netlink: specs: remove redundant type keys from attributes in subsets 473b6cb3696f dpll: docs: add support for pin signal phase offset/adjust 015ea1e2fbda Documentation: dpll: wrap DPLL_CMD_PIN_GET output in a code block 5167a94e40e1 Documentation: dpll: Fix code blocks 16ab1010e92d netdev: expose DPLL pin handle for netdevice aa78df66e66b dpll: netlink: Add DPLL framework base functions d0eafb969ef9 dpll: core: Add DPLL framework base functions 8bb4159242d6 dpll: spec: Add Netlink spec in YAML 3dbcbef38d8e dpll: documentation on DPLL subsystem interface ** 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/2053155 Title: Add DPLL and syncE support Status in linux-bluefield package in Ubuntu: New Bug description: * intro Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking that facilitates the transference of clock signals over the Ethernet physical layer. It is used to pass timing from node to node and is particularly important for mobile networks. The DPLL subsystem in the Linux kernel provides a general interface for configuring devices that use any kind of Digital PLL. This subsystem is desi
[Kernel-packages] [Bug 2053135] Re: Touchpad not working, device not detected
It started working again after rebooting 2-3 times -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053135 Title: Touchpad not working, device not detected Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Laptop model: Dell Precision 3560 Touchpad Manufacturer: can't find it First symptoms: today 14th February Description: Ubuntu 22.04.3 LTS Release: 22.04 Touchpad doesn't work and isn't detected as a device. Not sure if the issue started after boot or after the apt-upgrade I did right after boot. I've followed the DebuggingTouchpadDetection guide until here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 15:21:51 2024 InstallationDate: Installed on 2023-09-19 (148 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2053135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053194] [NEW] latest kernel update breaks sata hotplug on z690
Public bug reported: SATA hotplug is not working on these kernels: linux-image-6.5.0-17-generic linux-image-5.15.0-94-generic SATA hotplug is working on these kernels: linux-image-6.5.0-15-generic linux-image-5.15.0-92-generic Affected platform: Gigabyte Z690 AORUS PRO BIOS Version: F28 Note that I can only repro this on Z690. I also tried Z390 and Z370 platforms and SATA hotplug it is working there. Steps to repro: 1. Enable SATA hotplug in BIOS 2. Boot to affected kernel 3. Hotplug a SATA drive while monitoring kernel messages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 13:20:34 2024 InstallationDate: Installed on 2024-01-26 (18 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-01-26T15:01:36.495491 ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053194 Title: latest kernel update breaks sata hotplug on z690 Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: SATA hotplug is not working on these kernels: linux-image-6.5.0-17-generic linux-image-5.15.0-94-generic SATA hotplug is working on these kernels: linux-image-6.5.0-15-generic linux-image-5.15.0-92-generic Affected platform: Gigabyte Z690 AORUS PRO BIOS Version: F28 Note that I can only repro this on Z690. I also tried Z390 and Z370 platforms and SATA hotplug it is working there. Steps to repro: 1. Enable SATA hotplug in BIOS 2. Boot to affected kernel 3. Hotplug a SATA drive while monitoring kernel messages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 13:20:34 2024 InstallationDate: Installed on 2024-01-26 (18 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-01-26T15:01:36.495491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2053194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053104] Re: Kernel 6.5.0-17-generic HDD loudly parks heads in emergency mode
*** This bug is a duplicate of bug 2053041 *** https://bugs.launchpad.net/bugs/2053041 Hi Alex, please come over to bug 2053041 and we can try figure this out. Thanks! ** This bug has been marked a duplicate of bug 2053041 Issue when shutting down computer: internal hard drive is not shut down properly -- 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/2053104 Title: Kernel 6.5.0-17-generic HDD loudly parks heads in emergency mode Status in linux package in Ubuntu: New Bug description: When power is turned off, HDD drives park their heads loudly. This does not happen when using the 6.2.0-39-generic kernel, or when turning off the power after booting into Windows 10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-signed-hwe-6.5 (Ubuntu) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053041 Title: Issue when shutting down computer: internal hard drive is not shut down properly Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Bug description: After the last kernel upgrade, I noticed that, in the S.M.A.R.T. monitor, parameter ID 192 "Power Off Retract Count" increased every time I turned off the system. I also noticed the "click" of the head parking when shutting down the computer. By restarting the computer with previous kernel version (6.5.0-15.15~22.04.1) the issue didn't happen, so I assume it's a kernel bug, that causes it to shut down the computer before hard drive is deactivated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Feb 13 16:35:55 2024 InstallationDate: Installed on 2020-10-02 (1228 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2022-08-11 (550 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053212] [NEW] Jammy update: v5.15.146 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.146 upstream stable release from git://git.kernel.org/ ARM: dts: dra7: Fix DRA7 L3 NoC node register size ARM: OMAP2+: Fix null pointer dereference and memory leak in omap_soc_device_init reset: Fix crash when freeing non-existent optional resets s390/vx: fix save/restore of fpu kernel context wifi: iwlwifi: pcie: add another missing bh-disable for rxq->lock wifi: mac80211: mesh_plink: fix matches_local logic net/mlx5e: Fix slab-out-of-bounds in mlx5_query_nic_vport_mac_list() net/mlx5e: fix a potential double-free in fs_udp_create_groups net/mlx5: Fix fw tracer first block check net/mlx5e: Correct snprintf truncation handling for fw_version buffer used by representors net: sched: ife: fix potential use-after-free ethernet: atheros: fix a memleak in atl1e_setup_ring_resources net/rose: fix races in rose_kill_by_device() net: mana: select PAGE_POOL net: check vlan filter feature in vlan_vids_add_by_dev() and vlan_vids_del_by_dev() afs: Fix the dynamic root's d_delete to always delete unused dentries afs: Fix dynamic root lookup DNS check net: check dev->gso_max_size in gso_features_check() keys, dns: Allow key types (eg. DNS) to be reclaimed immediately on expiry keys, dns: Fix missing size check of V1 server-list header keys, dns: Fix size check of V1 server-list header afs: Fix overwriting of result of DNS query afs: Use refcount_t rather than atomic_t afs: Fix use-after-free due to get/remove race in volume tree ASoC: hdmi-codec: fix missing report for jack initial status i2c: aspeed: Handle the coalesced stop conditions with the start conditions. pinctrl: at91-pio4: use dedicated lock class for IRQ gpiolib: cdev: add gpio_device locking wrapper around gpio_ioctl() ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE drm/i915/mtl: limit second scaler vertical scaling in ver >= 14 drm/i915: Relocate intel_atomic_setup_scalers() drm/i915: Fix intel_atomic_setup_scalers() plane_state handling smb: client: fix NULL deref in asn1_ber_decoder() smb: client: fix OOB in smb2_query_reparse_point() interconnect: Treat xlate() returning NULL node as an error iio: imu: inv_mpu6050: fix an error code problem in inv_mpu6050_read_raw Input: ipaq-micro-keys - add error handling for devm_kmemdup scsi: bnx2fc: Fix skb double free in bnx2fc_rcv() iio: common: ms_sensors: ms_sensors_i2c: fix humidity conversion time table iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma() iio: triggered-buffer: prevent possible freeing of wrong buffer ALSA: usb-audio: Increase delay in MOTU M quirk wifi: cfg80211: Add my certificate wifi: cfg80211: fix certs build to not depend on file order USB: serial: ftdi_sio: update Actisense PIDs constant names USB: serial: option: add Quectel EG912Y module support USB: serial: option: add Foxconn T99W265 with new baseline USB: serial: option: add Quectel RM500Q R13 firmware support Bluetooth: hci_event: Fix not checking if HCI_OP_INQUIRY has been sent Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE Input: soc_button_array - add mapping for airplane mode button net: 9p: avoid freeing uninit memory in p9pdu_vreadf net: rfkill: gpio: set GPIO direction net: ks8851: Fix TX stall caused by TX buffer overrun dt-bindings: nvmem: mxs-ocotp: Document fsl,ocotp scsi: core: Always send batch on reset or error handling command tracing / synthetic: Disable events after testing in synth_event_gen_test_init() bus: ti-sysc: Flush posted write only after srst_udelay gpio: dwapb: mask/unmask IRQ when disable/enale it lib/vsprintf: Fix %pfwf when current node refcount == 0 KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy x86/alternatives: Sync core before enabling interrupts fuse: share lookup state between submount and its parent ksmbd: have a dependency on cifs ARC4 ksmbd: set epoch in create context v2 lease ksmbd: set v2 lease capability ksmbd: downgrade RWH lease caching state to RH for directory ksmbd: send v2 lease break notification for directory ksmbd: lazy v2 lease break on smb2_write() ksmbd: avoid duplicate opinfo_put() call on error of smb21_lease_break_ack() ksmbd: fix wrong allocation size update in smb2_open() ARM: dts: Fix occasional boot hang for am3 usb usb: fotg210-hcd: delete an incorrect bounds test ethernet: constify references to netdev->dev_addr in drivers net: usb: ax88179_178a: clean up pm calls net: usb: ax88179_178a: wol optimizations net: usb: ax88179_178a: avoid failed operations when device is disconnected device property: Add const qualifier to devic
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-nvidia/5.15.0.1046.46)
All autopkgtests for the newly accepted linux-meta-nvidia (5.15.0.1046.46) for jammy have finished running. The following regressions have been reported in tests triggered by the package: wireguard/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-nvidia [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
