[Kernel-packages] [Bug 2056227] Re: KVM: arm64: softlockups in stage2_apply_range
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Krister Johansen (kmjohansen) -- 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/2056227 Title: KVM: arm64: softlockups in stage2_apply_range Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Tearing down kvm VMs on arm64 can cause softlockups to appear on console. When terminating VMs with > 100Gb of memory and 4k pages, the memory unmap times often exceed 20 seconds, which can trigger the softlockup detector. Portions of the unmap path also have interrupts disabled while tlb invalidation instructions run, which can further contribute to latency problems. My team has observed networking latency problems if the cpu where the teardown is occurring is also mapped to handle a NIC interrupt. Fortunately, a solution has been in place since Linux 6.1. A small pair of patches modify stage2_apply_range to operate on smaller memory ranges before performing a cond_resched. With these patches applied, softlockups are no longer observed when tearing down VMs with large amounts of memory. Although I also submitted the patches to 5.15 LTS (link to LTS submission in "Backport" section), I'd appreciate it if Ubuntu were willing to take this submission in parallel since the impact has left us unable to utilize arm64 for kvm until we can either migrate our hypervisors to hugepages, pick up this fix, or some combination of the two. [Backport] Backport the following fixes from linux 6.1: 3b5c082bbf KVM: arm64: Work out supported block level at compile time 5994bc9e05 KVM: arm64: Limit stage2_apply_range() batch size to largest block The fix is in 5994bc9e05 and 3b5c082bbf is a dependency that was submitted as part of the series. The original submission is here: https://lore.kernel.org/all/20221007234151.461779-1-oliver.up...@linux.dev/ I've also submitted the patches to 5.15 LTS here: https://lore.kernel.org/stable/cover.1709665227.git.k...@templeofstupid.com/ Both fixes cherry picked cleanly and there were no conflicts. [Test] Executed the test from 5994bc9e05 as well as my own run of kvm_page_table_test on a VM with 4k pages and a memory size > 100Gb. Without the patches, softlockups were observed in both tests. With the patches applied, the tests ran without incident. This was tested against both LTS 5.15.150 and linux-aws-5.15.0-1055. [Potential Regression] Regression potential is low. These patches have been present in Linux since 6.1 and appear to have needed no further maintenance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056403] Re: Mantic update: upstream stable patchset 2024-03-07
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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/2056403 Title: Mantic update: upstream stable patchset 2024-03-07 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-03-07 Ported from the following upstream stable releases: v6.1.75, v6.6.14 from git://git.kernel.org/ x86/lib: Fix overflow when counting digits x86/mce/inject: Clear test status value EDAC/thunderx: Fix possible out-of-bounds string access powerpc: add crtsavres.o to always-y instead of extra-y powerpc/44x: select I2C for CURRITUCK powerpc/pseries/memhp: Fix access beyond end of drmem array selftests/powerpc: Fix error handling in FPU/VMX preemption tests powerpc/powernv: Add a null pointer check to scom_debug_init_one() powerpc/powernv: Add a null pointer check in opal_event_init() powerpc/powernv: Add a null pointer check in opal_powercap_init() powerpc/imc-pmu: Add a null pointer check in update_events_in_group() spi: spi-zynqmp-gqspi: fix driver kconfig dependencies mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response ACPI: video: check for error while searching for backlight device parent ACPI: LPIT: Avoid u32 multiplication overflow platform/x86/intel/vsec: Fix xa_alloc memory leak cpufreq: scmi: process the result of devm_of_clk_add_hw_provider() calipso: fix memory leak in netlbl_calipso_add_pass() efivarfs: force RO when remounting if SetVariable is not supported spi: sh-msiof: Enforce fixed DTDL for R-Car H3 ACPI: LPSS: Fix the fractional clock divider flags ACPI: extlog: Clear Extended Error Log status when RAS_CEC handled the error kunit: debugfs: Fix unchecked dereference in debugfs_print_results() mtd: Fix gluebi NULL pointer dereference caused by ftl notifier selinux: Fix error priority for bind with AF_UNSPEC on PF_INET6 socket crypto: virtio - Handle dataq logic with tasklet crypto: sa2ul - Return crypto_aead_setkey to transfer the error crypto: ccp - fix memleak in ccp_init_dm_workarea crypto: af_alg - Disallow multiple in-flight AIO requests crypto: safexcel - Add error handling for dma_map_sg() calls crypto: sahara - remove FLAGS_NEW_KEY logic crypto: sahara - fix cbc selftest failure crypto: sahara - fix ahash selftest failure crypto: sahara - fix processing requests with cryptlen < sg->length crypto: sahara - fix error handling in sahara_hw_descriptor_create() crypto: hisilicon/qm - save capability registers in qm init process crypto: hisilicon/zip - add zip comp high perf mode configuration crypto: hisilicon/qm - add a function to set qm algs crypto: hisilicon/hpre - save capability registers in probe process crypto: hisilicon/sec2 - save capability registers in probe process crypto: hisilicon/zip - save capability registers in probe process pstore: ram_core: fix possible overflow in persistent_ram_init_ecc() erofs: fix memory leak on short-lived bounced pages fs: indicate request originates from old mount API gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump crypto: virtio - Wait for tasklet to complete on device remove crypto: sahara - avoid skcipher fallback code duplication crypto: sahara - handle zero-length aes requests crypto: sahara - fix ahash reqsize crypto: sahara - fix wait_for_completion_timeout() error handling crypto: sahara - improve error handling in sahara_sha_process() crypto: sahara - fix processing hash requests with req->nbytes < sg->length crypto: sahara - do not resize req->src when doing hash operations crypto: scomp - fix req->dst buffer overflow csky: fix arch_jump_label_transform_static override blocklayoutdriver: Fix reference leak of pnfs_device_node NFSv4.1/pnfs: Ensure we handle the error NFS4ERR_RETURNCONFLICT SUNRPC: fix _xprt_switch_find_current_entry logic pNFS: Fix the pnfs block driver's calculation of layoutget size wifi: plfxlc: check for allocation failure in plfxlc_usb_wreq_async() wifi: rtw88: fix RX filter in FIF_ALLMULTI flag bpf, lpm: Fix check prefixlen before walking trie bpf: Add crosstask check to __bpf_get_stack wifi: ath11k: Defer on rproc_get failure wifi: libertas: stop selecting wext ARM: dts:
[Kernel-packages] [Bug 2042363] Comment bridged from LTC Bugzilla
--- Comment From david_pa...@uk.ibm.com 2024-03-11 03:51 EDT--- Has there been any further progress on this issue from the Linux NFS development team ? The AIX NFS development team will not progress the problem from their side until they understand why the BAD_SEQID errors has been returned from the Linux NFSv4 server. -- 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/2042363 Title: AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 server Status in linux package in Ubuntu: New Bug description: ---Problem Description--- AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl(). NFS server is Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not appear to affect other combinations of NFS client (including AIX 7.2) with this NFS server. The AIX team have indicated that the cause of the EIO is triggered by the NFS server returning a BAD_SEQID error which leads to the AIX NFS client incorrectly zeroing the stateid, which then leads to the NFS server returning a BAD_STATEID error and the NFS client then returns the EIO error. The AIX team would like to understand why the BAD_SEQID has been returned. ---uname output--- Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 2.30GHz ---Steps to Reproduce--- We cannot offer a simple way to recreate the problem as it involves IBM MQ running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 storage. However, we can provide any requested trace or dumps from any or all of the involved machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
Verified that the GAP/CONN/CPUP/BV-05-C could pass on 5.15.0-102.112 kernel using the following procedure: 1. On PTS, switch to the LE-only dongle 2. On the IUT, run bluetoothctl 3. On PTS, start the test case. 4. On the IUT, in the bluetoothctl shell, start scanning by entering "scan on". 5. When PTS asks for making LE connection, initiate the connection from bluetoothctl shell by "connect " 6. PTS would then ask IUT to initiate disconnection. On the bluetoothctl, enter "disconnect " ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052005 Title: Validate connection interval to pass Bluetooth Test Suite Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified. [Fix] Validate max connection interval to pass test case "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid Parameters Central Responder'" [Test] Run the test suite. With the patch applied the case is passed. [Where problems could occur] If any device requires setting a wrong interval to function properly, this might affect those devices in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056383] Re: Audio turned to dummy output from 5.15.0-1049-intel-iotg to 5.15.0-1050
** Also affects: linux-intel-iotg-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2056383 Title: Audio turned to dummy output from 5.15.0-1049-intel-iotg to 5.15.0-1050 Status in linux-intel-iotg-5.15 package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: [Summary] After updated kernel 5.15.0-1049-intel-iotg to 5.15.0-1050 Sound output device turned to dummy output. [Steps to reproduce] 1. Install OS image to DUT. 2. Update package from repository(include proposed) 3. Upgrade package from repository(include proposed) 4. After upgrade successfully, reboot system. 5. Audio didn't work functionally. [Expected result] Audio works normally. [Actual result] Audio device became dummy output. Sound cards are disappeared. [Failure rate] 100% Tester comments --- Audio works fine at kernel 5.15.0-1049-intel-iotg [Additional information] CID: 202109-29435 Image: ubuntu-22.04-desktop-amd64+intel-iot.iso system-manufacturer: Aaeon system-product-name: UPX-TGL01 CPU: Intel(R) Celeron(R) 6305E @ 1.80GHz kernel-version: 6.1.0-1028-oem [Stage] Issue reported. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-1050.56-intel-iotg 5.15.143 Uname: Linux 5.15.0-1050-intel-iotg x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 6 11:45:08 2024 InstallationDate: Installed on 2024-03-05 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: UPX-TGL01 dmi.board.vendor: AAEON dmi.board.version: V1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: AAEON dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd05/14/2021:br5.19:svnAAEON:pnUPX-TGL01:pvrV1.0:rvnAAEON:rnUPX-TGL01:rvrV1.0:cvnAAEON:ct3:cvrV1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: UPX-TGL01 dmi.product.sku: Default string dmi.product.version: V1.0 dmi.sys.vendor: AAEON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg-5.15/+bug/2056383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
