[Kernel-packages] [Bug 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/1996121 Title: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: The cs35l41 codec driver was backported to Jammy kernel a couple of months ago, recently the Jammy kernel was adopted as the hwe kernel for OEM machines and with this kernel the UBSAN calltrace was seen, need to backport these 2 patches. Kinetic kernel already has the patches, so this SRU is only for Jammy kernel. [Impact] Install the 5.15 hwe kernel on the machines with cs35l41 codec, after booting and check the dmesg, there is a UBSAN calltrace. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, check the dmesg, there is no UBSAN calltrace, and test the audio functions, all input and output devices coudl work as well as before. [Where problems could occur] The patch only affects the cirruslogic asoc codec driver, if it could introduce the regression, it will be on the machines with cs codec, and it will make the audio driver initialization fail and make the system lose the audio function. But this possibility is very low, we tested the patches on many oem machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998115 Title: Fix iosm: WWAN cannot build the connection (DW5823e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] WWAN(DW5823e) can't build the connection successfully. [Fix] With INTEL_IOMMU disable config or by forcing intel_iommu=off from grub some of the features of IOSM driver like browsing, flashing & coredump collection is not working. When driver calls DMA API - dma_map_single() for tx transfers. It is resulting in dma mapping error. Set the device DMA addressing capabilities using dma_set_mask() and remove the INTEL_IOMMU dependency in kconfig so that driver follows the platform config either INTEL_IOMMU enable or disable. Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] 1. boot up with kernel applied the FIX. 2. check the status of wwan by "mmcli -m 0" Status| unlock retries: sim-pin (3) | state: ^[32mconnected^[0m |power state: on |access tech: lte | signal quality: 45% (recent) -- 3GPP | imei: ## | enabled locks: sim, fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached |pco: | 0: (complete) [Where problems could occur] remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch is included in v6.2-rc1 9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998106] Re: Fix AMD-PState driver for Genoa CPU
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998883] Re: Micron NVME storage failure [1344, 5407]
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998883 Title: Micron NVME storage failure [1344,5407] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/1999528 Title: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [SRU Justification] == Impact == Since we split the lowlatency kernel into its own source package the check in the regression test suite is missing a case and will not run, even though the kernel can be booted in a VM instance. == Fix == Add the missing case to the test script which is used by ADT testing. The test scripts are inherited from the primary/distro kernel. The fix should be made there instead of changing the lowlatency tree. == Test == Inspecting the ADT logs we should start to see tests executed instead of: autopkgtest [19:22:21]: test ubuntu-regression-suite: [- ubuntu-regression-suite is pointless, if one cannot boot the kernel == Regression Potential == There are a couple of flaky tests which will start to show up, rather than only successful runs (which should have been a suspicious thing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2006453 Title: Fix selftests/ftracetests/Meta-selftests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: == SRU Justification == [Impact] Audio playback becomes silent on some Intel SoF systems. [Fix] Revert offending commit. [Test] The speaker can always play sound after the commit gets reverted. [Where problems could occur] Audio on linux 5.15 has been working fine without the patch for a long time, so this only restore it to where it was. == Original Bug Report == [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2008527 Title: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008527_dapc_kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Released Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu_2 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar_2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009024] Re: Fail to output sound to external monitor which connects via docking station
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009024 Title: Fail to output sound to external monitor which connects via docking station Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] No sound output from the external monitor which connect via some docking station. It only happens when user boot the system with docking station connected. Re-plug the docking station can fix this issue. Or plug the docking station later won't trigger this problem. [Fix] Turn on the CONFIG_SND_HDA_INTEL_HDMI_SILENT in kernel config. It will start sending an "audio keepalive" to the monitor as soon as it is connected. [Test] Connect the external monitor to the Atomic Type-C Dock (HD22Q) and boot the system with the dock connected. Play sound via HDMI/DP port and check if there's any audio output from the external monitor. [Where problems could occur] It sends the "audio keepalive"(silent stream) to the monitor when connected. Doesn't affect original workflow of the audio system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt_1 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic_1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008971] Re: Do not sort the task scan result from /proc when synthesizing perf events
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
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/2008971
Title:
Do not sort the task scan result from /proc when synthesizing perf
events
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
The perf tool use scandir() to iterate threads and sort in alphabetical order
when synthesizing PERF_RECORD_ events.
If the process ID is and it has one thread (tid = 1), the thread
will be processed before the process.
It results in PERF_RECORD_FORK events that come before PERF_RECORD_MMAP2
events.
The callstack will have missing symbols for threads where `PERF_RECORD_FORK`
events are processed before the `PERF_RECORD_MMAP2` event for the corresponding
process.
[Fix]
Do not use alphasort when calling scandir()
363afa3aef24f5e08df6a539f5dc3aae4cddcc1a (perf synthetic-events: Don't
sort the task scan result from /proc)
[Test Plan]
function update_last_pid()
local file = io.open("/proc/sys/kernel/ns_last_pid", "w")
file:write(9997)
end
update_last_pid()
os.execute("~/reproducer")
#include
#include
#include
constexpr int kThreadNum = 10;
void thread_job() { sleep(30); }
int main(void) {
std::thread threads[kThreadNum];
std::cout << "Parent process with pid " << getpid() << std::endl;
for (int i = 0; i < kThreadNum; ++i) {
threads[i] = std::thread(thread_job);
}
for (int i = 0; i < kThreadNum; ++i) {
threads[i].join();
}
std::cout << "All threads have finished" << std::endl;
return 0;
}
The flow is to set /proc/sys/kernel/ns_last_pid first, which represents the
last pid allocated in the current pid namespace.
The script (test.lua) sets ns_last_pid to 9997 and executes the reproducer
(reproducer.cpp).
After the reproducer creates ten threads, we execute the perf command as
follows: perf record -F 49 -e cpu-clock -a -g sleep 20.
Here is the result of command: perf report -f --tasks --mmaps -D | egrep -i
'perf_record_fork|perf_record_mmap' | grep
Before applying the patch, the output of the perf command was as follows:
0 0 0x34910 [0x40]: PERF_RECORD_FORK(:1):(:)
0 0 0x34990 [0x40]: PERF_RECORD_FORK(:10001):(:)
0 0 0x34a10 [0x40]: PERF_RECORD_FORK(:10002):(:)
0 0 0x34a90 [0x40]: PERF_RECORD_FORK(:10003):(:)
0 0 0x34b10 [0x40]: PERF_RECORD_FORK(:10004):(:)
0 0 0x34b90 [0x40]: PERF_RECORD_FORK(:10005):(:)
0 0 0x34c10 [0x40]: PERF_RECORD_FORK(:10006):(:)
0 0 0x34c90 [0x40]: PERF_RECORD_FORK(:10007):(:)
0 0 0x34d10 [0x40]: PERF_RECORD_FORK(:10008):(:)
0 0 0x34d90 [0x40]: PERF_RECORD_FORK(:10009):(:)
0 0 0x34e10 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
0 0 0x34e90 [0x80]: PERF_RECORD_MMAP2 /: [0x555de0159000(0x1000) @
0x1000 fd:00 2097758 0]: r-xp /root/reproducer
0 0 0x34f10 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd17f8000(0x7c000) @
0xe000 fd:00 1055098 0]: r-xp /usr/lib/x86_64-linux-gnu/libm.so.6
0 0 0x34fa0 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd18f9000(0x195000) @
0x28000 fd:00 1054988 0]: r-xp /usr/lib/x86_64-linux-gnu/libc.so.6
0 0 0x35030 [0x90]: PERF_RECORD_MMAP2 /: [0x7f9cd1afc000(0x17000) @
0x3000 fd:00 1054745 0]: r-xp /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
0 0 0x350c0 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1bb3000(0x11) @
0x9a000 fd:00 1068050 0]: r-xp /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30
0 0 0x35158 [0x98]: PERF_RECORD_MMAP2 /: [0x7f9cd1d4e000(0x2a000) @
0x2000 fd:00 1054949 0]: r-xp /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
0 0 0x351f0 [0x70]: PERF_RECORD_MMAP2 /: [0x7ffc983bb000(0x2000) @ 0
00:00 0 0]: r-xp [vdso]
0 0 0x35260 [0x78]: PERF_RECORD_MMAP2 /: [0xff60(0x1000)
@ 0 00:00 0 0]: --xp [vsyscall]
After applying the patch, the output of the perf command is as follows:
0 0 0x30c28 [0x40]: PERF_RECORD_FORK(:):(9998:9998)
0 0 0x30ca8 [0x80]: PERF_RECORD_MMAP2
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Fix Released Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
[Kernel-packages] [Bug 2000299] Re: Fix W6400 hang after resume of S3 stress
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2000299 Title: Fix W6400 hang after resume of S3 stress Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] amdgpu hang when stress S3 on AMD W6400 GPU. [Fix] Add a WA to manually adjust strobe calculation using FCLK restrict. [Test] Suspend AMD W6400 for 40 times, it works fine. [Where problems could occur] Low risk, upstream fix. It may cause AMD GPU hang. The patch is in 5.16, only Jammy kernel needs it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011926] Re: Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo child qdiscs"
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
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/2011926
Title:
Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue
pfifo child qdiscs"
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
Upstream commit: af7b29b1deaac6da3bb7637f0e263dfab7bfc7a3
Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo
child qdiscs"
taprio_attach() has this logic at the end, which should have been
removed with the blamed patch (which is now being reverted):
/* access to the child qdiscs is not needed in offload mode */
if (FULL_OFFLOAD_IS_ENABLED(q->flags)) {
kfree(q->qdiscs);
q->qdiscs = NULL;
}
because otherwise, we make use of q->qdiscs[] even after this array was
deallocated, namely in taprio_leaf(). Therefore, whenever one would try
to attach a valid child qdisc to a fully offloaded taprio root, one
would immediately dereference a NULL pointer.
$ tc qdisc replace dev eno0 handle 8001: parent root taprio \
num_tc 8 \
map 0 1 2 3 4 5 6 7 \
queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 \
max-sdu 0 0 0 0 0 200 0 0 \
base-time 200 \
sched-entry S 80 2 \
sched-entry S a0 2 \
sched-entry S 5f 6 \
flags 2
$ max_frame_size=1500
$ data_rate_kbps=2
$ port_transmit_rate_kbps=100
$ idleslope=$data_rate_kbps
$ sendslope=$(($idleslope - $port_transmit_rate_kbps))
$ locredit=$(($max_frame_size * $sendslope / $port_transmit_rate_kbps))
$ hicredit=$(($max_frame_size * $idleslope / $port_transmit_rate_kbps))
$ tc qdisc replace dev eno0 parent 8001:7 cbs \
idleslope $idleslope \
sendslope $sendslope \
hicredit $hicredit \
locredit $locredit \
offload 0
Unable to handle kernel NULL pointer dereference at virtual address
0030
pc : taprio_leaf+0x28/0x40
lr : qdisc_leaf+0x3c/0x60
Call trace:
taprio_leaf+0x28/0x40
tc_modify_qdisc+0xf0/0x72c
rtnetlink_rcv_msg+0x12c/0x390
netlink_rcv_skb+0x5c/0x130
rtnetlink_rcv+0x1c/0x2c
The solution is not as obvious as the problem. The code which deallocates
q->qdiscs[] is in fact copied and pasted from mqprio, which also
deallocates the array in mqprio_attach() and never uses it afterwards.
Therefore, the identical cleanup logic of priv->qdiscs[] that
mqprio_destroy() has is deceptive because it will never take place at
qdisc_destroy() time, but just at raw ops->destroy() time (otherwise
said, priv->qdiscs[] do not last for the entire lifetime of the mqprio
root), but rather, this is just the twisted way in which the Qdisc API
understands error path cleanup should be done (Qdisc_ops :: destroy() is
called even when Qdisc_ops :: init() never succeeded).
Side note, in fact this is also what the comment in mqprio_init()
says:
/* pre-allocate qdisc, attachment can't fail */
Or reworded, mqprio's priv->qdiscs[] scheme is only meant to serve as
data passing between Qdisc_ops :: init() and Qdisc_ops :: attach().
[ this comment was also copied and pasted into the initial taprio
commit, even though taprio_attach() came way later ]
The problem is that taprio also makes extensive use of the q->qdiscs[]
array in the software fast path (taprio_enqueue() and taprio_dequeue()),
but it does not keep a reference of its own on q->qdiscs[i] (you'd think
that since it creates these Qdiscs, it holds the reference, but nope,
this is not completely true).
To understand the difference between taprio_destroy() and mqprio_destroy()
one must look before commit 13511704f8d7 ("net: taprio offload: enforce
qdisc to netdev queue mapping"), because that just muddied the waters.
In the "original" taprio design, taprio always attached itself (the root
Qdisc) to all netdev TX queues, so that dev_qdisc_enqueue() would go
through taprio_enqueue().
It also called qdisc_refcount_inc() on itself for as many times as there
were netdev TX queues, in order to
[Kernel-packages] [Bug 2019868] Re: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2019868 Title: ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. The results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: tls # TAP version 13 # 1..179 # # Starting 179 tests from 6 test cases. # # RUN global.non_established ... # #OK global.non_established # ok 1 global.non_established # # RUN global.keysizes ... # #OK global.keysizes # ok 2 global.keysizes # # RUN tls_basic.base_base ... # #OK tls_basic.base_base # ok 3 tls_basic.base_base # # RUN tls.12_gcm.sendfile ... # #OK tls.12_gcm.sendfile # ok 4 tls.12_gcm.sendfile # # RUN tls.12_gcm.send_then_sendfile ... # #OK tls.12_gcm.send_then_sendfile # ok 5 tls.12_gcm.send_then_sendfile # # RUN tls.12_gcm.recv_max ... # #OK tls.12_gcm.recv_max # ok 6 tls.12_gcm.recv_max # # RUN tls.12_gcm.recv_small ... # #OK tls.12_gcm.recv_small # ok 7 tls.12_gcm.recv_small # # RUN tls.12_gcm.msg_more ... # #OK tls.12_gcm.msg_more # ok 8 tls.12_gcm.msg_more # # RUN tls.12_gcm.msg_more_unsent ... # #OK tls.12_gcm.msg_more_unsent # ok 9 tls.12_gcm.msg_more_unsent # # RUN tls.12_gcm.sendmsg_single ... # #OK tls.12_gcm.sendmsg_single # ok 10 tls.12_gcm.sendmsg_single # # RUN tls.12_gcm.sendmsg_fragmented ... # #OK tls.12_gcm.sendmsg_fragmented # ok 11 tls.12_gcm.sendmsg_fragmented # # RUN tls.12_gcm.sendmsg_large ... # #OK tls.12_gcm.sendmsg_large # ok 12 tls.12_gcm.sendmsg_large # # RUN tls.12_gcm.sendmsg_multiple ... # #OK tls.12_gcm.sendmsg_multiple # ok 13 tls.12_gcm.sendmsg_multiple # # RUN tls.12_gcm.sendmsg_multiple_stress ... # #OK tls.12_gcm.sendmsg_multiple_stress # ok 14 tls.12_gcm.sendmsg_multiple_stress # # RUN tls.12_gcm.splice_from_pipe ... # #OK tls.12_gcm.splice_from_pipe # ok 15 tls.12_gcm.splice_from_pipe # # RUN tls.12_gcm.splice_from_pipe2 ... # #OK tls.12_gcm.splice_from_pipe2 # ok 16 tls.12_gcm.splice_from_pipe2 # # RUN tls.12_gcm.send_and_splice ... # #OK tls.12_gcm.send_and_splice # ok 17 tls.12_gcm.send_and_splice # # RUN tls.12_gcm.splice_to_pipe ... # #OK tls.12_gcm.splice_to_pipe # ok 18 tls.12_gcm.splice_to_pipe # # RUN tls.12_gcm.recvmsg_single ... # #OK tls.12_gcm.recvmsg_single # ok 19 tls.12_gcm.recvmsg_single # # RUN tls.12_gcm.recvmsg_single_max ... # #OK tls.12_gcm.recvmsg_single_max # ok 20 tls.12_gcm.recvmsg_single_max # # RUN tls.12_gcm.recvmsg_multiple ... # #OK tls.12_gcm.recvmsg_multiple # ok 21 tls.12_gcm.recvmsg_multiple # # RUN tls.12_gcm.single_send_multiple_recv ... # #OK tls.12_gcm.single_send_multiple_recv # ok 22 tls.12_gcm.single_send_multiple_recv # # RUN tls.12_gcm.multiple_send_single_recv ... # #OK tls.12_gcm.multiple_send_single_recv # ok 23 tls.12_gcm.multiple_send_single_recv # # RUN tls.12_gcm.single_send_multiple_recv_non_align ... # #OK tls.12_gcm.single_send_multiple_recv_non_align # ok 24
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Won't Fix Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
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/2003267
Title:
[EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04
release
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
== SRU Justification ==
Intel has requested the following patches which enable enable Intel_idle for
eagle stream.
Intel has customers that would like to use the intel_idle driver on latest
SPR (Sapphire Rapids).
These patches have all landed upstream, but are not in Jammy.
These patches will enable customers to use Ubuntu 22.04 on new hardware
from Intel.
== Fixes ==
9edf3c0ffef0 ("intel_idle: add SPR support")
da0e58c038e6 ("intel_idle: add 'preferred_cstates' module argument")
3a9cf77b60dc ("intel_idle: add core C6 optimization for SPR")
03eb65224e57 ("cpuidle: intel_idle: Drop redundant backslash at line end")
39c184a6a9a7 ("intel_idle: Fix the 'preferred_cstates' module parameter")
7eac3bd38d18 ("intel_idle: Fix SPR C6 optimization")
1548fac47a11 ("intel_idle: make SPR C1 and C1E be independent")
== Regression Potential ==
Medium. These patches are specific to enable intel_idle support for Sapphire
Rapids. Changes
are specific to Intel and tested by Intel.
== Test Case ==
A test kernel was built with these patches and tested by Intel.
Intel tested on SPR-SP machine and see the correct 190us and 600us residency
for the C6 state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: Invalid Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux-azure source package in Kinetic: Fix Released Status in linux-gcp source package in Kinetic: Fix Released Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003374] Re: Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2003374 Title: Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols Status in dh-kpatches: Unknown Status in Ubuntu on IBM z Systems: Fix Committed Status in kpatch package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in kpatch source package in Jammy: In Progress Status in linux source package in Jammy: Fix Released Status in kpatch source package in Kinetic: Won't Fix Bug description: [ Impact ] * When UBSAN is enabled in an s390x kernel configuration, kpatch- build can fail to find matching symbols in the vmlinux symbol table (see attached example_livepatch.patch). This was discovered in both Jammy 5.15 and Kinetic 5.19 kernels, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log). * Disabling UBAAN in s390x kernel configurations resolved the issue for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality. [ Test Plan ] * Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel (see attached example_livepatch.patch). This should be successful. [ Where problems could occur ] * A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. To manage notifications about this bug go to: https://bugs.launchpad.net/dh-kpatches/+bug/2003374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2006077 Title: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] Some machines which have dynamically loaded SSDT tables, will not be loaded and get the CPPC not worked. [Fix] Fix the regression by some load supports for CPPC from an SSDT dynamically when _OSC reports CPPC v2. And make the "[\_SB.PR00._CPC], AE_NOT_FOUND" gone. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
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/2004262
Title:
Intel E810 NICs driver in causing hangs when booting and bonds
configured
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Won't Fix
Bug description:
[Impact]
* Intel E810-family NICs cause system hangs when booting with bonding
enabled
* This happens due to the driver unplugging auxiliary devices
* The unplug event happens under RTNL lock context, which causes a deadlock
where the RDMA driver waits for the RNL lock to complete removal
[Test Plan]
* Users have reported that after setting up bonding on switch and server
side, the system will hang when starting network services
[Fix]
* The upstream patch defers unplugging/re-plugging of the auxiliary device,
so that it's not performed under the RTNL lock context.
* Fix was introduced by commit:
248401cb2c46 ice: avoid bonding causing auxiliary plug/unplug under
RTNL lock
[Regression Potential]
* Regressions would manifest in devices that support RDMA functionality and
have been added to a bond
* We should look out for auxiliary devices that haven't been properly
unplugged, or that cause further issues with
ice_plug_aux_dev()/ice_unplug_aux_dev()
[Original Description]
jammy 22.04.1
linux-image-generic 5.15.0-58-generic
Intel E810-XXV Dual Port NICs in Dell PowerEdge 650
- 5.15 in jammy -> reproducible
- 5.19 in hwe-edge -> reproducible
- 6.2.rc6 in the mainline build -> works
- Intel's ice driver 1.10.1.2.2 -> works
After beonding is enabled on switch and server side, the system will
hang at initialing ubuntu. The kernel loads but around starting the
Network Services the system can hang for sometimes 5 minutes, and in
other cases, indefinitely.
The message of:
echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve
blocked for more than 120 seconds
appears, and eventually the Network services just attempts to start
and never does. This is with or without DHCP enabled.
Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
linux-oem kernels and all exhibit the same failure.
To work around this. installing the Intel 'ice' driver of version
1.10.1.2.2 works. The system doesn't even remotely hang at startup
and all networking functions remain working (ping, DNS, general
accessibility).
The driver can be found at
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jan 31 13:08 seq
crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia:
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R650
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
RelatedPackageVersions:
linux-restricted-modules-5.15.0-58-generic N/A
linux-backports-modules-5.15.0-58-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags: jammy
uec-images
Uname: Linux 5.15.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
[Kernel-packages] [Bug 2011616] Re: Connection timeout due to conntrack limits
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2011616 Title: Connection timeout due to conntrack limits Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-gcp source package in Kinetic: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux-gcp source package in Lunar: New Bug description: Customers of GKE 1.25 and 1.26 are affected by the conntrack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012335] Re: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256)
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2012335 Title: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256) Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] There is a user reporting errors in setup with their Intel E810 NIC with error messages saying that the driver cannot allocate enough MSI-X vectors on their 256 cpu-count system. It seems the ICE ethernet driver has an all or nothing approach to allocating MSI-X vectors and could request more MSI-X vectors than it finds available, which could lead to the driver failing to initialize and start. [Fix] The patch that fixes this allocates as many MSI-X vectors as it can to continue functionality by reducing the number of requested MSI-X vectors if it does not have enough to do full allocation. [Backport] In Jammy we do not carry patches for switchdev support in the driver so do not allocate the switchdev MSI-X vector for it. Also in Jammy use the older way of checking RDMA support by testing the RDMA bit is set as opposed to the newer ice_is_rdma_ena that the patch uses. [Test Plan] Install and startup Ice driver with an Intel 800 series NIC and check that we do not have the failure: Not enough device MSI-X vectors, requested = 260, available = 253 and check that everything works as expected. The backported patch for Jammy has been tested by the original user who submited the bug report with their high cpu count system and confirmed no errors. [Where problems could occur] There could be problems with the logic of reducing the MSI-X vector usage leading to more errors in the driver, but otherwise minimal regression potential as the code is mostly refactoring initial MSI-X setup. -- System Configuration OS: Ubuntu 22.04 LTS Kernel: 5.15.0-25-generic CPUs: 256 NIC: Intel E810 NIC with 512 MSIx vectors each function Errors Not enough device MSI-X vectors, requested = 260, available = 253 Findings (1) the current ice kernel driver (ice_main.c) will pre-allocate all required number of msix (even it's not enough for big core CPUs) (2) the commit https://github.com/torvalds/linux/commit/ce4626131112e1d0066a890371e14d8091323f99 has improved this logic, and it seems merged into kernel version from v6.1 So for supporting the new CPUs with more than 252 vCPUs, will Ubuntu kernel backport above patch to the current kernel (v5.15) ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013088] Re: kernel: fix __clear_user() inline assembly constraints
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: == [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [Fix] * For Kinetic and Jammy cherrypick of 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3 "s390/uaccess: add missing earlyclobber annotations to __clear_user()" * For Focal and Bionic a backport of the above commit is needed: https://launchpadlibrarian.net/659551648/s390-uaccess.patch [ Test Plan ] * A test program in C is needed and used for testing. * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 separately, and submit the SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013209] Re: expoline.o is packaged unconditionally for s390x
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2013209 Title: expoline.o is packaged unconditionally for s390x Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-5.15 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN for s390x in Jammy. While this works as expected on Jammy, it won't work on some derivatives of it: for example focal:hwe-5.15. On Focal, this config can't be enabled due to the GCC version it comes with. CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with 90400. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2015372 Title: Add support for intel EMR cpu Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. This support is a nice feature to have in Jammy because it is an LTS release and enabling extra hardware adds to its usability. Usually backporting new features to existing kernels it's not a common practice. But these commits were easy to backport. Most of them were clean cherry picks. Some of them were already picked up from upstream stable releases, and some required manual intervention because Jammy did not have some commits applied but the actual changes were very minimal. More information about each commit is addressed inline. [Commits] 1. 9c252ecf3036: "platform/x86: intel-uncore-freq: add Emerald Rapids support" Adjusted the path to uncore-frequency.c In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to uncore-frequency dir 2. 5a8a05f165fb18d37526062419774d9088c2a9b9 "perf/x86/intel/cstate: Add Emerald Rapids" Small context adjustment in intel_cstates_match array because of missing SPR, RPL and MDL cpu models introduced in 528c9f1daf20d 3. 57512b57dcfaf63c52d8ad2fb35321328cde31b0 "perf/x86/rapl: Add support for Intel Emerald Rapids" Context adjustment due to missing - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL domain" - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N" - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake" - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake" 4. 74528edfbc664f9d2c927c4e5a44f1285598ed0f clean cherry-pick 5. 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5 clean cherry-pick 6. 93cac4150727dae0ee89f501dd75413b88eedec0 clean cherry-pick 7. 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb clean cherry-pick 8. e4b2bc6616e21 clean cherry-pick [Testing] Kernel was built on cbd and boot tested on a VM. TODO ask for help from intel. [Regression potential] Very low, these are minimal new features, which actually reuse a lot of the existing cpu structures/functions. The following changes since commit 8feeaa9039a290b978e7855ab82955cd9348fc13 "platform/x86: intel-uncore-freq: add Emerald Rapids support" are available in the Git repository at: git://git.launchpad.net/~~roxanan/ubuntu/+source/linux/+git/jammy lp2015372 for you to fetch changes up to commit 7d88565e6777082265b373733fd93eb3e0914e12 "EDAC/i10nm: Add Intel Emerald Rapids server support" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015097] Re: Kernel crash during Mellanox performance testing
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2015097 Title: Kernel crash during Mellanox performance testing Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) * Change landed v5.19 upstream, Kinetic onward not affected [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013603] Re: Kernel livepatch ftrace graph fix
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2013603 Title: Kernel livepatch ftrace graph fix Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] * Additional patch required to support Livepatch for s390x * Fixes Livepatch transition issues when using ftrace graph tracing [Test Case] * Compile test * Boot test * Test a Livepatch (patch to /proc/meminfo module) * Test Livepatch from ftrace graphed function (via https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh) [Where things could go wrong] * Functionality already exists upstream, once kernel is boot and Livepatch tested - should have no regressions [Other info] * Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2015400 Title: losetup with mknod fails on jammy with kernel 5.15.0-69-generic Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Invalid Bug description: [ Impact ] * Regression in the loop block driver in Jammy kernel between 5.15.0-67 to 5.15.0-68 (in v5.15.86 stable), due to a change in the default behavior (value) of kernel parameter `max_loop` (from 0 to 8) in commit: `loop: Fix the max_loop commandline argument treatment when it is set to 0` (comment #6). * Users of loop devices (major 7) with minor >= 8 now fail to `open()` a loop device created with `mknod()`. * This is a corner case, as most people use `losetup` with usual /dev/loopNUMBER (or `--find`) which are not affected as it uses a different code path. (`losetup` for `/dev/loopNOT-A-NUMBER` is affected.) * Workaround: kernel parameter `max_loop=0`. [ Test Steps ] * Run the test cases (losetup and test-loop.c in comment #6): - max_loop not set (default) - max_loop=0 - max_loop=8 * Verify the default behavior (max_loop not set) is restored. * Verify the modified behavior (max_loop is set) is unchanged. [ Regression Potential ] * Regressions would be limited to the loop block driver, more specifically its default behavior (but it's that now) or specific usage of max_loop parameter (tested; looks OK). [ Other Info ] * Patch 1 [1] is not quite a fix, but adds CONFIG guards that Patch 2 [2] depends on. (Alternatively, a Patch 2 backport with that could be done, but Patch 1 seems trivial enough.) * The fix on Jammy is only Patch 2, with a trivial backport (that CONFIG option is not in Jammy/v5.15, only in v5.18). * The fix on Lunar is both patches; clean cherry-picks. * The fix on Mantic is both patches too, now in v6.5-rc3, which should be automatically incorporated as Mantic apparently will release with the 6.5 kernel [3] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23881aec85f3219e8462e87c708815ee2cd82358 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bb5faa99f0ce40756ab7bbbce4f16c01ca5ebd5a [3] https://discourse.ubuntu.com/t/introducing-kernel-6-5-for-the-23-10-mantic-minotaur-release Original Description: --- losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2015498 Title: Debian autoreconstruct Fix restoration of execute permissions Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU justification [Impact] Debian source package diffs cannot represent that a file should be executable. gen-auto-reconstruct detects when a commit adds a script that is supposed to be invoked during the build and restores the execute permissions in the reconstruct script by adding `chmod +x $file`. But, if a file removes its execute permission, this will change it back. This happened in the last jammy release (version 5.15.0-70.77) where a commit from upstream removed the execute permission for a header file but then our scripts brought it back. [Fix] Andy proposed the following fix https://dpaste.com/6SJ8YR3BM Basically it checks if the permission was added or removed and uses either +x or -x. [Test plan] Easily tested with jammy-kvm, latest release where a rebase picked this commit "treewide: fix up files incorrectly marked executable" where `drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 644 (removed execute). When debian packages are prepared, you'll notice the file has changed its permission back to 755. With the fix, it should be the same. [Regression potential] Low, it is a small fix. Scripts will still have execute permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015956] Re: selftest: fib_tests: Always cleanup before exit
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2015956 Title: selftest: fib_tests: Always cleanup before exit Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Copied from the commit message: Usage of `set -e` before executing a command causes immediate exit on failure, without cleanup up the resources allocated at setup. This can affect the next tests that use the same resources, leading to a chain of failures. A simple fix is to always call cleanup function when the script exists. This approach is already used by other existing tests. [Fix] * b60417a9f2 selftest: fib_tests: Always cleanup before exit This patch can be cherry-picked into affected kernels. [Test] Run the patched fib_tests.sh on KVM kernels, which is expected to fail due to bug 2007458. Check with `ip netns`, the ns1 added during setup() should be removed. [Where problems could occur] Test robustness improvement, this should not break things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015855] Re: Add split lock detection for EMR
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2015855 Title: Add split lock detection for EMR Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 The remaining feature needed to fully support EMR is the split lock detection mechanism. So far, bit 5 in IA32_CORE_CAPABILITIES says whether split lock detection is supported or not, but this is not architectural, meaning that this should be trusted only if it’s confirmed that a specific CPU model implements it. This lead to a mapping between a CPU model and whether it supports split lock detection by default (no need to check IA32_CORE_CAPABILITIES) or they may support the split lock detection → IA32_CORE_CAPABILITIES bit 5 has to be checked. With more and more CPU models, this becomes hard to maintain. Moreover, the December 2022 edition of the Intel Instruction Set Extensions manual defined that the split lock disable bit in the IA32_CORE_CAPABILITIES MSR is (and retrospectively always has been) architectural. Documentation also mentions “All processors that enumerate support for MSR_IA32_CORE_CAPS and set MSR_IA32_CORE_CAPS_SPLIT_LOCK_DETECT support split lock detection.” Thus, commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8: “ x86/split_lock: Enumerate architectural split lock disable bit” from linux-next removes the need of adding a new CPU model in that mapping. This is needed to support split lock detection for the new EMR CPU and future models that don’t suffer architectural changes. [Testing] Kernel was built on cbd and boot tested on a VM. Intel was asked to install and test the new kernel from this ppa https://launchpad.net/~roxanan/+archive/ubuntu/lp2015855 [Regression potential] Very low, it is a small refactor and in essence, it does the exact same thing for existing cpu models: 1. For Icelake which does not have IA32_CORE_CAPABILITIES it always assumes the mechanism is supported. 2. For the rest, it automatically checks bit 5 of IA32_CORE_CAPABILITIES without the extra step of checking the map if the CPU supports this (which was always true) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in alsa-ucm-conf source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
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/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2018591 Title: Enable Tracing Configs for OSNOISE and TIMERLAT Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: == SRU Justification == These config changes will allow tracing with the OSNOISE and TIMERLAT tracing tools. These tracers can be enabled at run-time and should not affect performance or add any additional overhead. == Fix == UBUNTU: [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs == Regression Potential == Low. These config changes will just allow the use of tracing tools. == Test Case == Test build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Confirmed Bug description: [Impact] Opened files reported in /proc/pid/map_files can be shows with the wrong mount point using overlayfs with filesystem namspaces. This incorrect behavior is fixed: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files However, the fix introduced a new regression, the reference to the original file stored in vma->vm_prfile is not properly released when vma->vm_prfile is replaced with a new file. This can cause a reference counter unbalance, leading errors such as "target is busy" when trying to unmount overlayfs, even if the filesystem has not active reference. [Test case] Reproducer provided by original bug reporter: https://launchpadlibrarian.net/663151659/overlayfsscript_example [Fix] Fix by properly releasing the original file stored in vm_prfile. [Regression potential] This fix seems to solve the reported bug (verified with the reproducer) and it doesn't seem to introduce other regressions or behavior change. However, we may experience regressions in overlayfs or potentially other "target is busy" errors when unmounting overlayfs filesystems with this fix applied, if there are still other corner cases not covered properly. [Original bug report] Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a
[Kernel-packages] [Bug 2019131] Re: Add PPIN support for Intel EMR cpu
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2019131 Title: Add PPIN support for Intel EMR cpu Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 and in #lp2015855. The remaining feature needed to fully support EMR is PPIN (the Protected Processor Inventory/Identification Number). This was recently pushed to upstream in 6.4 in commit 36168bc061b4368ad19e82b06a6463c95d3bb9a7. The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X in the cpuids table where cpus that support ppin are listed. The table is then used in `ppin_init`. In Jammy, this implementation is missing. Both Amd and Intel have their own implementation which is doing pretty much the same. Instead of a list of cpus supported, a switch case is used instead in their init functions (amd_detect_ppin and intel_ppin_init). To reduce duplication of code and to help backport smoothly the new addition of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918 “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too. Thus commits: - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD ppin_init() functions" - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids to list of CPUs that support PPIN" are needed to support PPIN for EMR. [Testing] Kernel was built on cbd and boot tested on a VM. [Regression potential] Very low, it is a small refactor that removes duplication and it should not affect the functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019131/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. The similiar patch has been included in v6.4-rc7 6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Committed Status in linux-kvm source package in Kinetic: Invalid Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Status in linux-meta-azure source package in Lunar: Invalid Status in linux-meta-kvm source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-kvm source package in Mantic: Invalid Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_INTEGRITY_MACHINE_KEYRING CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring implementation is patched to skip the check enabled by this kconfig) (The latter two are needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To verify whether this works, add a certificate to MOK, boot and check the content of the secondary keyring. The machine keyring should show up under it, and it should show the certificates loaded in MOK. E.g.: $ sudo keyctl show %:.secondary_trusted_keys Keyring 159454604 ---lswrv 0 0 keyring: .secondary_trusted_keys 88754641 ---lswrv 0 0 \_ keyring: .builtin_trusted_keys 889010778 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1 799434660 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f 541326986 ---lswrv 0 0 \_ keyring: .machine 188508854 ---lswrv 0 0 \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1 475039424 ---lswrv 0 0 \_ asymmetric: sb-bluca: Secure Boot Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479 [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019000] Re: Use new annotations model
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019000 Title: Use new annotations model Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Focal: Fix Released Status in linux-gcp source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: New Status in linux source package in Kinetic: Confirmed Status in linux-gcp source package in Kinetic: Invalid Status in linux-kvm source package in Kinetic: Invalid Bug description: [Impact] Starting with lunar we have introduced a new way to manage kernel configs, unifying the duplicated information defined in the annotations file + config chunks into an annotations-only model. [Test case] A kernel build can be considered a valid test case, in particular the specific command that is used to update the .config's for all the supported architectures and flavours: $ fakeroot debian/rules updateconfigs [Fix] Import the required changes in debian/ from lunar (with the required adjustments) to support the annotations-only model also in all the previous releases. [Regression potential] We may experience regressions during the updateconfigs step, especially with derivatives. Moreover, derivatives that want to transition to the new annotations model require to adjust the header in the annotations file as following (make sure to define the corresponding architectures and flavours): # FORMAT: 4 # ARCH: amd64 arm64 armhf ppc64el s390x # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae ppc64el-generic s390x-generic After adjusting the header a special command is provided to transition to the new annotations-only model: $ fakeroot debian/rules migrateconfigs This command should automatically import the old configs into the new annotations file. A kernel with this change applied can still support the old annotations+configs model, the transition to the new model is not mandatory. Basically without using `fakeroot debian/rules migrateconfigs` the updateconfigs step will continue to use the old model and the old scripts (that is the safest approach to avoid potential unexpected .config changes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019880] Re: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2019880 Title: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: These failures happen on all supported architectures, when fips=1. When fips=0, all test cases pass. Results are shown below: make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/src/linux' TAP version 13 1..1 # selftests: net: vrf-xfrm-tests.sh # # No qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # netem qdisc on VRF device # TEST: IPv4 no xfrm policy [ OK ] # TEST: IPv6 no xfrm policy [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy based on address [FAIL] # TEST: IPv6 xfrm policy with VRF in selector [ OK ] # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # RTNETLINK answers: Function not implemented # TEST: IPv4 xfrm policy with xfrm device [FAIL] # TEST: IPv6 xfrm policy with xfrm device [FAIL] # # Tests passed: 6 # Tests failed: 8 not ok 1 selftests: net: vrf-xfrm-tests.sh # exit=1 make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2019880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020295] Re: Include the MAC address pass through function on RTL8153DD-CG
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2020295 Title: Include the MAC address pass through function on RTL8153DD-CG Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When user connect network cable on the RJ45 port of RTL8153DD-CG on dock, it should show pass through MAC address set in BIOS. But the LAN MAC address pass through doesn't function on RTL8153DD-CG sku. [Fix] Commit in v6.3-rc1 fixes the issue. ec51fbd1b8a2 r8152: add USB device driver for config selection [Test] Verified by OEM. [Where problems could occur] It won't affect the old behavior if there is no preferred cfg is configured and will select the preferred one while probing. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020319] Re: Encountering an issue with memcpy_fromio causing failed boot of SEV-enabled guest
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2020319 Title: Encountering an issue with memcpy_fromio causing failed boot of SEV- enabled guest Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux source package in Focal: Fix Released Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Bug description: [Impact] When launching a SEV-enabled guest, the guest kernel panics with the following call trace, indicating a critical error in the system. == [1.090638] software IO TLB: Memory encryption is active and system is using DMA bounce buffers [1.092105] Linux agpgart interface v0.103 [1.092716] BUG: unable to handle page fault for address: 9b820003d068 [1.093445] #PF: supervisor read access in kernel mode [1.093966] #PF: error_code(0x) - not-present page [1.094481] PGD 80010067 P4D 80010067 PUD 8001001d7067 PMD 8001001da067 PTE 8000fed40173 [1.094629] Oops: [#1] SMP NOPTI [1.094629] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu [1.094629] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50 [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66 [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212 [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 0002 [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 9b820001ba90 [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 0f80 [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 8cc7068eca48 [1.094629] R13: 8cc700a64288 R14: R15: fed40080 [1.094629] FS: () GS:8cc77bd0() knlGS: [1.094629] CS: 0010 DS: ES: CR0: 80050033 [1.094629] CR2: 9b820003d068 CR3: 800174a1 CR4: 00350ee0 [1.094629] Call Trace: [1.094629] [1.094629] crb_map_io+0x315/0x870 [1.094629] ? radix_tree_iter_tag_clear+0x12/0x20 [1.094629] ? _raw_spin_unlock_irqrestore+0xe/0x30 [1.094629] crb_acpi_add+0xc2/0x140 [1.094629] acpi_device_probe+0x4c/0x170 [1.094629] really_probe+0x222/0x420 [1.094629] __driver_probe_device+0x119/0x190 [1.094629] driver_probe_device+0x23/0xc0 [1.094629] __driver_attach+0xbd/0x1e0 [1.094629] ? __device_attach_driver+0x120/0x120 [1.094629] bus_for_each_dev+0x7e/0xd0 [1.094629] driver_attach+0x1e/0x30 [1.094629] bus_add_driver+0x139/0x200 [1.094629] driver_register+0x95/0x100 [1.094629] ? init_tis+0xfd/0xfd [1.094629] acpi_bus_register_driver+0x39/0x50 [1.094629] crb_acpi_driver_init+0x15/0x1b [1.094629] do_one_initcall+0x48/0x1e0 [1.094629] do_initcalls+0x12f/0x159 [1.094629] kernel_init_freeable+0x162/0x1b5 [1.094629] ? rest_init+0x100/0x100 [1.094629] kernel_init+0x1b/0x150 [1.094629] ? rest_init+0x100/0x100 [1.094629] ret_from_fork+0x22/0x30 [1.094629] [1.094629] Modules linked in: [1.094629] CR2: 9b820003d068 [1.094629] ---[ end trace 3d6d81c42a3c2030 ]--- [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50 [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66 [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212 [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0
[Kernel-packages] [Bug 2023650] Re: Add microphone support of the front headphone port on P3 Tower
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023650 Title: Add microphone support of the front headphone port on P3 Tower Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The 3.5mm headphone port in front panel cannot detect the microphone. [Fix] Add quirk for headset mic pin on P3 Tower. [Test] Tested with alsa audio, mic works fine. [Where problems could occur] Low risk to add specific hardware ID. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: Fix Released Status in kexec-tools source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: Fix Released Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. 1) Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. 2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current
[Kernel-packages] [Bug 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028122 Title: Fix unreliable ethernet cable detection on I219 NIC Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE wake doesn't working properly anymore. [Fix] Always use PME poll to read PCI PME to know if there's wake event. [Test] With the patch applied, ethernet cable can always be detected. [Where problems could occur] PME poll mechanism periodically reads the PMCTRL register, so the power consumption can be slightly higher. The increase will be very low, probably won't be noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024900] Re: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2024900 Title: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools- common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026028] Re: usbrtl sometimes doesn't reload firmware
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2026028 Title: usbrtl sometimes doesn't reload firmware Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Committed Bug description: [Impact] The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load firmware which results in the BT adapter running potentially old firmware rather than the current version from /lib/firmware provided by the linux-firmware package. This will show in logs like so: Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=dfc6 lmp_ver=0a lmp_subver=d922 Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp subver d922, hci rev dfc6, hci ver 000a Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware upload needed The driver reads subver from the adapter to determine chip type. But that value is overwritten by a firmware load. In the above case, a firmware was already loaded which returns subver d922 which the driver does not recognize and it therefore won't load new firmware. [Test Case] 1) Boot machine with USB adapter plugged in. 2) Verify firmware is loaded. 3) Reboot a couple of times and verify that firmware is reloaded every time. [Where Problems Could Occur] Limited to Realtek USB bluetooth adapters that use the btrtl driver. Issues could show up as Bluetooth connection/initialization problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022098] Re: Severe NFS performance degradation after LP #2003053
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux package in Ubuntu: Confirmed Status in linux-gke package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Status in linux-gke source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023220 Title: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Trusty: Incomplete Status in linux-oem-6.1 source package in Trusty: Invalid Status in linux source package in Xenial: Incomplete Status in linux-oem-6.1 source package in Xenial: Invalid Status in linux source package in Bionic: Incomplete Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush the global TLB entries. This can lead to info leak or undefined behavior. [Mitigation] Boot with nopcid on affected systems. [Test case] There is no particular test case. [Potential regressions] This affects performance on the affected systems. TLB behavior could also be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023311] Re: Resolve synchronous exception on arm64
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
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/2023311
Title:
Resolve synchronous exception on arm64
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Committed
Bug description:
SRU Justification
[Impact]
MSFT has requested the inclusion of commit
e8dfdf3162eb549d064b8c10b1564f7e8ee82591 ('arm64: efi: Recover from
synchronous exceptions occurring in firmware'). It looks generic
enough to apply to the master kernel.
Unlike x86, which has machinery to deal with page faults that occur
during the execution of EFI runtime services, arm64 has nothing like
that, and a synchronous exception raised by firmware code brings down
the whole system.
[Test Plan]
This looks like a hard one to reproduce. Boot and regression testing
should be sufficient.
[Regression Potential]
Firmware exceptions could still take down the system.
[Other Info]
SF: #00362062
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023311/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022361] Re: Please enable Renesas RZ platform serial installer
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
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/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2023539 Title: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2 [Fix] Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2. [Test] Tested with alsa audio, audio works fine. [Where problems could occur] Risk low due to specific hardware. These 2 patches are already in Unstable and OEM-6.1 already got them via stable updates. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2023577 Title: cls_flower: off-by-one in fl_set_geneve_opt Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] An unprivileged user may cause an out-of-bounds write by setting up geneve options on the flower classifier. [Test case] https://seclists.org/oss-sec/2023/q2/219 [Potential regression] Users setting up geneve options on the flower tc classifier can be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028550] Re: Backport support to tolerate ZSTD compressed firmware files
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2028550 Title: Backport support to tolerate ZSTD compressed firmware files Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: [ Impact ] * To ensure reliable dist-upgrades in case of partial upgrades or upgrade failures, it is desirable for LTS GA kernel to support features that next-LTS GA kernel will rely on. * Specifically it is being discussed to switch linux-firmware to ZSTD compressed one (see bug #1942260) * To ensure that failed dist-upgrades can still boot after-partial upgrade it is desirable to suppport zstd compressed firmware [ Test Plan ] * Boot new build of GA linux kernel with CONFIG_FW_LOADER_COMPRESS_ZSTD * Check that existing firmware files loaded on a given machine can be compressed with zstd and still loaded by this kernel * Check that depmod / initramfs-tools all support .zst compressed firmware [ Where problems could occur ] * Once this is inroduced in jammy-GA kernel it may cripple into focal-hwe kernels too, and people may start relying on this feature despite not universally supported by all other focal kernels. This should be trivial to catch in SRUs for example, do not accept SRUs of firmwares that ship themselves as .zst in Jammy and lower. [ Other Info ] * See https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
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/2028158
Title:
[SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set
to flat mode. Duplicate device_dax ids were created and hence probing
is failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can change the devdax
to
system-ram
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"devdax" ---> HBM CPU 1, This we can change the devdax
to
system-ram
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i error
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
---
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax4.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, event-pid.tc in linux/tools/testing/selftests/ftrace will take too much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: sudo ./ftracetest -vvv test.d/event/event-pid.tc The test should finish within a few minutes. [Regression Potential] Change limited to testing tools, it should not have any actual impact to kernel functions. == Original Bug Report == First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2032176 Title: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Impact: We had reports of VM setups which would show intermediate crashes and after that locking up completely. This could be reproduced with large memory setups. The problem seems to be that fixes to performance regressions caused more problems in 5.15 kernels and the full fixes are too intrusive to be backported. Fix: The following patch was recently sent to the upstream stable mailing list and looks to be making its way into linux-5.15.y. This changes the default value of kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed back in config). Regression potential: VM hosts with many large memory tennants might see a performance impact which the TDP MMU approach tried to solve. If those did not see other problems they might turn this on again. Testcase: Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large second level guest (32GB memory). Repeatedly starting and stopping the 2nd level guest. --- original description --- The crash occurred on a juju machine, and the juju agent was lost. The juju machine is on an openstack instance provision by juju. The openstack console log indicts the it is related to spin_lock and KVM MMU: [418200.348830] ? _raw_spin_lock+0x22/0x30 [418200.349588] _raw_write_lock+0x20/0x30 [418200.350196] kvm_tdp_mmu_map+0x2b1/0x490 [kvm] [418200.351014] kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm] [418200.351796] direct_page_fault+0x206/0x310 [kvm] [418200.352667] __mmu_notifier_invalidate_range_start+0x91/0x1b0 [418200.353624] kvm_tdp_page_fault+0x72/0x90 [kvm] [418200.354496] try_to_migrate_one+0x691/0x730 [418200.355436] kvm_mmu_page_fault+0x73/0x1c0 [kvm] openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/ syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/ The syslog was rotated after the crash occurred, so the syslog at the time of the initial crash was lost. Other juju machine with 5.15.0.79.76 kernel seems to have the same issues. We previously have a similar issue with 5.15.0-73. The juju machine crashed with raw_spin_lock and kvm mmu in the logs as well: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Aug 21 08:59:46 2023 Ec2AMI: ami-0c61 Ec2AMIManifest: FIXME Ec2AvailabilityZone: availability-zone-1 Ec2InstanceType: builder-cpu4-ram72-disk20 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 03:23 seq crw-rw 1 root audio 116, 33 Aug 23 03:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSubPlatform: metadata
[Kernel-packages] [Bug 2029138] Re: cifs: fix mid leak during reconnection after timeout threshold
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2029138 Title: cifs: fix mid leak during reconnection after timeout threshold Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux-azure source package in Lunar: Fix Released Bug description: SRU Justification [Impact] A regression in the Ubuntu 5.15 kernel has been causing problems for multiple customers on Azure. This bug has been fixed in the mainline kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69cba9d3c1284e0838ae408830a02c4a063104bc [Test Plan] Microsoft tested [Regression Potential] Reconnections could fail. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030924] Re: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files.
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2030924 Title: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files. Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] On DELL EMC PowerEdge system when Ubuntu 22.04.1 OS is Installed, Unable to Interpret the values in cpuinfo_max_freq and cpuinfo_min_freq sysfs files as per the Intel specs document. Steps to Reproduce: 1. Install one CPU that supports DBS "Demand-Based Power Management". 2. Install Ubuntu 22.04.1 OS. 2. Enable "Logical Processor" under CPU Information menu from F2 setup. 3. Save changes and reboot to Ubuntu 22.04.1 OS. 4. Right click on "Computer" and select "File system" and check for the following CPU directories. /sys/devices/system/cpu/cpu0/cpufreq/cpu0 /sys/devices/system/cpu/cpu0/cpufreq/cpu1 5. View the Max Frequency and Min Frequency under CPU0 and CPU1 directory. 6. The Max and Min Frequency did not match as per the Intel specs datasheet. Actual results: /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 680 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 80 /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 390 Expected results: As per Intel datasheet specification. /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 5300 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 800 MHz /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 3000 MHz [Fix] cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores https://github.com/torvalds/linux/commit/0fcfc9e51990246a9813475716746ff5eb98c6aa [github.com] [Test Plan] Same as steps to reproduce [ Where problems could occur ] This issue is seen on Intel based system under development which supports DBS "Demand-Based Power Management", then install Ubuntu-22.04 and boot into OS then check for the frequency values under /sys/devices/system/cpu/cpu0/cpufreq/cpu0 Regression risk = Low to medium [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/cpuinfo_freq lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/cpuinfo_freq_lunar_2 Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/cpuinfo_freq_mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2031093 Title: libgnutls report "trap invalid opcode" when trying to install packages over https Status in ubuntu-kernel-tests: New Status in gnutls28 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in gnutls28 source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Status in gnutls28 source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in gnutls28 source package in Lunar: Won't Fix Status in linux source package in Lunar: Fix Released Bug description: [Impact] When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git. [Test case] git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] Works fine with the mitigation disabled by default. [Potential regressions] Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys. - When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with: E: Method https has died unexpectedly! E: Sub-process https received signal 4. $ sudo apt install linux-libc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-libc-dev 0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded. Need to get 1353 kB of archives. After this operation, 6943 kB of additional disk space will be used. E: Method https has died unexpectedly! E: Sub-process https received signal 4. From dmesg you will see: [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000] Also, git clone is not working as well. $ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] libgnutls30 version:3.7.3-4ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ? asm_exc_invalid_op+0x1b/0x20 [ 58.936310] ?
[Kernel-packages] [Bug 2033122] Re: Request backport of xen timekeeping performance improvements
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2033122 Title: Request backport of xen timekeeping performance improvements Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Users, especially those on EC2, are encouraged to select tsc as their default clocksource. However, this requires manual tuning of the operating system. Kvm can determine if it safe to use the tsc, and will default to that instead of its pvclock when appropriate. This requests a backport of patch does the same for Xen instances. If appropriate, it's fine if this is applied to only the linux-aws branches. Not all Xen EC2 instances advertise explicit nomigrate support, however, on those that do we'll select tsc by default. On the subset of hosts where this is advertised, users will safely default to the more performant clocksource. [Impact] Xen instances default to the xen clocksource which has been documented to be slower. This is required for instances where the tsc is not safe to use, or the guest is subject to migration. On some platforms the performance impact can be high, and users are encouraged to select the tsc when appropriate. Instead of leaving up to users to figure this out by reading a variety of different documents, pick the fast clocksource when it can be determined to be safe to do so. [Backport] Clean cherry pick. No conflicts applying to 5.15 or 6.2. [Test] Booted EC2 xen instances with and without this patch and validated that on those that properly advertised the required criteria via cpuid, that the clocksource defaulted to tsc instead of xen. [Potential Regression] Potential is low, since only absurd configurations could lead to a problem. If this is considered risky, it can be applied to only linux-aws where the documented guidance is for users to enable tsc as the clocksource on Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034479] Re: Fix suspend hang on Lenovo workstation
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1 and merged by stable update in oem-6.1, SRU for Jammy and Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031333] Re: Need to get fine-grained control for FAN(TFN) Participant.
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- 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/2031333 Title: Need to get fine-grained control for FAN(TFN) Participant. Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: This is a public version of the following bugs: https://bugs.launchpad.net/bugs/1987597 https://bugs.launchpad.net/bugs/2027754 [Feature Description] We need Fine-grained Control of TFN participant for enabling active 2 policy in Linux/chrome. Currently, The kernel has provided __FPS table and cur__state to adjust the fan level as per _FPS table . But there is no option to read *_FIF (Fan Information) and _FST (Fan Status).* Once the fine-grained control is enabled, we should be able to the set the control value from 0-100 through Arg0 of _FSL (Fan Set Level). *_FST (Fan Status)* should report current running RPM and control value of the FAN(TFN). please refer ACPI spec for more detail. [https://uefi.org/specs/ACPI/6.4/11_Thermal_Management/fan- device.html] [HW/SW Information] Hardware: Alder Lake Target Release: 22.04 Target Kernel: 5.15 Merged for 5.18-rc1 f1197343f077 ACPI: fan: Add additional attributes for fine grain control bea2d9868ef5 ACPI: fan: Properly handle fine grain control d445571fa369 ACPI: fan: Optimize struct acpi_fan_fif 00ae053a0533 ACPI: fan: Separate file for attributes creation Platform-independent [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) Actually also tried setting kernel.io_uring_disabled=2 and checking that neither (privileged or unprivileged worked). Then testing setting it back to 0. Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and that it worked for group 1000, then set it to 1001 and verified that it didn't work anymore for group 1000. [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035163] Re: Avoid address overwrite in kernel_connect
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux-gkeop package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Status in linux-gkeop source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035123] Re: scripts/pahole-flags.sh change return to exit 0
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2035123
Title:
scripts/pahole-flags.sh change return to exit 0
Status in linux package in Ubuntu:
Fix Released
Status in linux-bluefield package in Ubuntu:
Triaged
Status in linux source package in Jammy:
Fix Released
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2035123
[Impact]
When building the Jammy linux-bluefield kernel tree on a system
without pahole installed, the following warning is emitted:
./scripts/pahole-flags.sh: line 7: return: can only `return' from a
function or sourced script
scripts/pahole-flags.sh attempts to return from an if statement that
is not within a function, and generates a warning.
The fix is straightforward, changing return to an exit 0.
--- a/scripts/pahole-flags.sh
+++ b/scripts/pahole-flags.sh
@@ -4,7 +4,7 @@
extra_paholeopt=
if ! [ -x "$(command -v ${PAHOLE})" ]; then
- return
+ exit 0
fi
[Testcase]
Clone the linux-bluefield kernel tree and build it on a arm64 system without
pahole installed.
A test kernel is available with the fix applied in:
https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test
Both linux-bluefield and ubuntu-jammy build correctly.
[Fix]
This was fixed by Linus Torvalds in the following merge commit:
commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Merge: bfc484fe6abb 84882cf72cd7
Author: Linus Torvalds
Date: Tue Nov 2 06:20:58 2021 -0700
Subject: Merge tag 'net-next-for-5.16' of
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Note, the original commit does not have the fix included:
commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
Author: Jiri Olsa
Date: Fri Oct 29 14:57:29 2021 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8
The Ubuntu kernel cherry-picked the original commit and did not pick up the
silent fix made in the merge commit. Submitting the silent fix as a SAUCE
patch
with changelog describing the change.
Note: I know SAUCE patches are bad, but in this scenario, to revert
the initial commit and re-apply the fixed version would require us to
revert two additional dependency commits, making six patches to
review, vs, a one line change in a SAUCE commit that has a real
changelog entry.
[Where problems could occur]
The Ubuntu kernel is built with pahole enabled, and requires pahole to
be installed as a build dependency. It is extremely unlikely that any
users are disabling pahole at build time, apart from linux-bluefield
engineers.
If a regression were to occur, engineers would see errors during build
time about scripts/pahole-flags.sh not executing properly.
[Other info]
Linus remarked about the issue in the following lkml discussion:
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/
This was silently Incorporated into the linux-stable commit:
commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
From: Jiri Olsa
Date: Sun, 4 Sep 2022 15:19:00 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035123/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035166] Re: NULL Pointer Dereference During KVM MMU Page Invalidation
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035166 Title: NULL Pointer Dereference During KVM MMU Page Invalidation Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the cause. It's worth noting that the current kernel has replaced the
[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037403] Re: PCI BARs larger than 128GB are disabled
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2037403 Title: PCI BARs larger than 128GB are disabled Status in linux package in Ubuntu: Incomplete Status in linux-bluefield package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in linux-bluefield source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] Current linux-bluefield kernel reports that PCI BARs larger than 128GB are disabled. Increase the maximum PCI BAR size from 128GB to 8TB for future expansion. [Test Plan] Use updated kernel with PCI device with PCI BARs larger than 128GB. [Where problems could occur] No potential problems are expected. [Other Info] Testing has been provided by the customer. This patch is a cherry-pick from the upstream 5.18 kernel. It is intended for linux-bluefield kernel re-spin but it may be also suitable for the generic kernel (separate submission). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
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/2035181
Title:
Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
[Kernel-packages] [Bug 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035971
Title:
linux tools packages for derived kernels refuse to install
simultaneously due to libcpupower name collision
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[ Impact ]
* Multiple kernel flavours are conflicting with each on .deb / file
level via their tools packages
* Resolve the conflicting private libcpupower.so by statically
linking it into the only C binary that uses said library in the linux-
tools
[ Test Plan ]
* co-install tools packages from multiple kernel flavours of the same
major version and abi, it should be successful
[ Where problems could occur ]
* If one tries really hard to find the private location of
libcpupower.so and dlopen it by ever changing abi name, that will not
be possible, until the separate bug report is fixed to introduce the
public stable libcpupower.so.1 which so far ubuntu has never yet
provided.
[ Other Info ]
* original bug report
Taking linux-kvm and linux-gcp for example:
$ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103384 2023-07-25 20:00
./usr/lib/libcpupower.so.6.2.0-1011
$ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103392 2023-08-16 15:08
./usr/lib/libcpupower.so.6.2.0-1011
linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
utilities, and yet files of the same full path cannot be installed
from two distinct debian packages, which follows we won't be able to
install two linux-tools packages of two different derived kernels on
the same system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
Uname: Linux 6.5.0-9004-generic x86_64
NonfreeKernelModules: zfs wl
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vicamo 6331 F wireplumber
/dev/snd/controlC0: vicamo 6331 F wireplumber
/dev/snd/seq:vicamo 6315 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Sep 14 23:31:16 2023
InstallationDate: Installed on 2022-04-10 (522 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9004-generic N/A
linux-backports-modules-6.5.0-9004-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 432.60.3.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias:
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
dmi.product.family: Mac
dmi.product.name: MacBookPro11,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ Lunar, $ git push l_cbd Enumerating objects: 9, done. Counting objects: 100% (9/9), done. Delta compression using up to 8 threads Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done. Total 5 (delta 4), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-915de03d6ecf-V1nm remote: * 9/9 workers busy, 0 builds queued remote: 2023-11-20 16:00:11 kobako-lunar-915de03d6ecf-V1nm/amd64/BUILD-OK remote:
[Kernel-packages] [Bug 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2037513 Title: HP ProBook 450 G8 Notebook fail to wifi test Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-signed-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Bug description: I'm reviewing the SRU test result on this machine. I found that this machine always fails to wifi test and also pop out a lot of error message in dmesg. It's not a regression, since according to previous test run it has failed already. Just because we missed reviewing it for a while. The journal log is attach, please check further hardware informations at https://certification.canonical.com/hardware/202106-29176/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 27 15:47:37 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00 InstallationDate: Installed on 2023-09-25 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220621-04:14 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- linux-mtk'. If the problem still exists, change the tag 'verification- needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork 0
[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055473] Re: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU
** Description changed: + Issue found on J-gcp-6.5.0-1015.15~22.04.1 and M-gcp-6.5.0-1015.15 in + cycle sru-20240205 + + And can be reproduced with generic kernel on GCP cloud. + + This is not a regression but something emerges after the pmtu.sh result + parsing logic update, which landed via stable update in sru-20240205 + cycle (bug 2043198) + + Dive into test history, we can see this failure all the way back to + sru-20231030 with M-6.5.0-1010.10 on GCP cloud. + 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) ** Tags added: jammy sru-s20231030 ** Tags added: gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055473 Title: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: Issue found on J-gcp-6.5.0-1015.15~22.04.1 and M-gcp-6.5.0-1015.15 in cycle sru-20240205 And can be reproduced with generic kernel on GCP cloud. This is not a regression but something emerges after the pmtu.sh result parsing logic update, which landed via stable update in sru-20240205 cycle (bug 2043198) Dive into test history, we can see this failure all the way back to sru-20231030 with M-6.5.0-1010.10 on GCP cloud. 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055473] Re: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU
** Summary changed: - mtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU + pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU ** Tags added: 6.5 mantic sru-20240108 ubuntu-kselftests-net ** Tags removed: sru-20240108 ** Tags added: sru-20240205 -- 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/2055473 Title: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
Quick update, this was still happening with Jammy, and it it still happening with Noble. The pattern I identified for 90% chances of hanging on wake up: - boot or wake up from suspend to RAM - use the laptop for a short time (short being less than a couple hours) - suspend to RAM -- 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/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in linux package in Ubuntu: Confirmed Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. -- EDIT -- EDIT: This is actually not true. The laptop will eventually reboot by itself, and when this happens quickly enough after I have hit SysRq keys, it can be mistakenly taken for a working SysRq request. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). -- EDIT -- If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kernel (tested
[Kernel-packages] [Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
** Tags removed: verification-needed-jammy-linux-ibm-gt-fips ** Tags added: verification-done-jammy-linux-ibm-gt-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
** Tags removed: verification-needed-jammy-linux-ibm-gt-fips ** Tags added: verification-done-jammy-linux-ibm-gt-fips -- 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 Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux 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 2055483] [NEW] net:pmtu.sh ubuntu_kselftests_net fails vxlan test
Public bug reported: net:pmtu.sh fails on openstack cpu2 lowlatency-64k ubuntu_kselftests_net. It fails with: DEBUG| [stdout] # TEST: IPv4, bridged geneve6: PMTU exceptions [FAIL] DEBUG| [stdout] # File size 1001302 mismatches exepcted value in locally bridged vxlan test I've included a file containing the console output as well. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "pmtu.sh console output" https://bugs.launchpad.net/bugs/2055483/+attachment/5750832/+files/pmtu_bug_output.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055483 Title: net:pmtu.sh ubuntu_kselftests_net fails vxlan test Status in linux package in Ubuntu: New Bug description: net:pmtu.sh fails on openstack cpu2 lowlatency-64k ubuntu_kselftests_net. It fails with: DEBUG| [stdout] # TEST: IPv4, bridged geneve6: PMTU exceptions [FAIL] DEBUG| [stdout] # File size 1001302 mismatches exepcted value in locally bridged vxlan test I've included a file containing the console output as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055473] [NEW] mtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU
Public bug reported: 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Attachment added: "rt.log" https://bugs.launchpad.net/bugs/2055473/+attachment/5750793/+files/rt.log ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055473 Title: mtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
