[Kernel-packages] [Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
Thanks for testing this! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] This is caused by commit 08335308 "KVM: x86: check PIR even for vCPUs with disabled APICv", this patch needs 7e1901f6c "KVM: VMX: prepare sync_pir_to_irr for running with APICv disabled" otherwise if APICv is disabled in this vcpu it will trigger warning messages in vmx_sync_pir_to_irr() of vmx.c: WARN_ON(!vcpu->arch.apicv_active); With warnings like: [ cut here ] WARNING: CPU: 13 PID: 6997 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] ? xfer_to_guest_mode_work+0xe2/0x110 Modules linked in: vhost_net vhost vhost_iotlb tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds ioatdma rapl intel_cstate efi_pstore ipmi_si mei_me mei mac_hid acpi_pad vcpu_run+0x4d/0x220 [kvm] acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr 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 raid0 multipath linear hid_generic usbhid hid mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect sysimgblt ghash_clmulni_intel fb_sys_fops ixgbe cec aesni_intel rc_core crypto_simd xfrm_algo cryptd drm ahci dca i2c_i801 xhci_pci mdio libahci i2c_smbus lpc_ich xhci_pci_renesas wmi CPU: 13 PID: 6997 Comm: qemu-system-x86 Tainted: G W I 5.13.0-39-generic #44-Ubuntu Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.1008.031920151331 03/19/2015 kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] RIP: 0010:vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] Code: e8 47 f5 18 00 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 74 dc 48 8b 55 f0 65 48 2b 14 25 28 00 00 00 75 1d 48 8b 5d f8 c9 c3 <0f> 0b eb 87 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb RSP: 0018:ae4d8d107c98 EFLAGS: 00010046 RAX: RBX: 99c552942640 RCX: 99c5043a72f0 RDX: 99c552942640 RSI: 0001 RDI: 99c552942640 RBP: ae4d8d107cb0 R08: 99c86f6a7140 R09: 00027100 R10: 4228 R11: 000a R12: 99c552942640 R13: R14: ae4d8d1a63e0 R15: 99c552942640 FS: 7f6ae9be7640() GS:99c86f68() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: CR3: 00010b8a6006 CR4: 001726e0 Call Trace: kvm_vcpu_ioctl+0x243/0x5e0 [kvm] vcpu_enter_guest+0x383/0xf50 [kvm] ? xfer_to_guest_mode_work+0xe2/0x110 ? kvm_vm_ioctl+0x364/0x730 [kvm] ? __fget_files+0x86/0xc0 vcpu_run+0x4d/0x220 [kvm] __x64_sys_ioctl+0x91/0xc0 do_syscall_64+0x61/0xb0 ? fput+0x13/0x20 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6aebce1a2b Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 f3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6ae8ffe3f8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: ae80 RCX: 7f6aebce1a2b RDX: RSI: ae80 RDI: 000c RBP: 557d3b429b90 R08: 557d3a4ebff0 R09: kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] R10: 0001 R11: 0246 R12: R13: 0001 R14: 3000 R15: ---[ end trace 5b722d71a78069b1 ]--- This warning message will be flooding in system log files and eventually eat up all the disk space then crash the server. This issue will gone by either reverting it or adding the fixes below. Reference: https://patchwork.kernel.org/project/kvm/patch/2028072531.1534938-1-pbonz...@redhat.com/ [Fixes] * 0b8f11737 KVM: Add infrastructure and macro to mark VM as bugged * 673692735 KVM: x86: Use KVM_BUG/KVM_BUG_ON to handle bugs that are fatal to the VM * 7e1901f6c KVM: VMX: prepare sync_pir_to_irr for
[Kernel-packages] [Bug 1956098] Re: Kernel 5.0.13.* not working properly on Asus R542 machine
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1956098 Title: Kernel 5.0.13.* not working properly on Asus R542 machine Status in linux package in Ubuntu: Expired Bug description: with auto upgrade of kernel to 5.0.13.*, touchpad and wifi is not working properly on Asus R542U, the machine has out of box hardware installed plus 1 160 GB samsung evo SSD and 8 GB additional RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956098/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Description changed: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. - [Workaround] + [Workarounds] + * Always log into a Xorg session and if corruption occurs then type: + Alt+F2, R, Enter + + * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in
[Kernel-packages] [Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)
Mark unsupported series as Won't fix. ** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Won't Fix ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1938964 Title: icmp_redirect from selftests fails on F/kvm (unary operator expected) Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Bug description: [Impact] If any sub-test in this icmp_redirect.sh is failing but not expected to fail. The script will complain: ./icmp_redirect.sh: line 72: [: 1: unary operator expected This is because when the sub-test is not expected to fail, we won't pass any value for the xfail local variable in log_test() and thus it's empty. Fix this by passing 0 as the 4th variable to log_test() for non-xfail cases. This issue can be found on our KVM kernel with SRU tests, they're failing because of missing some kernel configs. [Fix] * 39d8622c72 "selftests: icmp_redirect: pass xfail=0 to log_test()" This patch can be cherry-picked into all of the affected kernels. [Test Plan] Run the patched icmp_redirect.sh script with a KVM kernel (e.g. F/kvm), and this "unary operator expected" error message should no longer exist. [Where problems could occur] Change limited to test script, it won't have any impact to real kernel function. And this issue is most likely specific to KVM kernels. == Original Bug Report == icmp_redirect from selftect is failing on F/kvm 5.4.0-1045.47 # selftests: net: icmp_redirect.sh # # ### # Legacy routing # ### # # TEST: IPv4: redirect exception [ OK ] # TEST: IPv6: redirect exception [ OK ] # TEST: IPv4: redirect exception plus mtu [ OK ] # TEST: IPv6: redirect exception plus mtu [ OK ] # TEST: IPv4: routing reset [ OK ] # TEST: IPv6: routing reset [ OK ] # TEST: IPv4: mtu exception [ OK ] # TEST: IPv6: mtu exception [ OK ] # TEST: IPv4: mtu exception plus redirect [ OK ] # TEST: IPv6: mtu exception plus redirect [XFAIL] # # ### # Legacy routing with VRF # ### # # Error: Unknown device type. # Cannot find device "red" # Error: argument "red" is wrong: Invalid VRF # # Error: argument "red" is wrong: Invalid VRF # # Cannot find device "red" # Cannot find device "red" # Error: argument "red" is wrong: Not a valid VRF name # # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception plus mtu [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception plus mtu [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: routing reset [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: routing reset [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: mtu exception [FAIL] # Error: argument "red" is wrong: Invalid VRF # #
[Kernel-packages] [Bug 1968902] Re: ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1968902
Title:
ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
Status in ubuntu-kernel-tests:
New
Status in linux-oracle package in Ubuntu:
In Progress
Status in linux-oracle source package in Focal:
In Progress
Status in linux-oracle source package in Impish:
In Progress
Bug description:
The ARM64_SW_TTBR0_PAN was disabled by commit:
c25f2bf469b3 ("UBUNTU: [config] oracle: Bring-up for arm64 support")
This config option is enabled on all other Ubuntu kernels and should
be enabled for the Oracle kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968902/+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 1966143] Re: Periodic glitch in LogiTech H390 headphone audio
*** This bug is a duplicate of bug 1966066 *** https://bugs.launchpad.net/bugs/1966066 Mark it as dup for bug 1966066, please feel free to unmark it if you think this is incorrect. ** This bug has been marked a duplicate of bug 1966066 audio from external sound card is distorted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966143 Title: Periodic glitch in LogiTech H390 headphone audio Status in linux-signed-hwe-5.13 package in Ubuntu: Incomplete Bug description: When running kernel version 5.13.0-37-generic the audio output through my Logitech H390 headphones has a periodic "glitch" every few seconds - noticable in Google Meetings and Youtube - its very distracting, its not exactly a scratch or pop; it's more like a really bad reception mobile phone call "robot voice" noise but lasts only for a moment, then maybe 30 seconds later occurs again, seems to be regularly periodic. The problem isn't present on 5.13.0-35-generic and doesn't effect my external speaker audio output just the headphones so it's not a network issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 24 10:26:12 2022 InstallationDate: Installed on 2018-02-17 (1495 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966143/+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 1968016] Re: Use kernel-testing repo from launchpad for ADT tests
ADT test started correctly. ** Tags removed: verification-needed-focal verification-needed-impish ** Tags added: verification-done-focal verification-done-impish -- 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/1968016 Title: Use kernel-testing repo from launchpad for ADT tests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux-oem-5.14 source package in Trusty: Invalid Status in linux-oem-5.17 source package in Trusty: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux-oem-5.17 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux-oem-5.17 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: In ADT tests, we are still using the kernel-testing repo from kernel.ubuntu.com, it should be migrated to launchpad instead to align with our other testing repos. For autotest-client-tests repo change, it will needs to be handled in the kernel-testing repo directly, see bug 1968257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968016/+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 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
Hi, Jeff Is there any updates? is there a fixed kernel for us test? -- 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/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+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 1969231] Re: Touch pad not working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1969231 Title: Touch pad not working Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Touch pad not working after installing Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 19:52:29 2022 InstallationDate: Installed on 2022-03-18 (27 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1969231/+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 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))
Focal 5.4.0-110.124 with node spitfire: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test' BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.8hYc1dgvp4 -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd /tmp/tmp.VW7zzXkBfL enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 filter = vmx_ldtr_test, test = test_vmx_feature_control filter = vmx_ldtr_test, test = test_vmxon filter = vmx_ldtr_test, test = test_vmptrld filter = vmx_ldtr_test, test = test_vmclear filter = vmx_ldtr_test, test = test_vmptrst filter = vmx_ldtr_test, test = test_vmwrite_vmread filter = vmx_ldtr_test, test = test_vmcs_high filter = vmx_ldtr_test, test = test_vmcs_lifecycle filter = vmx_ldtr_test, test = test_vmx_caps filter = vmx_ldtr_test, test = test_vmread_flags_touch filter = vmx_ldtr_test, test = test_vmwrite_flags_touch filter = vmx_ldtr_test, test = null filter = vmx_ldtr_test, test = vmenter filter = vmx_ldtr_test, test = preemption timer filter = vmx_ldtr_test, test = control field PAT filter = vmx_ldtr_test, test = control field EFER filter = vmx_ldtr_test, test = CR shadowing filter = vmx_ldtr_test, test = I/O bitmap filter = vmx_ldtr_test, test = instruction intercept filter = vmx_ldtr_test, test = EPT A/D disabled filter = vmx_ldtr_test, test = EPT A/D enabled filter = vmx_ldtr_test, test = PML filter = vmx_ldtr_test, test = interrupt filter = vmx_ldtr_test, test = nmi_hlt filter = vmx_ldtr_test, test = debug controls filter = vmx_ldtr_test, test = MSR switch filter = vmx_ldtr_test, test = vmmcall filter = vmx_ldtr_test, test = disable RDTSCP filter = vmx_ldtr_test, test = int3 filter = vmx_ldtr_test, test = into filter = vmx_ldtr_test, test = exit_monitor_from_l2_test filter = vmx_ldtr_test, test = invalid_msr filter = vmx_ldtr_test, test = v2_null_test filter = vmx_ldtr_test, test = v2_multiple_entries_test filter = vmx_ldtr_test, test = fixture_test_case1 filter = vmx_ldtr_test, test = fixture_test_case2 filter = vmx_ldtr_test, test = invvpid_test filter = vmx_ldtr_test, test = vmx_controls_test filter = vmx_ldtr_test, test = vmx_host_state_area_test filter = vmx_ldtr_test, test = vmx_guest_state_area_test filter = vmx_ldtr_test, test = vmentry_movss_shadow_test filter = vmx_ldtr_test, test = vmentry_unrestricted_guest_test filter = vmx_ldtr_test, test = vmx_eoi_bitmap_ioapic_scan_test filter = vmx_ldtr_test, test = vmx_hlt_with_rvi_test filter = vmx_ldtr_test, test = apic_reg_virt_test filter = vmx_ldtr_test, test = virt_x2apic_mode_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_thread_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_tpr_threshold_test filter = vmx_ldtr_test, test = vmx_init_signal_test filter = vmx_ldtr_test, test = vmx_sipi_signal_test filter = vmx_ldtr_test, test = vmx_vmcs_shadow_test filter = vmx_ldtr_test, test = vmx_ldtr_test Test suite: vmx_ldtr_test PASS: Expected 18 for L2 LDTR selector (got 18) PASS: Expected 0 for L1 LDTR selector (got 0) filter = vmx_ldtr_test, test = vmx_cr_load_test filter = vmx_ldtr_test, test = vmx_cr4_osxsave_test filter = vmx_ldtr_test, test = vmx_nm_test filter = vmx_ldtr_test, test = vmx_db_test filter = vmx_ldtr_test, test = vmx_nmi_window_test filter = vmx_ldtr_test, test = vmx_intr_window_test filter = vmx_ldtr_test, test = vmx_pending_event_test filter = vmx_ldtr_test, test = vmx_pending_event_hlt_test filter = vmx_ldtr_test, test = vmx_store_tsc_test filter = vmx_ldtr_test, test = vmx_preemption_timer_zero_test filter = vmx_ldtr_test, test = vmx_preemption_timer_tf_test filter = vmx_ldtr_test, test = vmx_preemption_timer_expiry_test filter = vmx_ldtr_test, test = ept_access_test_not_present filter = vmx_ldtr_test, test = ept_access_test_read_only filter = vmx_ldtr_test, test = ept_access_test_write_only filter = vmx_ldtr_test, test = ept_access_test_read_write filter = vmx_ldtr_test, test = ept_access_test_execute_only filter = vmx_ldtr_test, test = ept_access_test_read_execute filter = vmx_ldtr_test, test = ept_access_test_write_execute filter = vmx_ldtr_test, test = ept_access_test_read_write_execute filter = vmx_ldtr_test, test = ept_access_test_reserved_bits filter = vmx_ldtr_test, test = ept_access_test_ignored_bits filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_disabled filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_enabled filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_disabled filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_enabled filter = vmx_ldtr_test, test = ept_access_test_paddr_read_write filter = vmx_ldtr_test, test =
[Kernel-packages] [Bug 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))
Impish 5.13 with node vought: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test' BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.WvqHvN1Mpk -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd /tmp/tmp.gTntUdwZWg enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 filter = vmx_ldtr_test, test = test_vmx_feature_control filter = vmx_ldtr_test, test = test_vmxon filter = vmx_ldtr_test, test = test_vmptrld filter = vmx_ldtr_test, test = test_vmclear filter = vmx_ldtr_test, test = test_vmptrst filter = vmx_ldtr_test, test = test_vmwrite_vmread filter = vmx_ldtr_test, test = test_vmcs_high filter = vmx_ldtr_test, test = test_vmcs_lifecycle filter = vmx_ldtr_test, test = test_vmx_caps filter = vmx_ldtr_test, test = test_vmread_flags_touch filter = vmx_ldtr_test, test = test_vmwrite_flags_touch filter = vmx_ldtr_test, test = null filter = vmx_ldtr_test, test = vmenter filter = vmx_ldtr_test, test = preemption timer filter = vmx_ldtr_test, test = control field PAT filter = vmx_ldtr_test, test = control field EFER filter = vmx_ldtr_test, test = CR shadowing filter = vmx_ldtr_test, test = I/O bitmap filter = vmx_ldtr_test, test = instruction intercept filter = vmx_ldtr_test, test = EPT A/D disabled filter = vmx_ldtr_test, test = EPT A/D enabled filter = vmx_ldtr_test, test = PML filter = vmx_ldtr_test, test = interrupt filter = vmx_ldtr_test, test = nmi_hlt filter = vmx_ldtr_test, test = debug controls filter = vmx_ldtr_test, test = MSR switch filter = vmx_ldtr_test, test = vmmcall filter = vmx_ldtr_test, test = disable RDTSCP filter = vmx_ldtr_test, test = int3 filter = vmx_ldtr_test, test = into filter = vmx_ldtr_test, test = exit_monitor_from_l2_test filter = vmx_ldtr_test, test = invalid_msr filter = vmx_ldtr_test, test = v2_null_test filter = vmx_ldtr_test, test = v2_multiple_entries_test filter = vmx_ldtr_test, test = fixture_test_case1 filter = vmx_ldtr_test, test = fixture_test_case2 filter = vmx_ldtr_test, test = invvpid_test filter = vmx_ldtr_test, test = vmx_controls_test filter = vmx_ldtr_test, test = vmx_host_state_area_test filter = vmx_ldtr_test, test = vmx_guest_state_area_test filter = vmx_ldtr_test, test = vmentry_movss_shadow_test filter = vmx_ldtr_test, test = vmentry_unrestricted_guest_test filter = vmx_ldtr_test, test = vmx_eoi_bitmap_ioapic_scan_test filter = vmx_ldtr_test, test = vmx_hlt_with_rvi_test filter = vmx_ldtr_test, test = apic_reg_virt_test filter = vmx_ldtr_test, test = virt_x2apic_mode_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_thread_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_tpr_threshold_test filter = vmx_ldtr_test, test = vmx_init_signal_test filter = vmx_ldtr_test, test = vmx_sipi_signal_test filter = vmx_ldtr_test, test = vmx_vmcs_shadow_test filter = vmx_ldtr_test, test = vmx_ldtr_test Test suite: vmx_ldtr_test PASS: Expected 18 for L2 LDTR selector (got 18) PASS: Expected 0 for L1 LDTR selector (got 0) filter = vmx_ldtr_test, test = vmx_cr_load_test filter = vmx_ldtr_test, test = vmx_cr4_osxsave_test filter = vmx_ldtr_test, test = vmx_nm_test filter = vmx_ldtr_test, test = vmx_db_test filter = vmx_ldtr_test, test = vmx_nmi_window_test filter = vmx_ldtr_test, test = vmx_intr_window_test filter = vmx_ldtr_test, test = vmx_pending_event_test filter = vmx_ldtr_test, test = vmx_pending_event_hlt_test filter = vmx_ldtr_test, test = vmx_store_tsc_test filter = vmx_ldtr_test, test = vmx_preemption_timer_zero_test filter = vmx_ldtr_test, test = vmx_preemption_timer_tf_test filter = vmx_ldtr_test, test = vmx_preemption_timer_expiry_test filter = vmx_ldtr_test, test = ept_access_test_not_present filter = vmx_ldtr_test, test = ept_access_test_read_only filter = vmx_ldtr_test, test = ept_access_test_write_only filter = vmx_ldtr_test, test = ept_access_test_read_write filter = vmx_ldtr_test, test = ept_access_test_execute_only filter = vmx_ldtr_test, test = ept_access_test_read_execute filter = vmx_ldtr_test, test = ept_access_test_write_execute filter = vmx_ldtr_test, test = ept_access_test_read_write_execute filter = vmx_ldtr_test, test = ept_access_test_reserved_bits filter = vmx_ldtr_test, test = ept_access_test_ignored_bits filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_disabled filter = vmx_ldtr_test, test = ept_access_test_paddr_not_present_ad_enabled filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_disabled filter = vmx_ldtr_test, test = ept_access_test_paddr_read_only_ad_enabled filter = vmx_ldtr_test, test = ept_access_test_paddr_read_write filter = vmx_ldtr_test, test =
[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted
wuwei912 (wuwei912), please give the proposed kernel mentioned in #40 a
try, thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.4, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Triaged Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+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 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
Hi Dries,
Please do not feel a rush to validate the fix, I was more asking just to
confirm personally that your issue has been resolved :)
That message about dropping the fix is more of an empty threat by a bot
than anything else..
So feel free at your earliest convenience to update and confirm that the
new kernel fixes things for you.
Best,
- Luke
--
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/1968210
Title:
USB devices not detected during boot on USB 3.0 hubs
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
There are users with certain intel xHCI controllers that are
experiencing problems with USB devices not being detected at boot.
This is because when the primary roothub is registered, device
enumeration happens before xHC is running and leads to devices not being
detected. This results in the error that looks something like
'usb usb1-port3: couldn't allocate usb_device'.
[Fix]
Register both root hubs along with the secondary hcd for xhci.
This original fix was reverted upstream due to regressions that occured due to
racing that happened when both roothubs were registered simultaneously.
However with those fixes being addressed in commits
("usb: hub: Fix usb enumeration issue due to address0 race")
("usb: hub: Fix locking issues with address0_mutex")
the maintainers have stated that they will be reintroducing this commit.
So lets reintroduce it here to fix the issues that users are
experiencing.
[Test Case]
Confirmed by Chris Chiu that this issue exists on similiar hardware
reported by the users and that reverting these reverts fixes the issue
showing no signs of 'couldn't allocate usb_device' and with USB devices
available after boot.
[Regression Potential]
Should be low now that we carry the fixes that seemed to be caused by
this patch series.
There have been reports by some users using certain intel xHCI controllers
that their USB devices are not being detected after boot again after similar
issues were previously found and fixed. This seems to be related to both [1][2]
with the majority of the discussion on [1] about these problems reoccurring.
This bug report is being made more for documentation of this new regression.
These seems to be due to the patchset for [2] being reverted upstream
due to regressions.
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+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 1966066] Re: audio from external sound card is distorted
No changes with 5.13.0-40-generic #45-Ubuntu SMP Tue Mar 29 14:48:14 UTC
2022 to the issues described here:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-5.13/+bug/1966066/comments/36
Have to resort to the partial fix with the patchend kernel, mentionened here,
still:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/comments/37
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1966066] Re: audio from external sound card is distorted
Confirmed fixed for me on linux-generic-hwe-20.04 version 5.13.0-41.46
from impish-proposed.
(edit: whoops, got the version wrong)
eta@st-pancras ~> uname -a
Linux st-pancras 5.13.0-41-generic #46-Ubuntu SMP Thu Apr 14 20:06:04 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1969374] Re: linux-bluefield: Fix build failure in mlxbf_gige
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-bluefield (Ubuntu) Assignee: (unassigned) => Zachary Tahenakos (ztahenakos) ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Zachary Tahenakos (ztahenakos) -- 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/1969374 Title: linux-bluefield: Fix build failure in mlxbf_gige Status in linux-bluefield package in Ubuntu: Fix Committed Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification [Impact] The latest PR to fix a certification issue has introduced a build failure. Specifically: net: mellanox: mlxbf_gige: Replace non-standard interrupt handling A build of the kernel fails with the following error: drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_main.c:380:12: error: implicit declaration of function 'acpi_dev_gpio_irq_get_by'; did you mean 'acpi_dev_gpio_irq_get'? [-Werror=implicit-function-declaration] [Fix] Cherry-picking: 809390219fb9c gpiolib: acpi: Allow to find GpioInt() resource by name and index The above commit reworks GpioInt() to allow finding the resource via name and index while preserving previous functionality. [Test Case] Beyond ensuring build still works, no testing of drivers using the reworked acpi_dev_gpio_irq_get function will be done, but it should still work as previously designed when NULL is passed for name. [Where problems could occur] Chance of regression should be very low with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1969374/+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 1966499] Re: Recent 5.13 kernel has broken KVM support
Works great on my side with the 5.13.0-41.46 kernel. VM start correctly and no more log spamming. ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] This is caused by commit 08335308 "KVM: x86: check PIR even for vCPUs with disabled APICv", this patch needs 7e1901f6c "KVM: VMX: prepare sync_pir_to_irr for running with APICv disabled" otherwise if APICv is disabled in this vcpu it will trigger warning messages in vmx_sync_pir_to_irr() of vmx.c: WARN_ON(!vcpu->arch.apicv_active); With warnings like: [ cut here ] WARNING: CPU: 13 PID: 6997 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] ? xfer_to_guest_mode_work+0xe2/0x110 Modules linked in: vhost_net vhost vhost_iotlb tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds ioatdma rapl intel_cstate efi_pstore ipmi_si mei_me mei mac_hid acpi_pad vcpu_run+0x4d/0x220 [kvm] acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr 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 raid0 multipath linear hid_generic usbhid hid mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect sysimgblt ghash_clmulni_intel fb_sys_fops ixgbe cec aesni_intel rc_core crypto_simd xfrm_algo cryptd drm ahci dca i2c_i801 xhci_pci mdio libahci i2c_smbus lpc_ich xhci_pci_renesas wmi CPU: 13 PID: 6997 Comm: qemu-system-x86 Tainted: G W I 5.13.0-39-generic #44-Ubuntu Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.1008.031920151331 03/19/2015 kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] RIP: 0010:vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] Code: e8 47 f5 18 00 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 74 dc 48 8b 55 f0 65 48 2b 14 25 28 00 00 00 75 1d 48 8b 5d f8 c9 c3 <0f> 0b eb 87 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb RSP: 0018:ae4d8d107c98 EFLAGS: 00010046 RAX: RBX: 99c552942640 RCX: 99c5043a72f0 RDX: 99c552942640 RSI: 0001 RDI: 99c552942640 RBP: ae4d8d107cb0 R08: 99c86f6a7140 R09: 00027100 R10: 4228 R11: 000a R12: 99c552942640 R13: R14: ae4d8d1a63e0 R15: 99c552942640 FS: 7f6ae9be7640() GS:99c86f68() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: CR3: 00010b8a6006 CR4: 001726e0 Call Trace: kvm_vcpu_ioctl+0x243/0x5e0 [kvm] vcpu_enter_guest+0x383/0xf50 [kvm] ? xfer_to_guest_mode_work+0xe2/0x110 ? kvm_vm_ioctl+0x364/0x730 [kvm] ? __fget_files+0x86/0xc0 vcpu_run+0x4d/0x220 [kvm] __x64_sys_ioctl+0x91/0xc0 do_syscall_64+0x61/0xb0 ? fput+0x13/0x20 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6aebce1a2b Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 f3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6ae8ffe3f8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: ae80 RCX: 7f6aebce1a2b RDX: RSI: ae80 RDI: 000c RBP: 557d3b429b90 R08: 557d3a4ebff0 R09: kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] R10: 0001 R11: 0246 R12: R13: 0001 R14: 3000 R15: ---[ end trace 5b722d71a78069b1 ]--- This warning message will be flooding in system log files and eventually eat up all the disk space then crash the server. This issue will gone by either reverting it or adding the fixes below. Reference: https://patchwork.kernel.org/project/kvm/patch/2028072531.1534938-1-pbonz...@redhat.com/ [Fixes] * 0b8f11737 KVM: Add infrastructure and macro to
[Kernel-packages] [Bug 1969374] Re: linux-bluefield: Fix build failure in mlxbf_gige
** Changed in: linux-bluefield (Ubuntu) Status: New => Fix Committed -- 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/1969374 Title: linux-bluefield: Fix build failure in mlxbf_gige Status in linux-bluefield package in Ubuntu: Fix Committed Bug description: SRU Justification [Impact] The latest PR to fix a certification issue has introduced a build failure. Specifically: net: mellanox: mlxbf_gige: Replace non-standard interrupt handling A build of the kernel fails with the following error: drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_main.c:380:12: error: implicit declaration of function 'acpi_dev_gpio_irq_get_by'; did you mean 'acpi_dev_gpio_irq_get'? [-Werror=implicit-function-declaration] [Fix] Cherry-picking: 809390219fb9c gpiolib: acpi: Allow to find GpioInt() resource by name and index The above commit reworks GpioInt() to allow finding the resource via name and index while preserving previous functionality. [Test Case] Beyond ensuring build still works, no testing of drivers using the reworked acpi_dev_gpio_irq_get function will be done, but it should still work as previously designed when NULL is passed for name. [Where problems could occur] Chance of regression should be very low with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1969374/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
SRU: https://lists.ubuntu.com/archives/kernel- team/2022-April/129581.html (oem-5.15, jammy, oem-5.17, unstable) ** Description changed: + [SRU Justfication] + + [Impact] + + Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, + and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. + Not reproducible on every platform with AX211 installed, and the chances + of such failures vary from one to another. + + [Fix] + + A few solutions were considered. The very first one is to ask Intel to + fix -64 firmware directly, and the answer is a solid no claimed -64 is + not the planned production version of AX211. + + It's also possible to backport FW API from v5.16, but while iwlwifi FW + API is more or less a black box to us and the new FW APIs also depends + on updates on the wireless stack, this is going to be very risky and + actually we had regressions before after such backports. + + The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on + the effected platforms. This means oem-5.14 and its migration target, + hwe-5.15 will not be able to drive this piece of hw flawlessly without + backport-iwlwifi-dkms installed. + + However, while we need secureboot to be enabled on these platforms, + backport-iwlwifi-dkms must also be signed somehow. There are two + possible method to achieve this, too. One, to prebuild this dkms as zfs + and v4l2loopback does. However, while backport-iwlwifi-dkms generates + kernel modules with exactly the same name as the in-tree ones, when + prebuilt, they'll be available directly from the linux-modules package + and therefore overrides the in-tree ones always, turning the in-tree + driver completely useless and risk the stability of all other generic + installations. + + The second one is to build backport-iwlwifi-dkms as nvidia graphic + drivers in the linux-restricted-modules source package. In this way, + affected platforms may install the corresponding packages when needed + without interfering others. However, l-r-m is for restricted modules + that needs special care of redistribution of its binaries, and + backport-iwlwifi-dkms is GPL licensed. + + Here a similar but simpler process in the main kernel tree is + re-implemented. Two additional packages, + linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package + linux-modules-MODULE-FLAVOUR will be created. + + [Test Case] + + Test builds: + ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb + ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb + ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb + ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb + ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb + ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb + ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb + ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb + + [Where problems could occur] + + The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails + to build under this proposed process. Debdiff attached to the same + bug. + + Different from nvidia packages built from l-r-m, the generated package + names do not carry an additional short version string, e.g. nvidia-410, + as there is no such necessity to build multiple versions of iwlwifi. + The modules are installed to /lib/modules//kernel/iwlwifi, not + iwlwifi-9858/. + + == original bug report == + [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" -- 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/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: New 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: New Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances
[Kernel-packages] [Bug 1969482] Re: zfs-2.1.4+ sru
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969482 Title: zfs-2.1.4+ sru Status in zfs-linux package in Ubuntu: Confirmed Bug description: [Impact] * Upstream stable point release update with bugfixes, performance fixes, and newer kernel support as will be needed in the future hwe kernels. [Test Plan] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass [Where problems could occur] * The stable branches maintain api/abi. Certain bugfixes do change userspace visible behavior of either succeeeding (when previously operations failed), or return errors when previously succeeding in error. For example there are changes when unlinking files in full volumes; changes to fallocate behaviour, etc. Overall they are minor corner cases, and bugfixes to correct the bahaviour to what is universally expected and how things behave on other filesystems (i.e. ext4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
Tested: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb -- 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/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: New 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: New Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
The attachment "backport-iwlwifi-dkms_9858-0ubuntu3.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: New 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: New Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
Prebuilt PPA in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1969434 ** Merge proposal linked: https://code.launchpad.net/~vicamo/ubuntu/+source/backport-iwlwifi-dkms/+git/backport-iwlwifi-dkms/+merge/419698 -- 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/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: New 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: New Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** Patch added: "backport-iwlwifi-dkms_9858-0ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/focal/+source/linux-oem-5.17/+bug/1969434/+attachment/5581484/+files/backport-iwlwifi-dkms_9858-0ubuntu3.debdiff -- 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/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: New 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: New Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+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 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
I'm sorry, it looks like I won't be able to validate this fix on our
Ubuntu Core 20 systems. While waiting for this fix to become available,
we've used Ubuntu Core's refresh control (snap gating) mechanism to
ensure a non-affected version of the pc-kernel snap is installed across
our fleet of devices. Relevant docs:
https://ubuntu.com/core/docs/refresh-control
Due to this snap gating "validation assertion" currently being in-place,
I'm unable to update my test system to the fixed revision of the pc-
kernel snap (5.4.0-109.123.1, revision 978) to confirm the fix. I have a
pending support ticket with Canonical to find out how to lift the snap
gating restriction but at this time I haven't received a response yet.
However, I see that the fix has now been marked as released for Focal.
Indeed, the fixed revision of the pc-kernel snap (5.4.0-109.123.1,
revision 978) has already hit the "20/stable" channel as of today. Can I
conclude that the fix has been accepted based on Chris Chiu's
confirmation and that my confirmation is no longer required? In other
words: that the fix is now released and no longer at risk of being
dropped, for 20.04?
--
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/1968210
Title:
USB devices not detected during boot on USB 3.0 hubs
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
There are users with certain intel xHCI controllers that are
experiencing problems with USB devices not being detected at boot.
This is because when the primary roothub is registered, device
enumeration happens before xHC is running and leads to devices not being
detected. This results in the error that looks something like
'usb usb1-port3: couldn't allocate usb_device'.
[Fix]
Register both root hubs along with the secondary hcd for xhci.
This original fix was reverted upstream due to regressions that occured due to
racing that happened when both roothubs were registered simultaneously.
However with those fixes being addressed in commits
("usb: hub: Fix usb enumeration issue due to address0 race")
("usb: hub: Fix locking issues with address0_mutex")
the maintainers have stated that they will be reintroducing this commit.
So lets reintroduce it here to fix the issues that users are
experiencing.
[Test Case]
Confirmed by Chris Chiu that this issue exists on similiar hardware
reported by the users and that reverting these reverts fixes the issue
showing no signs of 'couldn't allocate usb_device' and with USB devices
available after boot.
[Regression Potential]
Should be low now that we carry the fixes that seemed to be caused by
this patch series.
There have been reports by some users using certain intel xHCI controllers
that their USB devices are not being detected after boot again after similar
issues were previously found and fixed. This seems to be related to both [1][2]
with the majority of the discussion on [1] about these problems reoccurring.
This bug report is being made more for documentation of this new regression.
These seems to be due to the patchset for [2] being reverted upstream
due to regressions.
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+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 1967848] Re: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3
Did you try just copying the URL and accessing it from a different laptop? Alternately, you could, on the failing system run this: ubuntu-bug --save=~/1967848-apport-logs linux which will create a new bug report log file (there's, unfortunately, no way to use apport-collect and NOT submit from the machine itself). But you could then upload that created log file to this bug with just an explanation that you were unable to send those logs from within your test lab due to security restrictions. -- 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/1967848 Title: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3 Status in linux package in Ubuntu: Confirmed Bug description: This bug is raised as per the suggestion by Jeff Email snapshot: -- File a bug, point me to a patch, and I'll see if I can pull it. Though we'd need more info... for are we talking the 4.15 GA kernel, or the 5.4 kernel? It would be a bit more involved If I have to pull the patch into 4 different kernels in order to get it back into 4.15 to avoid regressions. BUT it's not difficult, assuming any patches are only applied to lpfc. Once it lands in the scsi tree we can start looking, though I'd be more comfy for it to be in linux-next or mainline. I'll also need someone to fill out some info on the bug to create the SRU justification. -- There is an issue in which we are seeing login failure with Ubuntu 18.04.3, inbox driver version 12.0.0.0 but this issue is not seen with Ubuntu 20.04.2 with inbox driver 12.0.0.6. I found that upstream commit id [0a9e9687acaf6ac1198fd41f03d64f8b92e4515e] could potentially fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967848/+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 1969275] Re: end kernel panic not syncing attempted to kill init exit code 0x00000009 and the pc dont turn off
This seems to be a nouveau/nvidia drivers topic. I'm not a graphics expert, but if I recall correctly, the opensource `nouveau` driver is usually disabled in favor of the proprietary `nvidia` drivers, which seem to work better on the Nvidia cards/gpus. I can't provide the detailed steps right now, but just searching for 'how to install nvidia drivers on 18.04' gave many results which seem to be accurate about add a PPA, apt install, nouveau check/disable, and done. That should help you out. :) Hope this helps! ... P.S.: This is not to say the nouveau driver shouldn't be fixed, but I'd guess that due to the wider/more common usage of the nvidia drivers, that'd be a lower relative priority. ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969275 Title: end kernel panic not syncing attempted to kill init exit code 0x0009 and the pc dont turn off Status in linux package in Ubuntu: Confirmed Bug description: the pc can not be turn off untill i will force hiw to push the button for severla second and if not the screen freeze on this bug end kernel panic not syncing attempted to kill init exit code 0x0009 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-107-generic 5.4.0-107.121~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 16:32:04 2022 InstallationDate: Installed on 2021-09-23 (205 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969275/+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 1969275] Re: end kernel panic not syncing attempted to kill init exit code 0x00000009 and the pc dont turn off
Thanks! The picture in comment #4 contains the full stack trace. Some technical analysis for reference. Don't worry about it. Please see the next comment for suggestions, for now. ... When returning to userspace from the exit_group() syscall (as per: orig rax == 0xe7 == 231 -> sys_exit_group; see [1]), the work to release the last reference to a file closed (per fput() bits) called into the DRM handling (apparently the file might be /dev/drm*, I guess), which called into the _nouveau_driver (the implementation), which owns the majority of the trace from there. Finally, the nouveau probably performed an incorrect memory access (per CR2, showing what seems to be an over flown pointer). This crashed the kernel. [1] $ grep 231 git/linux/arch/x86/entry/syscalls/syscall_64.tbl 231 common exit_group sys_exit_group -- 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/1969275 Title: end kernel panic not syncing attempted to kill init exit code 0x0009 and the pc dont turn off Status in linux package in Ubuntu: Confirmed Bug description: the pc can not be turn off untill i will force hiw to push the button for severla second and if not the screen freeze on this bug end kernel panic not syncing attempted to kill init exit code 0x0009 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-107-generic 5.4.0-107.121~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 16:32:04 2022 InstallationDate: Installed on 2021-09-23 (205 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969275/+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 1969434] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1969434 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: New 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: New Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** Summary changed: - dkms.conf doesn't respect --kernelsourcedir passed to dkms build + build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI ** Description changed: + [backport-iwlwifi-dkms] + Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: - MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" + MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: backport-iwlwifi-dkms (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: backport-iwlwifi-dkms (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: New 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: New Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969434/+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 1967292] Re: net/mlx5e: Fix page DMA map/unmap attributes
This bug is awaiting verification that the linux/5.4.0-110.124 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- 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/1967292 Title: net/mlx5e: Fix page DMA map/unmap attributes Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Upstream commit 0b7cfa4082fbf550595bc0e40f05614bd83bf0cd is a fix to the Mellanox mlx5 driver that we would like to have you pick up. It fixes a bug that was introduced in the 4.7 kernel, so it should be applicable to pretty much every Linux distribution. The bug causes a Linux panic when a Mellanox CX-4 VF is present in the VM (for AccelNet) and swiotlb=force used on the kernel boot line. swiotlb=force would not normally be used, which is why we haven’t seen the problem reported previously, but it cropped up during some internal testing. We are trying to head off a potential problem in a future scenario for Confidential VMs. Primarily we want to ensure that any CVMs images have this fix, as we don’t want CVM images to exist in the wild that would fail in the future when CVMs with AccelNet are offered. Business Impact This scenario could also exist in non-Azure instances. [Test Case] Microsoft tested. [Where problems could appear] Weird DMA and data corruption issues might crop up. [Other Info] SF: #00328938 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967292/+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 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))
This bug is awaiting verification that the linux/5.4.0-110.124 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- 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/1956315 Title: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50)) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] vmx_ldtr_test in ubuntu_kvm_unit_tests will fail with: FAIL: Expected 0 for L1 LDTR selector (got 50) It's a test for commit afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" According to Intel 64 and IA-32 Architectures Software Developer’s Manual, L1's LDTR should be 0 after an emulated VM-exit from L2. [Fix] * afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" We already have this patch in Jammy. This patch can be cherry-picked into F/F-OEM-5.14/I. But some straightforward backport work is required for Bionic, as the code snippet for nested KVM haven't been split out to vmx/nested.c (55d2375e KVM: nVMX: Move nested code to dedicated files). [Test] Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1956315-vmx-ldtr/ Tested with: * B (bare-metal / KVM instance) * F (KVM instance) * I (bare-metal / KVM instance) With this patched kernel, this test will pass: PASS: Expected 0 for L1 LDTR selector (got 0) Also tested with ubuntu_kvm_unit_tests and ubuntu_kvm_smoke_test to make sure this is not causing any other regressions. [Where problem could occur] If the patch is incorrect it might affect the nested KVM functionality while existing from L2 to L1. [Original bug description] Issue found on Bionic 4.15.0-166.174 with node rizzo Running 'kvm-ok' INFO: /dev/kvm exists KVM acceleration can be used '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test' BUILD_HEAD=8a30588c timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Lnfifekq7r -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd /tmp/tmp.i9y5hdMh49 enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 filter = vmx_ldtr_test, test = test_vmx_feature_control filter = vmx_ldtr_test, test = test_vmxon filter = vmx_ldtr_test, test = test_vmptrld filter = vmx_ldtr_test, test = test_vmclear filter = vmx_ldtr_test, test = test_vmptrst filter = vmx_ldtr_test, test = test_vmwrite_vmread filter = vmx_ldtr_test, test = test_vmcs_high filter = vmx_ldtr_test, test = test_vmcs_lifecycle filter = vmx_ldtr_test, test = test_vmx_caps filter = vmx_ldtr_test, test = test_vmread_flags_touch filter = vmx_ldtr_test, test = test_vmwrite_flags_touch filter = vmx_ldtr_test, test = null filter = vmx_ldtr_test, test = vmenter filter = vmx_ldtr_test, test = preemption timer filter = vmx_ldtr_test, test = control field PAT filter = vmx_ldtr_test, test = control field EFER filter = vmx_ldtr_test, test = CR shadowing filter = vmx_ldtr_test, test = I/O bitmap filter = vmx_ldtr_test, test = instruction intercept filter = vmx_ldtr_test, test = EPT A/D disabled filter = vmx_ldtr_test, test = EPT A/D enabled filter = vmx_ldtr_test, test = PML filter = vmx_ldtr_test, test = interrupt filter = vmx_ldtr_test, test = nmi_hlt filter = vmx_ldtr_test, test = debug controls filter = vmx_ldtr_test, test = MSR switch filter = vmx_ldtr_test, test = vmmcall filter = vmx_ldtr_test, test = disable RDTSCP filter
[Kernel-packages] [Bug 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC
This bug is awaiting verification that the linux/5.4.0-110.124 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-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
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: verification-needed-focal
--
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/1917471
Title:
[SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
causes Bus Fatal Error when rebooting system with BCM5720 NIC
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
[IMPACT]
This is being reported by a hardware partner as it is being noticed a
lot both in their internal testing teams and also being reported with
some frequency by customers who are seeing these messages in their
logs and thus it is generating an unusualy high volume of support
calls from the field.
In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
Upstream, these errors were discovered and that patch was reverted
(see Fix Below). We carry the revert commit in all subsequent Focal
HWE kernels starting at 5.12, but the fix was never pulled back into
Focal 5.4.
according to the hardware partner:
the following error messages are observed when rebooting a machine
that uses the BCM5720 chipset, which is a widely used 1GbE controller
found on LOMs and OCP NICs as well as many PCIe NIC models.
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
The hardware partner did some bisection and observed the following:
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
[FIX]
The fix is to apply this patch from upstream:
commit 9d3fcb28f9b9750b474811a2964ce022df56336e
Author: Josef Bacik
Date: Tue Mar 16 22:17:48 2021 -0400
Revert "PM: ACPI: reboot: Use S5 for reboot"
This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.
This patch causes a panic when rebooting my Dell Poweredge r440. I do
not have the full panic log as it's lost at that stage of the reboot
[Kernel-packages] [Bug 1952933] Re: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952933 Title: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: In Progress Status in linux source package in Jammy: Fix Committed Bug description: During MAAS deployment: [ 107.768146] Unable to handle kernel read from unreadable memory at virtual address domain : maas[ 107.943413] Mem abort info: rootserver: 10.229.32.21 rootpath: filename :[ 108.043666] ESR = 0x9604 lpxelinux.0 :: root=squash:http://10.229.32.21:5248/images/ubu[ 108.147045] EC = 0x25: DABT (current EL), IL = 32 bits ntu/arm64/xgene-uboot/impish/stable/squashfs :: mount_squash do[ 108.277541] SET = 0, FnV = 0 wnloading http://10.229.32.21:5248/images/ubuntu/arm64/xgene-ubo[ 108.380921] EA = 0, S1PTW = 0 ot/impish/stable/squashfs to /root.tmp.img Connecting to 10.229[ 108.485351] Data abort info: .32.21:5248 (10.229.32.21:5248) [ 108.586639] ISV = 0, ISS = 0x0004 [ 108.667060] CM = 0, WnR = 0 [ 108.702635] user pgtable: 4k pages, 48-bit VAs, pgdp=00401ce02000 root.tmp.img [ 108.779941] [] pgd=, p4d= 4% [ 108.884372] Internal error: Oops: 9604 [#1] SMP [ 108.948102] Modules linked in: raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_ib ib_uverbs ib_core mlx4_en mlx4_core gpio_keys_polled gpio_dwapb crct10dif_ce ahci_xgene gpio_xgene_sb aes_neon_bs aes_neon_blk crypto_simd cryptd [ 109.286243] CPU: 0 PID: 11 Comm: ksoftirqd/0 Not tainted 5.13.0-20-generic #20-Ubuntu [ 109.380233] Hardware name: HP ProLiant m400 Server Cartridge (DT) [ 109.453258] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 109.525342] pc : mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 109.589087] lr : mlx4_en_poll_rx_cq+0x7c/0x17c [mlx4_en] [ 109.652828] sp : 8000129cbc60 [ 109.692470] x29: 8000129cbc60 x28: 012c x27: 000ff7e95fc0 [ 109.778115] x26: x25: 20908508 x24: 21b40940 [ 109.863763] x23: 20908508 x22: 20908400 x21: 21b4 [ 109.949409] x20: 0040 x19: 0040 x18: 0014 [ 110.035056] x17: 1122e350 x16: cb46f8bb x15: e2b6a183 [ 110.120703] x14: 26fff11e x13: 9312ff0b x12: [ 110.206349] x11: 0006 x10: 0040 x9 : 89119320 [ 110.291997] x8 : 08acdc00 x7 : 02c0 x6 : dff8 [ 110.377642] x5 : 0394 x4 : 03960040 x3 : 21c2 [ 110.463289] x2 : x1 : x0 : [ 110.548937] Call trace: [ 110.578147] mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 110.637719] __napi_poll+0x40/0x1e0 [ 110.679551] net_rx_action+0x2d8/0x34c [ 110.724513] __do_softirq+0x128/0x388 [ 110.768432] run_ksoftirqd+0x6c/0x94 [ 110.811308] smpboot_thread_fn+0x15c/0x1a0 [ 110.860443] kthread+0x114/0x120 [ 110.899145] ret_from_fork+0x10/0x18 [ 110.942024] Code: 1100fc41 1a82b021 13067c21 93407c21 (f8617800) [ 111.015158] ---[ end trace b37ae99414884442 ]--- [ 111.070550] Kernel panic - not syncing: Oops: Fatal exception in interrupt [ 111.152964] SMP: stopping secondary CPUs [ 111.200016] Kernel Offset: 0x8 from 0x80001000 [ 111.265837] PHYS_OFFSET: 0x40 [ 111.309651] CPU features: 0x0251,0046 [ 111.361915] Memory Limit: none [ 111.398431] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952933/+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 1966803] Re: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()
This bug is awaiting verification that the linux/5.4.0-110.124 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- 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/1966803 Title: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename() Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The xfs filesystem suffers from a deadlock issue in kernels < 5.5. This hangs IO to/from the affected filesystem. Sample backtraces added as a comment. [Fix] * 93597ae8dac0149b5c00b787cba6bf7ba213e666 93597ae8dac0 "xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()" * This is from the upstream 5.5 kernel. [Test Plan] * Set up an Ubuntu Bionic/Focal installation using kernel 5.4. * Create and mount an XFS filesystem on a block device. * Exercise the filesystem to verify that IO does not hang. [Where problems could occur] * This patch could cause locking issues on XFS filesystems, requiring a system restart to correct. [Other Info] * Bug is difficult to reproduce, a test kernel on affected systems with the above patch prevented the issue. * Backports to earlier (4.15 and earlier) kernels have been omitted as the upstream patch does not apply cleanly and the issue has not been reproduced on them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966803/+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 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] Add support for software steering on cx7 [Test Case] configure software steering on cx7 setup run asap testing (reference https://github.com/Mellanox/ovs-tests) [Regression Potential] TBD [Other Info] Feature patchset: All patches are cleanly applied on Jamy master-next beside these two who add minor conflicts due to context difference. net/mlx5: Introduce software defined steering capabilities net/mlx5: DR, Add support for matching on #fixes 624bf42c2e39 net/mlx5: DR, Fix querying eswitch manager vport for ECPF 0aec12d97b20 net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #CX7 SMFS support 6862c787c7e8 net/mlx5: DR, Add support for ConnectX-7 steering 638a07f1090e net/mlx5: DR, Refactor ste_ctx handling for STE v0/1 75a3926ca6a4 net/mlx5: DR, Rename action modify fields to reflect naming in HW spec bdc3ab5795a6 net/mlx5: DR, Fix handling of different actions on the same STE in STEv1 11659ef8d28e net/mlx5: DR, Remove unneeded comments 5c422bfad2fb net/mlx5: DR, Add support for matching on Internet Header Length (IHL) #dependencies: 60dc0ef674ec net/mlx5: VLAN push on RX, pop on TX 8348b71ccd92 net/mlx5: Introduce software defined steering capabilities #depencecies: #SW STEERING DEBUG DUMP aa36c94853b2 net/mlx5: Set SMFS as a default steering mode if device supports it 4ff725e1d4ad net/mlx5: DR, Ignore modify TTL if device doesn't support it cc2295cd54e4 net/mlx5: DR, Improve steering for empty or RX/TX-only matchers f59464e257bd net/mlx5: DR, Add support for matching on geneve_tlv_option_0_exist field 09753babaf46 net/mlx5: DR, Support matching on tunnel headers 0 and 1 8c2b4fee9c4b net/mlx5: DR, Add misc5 to match_param structs 0f2a6c3b9219 net/mlx5: Add misc5 flow table match parameters b54128275ef8 net/mlx5: DR, Warn on failure to destroy objects due to refcount e3a0f40b2f90 net/mlx5: DR, Add support for UPLINK destination type 9222f0b27da2 net/mlx5: DR, Add support for dumping steering info 7766c9b922fe net/mlx5: DR, Add missing reserved fields to dr_match_param 89cdba3224f0 net/mlx5: DR, Add check for flex parser ID value 08fac109f7bb net/mlx5: DR, Rename list field in matcher struct to list_node 32e9bd585307 net/mlx5: DR, Remove unused struct member in matcher c3fb0e280b4c net/mlx5: DR, Fix lower case macro prefix "mlx5_" to "MLX5_" 84dfac39c61f net/mlx5: DR, Fix error flow in creating matcher 58a606dba708 net/mlx5: Introduce new uplink destination type 455832d49666 net/mlx5: DR, Fix check for unsupported fields in match param 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #SW STEERING SF 515ce2ffa621 net/mlx5: DR, init_next_match only if needed 5dde00a73048 net/mlx5: DR, Fix typo 'offeset' to 'offset' 1ffd498901c1 net/mlx5: DR, Increase supported num of actions to 32 11a45def2e19 net/mlx5: DR, Add support for SF vports c0e90fc2ccaa net/mlx5: DR, Support csum recalculation flow table on SFs ee1887fb7cdd net/mlx5: DR, Align error messages for failure to obtain vport caps dd4acb2a0954 net/mlx5: DR, Add missing query for vport 0 7ae8ac9a5820 net/mlx5: DR, Replace local WIRE_PORT macro with the existing MLX5_VPORT_UPLINK f9f93bd55ca6 net/mlx5: DR, Fix vport number data type to u16 c228dce26222 net/mlx5: DR, Fix code indentation in dr_ste_v1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+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 1968016] Re: Use kernel-testing repo from launchpad for ADT tests
This bug is awaiting verification that the linux/5.4.0-110.124 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- 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/1968016 Title: Use kernel-testing repo from launchpad for ADT tests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux-oem-5.14 source package in Trusty: Invalid Status in linux-oem-5.17 source package in Trusty: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux-oem-5.17 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux-oem-5.17 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: In ADT tests, we are still using the kernel-testing repo from kernel.ubuntu.com, it should be migrated to launchpad instead to align with our other testing repos. For autotest-client-tests repo change, it will needs to be handled in the kernel-testing repo directly, see bug 1968257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968016/+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 1967754] Re: ubuntu 22.04 jammy, mlx5, can't change flow steering mode
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1967754
Title:
ubuntu 22.04 jammy, mlx5, can't change flow steering mode
Status in linux package in Ubuntu:
Fix Committed
Bug description:
on kernel 5.15.0-23-generic devlink cannot show/change flow steering
mode
[test case]
# devlink dev param show pci/:24:00.0 name flow_steering_mode
pci/:24:00.0:
name flow_steering_mode type driver-specific
values:
(flow steering mode description is missing beneath "values:")
# devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs
cmode runtime
Segmentation fault (core dumped)
and also with upstream iproute
# ./iproute2/devlink/devlink dev param set pci/:24:00.0 name
flow_steering_mode value smfs cmode runtime
Configuration mode not supported
this issue is a degradation introduced by commit from jammy tree
76385c47db37 ("net/mlx5: Accept devlink user input after driver
initialization complete")
issue do not repro on v5.15.0 or when the above commit is reverted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+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 1968591] Re: xfrm interface cannot be changed anymore
This bug is awaiting verification that the linux/5.4.0-110.124 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- 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/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
** Changed in: mysql-8.0 (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: New Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Triaged Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1969482] [NEW] zfs-2.1.4+ sru
Public bug reported: [Impact] * Upstream stable point release update with bugfixes, performance fixes, and newer kernel support as will be needed in the future hwe kernels. [Test Plan] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass [Where problems could occur] * The stable branches maintain api/abi. Certain bugfixes do change userspace visible behavior of either succeeeding (when previously operations failed), or return errors when previously succeeding in error. For example there are changes when unlinking files in full volumes; changes to fallocate behaviour, etc. Overall they are minor corner cases, and bugfixes to correct the bahaviour to what is universally expected and how things behave on other filesystems (i.e. ext4). ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969482 Title: zfs-2.1.4+ sru Status in zfs-linux package in Ubuntu: New Bug description: [Impact] * Upstream stable point release update with bugfixes, performance fixes, and newer kernel support as will be needed in the future hwe kernels. [Test Plan] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass [Where problems could occur] * The stable branches maintain api/abi. Certain bugfixes do change userspace visible behavior of either succeeeding (when previously operations failed), or return errors when previously succeeding in error. For example there are changes when unlinking files in full volumes; changes to fallocate behaviour, etc. Overall they are minor corner cases, and bugfixes to correct the bahaviour to what is universally expected and how things behave on other filesystems (i.e. ext4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
yeap that's bad. ** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: zfs-linux (Ubuntu) Importance: Wishlist => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: New Status in mysql-8.0 package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Triaged Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
On jammy, it works on btrfs: root@nsn7:/mnt# rm -f foo.img; touch foo.img; fallocate -z -l 10M foo.img; ls -lah foo.img -rw-r--r-- 1 root root 10M abr 19 10:46 foo.img root@nsn7:/mnt# mount -t btrfs /btrfs.img on /mnt type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=5,subvol=/) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: New Status in mysql-8.0 package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Confirmed Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1967988] Re: Support different Cirrus audio codec configurations on Dell laptops
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid -- 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/1967988 Title: Support different Cirrus audio codec configurations on Dell laptops Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On Dell's platform, Warlock/Bullseye Laptops have a mono DMIC, Cyborg and some Warlock variants uses a stereo DMIC. They are not correctly mapped to the corresponding configurations so the microphone function are not working as expected. [Fix] Cirrus upstream new FIXUPs to support different microphone configurations on different Dell laptop variants. [Test Case] 1. Go to Audio Settings 2. Make sure the microphone is correctly detected and responds to audio input. 3. Issue command "arecord record_file" and check the record_file is consistent with audio input. [Where problems could occur] Risk should be Low. The patches come from Cirrus and the configurations are mapped based on the audio codec's SSIDs for different Dell variants. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967988/+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 1968892] Re: Micmute LED support for Zbook Fury 16 G9
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1968892 Title: Micmute LED support for Zbook Fury 16 G9 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The audio mute key(F5) LED does not work. [Fix] Need this commit from v5.18-rc1 ce18f905a500 ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 [Test] Verified on the target machine. [Where problems could occur] The modified hda_fixups, ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED, has the same contain as ALC245_FIXUP_CS35L41_SPI_2, but with new mic mute led gpio settings. So, if might affect the machines with the same chip ID that mic mute led is already working. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968892/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
I applied zfs_fallocate_reserve_percent=0 to the kernel module, confirmed it was set, but I still see the same incorrect behavior with fallocate: root@nsn7:/tank/test# rm -f foo.img; touch foo.img; fallocate -z -l 10M foo.img; ls -lah foo.img -rw-r--r-- 1 root root 0 abr 19 10:35 foo.img root@nsn7:/tank/test# uname -a Linux nsn7 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@nsn7:/tank/test# cat /sys/module/zfs/parameters/zfs_fallocate_reserve_percent 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: New Status in mysql-8.0 package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Confirmed Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
jammy needs sru too at this point -- 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/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress 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: Fix Committed Status in firmware-sof source package in Focal: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
Impish kernel on zfs: andreas@nsnx:~$ rm foo.img andreas@nsnx:~$ touch foo.img andreas@nsnx:~$ fallocate -z -l 10M foo.img fallocate: fallocate failed: Operation not supported Jammy kernel on zfs: root@j1:~# touch foo.img root@j1:~# fallocate -z -l 10M foo.img root@j1:~# ll foo.img -rw-r--r-- 1 root root 0 Apr 18 18:06 foo.img Jammy kernel on ext4: andreas@nsn7:~$ touch foo.img andreas@nsn7:~$ fallocate -z -l 10M foo.img andreas@nsn7:~$ l foo.img -rw-rw-r-- 1 andreas andreas 10M abr 19 09:32 foo.img andreas@nsn7:~$ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: New Status in mysql-8.0 package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Confirmed Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
The jammy RC (20220418.2) looks good for Ampere Mt. Jade Altra (bizzy). I can pxe install the server successfully. By the way autoinstall of subiquity also works like a charm. -- 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/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Invalid Status in grub2 source package in Jammy: Fix Released Status in grub2-signed source package in Jammy: Fix Released Status in linux source package in Jammy: Invalid Status in subiquity source package in Jammy: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+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 1961850] Re: [UBUNTU 20.04] s390/pci: move pseudo-MMIO to prevent MIO overlap
Commit "s390/pci: move pseudo-MMIO to prevent MIO overlap" landed in impish with hash 35705e7746d4 and is included in impish's kernel 'Ubuntu-5.13.0-36.41' and later. Latest kernel in impish-updates is linux-generic | 5.13.0.40.49 | impish-updates hence this incl. the needed commit. With that I'm updating the affects impish entry to Fix Released, and with that I can close the ticket (means the project entry) with Fix Released, too. ** Changed in: linux (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961850 Title: [UBUNTU 20.04] s390/pci: move pseudo-MMIO to prevent MIO overlap Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Description: s390/pci: move pseudo-MMIO to prevent MIO overlap Symptom: On some configurations of z15 LPARs having an ISM device attached may cause other PCI devices like NVMes or RoCEs to be unusable and fail to probe. An error message in the kernel log indicates that a PCI memory BAR could not be assigned. Problem: On z15 with the enhanced PCI memory I/O instructions (MIO) ISM devices still rely on the classic PCI instructions which used pseud-MMIO addresses created by Linux. These addresses can conflict with the firmware created MIO addresses which is detected by the Linux PCI resource allocation code which then prevents probing of the device even though technically the address conflict would not cause issues. Solution: Use disjunct ranges for Linux generated pseudo-MMIO and firmware provided MIO addresses. Reproduction: On an LPAR with a lot of PCI devices and in particular many ISM devices the conflict is more likely. It is however unclear how to provoke a conflict without special firmware. The fix was and will be tested on a known affected system. Upstream-ID: 52d04d408185b7aa47628d2339c28ec70074e0ae Distros: Ubuntu 20.04 and higher Preventive:yes Author:Niklas Schnelle Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961850/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
The impish kernel returns "not supported" when fallocate is used in the way mysql does it. That makes mysql aware of the problem, and switch strategies, and it works. The jammy kernel is saying all is fine with the call and its results, but it isn't. Mysql, or any userspace, shouldn't be second guessing the kernel. > Please let me know if setting zfs_fallocate_reserve_percent=0 is a workaround for now. We will test it and put in the release notes as a workaround if it works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: New Status in mysql-8.0 package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Confirmed Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1963717] Re: Bionic update: upstream stable patchset 2022-03-04
This bug was fixed in the package linux - 4.15.0-176.185 --- linux (4.15.0-176.185) bionic; urgency=medium * bionic/linux: 4.15.0-176.185 -proposed tracker (LP: #1966771) * Bionic update: upstream stable patchset 2022-03-04 (LP: #1963717) - can: bcm: fix UAF of bcm op - net: bridge: clear bridge's private skb space on xmit - s390/hypfs: include z/VM guests with access control group set - scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP devices - udf: Restore i_lenAlloc when inode expansion fails - udf: Fix NULL ptr deref when converting from inline format - PM: wakeup: simplify the output logic of pm_show_wakelocks() - netfilter: nft_payload: do not update layer 4 checksum when mangling fragments - serial: stm32: fix software flow control transfer - tty: n_gsm: fix SW flow control encoding/handling - tty: Add support for Brainboxes UC cards. - usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge - usb: common: ulpi: Fix crash in ulpi_match() - usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS - USB: core: Fix hang in usb_kill_urb by adding memory barriers - usb: typec: tcpm: Do not disconnect while receiving VBUS off - net: sfp: ignore disabled SFP node - powerpc/32: Fix boot failure with GCC latent entropy plugin - lkdtm: Fix content of section containing lkdtm_rodata_do_nothing() - i40e: Increase delay to 1 s after global EMP reset - i40e: fix unsigned stat widths - rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev - rpmsg: char: Fix race between the release of rpmsg_eptdev and cdev - scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() - ipv6_tunnel: Rate limit warning messages - net: fix information leakage in /proc/net/ptype - ping: fix the sk_bound_dev_if match in ping_lookup - ipv4: avoid using shared IP generator for connected sockets - hwmon: (lm90) Reduce maximum conversion rate for G781 - NFSv4: Handle case where the lookup of a directory fails - NFSv4: nfs_atomic_open() can race when looking up a non-regular file - net-procfs: show net devices bound packet types - drm/msm: Fix wrong size calculation - drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable - ibmvnic: don't spin in tasklet - yam: fix a memory leak in yam_siocdevprivate() - ipv4: raw: lock the socket in raw_bind() - ipv4: tcp: send zero IPID in SYNACK messages - netfilter: nat: remove l4 protocol port rovers - netfilter: nat: limit port clash resolution attempts - ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback - net: amd-xgbe: ensure to reset the tx_timer_active flag - net: amd-xgbe: Fix skb data length underflow - rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() - af_packet: fix data-race in packet_setsockopt / packet_setsockopt - ASoC: ops: Reject out of bounds values in snd_soc_put_volsw() - ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx() - ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx() - drm/nouveau: fix off by one in BIOS boundary checking - block: bio-integrity: Advance seed correctly for larger interval sizes - RDMA/mlx4: Don't continue event handler after memory allocation failure - iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping() - iommu/amd: Fix loop timeout issue in iommu_ga_log_enable() - spi: bcm-qspi: check for valid cs before applying chip select - spi: mediatek: Avoid NULL pointer crash in interrupt - spi: meson-spicc: add IRQ check in meson_spicc_probe - net: ieee802154: ca8210: Stop leaking skb's - net: ieee802154: Return meaningful error codes from the netlink helpers - net: macsec: Verify that send_sci is on when setting Tx sci explicitly - drm/i915/overlay: Prevent divide by zero bugs in scaling - ASoC: fsl: Add missing error handling in pcm030_fabric_probe - scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe - nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client. - selftests: futex: Use variable MAKE instead of make - rtc: cmos: Evaluate century appropriate - EDAC/altera: Fix deferred probing - EDAC/xgene: Fix deferred probing - ext4: fix error handling in ext4_restore_inline_data() - serial: 8250: of: Fix mapped region size when using reg-offset property - i40e: Fix issue when maximum queues is exceeded - i40e: Fix queues reservation for XDP - ipv6: annotate accesses to fn->fn_sernum - ibmvnic: init ->running_cap_crqs early * Bionic update: upstream stable patchset 2022-03-04 (LP: #1963717) // audit: improve audit queue handling when "audit=1" on cmdline (LP: #1965723) - audit: improve audit queue handling when "audit=1" on cmdline * CVE-2021-43975 - atlantic: Fix OOB read and write in
[Kernel-packages] [Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
This bug was fixed in the package linux - 4.15.0-176.185 --- linux (4.15.0-176.185) bionic; urgency=medium * bionic/linux: 4.15.0-176.185 -proposed tracker (LP: #1966771) * Bionic update: upstream stable patchset 2022-03-04 (LP: #1963717) - can: bcm: fix UAF of bcm op - net: bridge: clear bridge's private skb space on xmit - s390/hypfs: include z/VM guests with access control group set - scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP devices - udf: Restore i_lenAlloc when inode expansion fails - udf: Fix NULL ptr deref when converting from inline format - PM: wakeup: simplify the output logic of pm_show_wakelocks() - netfilter: nft_payload: do not update layer 4 checksum when mangling fragments - serial: stm32: fix software flow control transfer - tty: n_gsm: fix SW flow control encoding/handling - tty: Add support for Brainboxes UC cards. - usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge - usb: common: ulpi: Fix crash in ulpi_match() - usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS - USB: core: Fix hang in usb_kill_urb by adding memory barriers - usb: typec: tcpm: Do not disconnect while receiving VBUS off - net: sfp: ignore disabled SFP node - powerpc/32: Fix boot failure with GCC latent entropy plugin - lkdtm: Fix content of section containing lkdtm_rodata_do_nothing() - i40e: Increase delay to 1 s after global EMP reset - i40e: fix unsigned stat widths - rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev - rpmsg: char: Fix race between the release of rpmsg_eptdev and cdev - scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() - ipv6_tunnel: Rate limit warning messages - net: fix information leakage in /proc/net/ptype - ping: fix the sk_bound_dev_if match in ping_lookup - ipv4: avoid using shared IP generator for connected sockets - hwmon: (lm90) Reduce maximum conversion rate for G781 - NFSv4: Handle case where the lookup of a directory fails - NFSv4: nfs_atomic_open() can race when looking up a non-regular file - net-procfs: show net devices bound packet types - drm/msm: Fix wrong size calculation - drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable - ibmvnic: don't spin in tasklet - yam: fix a memory leak in yam_siocdevprivate() - ipv4: raw: lock the socket in raw_bind() - ipv4: tcp: send zero IPID in SYNACK messages - netfilter: nat: remove l4 protocol port rovers - netfilter: nat: limit port clash resolution attempts - ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback - net: amd-xgbe: ensure to reset the tx_timer_active flag - net: amd-xgbe: Fix skb data length underflow - rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() - af_packet: fix data-race in packet_setsockopt / packet_setsockopt - ASoC: ops: Reject out of bounds values in snd_soc_put_volsw() - ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx() - ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx() - drm/nouveau: fix off by one in BIOS boundary checking - block: bio-integrity: Advance seed correctly for larger interval sizes - RDMA/mlx4: Don't continue event handler after memory allocation failure - iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping() - iommu/amd: Fix loop timeout issue in iommu_ga_log_enable() - spi: bcm-qspi: check for valid cs before applying chip select - spi: mediatek: Avoid NULL pointer crash in interrupt - spi: meson-spicc: add IRQ check in meson_spicc_probe - net: ieee802154: ca8210: Stop leaking skb's - net: ieee802154: Return meaningful error codes from the netlink helpers - net: macsec: Verify that send_sci is on when setting Tx sci explicitly - drm/i915/overlay: Prevent divide by zero bugs in scaling - ASoC: fsl: Add missing error handling in pcm030_fabric_probe - scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe - nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client. - selftests: futex: Use variable MAKE instead of make - rtc: cmos: Evaluate century appropriate - EDAC/altera: Fix deferred probing - EDAC/xgene: Fix deferred probing - ext4: fix error handling in ext4_restore_inline_data() - serial: 8250: of: Fix mapped region size when using reg-offset property - i40e: Fix issue when maximum queues is exceeded - i40e: Fix queues reservation for XDP - ipv6: annotate accesses to fn->fn_sernum - ibmvnic: init ->running_cap_crqs early * Bionic update: upstream stable patchset 2022-03-04 (LP: #1963717) // audit: improve audit queue handling when "audit=1" on cmdline (LP: #1965723) - audit: improve audit queue handling when "audit=1" on cmdline * CVE-2021-43975 - atlantic: Fix OOB read and write in
[Kernel-packages] [Bug 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.147-0ubuntu0.18.04.1 --- nvidia-graphics-drivers-390 (390.147-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. -- Alberto Milone Thu, 24 Mar 2022 16:39:52 +0100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Released Status in nvidia-graphics-drivers-510 source package in Impish: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+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 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.147-0ubuntu0.18.04.1 --- nvidia-graphics-drivers-390 (390.147-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. -- Alberto Milone Thu, 24 Mar 2022 16:39:52 +0100 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Released Status in nvidia-graphics-drivers-510 source package in Impish: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+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 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
This bug was fixed in the package nvidia-graphics-drivers-510 - 510.60.02-0ubuntu0.18.04.1 --- nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. -- Alberto Milone Wed, 23 Mar 2022 16:44:37 +0100 ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Released Status in nvidia-graphics-drivers-510 source package in Impish: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+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 1942624] Re: NVMe devices fail to probe due to ACPI power state change
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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: verification-needed-impish -- 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/1942624 Title: NVMe devices fail to probe due to ACPI power state change Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] * Specific NVMe devices fail to probe and become unusable after boot * Caused by an ACPI regression that doesn't correctly handle power states * Upstream regression commit: 7e4fdeafa61f ACPI: power: Turn off unused power resources unconditionally * Regression window for Ubuntu kernels includes 5.13 and 5.14 [Test Plan] * Boot affected kernel and validate whether NVMe device is usable * Check kernel logs for failed probe message: "can't change power state from D3Cold to D0 (config space inaccessible)" [Fix] * Fixed by not turning off power resources in unknown state * Fix was introduced by commit: bc2836859643 ACPI: PM: Do not turn off power resources in unknown state * Kernels starting with 5.15 (e.g. Jammy) not affected, as they already contain the fix above [Regression Potential] * NVMe devices continue failing to probe * Other devices become unusable after power state changes * Further regressions would affect power state of devices, possibly after boot -- [Original Description] NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH
[Kernel-packages] [Bug 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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: verification-needed-impish -- 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/1956315 Title: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50)) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] vmx_ldtr_test in ubuntu_kvm_unit_tests will fail with: FAIL: Expected 0 for L1 LDTR selector (got 50) It's a test for commit afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" According to Intel 64 and IA-32 Architectures Software Developer’s Manual, L1's LDTR should be 0 after an emulated VM-exit from L2. [Fix] * afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" We already have this patch in Jammy. This patch can be cherry-picked into F/F-OEM-5.14/I. But some straightforward backport work is required for Bionic, as the code snippet for nested KVM haven't been split out to vmx/nested.c (55d2375e KVM: nVMX: Move nested code to dedicated files). [Test] Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1956315-vmx-ldtr/ Tested with: * B (bare-metal / KVM instance) * F (KVM instance) * I (bare-metal / KVM instance) With this patched kernel, this test will pass: PASS: Expected 0 for L1 LDTR selector (got 0) Also tested with ubuntu_kvm_unit_tests and ubuntu_kvm_smoke_test to make sure this is not causing any other regressions. [Where problem could occur] If the patch is incorrect it might affect the nested KVM functionality while existing from L2 to L1. [Original bug description] Issue found on Bionic 4.15.0-166.174 with node rizzo Running 'kvm-ok' INFO: /dev/kvm exists KVM acceleration can be used '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test' BUILD_HEAD=8a30588c timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Lnfifekq7r -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd /tmp/tmp.i9y5hdMh49 enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 filter = vmx_ldtr_test, test = test_vmx_feature_control filter = vmx_ldtr_test, test = test_vmxon filter = vmx_ldtr_test, test = test_vmptrld filter = vmx_ldtr_test, test = test_vmclear filter = vmx_ldtr_test, test = test_vmptrst filter = vmx_ldtr_test, test = test_vmwrite_vmread filter = vmx_ldtr_test, test = test_vmcs_high filter = vmx_ldtr_test, test = test_vmcs_lifecycle filter = vmx_ldtr_test, test = test_vmx_caps filter = vmx_ldtr_test, test = test_vmread_flags_touch filter = vmx_ldtr_test, test = test_vmwrite_flags_touch filter = vmx_ldtr_test, test = null filter = vmx_ldtr_test, test = vmenter filter = vmx_ldtr_test, test = preemption timer filter = vmx_ldtr_test, test = control field PAT filter = vmx_ldtr_test, test = control field EFER filter = vmx_ldtr_test, test = CR shadowing filter = vmx_ldtr_test, test = I/O bitmap filter = vmx_ldtr_test, test = instruction intercept filter = vmx_ldtr_test, test = EPT A/D disabled filter = vmx_ldtr_test, test = EPT A/D enabled filter = vmx_ldtr_test, test = PML filter = vmx_ldtr_test, test = interrupt filter = vmx_ldtr_test, test = nmi_hlt filter = vmx_ldtr_test, test = debug controls filter = vmx_ldtr_test, test = MSR switch filter = vmx_ldtr_test, test = vmmcall filter = vmx_ldtr_test, test = disable RDTSCP
[Kernel-packages] [Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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: verification-needed-impish -- 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/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] This is caused by commit 08335308 "KVM: x86: check PIR even for vCPUs with disabled APICv", this patch needs 7e1901f6c "KVM: VMX: prepare sync_pir_to_irr for running with APICv disabled" otherwise if APICv is disabled in this vcpu it will trigger warning messages in vmx_sync_pir_to_irr() of vmx.c: WARN_ON(!vcpu->arch.apicv_active); With warnings like: [ cut here ] WARNING: CPU: 13 PID: 6997 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] ? xfer_to_guest_mode_work+0xe2/0x110 Modules linked in: vhost_net vhost vhost_iotlb tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds ioatdma rapl intel_cstate efi_pstore ipmi_si mei_me mei mac_hid acpi_pad vcpu_run+0x4d/0x220 [kvm] acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr 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 raid0 multipath linear hid_generic usbhid hid mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect sysimgblt ghash_clmulni_intel fb_sys_fops ixgbe cec aesni_intel rc_core crypto_simd xfrm_algo cryptd drm ahci dca i2c_i801 xhci_pci mdio libahci i2c_smbus lpc_ich xhci_pci_renesas wmi CPU: 13 PID: 6997 Comm: qemu-system-x86 Tainted: G W I 5.13.0-39-generic #44-Ubuntu Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.1008.031920151331 03/19/2015 kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] RIP: 0010:vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] Code: e8 47 f5 18 00 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 74 dc 48 8b 55 f0 65 48 2b 14 25 28 00 00 00 75 1d 48 8b 5d f8 c9 c3 <0f> 0b eb 87 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb RSP: 0018:ae4d8d107c98 EFLAGS: 00010046 RAX: RBX: 99c552942640 RCX: 99c5043a72f0 RDX: 99c552942640 RSI: 0001 RDI: 99c552942640 RBP: ae4d8d107cb0 R08: 99c86f6a7140 R09: 00027100 R10: 4228 R11: 000a R12: 99c552942640 R13: R14: ae4d8d1a63e0 R15: 99c552942640 FS: 7f6ae9be7640() GS:99c86f68() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: CR3: 00010b8a6006 CR4: 001726e0 Call Trace: kvm_vcpu_ioctl+0x243/0x5e0 [kvm] vcpu_enter_guest+0x383/0xf50 [kvm] ? xfer_to_guest_mode_work+0xe2/0x110 ? kvm_vm_ioctl+0x364/0x730 [kvm] ? __fget_files+0x86/0xc0 vcpu_run+0x4d/0x220 [kvm] __x64_sys_ioctl+0x91/0xc0 do_syscall_64+0x61/0xb0 ? fput+0x13/0x20 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6aebce1a2b Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 f3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6ae8ffe3f8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: ae80 RCX: 7f6aebce1a2b RDX: RSI: ae80 RDI: 000c RBP: 557d3b429b90 R08: 557d3a4ebff0 R09: kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] R10: 0001 R11: 0246 R12: R13:
[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.
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: verification-needed-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1968016] Re: Use kernel-testing repo from launchpad for ADT tests
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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: verification-needed-impish -- 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/1968016 Title: Use kernel-testing repo from launchpad for ADT tests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux-oem-5.14 source package in Trusty: Invalid Status in linux-oem-5.17 source package in Trusty: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux-oem-5.17 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux-oem-5.17 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: In ADT tests, we are still using the kernel-testing repo from kernel.ubuntu.com, it should be migrated to launchpad instead to align with our other testing repos. For autotest-client-tests repo change, it will needs to be handled in the kernel-testing repo directly, see bug 1968257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968016/+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 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.
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: verification-needed-impish
--
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/1968210
Title:
USB devices not detected during boot on USB 3.0 hubs
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
There are users with certain intel xHCI controllers that are
experiencing problems with USB devices not being detected at boot.
This is because when the primary roothub is registered, device
enumeration happens before xHC is running and leads to devices not being
detected. This results in the error that looks something like
'usb usb1-port3: couldn't allocate usb_device'.
[Fix]
Register both root hubs along with the secondary hcd for xhci.
This original fix was reverted upstream due to regressions that occured due to
racing that happened when both roothubs were registered simultaneously.
However with those fixes being addressed in commits
("usb: hub: Fix usb enumeration issue due to address0 race")
("usb: hub: Fix locking issues with address0_mutex")
the maintainers have stated that they will be reintroducing this commit.
So lets reintroduce it here to fix the issues that users are
experiencing.
[Test Case]
Confirmed by Chris Chiu that this issue exists on similiar hardware
reported by the users and that reverting these reverts fixes the issue
showing no signs of 'couldn't allocate usb_device' and with USB devices
available after boot.
[Regression Potential]
Should be low now that we carry the fixes that seemed to be caused by
this patch series.
There have been reports by some users using certain intel xHCI controllers
that their USB devices are not being detected after boot again after similar
issues were previously found and fixed. This seems to be related to both [1][2]
with the majority of the discussion on [1] about these problems reoccurring.
This bug report is being made more for documentation of this new regression.
These seems to be due to the patchset for [2] being reverted upstream
due to regressions.
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968210/+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 1952222] Re: io_uring regression - lost write request
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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: verification-needed-impish -- 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/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+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 1968591] Re: xfrm interface cannot be changed anymore
This bug is awaiting verification that the linux/5.13.0-41.46 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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: verification-needed-impish -- 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/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+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 1962831] Re: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962831 Title: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification: == [Impact] * KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. * If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. * But this is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. * This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. [Fix] * The following changes since commit dbdbd581976f9dfcc9e21a777273b55bdb9bf138: UBUNTU: Ubuntu-5.4.0-102.115 (2022-02-23 15:32:05 +0100) are available in the Git repository at: https://git.launchpad.net/~fheimes/+git/lp1962831/ 16c0809cf1012e68279a8936a482c1d63cc4d14c for you to fetch changes up to 16c0809cf1012e68279a8936a482c1d63cc4d14c: KVM: s390: Add missing vm MEM_OP size check (2022-03-03 22:45:50 +0100) * Patches are upstream accepted (but some are as of today still in linux-next). * Notes on why the backports are needed are included in the provenance of the corresponding commit. [Test Case] * An IBM z13 or LinuxONE system is needed running Ubuntu Server 20.04 with QEMU/KVM setup. * These modification here are covered by the following three tests: * [kvm-unit-tests,v2] s390x: Test effect of storage keys on some instructions https://patchwork.kernel.org/project/kvm/patch/20220301095059.3026178-1-s...@linux.ibm.com/ * [PATCH v2 0/5] memop selftest for storage key checking https://lore.kernel.org/kvm/20220225155311.3540514-1-s...@linux.ibm.com/ * c7ef9ebbed20 "KVM: s390: selftests: Test TEST PROTECTION emulation" * The tests and the verification will be done by the IBM Z team. * On top a test build is available (see below). [Where problems could occur] * Issues with vm ioctl may occur due to the introduction of _vm_ioctl. * Tests may fail or may report wrong states due to the new TEST_FAIL macro in tests/utilities or due to new variants of GUEST_ASSERT in selftests. * Problems on gaccess might be caused due to the refactoring of gpa, length calculation, access address range check and the new access_guest_page helper function. * In uaccess issues may occur due to the introduction of the bit field for OAC specifier, that causes lot's but relatively straight forward changes or due to the new storage key checking functions copy_from/to_user_key functions. * Compile issues may happen if the changes in uaccess.h bout z10 features are erroneous. * Instructions that are emulated by KVM might be impacted due to the expanded storage key checking, that now covers intercepted instructions, too. This is the most significant modification in terms of size and complexity and therefore carries the highest risk. * MEM_OP IOCTL could be harmed due to the additional, but optional, storage key extension and checking, or the new size check and I/O emulation can be impacted due to the new vm IOCTL for key checked guest memory access. * Some tests were added to mitigate this, like the selftests TEST PROTECTION. * The renaming of the existing vcpu memop functions shouldn't be very harmful, since issues will already occur test build. * The rest are API documentation updates and clarifications. * Except two include/header changes and changes in tools/testing all other modifications are s390x specific [Other] * It was ensured that these changes are in jammy based on LP#1933179. __ Description: KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. This is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. This item will add the missing key checking to
[Kernel-packages] [Bug 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962578 Title: [UBUNTU 20.04] Fix SIGP processing on KVM/s390 Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification: == [Impact] * The SIGP processing on KVM/s390x is incorrect and not fully conform to the 'Principles of Operations', the IBM Z architecture definition and documentation. * KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. * The fix for this consists of three patches: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" whereas 812de04661c4 already landed via upstream stable, hence only two are left and need to be cherry-picked: [Fix] * 67cf68b6a5ccac8bc7dfef0a220b59af4c83fd2c 67cf68b6a5cc "KVM: s390: Add a routine for setting userspace CPU state" * 8eeba194a32e0f50329354a696baaa2e3d9accc5 8eeba194a32e "KVM: s390: Simplify SIGP Set Arch handling" [Test Case] * Install an LPAR on IBM Z (z13+) or LinuxONE (Emperor / Rockhopper) with Ubuntu Server 20.04 using kernel standard kernel 5.4. * Setup this LPAR as QEMU/KVM host and a focal VM as guest. * The test itself is the following unit test: https://lore.kernel.org/r/20220303210425.1693486-1-far...@linux.ibm.com/ * The test and verification will be done by the IBM Z team. [Where problems could occur] * A broken patch could harm KVM ioctl on s390x or the (virtual) CPU state control in general. * The SIGP handing (on s390x) can become broken, which could lead to incorrect (virtual) CPU states. * In worst case KVM can become broken on s390x entirely. * The modified code is all s390x specific QEMU/KVM code, no common code is touched. [Other] * The two remaining patches are upstream since 5.16, the first one already landed in 5.4 via upstream stable bug LP#1959701 and in 5.13 via upstream stable bug LP#1960861. * The patches already landed in jammy (master-next) based on LP#1959735, hence only SRU to impish and focal is needed. * This patches got discussed here: https://lore.kernel.org/all/20211008203112.1979843-2-far...@linux.ibm.com/ * This not only fixes the SIGP processing, but is also important in terms of long term maintainability. __ Description: KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. The patches to fix this have already been picked for jammy/master- next: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" For Ubuntu 20.04 the focal/master-next already contains: d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART so we additionally need the following two upstream commits in focal 67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state 8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1962578/+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 1925421] Re: arm64 support
This bug was fixed in the package linux-gcp - 5.4.0-1072.77
---
linux-gcp (5.4.0-1072.77) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1072.77 -proposed tracker (LP: #1968829)
* Miscellaneous Ubuntu changes
- [packaging] Update annotations for arm64
- [packaging] update getabis for arm64
- [packaging] Fix annotations file
- [config] Update config for arm64
[ Ubuntu: 5.4.0-109.123 ]
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux-gcp (5.4.0-1071.76) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1071.76 -proposed tracker (LP: #1967374)
* Update gvnic driver code (LP: #1953575)
- netdev: pass the stuck queue to the timeout handler
- gve: Get and set Rx copybreak via ethtool
- gve: Add stats for gve.
- gve: Use dev_info/err instead of netif_info/err.
- gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags.
- gve: NIC stats for report-stats and for ethtool
- gve: Batch AQ commands for creating and destroying queues.
- gve: Use link status register to report link status
- gve: Enable Link Speed Reporting in the driver.
- gve: Replace zero-length array with flexible-array member
- gve: Add support for raw addressing device option
- gve: Add support for raw addressing to the rx path
- gve: Rx Buffer Recycling
- net: gve: convert strlcpy to strscpy
- net: gve: remove duplicated allowed
- gve: Move some static functions to a common file
- gve: gve_rx_copy: Move padding to an argument
- gve: Make gve_rx_slot_page_info.page_offset an absolute offset
- SAUCE: Revert "gve: Check TX QPL was actually assigned"
- gve: Add support for raw addressing in the tx path
- gve: Introduce a new model for device options
- gve: Introduce per netdev `enum gve_queue_format`
- gve: adminq: DQO specific device descriptor logic
- gve: Add support for DQO RX PTYPE map
- gve: Add dqo descriptors
- gve: Add DQO fields for core data structures
- gve: Update adminq commands to support DQO queues
- gve: DQO: Add core netdev features
- gve: DQO: Add ring allocation and initialization
- gve: DQO: Configure interrupts on device up
- gve: DQO: Add TX path
- gve: DQO: Add RX path
- gve: Fix warnings reported for DQO patchset
- gve: DQO: Fix off by one in gve_rx_dqo()
- gve: Propagate error codes to caller
- gve: Simplify code and axe the use of a deprecated API
- gve: DQO: Remove incorrect prefetch
- gve: fix the wrong AdminQ buffer overflow check
- gve: DQO: avoid unused variable warnings
- gve: Check TX QPL was actually assigned
- gve: Avoid freeing NULL pointer
- gve: Properly handle errors in gve_assign_qpl
- gve: report 64bit tx_bytes counter from gve_handle_report_stats()
- gve: Switch to use napi_complete_done
- gve: Add rx buffer pagecnt bias
- gve: Do lazy cleanup in TX path
- gve: Recover from queue stall due to missed IRQ
- gve: Add netif_set_xps_queue call
- gve: Allow pageflips on larger pages
- gve: Track RX buffer allocation failures
- gve: Add RX context.
- gve: Implement packet continuation for RX.
- gve: Add a jumbo-frame device option.
- gve: Fix off by one in gve_tx_timeout()
- gve: fix unmatched u64_stats_update_end()
- gve: fix for null pointer dereference.
- gve: Correct order of processing device options
- gve: Add optional metadata descriptor type GVE_TXD_MTD
- gve: Move the irq db indexes out of the ntfy block struct
- gve: Update gve_free_queue_page_list signature
- gve: remove memory barrier around seqno
- gve: Implement suspend/resume/shutdown
- gve: Add consumed counts to ethtool stats
- gve: Add tx|rx-coalesce-usec for DQO
- gve: Use kvcalloc() instead of kvzalloc()
[ Ubuntu: 5.4.0-108.122 ]
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit
[Kernel-packages] [Bug 1953575] Re: Update gvnic driver code
This bug was fixed in the package linux-gcp - 5.4.0-1072.77
---
linux-gcp (5.4.0-1072.77) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1072.77 -proposed tracker (LP: #1968829)
* Miscellaneous Ubuntu changes
- [packaging] Update annotations for arm64
- [packaging] update getabis for arm64
- [packaging] Fix annotations file
- [config] Update config for arm64
[ Ubuntu: 5.4.0-109.123 ]
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux-gcp (5.4.0-1071.76) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1071.76 -proposed tracker (LP: #1967374)
* Update gvnic driver code (LP: #1953575)
- netdev: pass the stuck queue to the timeout handler
- gve: Get and set Rx copybreak via ethtool
- gve: Add stats for gve.
- gve: Use dev_info/err instead of netif_info/err.
- gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags.
- gve: NIC stats for report-stats and for ethtool
- gve: Batch AQ commands for creating and destroying queues.
- gve: Use link status register to report link status
- gve: Enable Link Speed Reporting in the driver.
- gve: Replace zero-length array with flexible-array member
- gve: Add support for raw addressing device option
- gve: Add support for raw addressing to the rx path
- gve: Rx Buffer Recycling
- net: gve: convert strlcpy to strscpy
- net: gve: remove duplicated allowed
- gve: Move some static functions to a common file
- gve: gve_rx_copy: Move padding to an argument
- gve: Make gve_rx_slot_page_info.page_offset an absolute offset
- SAUCE: Revert "gve: Check TX QPL was actually assigned"
- gve: Add support for raw addressing in the tx path
- gve: Introduce a new model for device options
- gve: Introduce per netdev `enum gve_queue_format`
- gve: adminq: DQO specific device descriptor logic
- gve: Add support for DQO RX PTYPE map
- gve: Add dqo descriptors
- gve: Add DQO fields for core data structures
- gve: Update adminq commands to support DQO queues
- gve: DQO: Add core netdev features
- gve: DQO: Add ring allocation and initialization
- gve: DQO: Configure interrupts on device up
- gve: DQO: Add TX path
- gve: DQO: Add RX path
- gve: Fix warnings reported for DQO patchset
- gve: DQO: Fix off by one in gve_rx_dqo()
- gve: Propagate error codes to caller
- gve: Simplify code and axe the use of a deprecated API
- gve: DQO: Remove incorrect prefetch
- gve: fix the wrong AdminQ buffer overflow check
- gve: DQO: avoid unused variable warnings
- gve: Check TX QPL was actually assigned
- gve: Avoid freeing NULL pointer
- gve: Properly handle errors in gve_assign_qpl
- gve: report 64bit tx_bytes counter from gve_handle_report_stats()
- gve: Switch to use napi_complete_done
- gve: Add rx buffer pagecnt bias
- gve: Do lazy cleanup in TX path
- gve: Recover from queue stall due to missed IRQ
- gve: Add netif_set_xps_queue call
- gve: Allow pageflips on larger pages
- gve: Track RX buffer allocation failures
- gve: Add RX context.
- gve: Implement packet continuation for RX.
- gve: Add a jumbo-frame device option.
- gve: Fix off by one in gve_tx_timeout()
- gve: fix unmatched u64_stats_update_end()
- gve: fix for null pointer dereference.
- gve: Correct order of processing device options
- gve: Add optional metadata descriptor type GVE_TXD_MTD
- gve: Move the irq db indexes out of the ntfy block struct
- gve: Update gve_free_queue_page_list signature
- gve: remove memory barrier around seqno
- gve: Implement suspend/resume/shutdown
- gve: Add consumed counts to ethtool stats
- gve: Add tx|rx-coalesce-usec for DQO
- gve: Use kvcalloc() instead of kvzalloc()
[ Ubuntu: 5.4.0-108.122 ]
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit
[Kernel-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36 --- linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP: #1967397) * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * Fix non-working MT7921 BT after reboot (LP: #1966497) - Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921) * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * Enable headset mic on Lenovo P360 (LP: #1967069) - ALSA: hda/realtek: Enable headset mic on Lenovo P360 * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Focal update: upstream stable patchset 2022-03-21 (LP: #1965737) - mm/filemap: Fix handling of THPs in generic_file_buffered_read() - cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug - cgroup-v1: Correct privileges check in release_agent writes - x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing - btrfs: tree-checker: check item_size for inode_item - btrfs: tree-checker: check item_size for dev_item - clk: jz4725b: fix mmc0 clock gating - io_uring: don't convert to jiffies for waiting on timeouts - io_uring: disallow modification of rsrc_data during quiesce - selinux: fix misuse of mutex_is_locked() - vhost/vsock: don't check owner in vhost_vsock_stop() while releasing - parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel - parisc/unaligned: Fix ldw() and stw() unalignment handlers - KVM: x86/mmu: make apf token non-zero to fix bug - drm/amd/display: Protect update_bw_bounding_box FPU code. - drm/amd/pm: fix some OEM SKU specific stability issues - drm/amdgpu: disable MMHUB PG for Picasso - drm/amdgpu: do not enable asic reset for raven2 - drm/i915: Widen the QGV point mask - drm/i915: Correctly populate use_sagv_wm for all pipes - drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV - sr9700: sanity check for packet length - USB: zaurus: support another broken Zaurus - CDC-NCM: avoid overflow in sanity checking - netfilter: xt_socket: fix a typo in socket_mt_destroy() - netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency - tee: export teedev_open() and teedev_close_context() - optee: use driver internal tee_context for some rpc - ping: remove pr_err from ping_lookup - Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC" - gpu: host1x: Always return syncpoint value when waiting - perf data: Fix double free in perf_session__delete() - mptcp: fix race in incoming ADD_ADDR option processing - mptcp: add mibs counter for ignored incoming options - selftests: mptcp: fix diag instability - selftests: mptcp: be more conservative with cookie MPJ limits - bnx2x: fix driver load from initrd - bnxt_en: Fix active FEC reporting to ethtool - bnxt_en: Fix offline ethtool selftest with RDMA enabled - bnxt_en: Fix incorrect multicast rx mask setting when not requested - hwmon: Handle failure to register sensor with thermal zone correctly - net/mlx5: Fix tc max supported prio for nic mode - ice: check the return of ice_ptp_gettimex64 - ice: initialize local variable 'tlv' - net/mlx5: Update the list of the PCI supported devices - bpf: Do not try bpf_msg_push_data with len 0 - selftests: bpf: Check bpf_msg_push_data return value - bpf: Add schedule points in batch ops - io_uring: add a schedule point in io_add_buffers() - net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends - tipc: Fix end of loop tests for list_for_each_entry() - gso: do not skip outer ip header in case of ipip and net_failover - net: mv643xx_eth: process retval from of_get_mac_address - openvswitch: Fix setting ipv6 fields causing hw csum failure - drm/edid: Always set RGB444 - net/mlx5e: Fix wrong return value on ioctl EEPROM query failure - drm/vc4: crtc: Fix runtime_pm reference counting - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones - net: ll_temac: check the return value of devm_kmalloc() - net: Force inlining of checksum functions in net/checksum.h - netfilter: nf_tables: unregister flowtable hooks on netns exit - nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() - netfilter: nf_tables: fix memory leak during stateful obj update - net/smc: Use a mutex for locking "struct smc_pnettable" - surface:
[Kernel-packages] [Bug 1964850] Re: Choppy trackpad/USB mouse behavior with oem-1023 or above kernel version
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36 --- linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP: #1967397) * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * Fix non-working MT7921 BT after reboot (LP: #1966497) - Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921) * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * Enable headset mic on Lenovo P360 (LP: #1967069) - ALSA: hda/realtek: Enable headset mic on Lenovo P360 * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Focal update: upstream stable patchset 2022-03-21 (LP: #1965737) - mm/filemap: Fix handling of THPs in generic_file_buffered_read() - cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug - cgroup-v1: Correct privileges check in release_agent writes - x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing - btrfs: tree-checker: check item_size for inode_item - btrfs: tree-checker: check item_size for dev_item - clk: jz4725b: fix mmc0 clock gating - io_uring: don't convert to jiffies for waiting on timeouts - io_uring: disallow modification of rsrc_data during quiesce - selinux: fix misuse of mutex_is_locked() - vhost/vsock: don't check owner in vhost_vsock_stop() while releasing - parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel - parisc/unaligned: Fix ldw() and stw() unalignment handlers - KVM: x86/mmu: make apf token non-zero to fix bug - drm/amd/display: Protect update_bw_bounding_box FPU code. - drm/amd/pm: fix some OEM SKU specific stability issues - drm/amdgpu: disable MMHUB PG for Picasso - drm/amdgpu: do not enable asic reset for raven2 - drm/i915: Widen the QGV point mask - drm/i915: Correctly populate use_sagv_wm for all pipes - drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV - sr9700: sanity check for packet length - USB: zaurus: support another broken Zaurus - CDC-NCM: avoid overflow in sanity checking - netfilter: xt_socket: fix a typo in socket_mt_destroy() - netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency - tee: export teedev_open() and teedev_close_context() - optee: use driver internal tee_context for some rpc - ping: remove pr_err from ping_lookup - Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC" - gpu: host1x: Always return syncpoint value when waiting - perf data: Fix double free in perf_session__delete() - mptcp: fix race in incoming ADD_ADDR option processing - mptcp: add mibs counter for ignored incoming options - selftests: mptcp: fix diag instability - selftests: mptcp: be more conservative with cookie MPJ limits - bnx2x: fix driver load from initrd - bnxt_en: Fix active FEC reporting to ethtool - bnxt_en: Fix offline ethtool selftest with RDMA enabled - bnxt_en: Fix incorrect multicast rx mask setting when not requested - hwmon: Handle failure to register sensor with thermal zone correctly - net/mlx5: Fix tc max supported prio for nic mode - ice: check the return of ice_ptp_gettimex64 - ice: initialize local variable 'tlv' - net/mlx5: Update the list of the PCI supported devices - bpf: Do not try bpf_msg_push_data with len 0 - selftests: bpf: Check bpf_msg_push_data return value - bpf: Add schedule points in batch ops - io_uring: add a schedule point in io_add_buffers() - net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends - tipc: Fix end of loop tests for list_for_each_entry() - gso: do not skip outer ip header in case of ipip and net_failover - net: mv643xx_eth: process retval from of_get_mac_address - openvswitch: Fix setting ipv6 fields causing hw csum failure - drm/edid: Always set RGB444 - net/mlx5e: Fix wrong return value on ioctl EEPROM query failure - drm/vc4: crtc: Fix runtime_pm reference counting - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones - net: ll_temac: check the return value of devm_kmalloc() - net: Force inlining of checksum functions in net/checksum.h - netfilter: nf_tables: unregister flowtable hooks on netns exit - nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() - netfilter: nf_tables: fix memory leak during stateful obj update - net/smc: Use a mutex for locking "struct smc_pnettable" - surface:
[Kernel-packages] [Bug 1965080] Re: Mute/mic LEDs no function on some HP platfroms
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36 --- linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP: #1967397) * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * Fix non-working MT7921 BT after reboot (LP: #1966497) - Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921) * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * Enable headset mic on Lenovo P360 (LP: #1967069) - ALSA: hda/realtek: Enable headset mic on Lenovo P360 * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Focal update: upstream stable patchset 2022-03-21 (LP: #1965737) - mm/filemap: Fix handling of THPs in generic_file_buffered_read() - cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug - cgroup-v1: Correct privileges check in release_agent writes - x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing - btrfs: tree-checker: check item_size for inode_item - btrfs: tree-checker: check item_size for dev_item - clk: jz4725b: fix mmc0 clock gating - io_uring: don't convert to jiffies for waiting on timeouts - io_uring: disallow modification of rsrc_data during quiesce - selinux: fix misuse of mutex_is_locked() - vhost/vsock: don't check owner in vhost_vsock_stop() while releasing - parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel - parisc/unaligned: Fix ldw() and stw() unalignment handlers - KVM: x86/mmu: make apf token non-zero to fix bug - drm/amd/display: Protect update_bw_bounding_box FPU code. - drm/amd/pm: fix some OEM SKU specific stability issues - drm/amdgpu: disable MMHUB PG for Picasso - drm/amdgpu: do not enable asic reset for raven2 - drm/i915: Widen the QGV point mask - drm/i915: Correctly populate use_sagv_wm for all pipes - drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV - sr9700: sanity check for packet length - USB: zaurus: support another broken Zaurus - CDC-NCM: avoid overflow in sanity checking - netfilter: xt_socket: fix a typo in socket_mt_destroy() - netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency - tee: export teedev_open() and teedev_close_context() - optee: use driver internal tee_context for some rpc - ping: remove pr_err from ping_lookup - Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC" - gpu: host1x: Always return syncpoint value when waiting - perf data: Fix double free in perf_session__delete() - mptcp: fix race in incoming ADD_ADDR option processing - mptcp: add mibs counter for ignored incoming options - selftests: mptcp: fix diag instability - selftests: mptcp: be more conservative with cookie MPJ limits - bnx2x: fix driver load from initrd - bnxt_en: Fix active FEC reporting to ethtool - bnxt_en: Fix offline ethtool selftest with RDMA enabled - bnxt_en: Fix incorrect multicast rx mask setting when not requested - hwmon: Handle failure to register sensor with thermal zone correctly - net/mlx5: Fix tc max supported prio for nic mode - ice: check the return of ice_ptp_gettimex64 - ice: initialize local variable 'tlv' - net/mlx5: Update the list of the PCI supported devices - bpf: Do not try bpf_msg_push_data with len 0 - selftests: bpf: Check bpf_msg_push_data return value - bpf: Add schedule points in batch ops - io_uring: add a schedule point in io_add_buffers() - net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends - tipc: Fix end of loop tests for list_for_each_entry() - gso: do not skip outer ip header in case of ipip and net_failover - net: mv643xx_eth: process retval from of_get_mac_address - openvswitch: Fix setting ipv6 fields causing hw csum failure - drm/edid: Always set RGB444 - net/mlx5e: Fix wrong return value on ioctl EEPROM query failure - drm/vc4: crtc: Fix runtime_pm reference counting - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones - net: ll_temac: check the return value of devm_kmalloc() - net: Force inlining of checksum functions in net/checksum.h - netfilter: nf_tables: unregister flowtable hooks on netns exit - nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() - netfilter: nf_tables: fix memory leak during stateful obj update - net/smc: Use a mutex for locking "struct smc_pnettable" - surface:
[Kernel-packages] [Bug 1965737] Re: Focal update: upstream stable patchset 2022-03-21
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36 --- linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP: #1967397) * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * Fix non-working MT7921 BT after reboot (LP: #1966497) - Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921) * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * Enable headset mic on Lenovo P360 (LP: #1967069) - ALSA: hda/realtek: Enable headset mic on Lenovo P360 * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Focal update: upstream stable patchset 2022-03-21 (LP: #1965737) - mm/filemap: Fix handling of THPs in generic_file_buffered_read() - cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug - cgroup-v1: Correct privileges check in release_agent writes - x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing - btrfs: tree-checker: check item_size for inode_item - btrfs: tree-checker: check item_size for dev_item - clk: jz4725b: fix mmc0 clock gating - io_uring: don't convert to jiffies for waiting on timeouts - io_uring: disallow modification of rsrc_data during quiesce - selinux: fix misuse of mutex_is_locked() - vhost/vsock: don't check owner in vhost_vsock_stop() while releasing - parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel - parisc/unaligned: Fix ldw() and stw() unalignment handlers - KVM: x86/mmu: make apf token non-zero to fix bug - drm/amd/display: Protect update_bw_bounding_box FPU code. - drm/amd/pm: fix some OEM SKU specific stability issues - drm/amdgpu: disable MMHUB PG for Picasso - drm/amdgpu: do not enable asic reset for raven2 - drm/i915: Widen the QGV point mask - drm/i915: Correctly populate use_sagv_wm for all pipes - drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV - sr9700: sanity check for packet length - USB: zaurus: support another broken Zaurus - CDC-NCM: avoid overflow in sanity checking - netfilter: xt_socket: fix a typo in socket_mt_destroy() - netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency - tee: export teedev_open() and teedev_close_context() - optee: use driver internal tee_context for some rpc - ping: remove pr_err from ping_lookup - Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC" - gpu: host1x: Always return syncpoint value when waiting - perf data: Fix double free in perf_session__delete() - mptcp: fix race in incoming ADD_ADDR option processing - mptcp: add mibs counter for ignored incoming options - selftests: mptcp: fix diag instability - selftests: mptcp: be more conservative with cookie MPJ limits - bnx2x: fix driver load from initrd - bnxt_en: Fix active FEC reporting to ethtool - bnxt_en: Fix offline ethtool selftest with RDMA enabled - bnxt_en: Fix incorrect multicast rx mask setting when not requested - hwmon: Handle failure to register sensor with thermal zone correctly - net/mlx5: Fix tc max supported prio for nic mode - ice: check the return of ice_ptp_gettimex64 - ice: initialize local variable 'tlv' - net/mlx5: Update the list of the PCI supported devices - bpf: Do not try bpf_msg_push_data with len 0 - selftests: bpf: Check bpf_msg_push_data return value - bpf: Add schedule points in batch ops - io_uring: add a schedule point in io_add_buffers() - net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends - tipc: Fix end of loop tests for list_for_each_entry() - gso: do not skip outer ip header in case of ipip and net_failover - net: mv643xx_eth: process retval from of_get_mac_address - openvswitch: Fix setting ipv6 fields causing hw csum failure - drm/edid: Always set RGB444 - net/mlx5e: Fix wrong return value on ioctl EEPROM query failure - drm/vc4: crtc: Fix runtime_pm reference counting - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones - net: ll_temac: check the return value of devm_kmalloc() - net: Force inlining of checksum functions in net/checksum.h - netfilter: nf_tables: unregister flowtable hooks on netns exit - nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() - netfilter: nf_tables: fix memory leak during stateful obj update - net/smc: Use a mutex for locking "struct smc_pnettable" - surface:
[Kernel-packages] [Bug 1966497] Re: Fix non-working MT7921 BT after reboot
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36 --- linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP: #1967397) * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * Fix non-working MT7921 BT after reboot (LP: #1966497) - Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921) * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * Enable headset mic on Lenovo P360 (LP: #1967069) - ALSA: hda/realtek: Enable headset mic on Lenovo P360 * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Focal update: upstream stable patchset 2022-03-21 (LP: #1965737) - mm/filemap: Fix handling of THPs in generic_file_buffered_read() - cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug - cgroup-v1: Correct privileges check in release_agent writes - x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing - btrfs: tree-checker: check item_size for inode_item - btrfs: tree-checker: check item_size for dev_item - clk: jz4725b: fix mmc0 clock gating - io_uring: don't convert to jiffies for waiting on timeouts - io_uring: disallow modification of rsrc_data during quiesce - selinux: fix misuse of mutex_is_locked() - vhost/vsock: don't check owner in vhost_vsock_stop() while releasing - parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel - parisc/unaligned: Fix ldw() and stw() unalignment handlers - KVM: x86/mmu: make apf token non-zero to fix bug - drm/amd/display: Protect update_bw_bounding_box FPU code. - drm/amd/pm: fix some OEM SKU specific stability issues - drm/amdgpu: disable MMHUB PG for Picasso - drm/amdgpu: do not enable asic reset for raven2 - drm/i915: Widen the QGV point mask - drm/i915: Correctly populate use_sagv_wm for all pipes - drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV - sr9700: sanity check for packet length - USB: zaurus: support another broken Zaurus - CDC-NCM: avoid overflow in sanity checking - netfilter: xt_socket: fix a typo in socket_mt_destroy() - netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency - tee: export teedev_open() and teedev_close_context() - optee: use driver internal tee_context for some rpc - ping: remove pr_err from ping_lookup - Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC" - gpu: host1x: Always return syncpoint value when waiting - perf data: Fix double free in perf_session__delete() - mptcp: fix race in incoming ADD_ADDR option processing - mptcp: add mibs counter for ignored incoming options - selftests: mptcp: fix diag instability - selftests: mptcp: be more conservative with cookie MPJ limits - bnx2x: fix driver load from initrd - bnxt_en: Fix active FEC reporting to ethtool - bnxt_en: Fix offline ethtool selftest with RDMA enabled - bnxt_en: Fix incorrect multicast rx mask setting when not requested - hwmon: Handle failure to register sensor with thermal zone correctly - net/mlx5: Fix tc max supported prio for nic mode - ice: check the return of ice_ptp_gettimex64 - ice: initialize local variable 'tlv' - net/mlx5: Update the list of the PCI supported devices - bpf: Do not try bpf_msg_push_data with len 0 - selftests: bpf: Check bpf_msg_push_data return value - bpf: Add schedule points in batch ops - io_uring: add a schedule point in io_add_buffers() - net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends - tipc: Fix end of loop tests for list_for_each_entry() - gso: do not skip outer ip header in case of ipip and net_failover - net: mv643xx_eth: process retval from of_get_mac_address - openvswitch: Fix setting ipv6 fields causing hw csum failure - drm/edid: Always set RGB444 - net/mlx5e: Fix wrong return value on ioctl EEPROM query failure - drm/vc4: crtc: Fix runtime_pm reference counting - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones - net: ll_temac: check the return value of devm_kmalloc() - net: Force inlining of checksum functions in net/checksum.h - netfilter: nf_tables: unregister flowtable hooks on netns exit - nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() - netfilter: nf_tables: fix memory leak during stateful obj update - net/smc: Use a mutex for locking "struct smc_pnettable" - surface:
[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36 --- linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP: #1967397) * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * Fix non-working MT7921 BT after reboot (LP: #1966497) - Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921) * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * Enable headset mic on Lenovo P360 (LP: #1967069) - ALSA: hda/realtek: Enable headset mic on Lenovo P360 * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Focal update: upstream stable patchset 2022-03-21 (LP: #1965737) - mm/filemap: Fix handling of THPs in generic_file_buffered_read() - cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug - cgroup-v1: Correct privileges check in release_agent writes - x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing - btrfs: tree-checker: check item_size for inode_item - btrfs: tree-checker: check item_size for dev_item - clk: jz4725b: fix mmc0 clock gating - io_uring: don't convert to jiffies for waiting on timeouts - io_uring: disallow modification of rsrc_data during quiesce - selinux: fix misuse of mutex_is_locked() - vhost/vsock: don't check owner in vhost_vsock_stop() while releasing - parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel - parisc/unaligned: Fix ldw() and stw() unalignment handlers - KVM: x86/mmu: make apf token non-zero to fix bug - drm/amd/display: Protect update_bw_bounding_box FPU code. - drm/amd/pm: fix some OEM SKU specific stability issues - drm/amdgpu: disable MMHUB PG for Picasso - drm/amdgpu: do not enable asic reset for raven2 - drm/i915: Widen the QGV point mask - drm/i915: Correctly populate use_sagv_wm for all pipes - drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV - sr9700: sanity check for packet length - USB: zaurus: support another broken Zaurus - CDC-NCM: avoid overflow in sanity checking - netfilter: xt_socket: fix a typo in socket_mt_destroy() - netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency - tee: export teedev_open() and teedev_close_context() - optee: use driver internal tee_context for some rpc - ping: remove pr_err from ping_lookup - Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC" - gpu: host1x: Always return syncpoint value when waiting - perf data: Fix double free in perf_session__delete() - mptcp: fix race in incoming ADD_ADDR option processing - mptcp: add mibs counter for ignored incoming options - selftests: mptcp: fix diag instability - selftests: mptcp: be more conservative with cookie MPJ limits - bnx2x: fix driver load from initrd - bnxt_en: Fix active FEC reporting to ethtool - bnxt_en: Fix offline ethtool selftest with RDMA enabled - bnxt_en: Fix incorrect multicast rx mask setting when not requested - hwmon: Handle failure to register sensor with thermal zone correctly - net/mlx5: Fix tc max supported prio for nic mode - ice: check the return of ice_ptp_gettimex64 - ice: initialize local variable 'tlv' - net/mlx5: Update the list of the PCI supported devices - bpf: Do not try bpf_msg_push_data with len 0 - selftests: bpf: Check bpf_msg_push_data return value - bpf: Add schedule points in batch ops - io_uring: add a schedule point in io_add_buffers() - net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends - tipc: Fix end of loop tests for list_for_each_entry() - gso: do not skip outer ip header in case of ipip and net_failover - net: mv643xx_eth: process retval from of_get_mac_address - openvswitch: Fix setting ipv6 fields causing hw csum failure - drm/edid: Always set RGB444 - net/mlx5e: Fix wrong return value on ioctl EEPROM query failure - drm/vc4: crtc: Fix runtime_pm reference counting - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones - net: ll_temac: check the return value of devm_kmalloc() - net: Force inlining of checksum functions in net/checksum.h - netfilter: nf_tables: unregister flowtable hooks on netns exit - nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() - netfilter: nf_tables: fix memory leak during stateful obj update - net/smc: Use a mutex for locking "struct smc_pnettable" - surface:
[Kernel-packages] [Bug 1967069] Re: Enable headset mic on Lenovo P360
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36 --- linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP: #1967397) * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * Fix non-working MT7921 BT after reboot (LP: #1966497) - Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921) * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * Enable headset mic on Lenovo P360 (LP: #1967069) - ALSA: hda/realtek: Enable headset mic on Lenovo P360 * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Focal update: upstream stable patchset 2022-03-21 (LP: #1965737) - mm/filemap: Fix handling of THPs in generic_file_buffered_read() - cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug - cgroup-v1: Correct privileges check in release_agent writes - x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing - btrfs: tree-checker: check item_size for inode_item - btrfs: tree-checker: check item_size for dev_item - clk: jz4725b: fix mmc0 clock gating - io_uring: don't convert to jiffies for waiting on timeouts - io_uring: disallow modification of rsrc_data during quiesce - selinux: fix misuse of mutex_is_locked() - vhost/vsock: don't check owner in vhost_vsock_stop() while releasing - parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel - parisc/unaligned: Fix ldw() and stw() unalignment handlers - KVM: x86/mmu: make apf token non-zero to fix bug - drm/amd/display: Protect update_bw_bounding_box FPU code. - drm/amd/pm: fix some OEM SKU specific stability issues - drm/amdgpu: disable MMHUB PG for Picasso - drm/amdgpu: do not enable asic reset for raven2 - drm/i915: Widen the QGV point mask - drm/i915: Correctly populate use_sagv_wm for all pipes - drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV - sr9700: sanity check for packet length - USB: zaurus: support another broken Zaurus - CDC-NCM: avoid overflow in sanity checking - netfilter: xt_socket: fix a typo in socket_mt_destroy() - netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency - tee: export teedev_open() and teedev_close_context() - optee: use driver internal tee_context for some rpc - ping: remove pr_err from ping_lookup - Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC" - gpu: host1x: Always return syncpoint value when waiting - perf data: Fix double free in perf_session__delete() - mptcp: fix race in incoming ADD_ADDR option processing - mptcp: add mibs counter for ignored incoming options - selftests: mptcp: fix diag instability - selftests: mptcp: be more conservative with cookie MPJ limits - bnx2x: fix driver load from initrd - bnxt_en: Fix active FEC reporting to ethtool - bnxt_en: Fix offline ethtool selftest with RDMA enabled - bnxt_en: Fix incorrect multicast rx mask setting when not requested - hwmon: Handle failure to register sensor with thermal zone correctly - net/mlx5: Fix tc max supported prio for nic mode - ice: check the return of ice_ptp_gettimex64 - ice: initialize local variable 'tlv' - net/mlx5: Update the list of the PCI supported devices - bpf: Do not try bpf_msg_push_data with len 0 - selftests: bpf: Check bpf_msg_push_data return value - bpf: Add schedule points in batch ops - io_uring: add a schedule point in io_add_buffers() - net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends - tipc: Fix end of loop tests for list_for_each_entry() - gso: do not skip outer ip header in case of ipip and net_failover - net: mv643xx_eth: process retval from of_get_mac_address - openvswitch: Fix setting ipv6 fields causing hw csum failure - drm/edid: Always set RGB444 - net/mlx5e: Fix wrong return value on ioctl EEPROM query failure - drm/vc4: crtc: Fix runtime_pm reference counting - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones - net: ll_temac: check the return value of devm_kmalloc() - net: Force inlining of checksum functions in net/checksum.h - netfilter: nf_tables: unregister flowtable hooks on netns exit - nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() - netfilter: nf_tables: fix memory leak during stateful obj update - net/smc: Use a mutex for locking "struct smc_pnettable" - surface:
[Kernel-packages] [Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36 --- linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP: #1967397) * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * Fix non-working MT7921 BT after reboot (LP: #1966497) - Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921) * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * Enable headset mic on Lenovo P360 (LP: #1967069) - ALSA: hda/realtek: Enable headset mic on Lenovo P360 * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Focal update: upstream stable patchset 2022-03-21 (LP: #1965737) - mm/filemap: Fix handling of THPs in generic_file_buffered_read() - cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug - cgroup-v1: Correct privileges check in release_agent writes - x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing - btrfs: tree-checker: check item_size for inode_item - btrfs: tree-checker: check item_size for dev_item - clk: jz4725b: fix mmc0 clock gating - io_uring: don't convert to jiffies for waiting on timeouts - io_uring: disallow modification of rsrc_data during quiesce - selinux: fix misuse of mutex_is_locked() - vhost/vsock: don't check owner in vhost_vsock_stop() while releasing - parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel - parisc/unaligned: Fix ldw() and stw() unalignment handlers - KVM: x86/mmu: make apf token non-zero to fix bug - drm/amd/display: Protect update_bw_bounding_box FPU code. - drm/amd/pm: fix some OEM SKU specific stability issues - drm/amdgpu: disable MMHUB PG for Picasso - drm/amdgpu: do not enable asic reset for raven2 - drm/i915: Widen the QGV point mask - drm/i915: Correctly populate use_sagv_wm for all pipes - drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV - sr9700: sanity check for packet length - USB: zaurus: support another broken Zaurus - CDC-NCM: avoid overflow in sanity checking - netfilter: xt_socket: fix a typo in socket_mt_destroy() - netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency - tee: export teedev_open() and teedev_close_context() - optee: use driver internal tee_context for some rpc - ping: remove pr_err from ping_lookup - Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC" - gpu: host1x: Always return syncpoint value when waiting - perf data: Fix double free in perf_session__delete() - mptcp: fix race in incoming ADD_ADDR option processing - mptcp: add mibs counter for ignored incoming options - selftests: mptcp: fix diag instability - selftests: mptcp: be more conservative with cookie MPJ limits - bnx2x: fix driver load from initrd - bnxt_en: Fix active FEC reporting to ethtool - bnxt_en: Fix offline ethtool selftest with RDMA enabled - bnxt_en: Fix incorrect multicast rx mask setting when not requested - hwmon: Handle failure to register sensor with thermal zone correctly - net/mlx5: Fix tc max supported prio for nic mode - ice: check the return of ice_ptp_gettimex64 - ice: initialize local variable 'tlv' - net/mlx5: Update the list of the PCI supported devices - bpf: Do not try bpf_msg_push_data with len 0 - selftests: bpf: Check bpf_msg_push_data return value - bpf: Add schedule points in batch ops - io_uring: add a schedule point in io_add_buffers() - net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends - tipc: Fix end of loop tests for list_for_each_entry() - gso: do not skip outer ip header in case of ipip and net_failover - net: mv643xx_eth: process retval from of_get_mac_address - openvswitch: Fix setting ipv6 fields causing hw csum failure - drm/edid: Always set RGB444 - net/mlx5e: Fix wrong return value on ioctl EEPROM query failure - drm/vc4: crtc: Fix runtime_pm reference counting - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones - net: ll_temac: check the return value of devm_kmalloc() - net: Force inlining of checksum functions in net/checksum.h - netfilter: nf_tables: unregister flowtable hooks on netns exit - nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() - netfilter: nf_tables: fix memory leak during stateful obj update - net/smc: Use a mutex for locking "struct smc_pnettable" - surface:
[Kernel-packages] [Bug 1943301] Re: 【sec-0911】 fail to reset sec module
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1962345] Re: Focal update: v5.4.176 upstream stable release
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1962330] Re: Focal update: v5.4.175 upstream stable release
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1962831] Re: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
This bug was fixed in the package nvidia-graphics-drivers-510 - 510.60.02-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Fix regex in modalias addition, since it does not work in dash (LP: #1964756). nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. -- Alberto Milone Thu, 31 Mar 2022 15:33:30 +0200 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Released Status in nvidia-graphics-drivers-510 source package in Impish: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+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 1964634] Re: Focal update: v5.4.178 upstream stable release
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1964756] Re: The nvidia debian/rules mis-compiles Modaliases
This bug was fixed in the package nvidia-graphics-drivers-510 - 510.60.02-0ubuntu0.21.10.2 --- nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.21.10.2) impish; urgency=medium [ Jeremy Szu ] * Fix regex in modalias addition, since it does not work in dash (LP: #1964756) nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.21.10.1) impish; urgency=medium * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. -- Alberto Milone Thu, 31 Mar 2022 15:30:48 +0200 ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1964756 Title: The nvidia debian/rules mis-compiles Modaliases Status in OEM Priority Project: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Impish: Fix Released Bug description: [Impact] The nvidia drivers packaging scripts have a way to add PCI IDs manually to the Modaliases and Pmaliases field in the debian/control. Because of a bug, doing so, only works for the Pmaliases field. [Test Case] 1) Add the proposed repository 2) Look for the following IDs, using apt-cache, making sure they show up for both the Modaliases field and the Pmaliases field: 2438 24BA 24BB 25B9 25BA Something as follows should be enough: apt-cache show nvidia-driver-510 | grep $ID 3) Attach the result. [Regression Potential] This change does not affect anything else in the package other than the modaliases, hence the regression potential is extremely low. [Discussion] [Changelog] __ Although adding support GPU list here: https://github.com/tseliot/nvidia-graphics-drivers/commit/d2533550bc88ef00d6a56f71c4c09e43026a93d7 They are only show in "Pmaliases:" but "Modaliases:". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964756/+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 1964628] Re: Focal update: v5.4.177 upstream stable release
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1964512] Re: Low RX performance for 40G Solarflare NICs
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1965618] Re: linux-azure: Focal 5.4 arm64 support
This bug was fixed in the package linux-azure - 5.4.0-1077.80 --- linux-azure (5.4.0-1077.80) focal; urgency=medium * focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.03.21) * focal/linux-azure: Enable missing config options (LP: #1968749) - Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device - PCI: hv: Propagate coherence from VMbus device to PCI device - [Config] azure: arm64: Ignore module movements - [Config] azure: arm64: Enable RAID config options - [Config] azure: arm64: Enable SQUASHFS config options -- Tim Gardner Tue, 12 Apr 2022 18:53:53 -0600 ** Changed in: linux-azure (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1965618 Title: linux-azure: Focal 5.4 arm64 support Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Released Bug description: SRU Justification [Impact] Focal linux-azure does not support arm64 [Fix] Backport/cherry-pick approximately 100 patches to support arm64 on hyperv [Where things could go wrong] A number of the patches reorganize hyperv CPU support. Therefore amd64 could be affected. [Other Info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1965618/+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 1967336] Re: linux-azure: CONFIG_HIBERNATION=y
This bug was fixed in the package linux-azure - 5.4.0-1077.80 --- linux-azure (5.4.0-1077.80) focal; urgency=medium * focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.03.21) * focal/linux-azure: Enable missing config options (LP: #1968749) - Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device - PCI: hv: Propagate coherence from VMbus device to PCI device - [Config] azure: arm64: Ignore module movements - [Config] azure: arm64: Enable RAID config options - [Config] azure: arm64: Enable SQUASHFS config options -- Tim Gardner Tue, 12 Apr 2022 18:53:53 -0600 ** Changed in: linux-azure (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not support hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+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 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.147-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-390 (390.147-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. -- Alberto Milone Thu, 24 Mar 2022 16:37:55 +0100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Released Status in nvidia-graphics-drivers-510 source package in Impish: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+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 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
This bug was fixed in the package nvidia-graphics-drivers-510 - 510.60.02-0ubuntu0.21.10.2 --- nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.21.10.2) impish; urgency=medium [ Jeremy Szu ] * Fix regex in modalias addition, since it does not work in dash (LP: #1964756) nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.21.10.1) impish; urgency=medium * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. -- Alberto Milone Thu, 31 Mar 2022 15:30:48 +0200 ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Released Status in nvidia-graphics-drivers-510 source package in Impish: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1968564] Re: linux-azure-cvm doesn't currently support arm64
This bug was fixed in the package linux-azure-cvm - 5.4.0-1076.79+cvm1 --- linux-azure-cvm (5.4.0-1076.79+cvm1) focal; urgency=medium * focal/linux-azure-cvm: 5.4.0-1076.79+cvm1 -proposed tracker (LP: #1968347) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.03.21) * linux-azure-cvm doesn't currently support arm64 (LP: #1968564) - Revert "UBUNTU: SAUCE: azure: Fixup MSI domain ops" - Revert "UBUNTU: [Config] azure: arm64 CONFIG_HIBERNATION=y" - Revert "UBUNTU: [Config] arm64: CONFIG_XFS_FS=m" - Revert "UBUNTU: [Package] Initial arm64 packaging" - Revert "Ubuntu: SAUCE: clocksource/drivers/hyper-v: Untangle stimers and timesync from clocksources" - Revert "PCI: hv: Add arm64 Hyper-V vPCI support" - Revert "PCI: hv: Make the code arch neutral by adding arch specific interfaces" - Revert "Drivers: hv: balloon: Use VMBUS_RING_SIZE() wrapper for dm_ring_size" - Revert "PCI: hv: Turn on the host bridge probing on ARM64" - Revert "PCI: hv: Set up MSI domain at bridge probing time" - Revert "PCI: hv: Set ->domain_nr of pci_host_bridge at probing time" - Revert "PCI: hv: Generify PCI probing" - Revert "arm64: PCI: Support root bridge preparation for Hyper-V" - Revert "arm64: PCI: Restructure pcibios_root_bridge_prepare()" - Revert "PCI: Support populating MSI domains of root buses via bridges" - Revert "PCI: Introduce domain_nr in pci_host_bridge" - Revert "PCI: hv: Support for create interrupt v3" - Revert "Drivers: hv: Enable Hyper-V code to be built on ARM64" - Revert "arm64: efi: Export screen_info" - Revert "arm64: hyperv: Initialize hypervisor on boot" - Revert "arm64: hyperv: Add panic handler" - Revert "arm64: hyperv: Add Hyper-V hypercall and register access utilities" - Revert "drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers" - Revert "Drivers: hv: Move Hyper-V misc functionality to arch-neutral code" - Revert "Drivers: hv: Add arch independent default functions for some Hyper-V handlers" - Revert "Drivers: hv: Make portions of Hyper-V init code be arch neutral" - Revert "asm-generic/hyperv: Add missing #include of nmi.h" - Revert "arm64: smccc: Add support for SMCCCv1.2 extended input/output registers" - Revert "Drivers: hv: vmbus: Fix duplicate CPU assignments within a device" - Revert "PCI: hv: Remove bus device removal unused refcount/functions" - Revert "PCI: hv: Fix a race condition when removing the device" - Revert "Drivers: hv: Move Hyper-V extended capability check to arch neutral code" - Revert "PCI: hv: Drop msi_controller structure" - Revert "drivers: hv: Create a consistent pattern for checking Hyper-V hypercall status" - Revert "clocksource/drivers/hyper-v: Move handling of STIMER0 interrupts" - Revert "clocksource/drivers/hyper-v: Set clocksource rating based on Hyper-V feature" - Revert "clocksource/drivers/hyper-v: Handle sched_clock differences inline" - Revert "clocksource/drivers/hyper-v: Handle vDSO differences inline" - Revert "Drivers: hv: vmbus: Move handling of VMbus interrupts" - Revert "Drivers: hv: vmbus: Handle auto EOI quirk inline" - Revert "Drivers: hv: vmbus: Move hyperv_report_panic_msg to arch neutral code" - Revert "Drivers: hv: Redo Hyper-V synthetic MSR get/set functions" - Revert "x86/hyper-v: Move hv_message_type to architecture neutral module" - Revert "Drivers: hv: vmbus: Move Hyper-V page allocator to arch neutral code" - Revert "asm-generic/hyperv: update hv_interrupt_entry" - Revert "asm-generic/hyperv: update hv_msi_entry" - Revert "drivers: hv: vmbus: Fix checkpatch SPLIT_STRING" - Revert "x86/apic: Cleanup delivery mode defines" - Revert "smccc: Define vendor hyp owned service call region" - Revert "Drivers: hv: vmbus: Add parsing of VMbus interrupt in ACPI DSDT" - Revert "scsi: storvsc: Support PAGE_SIZE larger than 4K" - Revert "Driver: hv: util: Use VMBUS_RING_SIZE() for ringbuffer sizes" - Revert "HID: hyperv: Use VMBUS_RING_SIZE() for ringbuffer sizes" - Revert "Input: hyperv-keyboard: Use VMBUS_RING_SIZE() for ringbuffer sizes" - Revert "hv_netvsc: Use HV_HYP_PAGE_SIZE for Hyper-V communication" - Revert "hv: hyperv.h: Introduce some hvpfn helper functions" - Revert "Drivers: hv: vmbus: Move virt_to_hvpfn() to hyperv header" - Revert "Drivers: hv: Use HV_HYP_PAGE in hv_synic_enable_regs()" - Revert "Drivers: hv: vmbus: Introduce types of GPADL" - Revert "Drivers: hv: vmbus: Move __vmbus_open()" - Revert "Drivers: hv: vmbus: Always use HV_HYP_PAGE_SIZE for gpadl" - Revert "Drivers: hv: vmbus: Remove the lock field from the vmbus_channel struct" - Revert "scsi: storvsc: Introduce the per-storvsc_device spinlock" - Revert "Drivers: hv:
[Kernel-packages] [Bug 1968210] Re: USB devices not detected during boot on USB 3.0 hubs
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD flag to defer primary roothub
registration""
- SAUCE: Revert "Revert "usb: core: hcd: Add support for deferring roothub
registration""
linux (5.4.0-108.122) focal; urgency=medium
* focal/linux: 5.4.0-108.122 -proposed tracker (LP: #1966740)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/2022.03.21)
* Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
* [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
(LP: #1962831)
- selftests: kvm: add _vm_ioctl
- selftests: kvm: Introduce the TEST_FAIL macro
- KVM: selftests: Add GUEST_ASSERT variants to pass values to host
- KVM: s390: gaccess: Refactor gpa and length calculation
- KVM: s390: gaccess: Refactor access address range check
- KVM: s390: gaccess: Cleanup access to guest pages
- s390/uaccess: introduce bit field for OAC specifier
- s390/uaccess: fix compile error
- s390/uaccess: Add copy_from/to_user_key functions
- KVM: s390: Honor storage keys when accessing guest memory
- KVM: s390: handle_tprot: Honor storage keys
- KVM: s390: selftests: Test TEST PROTECTION emulation
- KVM: s390: Add optional storage key checking to MEMOP IOCTL
- KVM: s390: Add vm IOCTL for key checked guest absolute memory access
- KVM: s390: Rename existing vcpu memop functions
- KVM: s390: Add capability for storage key extension of MEM_OP IOCTL
- KVM: s390: Update api documentation for memop ioctl
- KVM: s390: Clarify key argument for MEM_OP in api docs
- KVM: s390: Add missing vm MEM_OP size check
* 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon/sec2 - Add workqueue for SEC driver.
- crypto: hisilicon/sec2 - update SEC initialization and reset
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117)
- crypto: hisilicon - Use one workqueue per qm instead of per qp
* Lots of hisi_qm zombie task slow down system after stress test
(LP: #1932117) // 【sec-0911】 fail to reset sec module (LP: #1943301)
- crypto: hisilicon - Unify hardware error init/uninit into QM
* [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
* Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
* Focal update: v5.4.178 upstream stable release (LP: #1964634)
- audit: improve audit queue handling when "audit=1" on cmdline
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Simplify quirk entries with a macro
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
reboot from Windows
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- drm/nouveau: fix off by one in BIOS boundary checking
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- memcg: charge fs_context and legacy_fs_context
- IB/rdmavt: Validate remote_addr during loopback atomic tests
- RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
- RDMA/mlx4: Don't continue event handler after memory allocation failure
- iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
- spi: bcm-qspi: check for valid cs before applying chip select
- spi: mediatek: Avoid NULL pointer crash in interrupt
- spi: meson-spicc: add IRQ check in meson_spicc_probe
- net: ieee802154: hwsim: Ensure proper channel selection at probe time
- net: ieee802154: mcr20a: Fix lifs/sifs periods
- net: ieee802154: ca8210: Stop leaking skb's
- net: ieee802154: Return meaningful error codes from the netlink helpers
- net: macsec: Verify that send_sci is on when setting Tx sci explicitly
- net: stmmac: dump gmac4 DMA registers correctly
- net: stmmac: ensure PTP time register reads are consistent
-
[Kernel-packages] [Bug 1968344] Re: linux-azure: Fixup Hyperv backport bugs
This bug was fixed in the package linux-azure - 5.4.0-1077.80 --- linux-azure (5.4.0-1077.80) focal; urgency=medium * focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.03.21) * focal/linux-azure: Enable missing config options (LP: #1968749) - Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device - PCI: hv: Propagate coherence from VMbus device to PCI device - [Config] azure: arm64: Ignore module movements - [Config] azure: arm64: Enable RAID config options - [Config] azure: arm64: Enable SQUASHFS config options -- Tim Gardner Tue, 12 Apr 2022 18:53:53 -0600 ** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Released -- 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/1968344 Title: linux-azure: Fixup Hyperv backport bugs Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Released Bug description: SRU Justification [Impact] The initial release of arm64 support for Hyperv in the v5.4 was found to have an x86 bug related to IRQ mapping. There is a SAUCE patch to correct a boot failure. [Test Case] Boot an Azure instance with advanced networking enabled (mlx5_ib) [Where things could go wrong] There could be other interrupt allocation and mapping issues. [Other Info] These patches are dependent on LP: #1961300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1968344/+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 1968749] Re: focal/linux-azure: Enable missing config options
This bug was fixed in the package linux-azure - 5.4.0-1077.80 --- linux-azure (5.4.0-1077.80) focal; urgency=medium * focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.03.21) * focal/linux-azure: Enable missing config options (LP: #1968749) - Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device - PCI: hv: Propagate coherence from VMbus device to PCI device - [Config] azure: arm64: Ignore module movements - [Config] azure: arm64: Enable RAID config options - [Config] azure: arm64: Enable SQUASHFS config options -- Tim Gardner Tue, 12 Apr 2022 18:53:53 -0600 ** Changed in: linux-azure (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1968749 Title: focal/linux-azure: Enable missing config options Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Released Bug description: SRU Justification [Impact] focal/linux-azure is missing a number of config options compared to impish/linux-azure. This kernel is also missing 2 patches that significantly impact network performance. From Microsoft: We tested this kernel. The P0P1 test cases are finished. Below are we found. P2 test cases are still running. I will update you when they are finished. 1. From dmesg, we can see following lines. Could you check why it has these messages and if the messages impact the system? [3.341802] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored [3.346056] unable to read xattr id index table 2. The kernel hasn't backport Michael's SRIOV performance improvement patches. The network performance is not expected. Here are the patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=37200078ed6aa2ac3c88a01a64996133dccfdd34 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=8d21732475c637c7efcdb91dc927a4c594e97898 3. It is failed to create raid 0 using below command. # mdadm --create /dev/md0 --level 0 --raid-devices 16 /dev/sd[abcdghijklmnopqr][1-5] mdadm: Defaulting to version 1.2 metadata mdadm: RUN_ARRAY failed: Invalid argument From dmesg, it has following lines: [ 235.830712] md: personality for level 0 is not loaded! [ 235.830733] md: md0 stopped. I see many raid related configuration is not set. Could you check the raid related and other configuration? # cat /boot/config-5.4.0-1076-azure | grep RAID CONFIG_RAID_ATTRS=m # CONFIG_BLK_DEV_3W__RAID is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set CONFIG_MEGARAID_SAS=y # CONFIG_SCSI_PMCRAID is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID10 is not set # CONFIG_MD_RAID456 is not set # CONFIG_DM_RAID is not set CONFIG_BCM_SBA_RAID=m CONFIG_DMA_ENGINE_RAID=y CONFIG_RAID6_PQ=m CONFIG_RAID6_PQ_BENCHMARK=y [Test Case] Microsoft tested [Where things could go wrong] There should be little chance of regression given that these are config options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1968749/+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 1969457] [NEW] /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed out waiting on zvol links
Public bug reported: Fresh installation of 20.04.4 with installer created zfs native encrypted root zfsutils-linux: 0.8.3-1ubuntu12.13 On reboot, zvol /dev/zvol entries are not being created. This seems to effect different zvols each reboot. Example logs: ``` -- A start job for unit zsys-gc.service has finished successfully. -- -- The job identifier is 3139. Apr 19 06:43:49 monolith zvol_wait[74768]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:50 monolith zvol_wait[74786]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:51 monolith zvol_wait[74805]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:52 monolith zvol_wait[74823]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:53 monolith zvol_wait[74932]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:54 monolith zvol_wait[74950]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:55 monolith zvol_wait[74969]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:56 monolith zvol_wait[74987]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:57 monolith zvol_wait[75006]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:58 monolith zvol_wait[4440]: Still waiting on 1 zvol links ... Apr 19 06:43:58 monolith zvol_wait[4440]: No progress since last loop. Apr 19 06:43:58 monolith zvol_wait[4440]: Checking if any zvols were deleted. Apr 19 06:43:58 monolith zvol_wait[4440]: Remaining zvols: Apr 19 06:43:58 monolith zvol_wait[4440]: rpool/libvirt_zvols/kube-04-disk0 Apr 19 06:43:58 monolith zvol_wait[4440]: Timed out waiting on zvol links Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit zfs-volume-wait.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit zfs-volume-wait.service has entered the 'failed' state with result 'exit-code'. Apr 19 06:43:58 monolith systemd[1]: Failed to start Wait for ZFS Volume (zvol) links in /dev. -- Subject: A start job for unit zfs-volume-wait.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit zfs-volume-wait.service has finished with a failure. -- -- The job identifier is 226 and the job result is failed. Apr 19 06:43:58 monolith systemd[1]: Dependency failed for ZFS volumes are ready. -- Subject: A start job for unit zfs-volumes.target has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit zfs-volumes.target has finished with a failure. ``` I believe this is related to changes made here: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969457 Title: /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed out waiting on zvol links Status in zfs-linux package in Ubuntu: New Bug description: Fresh installation of 20.04.4 with installer created zfs native encrypted root zfsutils-linux: 0.8.3-1ubuntu12.13 On reboot, zvol /dev/zvol entries are not being created. This seems to effect different zvols each reboot. Example logs: ``` -- A start job for unit zsys-gc.service has finished successfully. -- -- The job identifier is 3139. Apr 19 06:43:49 monolith zvol_wait[74768]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:50 monolith zvol_wait[74786]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:51 monolith zvol_wait[74805]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:52 monolith zvol_wait[74823]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:53 monolith zvol_wait[74932]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:54 monolith zvol_wait[74950]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:55 monolith zvol_wait[74969]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:56 monolith zvol_wait[74987]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:57 monolith zvol_wait[75006]: cannot open 'rpool/export/vault/block': dataset does not exist Apr 19 06:43:58 monolith zvol_wait[4440]: Still
[Kernel-packages] [Bug 1960777] Re: Bail out when USB port is stuck in reset loop
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1011.11 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-focal' to 'verification-
done-focal'. If the problem still exists, change the tag 'verification-
needed-focal' to 'verification-failed-focal'.
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: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1960777
Title:
Bail out when USB port is stuck in reset loop
Status in HWE Next:
New
Status in linux-intel-5.13 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
USB port stops working after unplug an USB device.
[Fix]
Commit c89686118c786a523eee3ef68ed38330319626d8 ("usb: core: Bail out when
port is stuck in reset loop")
[Test]
Affected vendor confirmed the patch can fix the issue after numerous round of
tests.
[Where problems could occur]
If there's any peculiar USB hub depends on the old (and buggy) behavior, this
can potentially bring a regression to the hub.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1960777/+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 1962674] Re: Add IIO sensors ID for ACPI based platform
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1011.11 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-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962674 Title: Add IIO sensors ID for ACPI based platform Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: [Impact] On ACPI based platforms, some sensors aren't probed because driver doesn't have ACPI IDs, so they are useless. [Fix] For pressure sensor: 72ff282819d0526d3e4417c2a61414557981b5af iio: pressure: dps310: Add ACPI HID table For humidity sensor: 711b6a3f4af137c4a7f759136ccd50d455095b95 iio: humidity: hdc100x: Add ACPI HID table For accelerator sensor: b9493d595226b598ed79b3769f7038fda1a5391b iio: accel: adxl345: Add ACPI HID table The commit is part of patch series, for the whole series, please cherry-pick 01676b0f3b625a9aa608d5b716898e9dba2fb63e^..4781f3e0e6cadf332f49f723ba820f35960a058d [Test] All sensors are working under /sys/bus/iio. [Where problems could occur] Unless there's an ID collision, these patches don't really bring any change, hence no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1962674/+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
