[Kernel-packages] [Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)
Verified "unary operator expected" error is not showing on any kvm selftests results for the kernels in -proposed. Thank you! ** Tags removed: verification-needed-focal verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-focal verification-done-hirsute verification-done-impish -- 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: In Progress 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 Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed 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
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
Hi Frank, may you please verify this bug is resolved on the
focal/hirsute/impish kernels in -proposed? Appreciate your help!
--
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/1953334
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel - kernel part
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Hardware diagnose data (diag 318) of KVM guest kernel cannot be
handled.
* A fix is needed to enhance problem determination of guest kernel
under KVM using DIAG 0x318 instruction execution.
* The s390x diagnose 318 instruction sets the control program name
code (CPNC) and control program version code (CPVC) to provide useful
information regarding the OS during debugging.
* The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.
[Fix]
* In general the following 4 commits are needed:
* 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug
statement for diag 318 CPNC data"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch
* 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove
diag318 reset code"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch
* 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose
0x318 sync and reset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch
* a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag
318: refactor struct"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch
* For jammy, hirsute and impish only the first commit is needed, the
others are already in.
* For focal all 4 commits are needed, but since they do not apply
cleanly on focal, the attached backports need to be used instead.
[Test Case]
* Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.
* And setup an Ubuntu KVM virtual on top.
* It can then be observed if the CPNC (diag318 data) has been
successfully set by looking at the s390dbf messages for the KVM guest.
* The CPNC will always be 4 (denotes Linux environment).
* Another way to test this is by running the sync_regs_test under
tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the
kernel self test suite can trigger this.
[Where problems could occur]
* The approach here is to provide additional debug and diagnose
information on top.
* Hence even if the diag318 changes are broken, the existing
functionality shouldn't be harmed.
* The changes themselves are relatively discernible and mostly
introduce new structures.
* However, with the functional changes broken code could be introduced
(e.g. due to erroneous pointer arithmetic for example) that does not
compile or causes crashes. But this is what the test builds are for
(https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).
* On top the diag318 diagnose data might not properly provided - maybe
empty or wrong. Again that is what the test builds and the
verification later is targeted at.
* Since diag318 is s390x specific, all the modifications touch s390x
code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
diag.h). At least no other other architecture will be affected.
* Well, there is one tiny bit of a common code change, but it's just a
new define statement in include/uapi/linux/kvm.h ('#define
KVM_CAP_S390_DIAG318 186').
[Other]
* Request was to add the patches to focal / 20.04, but to avoid
potential regressions on upgrades, the patches need to be added to
jammy, impish and hirsute, too.
* As mentioned above, Jammy, Hirsute and Impish includes almost
everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
for diag 318 CPNC data".
* Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
invasive for Jammy, Hirsute and Impish, also because commit
3fd8417f2c72 can be cleanly cherry-picked form there.
* LP#1953338 is related to this bug and covers the qemu/KVM bits.
__
Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled.
Fix needed to enhance problem determination of guest
[Kernel-packages] [Bug 1954773] Re: New fix for jack detection after resume on CS8409 sound driver
Hi Chris, may you please verify if this bug is resolved for the impish
kernel in -proposed too? Thank you!
--
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/1954773
Title:
New fix for jack detection after resume on CS8409 sound driver
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
On some platforms with Cirrus CS8409 audio codec, the external headset will
fail to be detected after system resume.
[Fix]
Cirrus released a new fix commit 65cc4ad62a9e ('ALSA: hda/cs8409: Set PMSG_ON
earlier inside cs8409 driver'). It sets the power_state to ON before the
unsolicited event arrives to make sure the jack detection can be invoked after
resume.
[Test]
Plug-in an external headset in front headset port, suspend/resume the system
then check whether the headset function works as expected.
[Where problem could occur]
Low. It only affect the platforms with Cirrus codec CS8409 which used to have
problem.
== Original Bug Description ==
[Summary] System can't detect external headset after suspend
[Steps to reproduce]
1. install manifest and boot into OS
2. plug-in an external headset in front headset port
3. un-plug external headset
4. suspend system
5. resume system from suspend
6. plug-in an external headset
[Expected result]
System could detect external headset after suspend
[Actual result]
System can't detect external headset after suspend
[Failure rate]
3/3
[Additional information]
CID: 202110-29567
SKU: DLPV-SFF-DVT-C1
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152
system-manufacturer: Dell Inc.
system-product-name: Vostro 3710
bios-version: 0.13.73
CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x)
GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4680] (rev 0c)
kernel-version: 5.13.0-1019-oem
[Stage]
Issue reported and logs collected right after it happened
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954773/+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 1958690] [NEW] initramfs-tools/0.136ubuntu6.6 ADT test failure with linux/5.4.0-97.110 (No space left on device)
Public bug reported: This is a scripted bug report about ADT failures while running initramfs-tools tests for linux/5.4.0-97.110 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined.' Failing with "No space left on device" Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/i/initramfs-tools/20220120_163952_3eaab@/log.gz ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: focal kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - initramfs-tools/0.136ubuntu6.6 ADT test failure with linux/5.4.0-97.110 + initramfs-tools/0.136ubuntu6.6 ADT test failure with linux/5.4.0-97.110 (No space left on device) ** Description changed: This is a scripted bug report about ADT failures while running initramfs-tools tests for linux/5.4.0-97.110 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to - be determined. + be determined.' + + Failing with "No space left on device" Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/i/initramfs-tools/20220120_163952_3eaab@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/i/initramfs-tools/20220120_163952_3eaab@/log.gz ** Tags added: 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/1958690 Title: initramfs-tools/0.136ubuntu6.6 ADT test failure with linux/5.4.0-97.110 (No space left on device) Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running initramfs-tools tests for linux/5.4.0-97.110 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined.' Failing with "No space left on device" Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/i/initramfs-tools/20220120_163952_3eaab@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958690/+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 1956422] Re: Linux Kernel 5.13.0-23 Suspend Modus
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Thank you for the report and information! We're working to get a fix out. Please refer to bug 1956401 for updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956422 Title: Linux Kernel 5.13.0-23 Suspend Modus Status in linux package in Ubuntu: Confirmed Bug description: Hi there, after updating to kernel 5.13.0-23 the suspend modus is not working anymore. I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a Intel processor. I have to start with Kernel 5.13.0-22 and then it works fine. When is suspend modus the computer doesn't wake up again. Thanx in advance. Dietmar ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dietmar1227 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 08:06:59 2022 InstallationDate: Installed on 2021-10-21 (75 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Apple Inc. MacBook5,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/09 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB51.88Z.007D.B03.0904271443 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D89C8 dmi.board.vendor: Apple Inc. dmi.board.version: Proto dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#: dmi.product.family: MacBook dmi.product.name: MacBook5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956422/+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 1956408] Re: Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Thank you for the report and information! We're working to get a fix out. Please refer to bug 1956401 for updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956408 Title: Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic Status in linux package in Ubuntu: Confirmed Bug description: After updating the kernel to 5.13.0-23-generic, everything seems very very slow. The operating system takes a long time to reach the desktop, applications like google chrome, telegram take a long time to open. Till now, out of the 4 times I have started ubuntu using kernel 5.13.0-23-generic, 3 times everything was slow, and 1 time things were normal and fast as usual. My processor is AMD Ryzen 3500u. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumadeepsarkar1 1671 F pulseaudio /dev/snd/controlC0: soumadeepsarkar1 1671 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 09:38:49 2022 InstallationDate: Installed on 2021-12-06 (29 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Laptop 15s-eq0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=7e493e25-d42c-4448-beec-66294ac825d3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2021 dmi.bios.release: 15.53 dmi.bios.vendor: AMI dmi.bios.version: F.53 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.42 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 99.42 dmi.modalias: dmi:bvnAMI:bvrF.53:bd10/15/2021:br15.53:efr99.42:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.42:cvnHP:ct10:cvrChassisVersion:sku440L6PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 440L6PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956408/+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 1956396] Re: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Thank you for the report and information! We're working to get a fix out. Please refer to bug 1956401 for updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956396 Title: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3) Had been using the 5.13 HWE kernel for months with no problems. Today the kernel and linux-firmware updated. 5.13.0-23 kernel now takes about 2 minutes to boot to the login screen. Normal boot time is 8 seconds. During that time the pc is frozen with only a _ underline cursor that doesn't flash. Can't change terminals with Ctrl+Alt+F1, etc. Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure the problem is in the kernel and not linux-firmware. System information (while using 5.11 kernel) CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59089 Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330 Graphics: Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 0c:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.11.0-44-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 direct render: Yes Forums threads about it: https://ubuntuforums.org/showthread.php?t=2470574 https://forums.linuxmint.com/viewtopic.php?f=46=364729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956396/+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 1956519] Re: kernel panic after upgrading to kernel 5.13.0-23
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Thank you for the report and information! We're working to get a fix out. Please refer to bug 1956401 for updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956519 Title: kernel panic after upgrading to kernel 5.13.0-23 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading my son's Asus PN50 with Ubuntu 21.10 to the latest kernel 5.13.0-23, I am no longer able to boot it normally. Kernel fails with the panic halfway through the boot process (which got overall suspiciously slow): [1.359465] BUG: kernel NULL pointer dereference, address: 000c [1.359498] #PF: supervisor write access in kernel mode [1.359519] #PF: error_code(0x0002) - not-present page [1.359540] PGD 0 P4D 0 [1.359553] Oops: 0002 [#1] SMP NOPTI [1.359569] CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu [1.359602] Hardware name: ASUSTeK COMPUTER INC. MINIPC PN50/PN50, BIOS 0623 05/13/2021 [1.359632] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] [1.359661] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d [1.359729] RSP: 0018:bf71c099f9d8 EFLAGS: 00010246 [1.359750] RAX: RBX: RCX: [1.359777] RDX: 0020 RSI: c03cd249 RDI: a680004c [1.359804] RBP: bf71c099fa20 R08: R09: 0006 [1.359831] R10: bf71c0d0 R11: 0007 R12: 000fffe0 [1.359857] R13: 992bc3387cd8 R14: 992bc11560c8 R15: 992bc3387cd8 [1.359884] FS: 7ff0ec1a48c0() GS:992ebf60() knlGS: [1.359915] CS: 0010 DS: ES: CR0: 80050033 [1.359937] CR2: 000c CR3: 000102fd CR4: 00350ef0 [1.359964] Call Trace: [1.359976] ? __pci_set_master+0x5f/0xe0 [1.359997] amd_mp2_pci_probe+0xad/0x160 [amd_sfh] [1.360021] local_pci_probe+0x48/0x80 [1.360038] pci_device_probe+0x105/0x1c0 [1.360056] really_probe+0x24b/0x4c0 [1.360073] driver_probe_device+0xf0/0x160 [1.360091] device_driver_attach+0xab/0xb0 [1.360110] __driver_attach+0xb2/0x140 [1.360126] ? device_driver_attach+0xb0/0xb0 [1.360145] bus_for_each_dev+0x7e/0xc0 [1.360161] driver_attach+0x1e/0x20 [1.360177] bus_add_driver+0x135/0x1f0 [1.360194] driver_register+0x95/0xf0 [1.360210] ? 0xc03d2000 [1.360225] __pci_register_driver+0x57/0x60 [1.360242] amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] [1.360266] do_one_initcall+0x48/0x1d0 [1.360284] ? kmem_cache_alloc_trace+0xfb/0x240 [1.360306] do_init_module+0x62/0x290 [1.360323] load_module+0xa8f/0xb10 [1.360340] __do_sys_finit_module+0xc2/0x120 [1.360359] __x64_sys_finit_module+0x18/0x20 [1.360377] do_syscall_64+0x61/0xb0 [1.361638] ? ksys_mmap_pgoff+0x135/0x260 [1.362883] ? exit_to_user_mode_prepare+0x37/0xb0 [1.364121] ? syscall_exit_to_user_mode+0x27/0x50 [1.365343] ? __x64_sys_mmap+0x33/0x40 [1.366550] ? do_syscall_64+0x6e/0xb0 [1.367749] ? do_syscall_64+0x6e/0xb0 [1.368923] ? do_syscall_64+0x6e/0xb0 [1.370079] ? syscall_exit_to_user_mode+0x27/0x50 [1.371227] ? do_syscall_64+0x6e/0xb0 [1.372359] ? exc_page_fault+0x8f/0x170 [1.373478] ? asm_exc_page_fault+0x8/0x30 [1.374584] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.375684] RIP: 0033:0x7ff0ec73a94d [1.376767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48 [1.377926] RSP: 002b:7ffd00724ba8 EFLAGS: 0246 ORIG_RAX: 0139 [1.379076] RAX: ffda RBX: 55e130084390 RCX: 7ff0ec73a94d [1.380225] RDX: RSI: 7ff0ec8ca3fe RDI: 0005 [1.381363] RBP: 0002 R08: R09: [1.382488] R10: 0005 R11: 0246 R12: 7ff0ec8ca3fe [1.383598] R13: 55e130083370 R14: 55e130084480 R15: 55e130086cb0 [1.384698] Modules linked in: ahci(+) libahci i2c_piix4(+) r8169(+) amd_sfh(+) i2c_hid_acpi realtek i2c_hid xhci_pci(+) xhci_pci_renesas wmi(+) video(+) fjes(+) hid [1.385841] CR2: 000c [1.386955] ---[ end trace b2ebcacf74b788da ]--- [1.388064] RIP:
[Kernel-packages] [Bug 1956399] Re: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Thank you for the report and information! We're working to get a fix out. Please refer to bug 1956401 for updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956399 Title: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G Status in linux package in Ubuntu: Confirmed Bug description: After latest upgrade of linux-image to 5.13.0.23.34 system seem to boot, but it looks like graphics does not initialize correctly. After showing initial init logging, at the moment when X should init and graphics login should appear, monitor just goes to sleep and provides diagnostic message that there is no signal on selected input. apt upgrade log: Start-Date: 2022-01-04 23:21:11 Commandline: apt upgrade Requested-By: xx (1000) Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), google-chrome-stable:amd64 (96.0.4664.110-1, 97.0.4692.71-1), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) End-Date: 2022-01-04 23:22:39 Currently working around this issues by booting previous version of the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-generic 5.13.0.23.34 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2532 F pulseaudio /dev/snd/pcmC1D0p: alexei 2532 F...m pulseaudio /dev/snd/controlC0: alexei 2532 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 01:02:53 2022 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (2190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp8s0no wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-05 (91 days ago) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956399/+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 1956469] Re: [amdgpu] GPU related problems after kernel update
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Thank you for the report and information! We're working to get a fix out. Please refer to bug 1956401 for updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956469 Title: [amdgpu] GPU related problems after kernel update Status in linux package in Ubuntu: Confirmed Bug description: After the last stable kernel update, my system is slow, browsers fail to start and crash and dmesg is full of gpu related error messages. Loading the previous kernel does not result in any problems. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 14:57:16 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-22-generic, x86_64: installed v4l2loopback, 0.12.5, 5.13.0-23-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-22-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:8643] InstallationDate: Installed on 2021-07-16 (172 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210715) MachineType: HP HP Desktop M01-F0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.release: 15.17 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.38 dmi.modalias: dmi:bvnAMI:bvrF.11:bd11/26/2019:br15.17:efr52.38:svnHP:pnHPDesktopM01-F0xxx:pvr:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr:sku8KX18EA#ABD: dmi.product.family: 103C_53311M HP Desktop PC dmi.product.name: HP Desktop M01-F0xxx dmi.product.sku: 8KX18EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956469/+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 1956532] Re: Linux Kernel 5.13.0-23 Slows everything
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Thank you for the report and information! We're working to get a fix out. Please refer to bug 1956401 for updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956532 Title: Linux Kernel 5.13.0-23 Slows everything Status in linux package in Ubuntu: Confirmed Bug description: I installed the Linux Kernel version today (5 Jan 2022) 5.13.0-23 and my laptop slowed on boot time A LOT and after login it takes A VERY LONG TIME. Apps take a long time to open including snap apps. I switched back to 5.13.0-22-generic everything works like a charm. Please register this bug for Linus Torvald or its support page to fix this. Thank you, here are my laptop specs: Hardware model: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Memory: 9.7 GiB Processor: AMD® Ryzen 7 3700u with radeon vega mobile gfx × 8 Graphics: AMD® Radeon(tm) vega 10 graphics Disk: 1.5 TB OS: Ubuntu 21.10 64-bit Gnome: 40.4.0 windowing System: X11/Wayland --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abel 2599 F pulseaudio /dev/snd/controlC0: abel 2599 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-30 (401 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=e371e9ab-3ad5-414b-a7cb-0a9c4953453b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-15 (82 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DA.310:bd12/24/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956532/+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 1956383] Re: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Hi Alex, Thank you for the report and information! We're working to get a fix out. Please refer to https://bugs.launchpad.net/bugs/1956401 for updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+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 1956408] Re: Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 ** This bug is no longer a duplicate of bug 1956396 kernel 5.13.0-23 extremely slow boot on AMD proc/graphics ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time -- 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/1956408 Title: Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic Status in linux package in Ubuntu: Confirmed Bug description: After updating the kernel to 5.13.0-23-generic, everything seems very very slow. The operating system takes a long time to reach the desktop, applications like google chrome, telegram take a long time to open. Till now, out of the 4 times I have started ubuntu using kernel 5.13.0-23-generic, 3 times everything was slow, and 1 time things were normal and fast as usual. My processor is AMD Ryzen 3500u. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumadeepsarkar1 1671 F pulseaudio /dev/snd/controlC0: soumadeepsarkar1 1671 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 09:38:49 2022 InstallationDate: Installed on 2021-12-06 (29 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Laptop 15s-eq0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=7e493e25-d42c-4448-beec-66294ac825d3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2021 dmi.bios.release: 15.53 dmi.bios.vendor: AMI dmi.bios.version: F.53 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.42 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 99.42 dmi.modalias: dmi:bvnAMI:bvrF.53:bd10/15/2021:br15.53:efr99.42:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.42:cvnHP:ct10:cvrChassisVersion:sku440L6PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 440L6PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956408/+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 1956396] Re: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time -- 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/1956396 Title: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3) Had been using the 5.13 HWE kernel for months with no problems. Today the kernel and linux-firmware updated. 5.13.0-23 kernel now takes about 2 minutes to boot to the login screen. Normal boot time is 8 seconds. During that time the pc is frozen with only a _ underline cursor that doesn't flash. Can't change terminals with Ctrl+Alt+F1, etc. Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure the problem is in the kernel and not linux-firmware. System information (while using 5.11 kernel) CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59089 Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330 Graphics: Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 0c:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.11.0-44-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 direct render: Yes Forums threads about it: https://ubuntuforums.org/showthread.php?t=2470574 https://forums.linuxmint.com/viewtopic.php?f=46=364729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956396/+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 1956422] Re: Linux Kernel 5.13.0-23 Suspend Modus
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time -- 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/1956422 Title: Linux Kernel 5.13.0-23 Suspend Modus Status in linux package in Ubuntu: Confirmed Bug description: Hi there, after updating to kernel 5.13.0-23 the suspend modus is not working anymore. I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a Intel processor. I have to start with Kernel 5.13.0-22 and then it works fine. When is suspend modus the computer doesn't wake up again. Thanx in advance. Dietmar ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dietmar1227 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 08:06:59 2022 InstallationDate: Installed on 2021-10-21 (75 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Apple Inc. MacBook5,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/09 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB51.88Z.007D.B03.0904271443 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D89C8 dmi.board.vendor: Apple Inc. dmi.board.version: Proto dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#: dmi.product.family: MacBook dmi.product.name: MacBook5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956422/+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 1956399] Re: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time -- 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/1956399 Title: Regression: kernel does not init graphics (?) on AMD Ryzen 5 3400G Status in linux package in Ubuntu: Confirmed Bug description: After latest upgrade of linux-image to 5.13.0.23.34 system seem to boot, but it looks like graphics does not initialize correctly. After showing initial init logging, at the moment when X should init and graphics login should appear, monitor just goes to sleep and provides diagnostic message that there is no signal on selected input. apt upgrade log: Start-Date: 2022-01-04 23:21:11 Commandline: apt upgrade Requested-By: xx (1000) Install: linux-modules-extra-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-image-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-modules-5.13.0-23-generic:amd64 (5.13.0-23.23, automatic), linux-headers-5.13.0-23:amd64 (5.13.0-23.23, automatic) Upgrade: linux-headers-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), google-chrome-stable:amd64 (96.0.4664.110-1, 97.0.4692.71-1), linux-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-image-generic:amd64 (5.13.0.22.33, 5.13.0.23.34), linux-libc-dev:amd64 (5.13.0-22.22, 5.13.0-23.23) End-Date: 2022-01-04 23:22:39 Currently working around this issues by booting previous version of the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-generic 5.13.0.23.34 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2532 F pulseaudio /dev/snd/pcmC1D0p: alexei 2532 F...m pulseaudio /dev/snd/controlC0: alexei 2532 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 01:02:53 2022 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (2190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp8s0no wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-05 (91 days ago) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956399/+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 1956383] Re: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time -- 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/1956383 Title: Ubuntu "impish" 21.10 Linux kernel "5.13.0-23.23" no video after reboot Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-22 worked acceptably well before the update and still works now. Not sure 'ubuntu-bug linux' makes sense in this case, since I booted the older kernel, not the latest one with the problem being reported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: an 1849 F pulseaudio /dev/snd/controlC0: an 1849 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2019-10-14 (813 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191012) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=08f33e8a-3af6-448d-a669-0f2dd2363790 ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 RfKill: Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-12-29 (6 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956383/+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 1956469] Re: [amdgpu] GPU related problems after kernel update
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time -- 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/1956469 Title: [amdgpu] GPU related problems after kernel update Status in linux package in Ubuntu: Confirmed Bug description: After the last stable kernel update, my system is slow, browsers fail to start and crash and dmesg is full of gpu related error messages. Loading the previous kernel does not result in any problems. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 14:57:16 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-22-generic, x86_64: installed v4l2loopback, 0.12.5, 5.13.0-23-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-22-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:8643] InstallationDate: Installed on 2021-07-16 (172 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210715) MachineType: HP HP Desktop M01-F0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.release: 15.17 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.38 dmi.modalias: dmi:bvnAMI:bvrF.11:bd11/26/2019:br15.17:efr52.38:svnHP:pnHPDesktopM01-F0xxx:pvr:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr:sku8KX18EA#ABD: dmi.product.family: 103C_53311M HP Desktop PC dmi.product.name: HP Desktop M01-F0xxx dmi.product.sku: 8KX18EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956469/+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 1956519] Re: kernel panic after upgrading to kernel 5.13.0-23
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time -- 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/1956519 Title: kernel panic after upgrading to kernel 5.13.0-23 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading my son's Asus PN50 with Ubuntu 21.10 to the latest kernel 5.13.0-23, I am no longer able to boot it normally. Kernel fails with the panic halfway through the boot process (which got overall suspiciously slow): [1.359465] BUG: kernel NULL pointer dereference, address: 000c [1.359498] #PF: supervisor write access in kernel mode [1.359519] #PF: error_code(0x0002) - not-present page [1.359540] PGD 0 P4D 0 [1.359553] Oops: 0002 [#1] SMP NOPTI [1.359569] CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu [1.359602] Hardware name: ASUSTeK COMPUTER INC. MINIPC PN50/PN50, BIOS 0623 05/13/2021 [1.359632] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] [1.359661] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d [1.359729] RSP: 0018:bf71c099f9d8 EFLAGS: 00010246 [1.359750] RAX: RBX: RCX: [1.359777] RDX: 0020 RSI: c03cd249 RDI: a680004c [1.359804] RBP: bf71c099fa20 R08: R09: 0006 [1.359831] R10: bf71c0d0 R11: 0007 R12: 000fffe0 [1.359857] R13: 992bc3387cd8 R14: 992bc11560c8 R15: 992bc3387cd8 [1.359884] FS: 7ff0ec1a48c0() GS:992ebf60() knlGS: [1.359915] CS: 0010 DS: ES: CR0: 80050033 [1.359937] CR2: 000c CR3: 000102fd CR4: 00350ef0 [1.359964] Call Trace: [1.359976] ? __pci_set_master+0x5f/0xe0 [1.359997] amd_mp2_pci_probe+0xad/0x160 [amd_sfh] [1.360021] local_pci_probe+0x48/0x80 [1.360038] pci_device_probe+0x105/0x1c0 [1.360056] really_probe+0x24b/0x4c0 [1.360073] driver_probe_device+0xf0/0x160 [1.360091] device_driver_attach+0xab/0xb0 [1.360110] __driver_attach+0xb2/0x140 [1.360126] ? device_driver_attach+0xb0/0xb0 [1.360145] bus_for_each_dev+0x7e/0xc0 [1.360161] driver_attach+0x1e/0x20 [1.360177] bus_add_driver+0x135/0x1f0 [1.360194] driver_register+0x95/0xf0 [1.360210] ? 0xc03d2000 [1.360225] __pci_register_driver+0x57/0x60 [1.360242] amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] [1.360266] do_one_initcall+0x48/0x1d0 [1.360284] ? kmem_cache_alloc_trace+0xfb/0x240 [1.360306] do_init_module+0x62/0x290 [1.360323] load_module+0xa8f/0xb10 [1.360340] __do_sys_finit_module+0xc2/0x120 [1.360359] __x64_sys_finit_module+0x18/0x20 [1.360377] do_syscall_64+0x61/0xb0 [1.361638] ? ksys_mmap_pgoff+0x135/0x260 [1.362883] ? exit_to_user_mode_prepare+0x37/0xb0 [1.364121] ? syscall_exit_to_user_mode+0x27/0x50 [1.365343] ? __x64_sys_mmap+0x33/0x40 [1.366550] ? do_syscall_64+0x6e/0xb0 [1.367749] ? do_syscall_64+0x6e/0xb0 [1.368923] ? do_syscall_64+0x6e/0xb0 [1.370079] ? syscall_exit_to_user_mode+0x27/0x50 [1.371227] ? do_syscall_64+0x6e/0xb0 [1.372359] ? exc_page_fault+0x8f/0x170 [1.373478] ? asm_exc_page_fault+0x8/0x30 [1.374584] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.375684] RIP: 0033:0x7ff0ec73a94d [1.376767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48 [1.377926] RSP: 002b:7ffd00724ba8 EFLAGS: 0246 ORIG_RAX: 0139 [1.379076] RAX: ffda RBX: 55e130084390 RCX: 7ff0ec73a94d [1.380225] RDX: RSI: 7ff0ec8ca3fe RDI: 0005 [1.381363] RBP: 0002 R08: R09: [1.382488] R10: 0005 R11: 0246 R12: 7ff0ec8ca3fe [1.383598] R13: 55e130083370 R14: 55e130084480 R15: 55e130086cb0 [1.384698] Modules linked in: ahci(+) libahci i2c_piix4(+) r8169(+) amd_sfh(+) i2c_hid_acpi realtek i2c_hid xhci_pci(+) xhci_pci_renesas wmi(+) video(+) fjes(+) hid [1.385841] CR2: 000c [1.386955] ---[ end trace b2ebcacf74b788da ]--- [1.388064] RIP:
[Kernel-packages] [Bug 1956532] Re: Linux Kernel 5.13.0-23 Slows everything
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time -- 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/1956532 Title: Linux Kernel 5.13.0-23 Slows everything Status in linux package in Ubuntu: Confirmed Bug description: I installed the Linux Kernel version today (5 Jan 2022) 5.13.0-23 and my laptop slowed on boot time A LOT and after login it takes A VERY LONG TIME. Apps take a long time to open including snap apps. I switched back to 5.13.0-22-generic everything works like a charm. Please register this bug for Linus Torvald or its support page to fix this. Thank you, here are my laptop specs: Hardware model: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Memory: 9.7 GiB Processor: AMD® Ryzen 7 3700u with radeon vega mobile gfx × 8 Graphics: AMD® Radeon(tm) vega 10 graphics Disk: 1.5 TB OS: Ubuntu 21.10 64-bit Gnome: 40.4.0 windowing System: X11/Wayland --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abel 2599 F pulseaudio /dev/snd/controlC0: abel 2599 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-30 (401 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=e371e9ab-3ad5-414b-a7cb-0a9c4953453b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-15 (82 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DA.310:bd12/24/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956532/+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 1956401] Re: amdgpu hangs for 90 seconds at a time
** Package changed: linux-hwe-5.13 (Ubuntu Impish) => linux (Ubuntu Impish) ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux source package in Impish: Confirmed Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/impish/+source/linux/+bug/1956401/+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 1956401] Re: amdgpu hangs for 90 seconds at a time
** Also affects: linux-hwe-5.13 (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time Status in linux source package in Impish: Confirmed Bug description: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/impish/+source/linux/+bug/1956401/+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 1950666] Re: system crash when removing ipmi_msghandler module
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Impish) 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/1950666 Title: system crash when removing ipmi_msghandler module Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [IMPACT] Commit 3b9a907223d7 (ipmi: fix sleep-in-atomic in free_user at cleanup SRCU user->release_barrier) pushes the removal of an ipmi_user into the system's workqueue. Whenever an ipmi_user struct is about to be removed it is scheduled as a work on the system's workqueue to guarantee the free operation won't be executed in atomic context. When the work is executed the free_user_work() function is invoked which frees the ipmi_user. When ipmi_msghandler module is removed in cleanup_ipmi() function, there is no check if there are any pending works to be executed. Therefore, there is a potential race condition : An ipmi_user is scheduled for removal and shortly after to remove the ipmi_msghandler module. If the scheduled work delays execution for any reason and the module is removed first, then when the work is executed the pages of free_user_work() are gone and the system crashes with the following : BUG: unable to handle page fault for address: c05c3450 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 635420e067 P4D 635420e067 PUD 6354210067 PMD 4711e51067 PTE 0 Oops: 0010 [#1] SMP PTI CPU: 19 PID: 29646 Comm: kworker/19:1 Kdump: loaded Not tainted 5.4.0-77-generic #86~18.04.1-Ubuntu Hardware name: Ciara Technologies ORION RS610-G4-DTH4S/MR91-FS1-Y9, BIOS F29 05/23/2019 Workqueue: events 0xc05c3450 RIP: 0010:0xc05c3450 Code: Bad RIP value. RSP: 0018:b721333c3e88 EFLAGS: 00010286 RAX: c05c3450 RBX: 92a95f56a740 RCX: b7221cfd14e8 RDX: 0001 RSI: 92616040d4b0 RDI: b7221cf404e0 RBP: b721333c3ec0 R08: 73746e657665 R09: 8080808080808080 R10: b721333c3de0 R11: fefefefefefefeff R12: 92a95f570700 R13: 92a0a40ece40 R14: b7221cf404e0 R15: 092a95f57070 FS: () GS:92a95f54() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: c05c3426 CR3: 0081e9bfc005 CR4: 007606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: ? process_one_work+0x20f/0x400 worker_thread+0x34/0x410 kthread+0x121/0x140 ? process_one_work+0x400/0x400 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 Modules linked in: xt_REDIRECT xt_owner ipt_rpfilter xt_CT xt_multiport xt_set ip_set_hash_ip veth xt_statistic ipt_REJECT ... megaraid_sas ahci libahci wmi [last unloaded: ipmi_msghandler] CR2: c05c3450 [TEST CASE] The user who reported the issue can reproduce reliably by stopping the ipmi related services and then removing the ipmi modules. I could reproduce the issue only when turning the normal 'work' to delayed work. [WHERE PROBLEMS COULD OCCUR] The fixing patch creates a dedicated workqueue for the remove_work struct of ipmi_user when loading the ipmi_msghandler modules and destroys the workqueue when removing the module. Therefore any potential problems would occur during these two operations or when scheduling works on the dedicated workqueue. [OTHER] Upstream patches : 1d49eb91e86e (ipmi: Move remove_work to dedicated workqueue) 5a3ba99b62d8 (ipmi: msghandler: Make symbol 'remove_work_wq' static) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950666/+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 1954930] Re: AMD: Suspend not working when some cores are disabled through cpufreq
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954930
Title:
AMD: Suspend not working when some cores are disabled through cpufreq
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
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 Impish:
Fix Committed
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
Detailed in https://gitlab.freedesktop.org/drm/amd/-/issues/1708, taking
some cpu cores offline using cpufreq gadgets or via sysfs may hang the
system.
[Fix]
In v5.16-rc1 commit d6b88ce2eb9d ("ACPI: processor idle: Allow playing
dead in C3 state") fixes this issue.
[Test Case]
As stated in aforementioned bug url, setup cpufreq extention to take
down a few cpu cores, and trigger system suspend. There are ~50% chances
that networking/input/... would hang and the user can only reboot by
sysrq keys.
[Where problems could occur]
According to the patch discussion thread in
https://lore.kernel.org/linux-acpi/20210922133116.102-1-richard.g...@amd.com/,
the limitation to allow enter_dead in no more than ACPI_STATE_C2 might
not have a practical meaning, but simply C2 was the deepest supported
then.
[Other Info]
While this is currently only available in v5.16-rc1 and affects AMD
Cezanne/Barcelo, oem-5.14/impish and jammy are nominated.
== original bug report ==
https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Reproduce steps:
1. Install cpufeq gnome extension
(https://extensions.gnome.org/extension/1082/cpufreq/)
2. Click on the cpu freq extention in the top bar
3. Slide the "cores online" from 16 to 3
4. close lid of laptop
Expected result: the laptop goes into suspend
Actual result: the laptop stay on but screen is now always black and keyboard
input is ignored
Fix committed to v5.16-rc1:
https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1188 F pulseaudio
/dev/snd/controlC2: ubuntu 1188 F pulseaudio
/dev/snd/controlC0: ubuntu 1188 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-09-09 (97 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
IwConfig:
lono wireless extensions.
enp1s0f0 no wireless extensions.
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: AMD Celadon-CZN
Package: linux-firmware 1.187.23+staging.38 [origin:
LP-PPA-canonical-hwe-team-linux-firmware-staging]
PackageArchitecture: all
ProcFB: 0 amdgpu
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem
root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config
no_console_suspend
ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.14.0-9011-oem N/A
linux-backports-modules-5.14.0-9011-oem N/A
linux-firmware 1.187.23+staging.38
RfKill:
Tags: third-party-packages focal
Uname: Linux 5.14.0-9011-oem x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/30/2021
dmi.bios.release: 19.1
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: RLD1005B_AB
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Celadon-CZN
[Kernel-packages] [Bug 1954926] Re: Focal: CIFS stable updates
** Changed in: linux (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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1954926 Title: Focal: CIFS stable updates Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] Backport several stable updates to v5.4 Azure [Test Case] Microsoft tested [Where things could go wrong] Samba connections could fail [Other Info] SF: #00324495 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954926/+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 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
Thank you for verifying, Colin! :)
--
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/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
->adjust_perf() callback") caused intel_pstate to use nonzero HWP
desired values in certain usage scenarios, but it did not prevent
them from being leaked into the confugirations in which HWP desired
is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cking 2316 F pulseaudio
/dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
/dev/snd/controlC0: cking 2316 F pulseaudio
/dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
linux-restricted-modules-5.13.0-20-generic N/A
linux-backports-modules-5.13.0-20-generic N/A
linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+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 1946672] Re: Enable multicast in the "kvm" kernels
verified CONFIG_IP_MULTICAST is enabled on focal/kvm in proposed. switching verification testing to done. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1946672 Title: Enable multicast in the "kvm" kernels Status in cloud-images: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Focal: Fix Committed Bug description: I work in the OpenStack Neutron project and recently I wanted to optimize our CI scenario jobs by using Ubuntu minimal image as guest image for some tests (see patch https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/813195) Unfortunately it seems that there is problem with one multicast scenario test while using ubuntu-minimal image (https://cloud-images.ubuntu.com/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img). The problem is that VM booted from that image don't subscribes properly to the IGMP multicast group thus test is failing. All works fine when image https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img is used in the same test. The problem is that in the minimal image kernel linux-image-kvm (vs. linux-image-generic in the "regular" cloud image) and that "-kvm" image has disabled MULTICAST: # CONFIG_IP_MULTICAST is not set Would it be maybe possible to enable this option in the kernel used in the "minimal" cloud images? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1946672/+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 1837040] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on ARM64 / B-hwe P9
spotted on impish 5.13.0-23.23 amd64 kili -- 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/1837040 Title: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on ARM64 / B-hwe P9 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Invalid Status in linux source package in Hirsute: Confirmed Bug description: Test failed with the disco master-next branch, issue spotted on Thunder X ARM64 (passed with Moonshot ARM64): TAP version 13 selftests: ftrace: ftracetest === Ftrace unit tests === [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] [3] Basic trace clock test[PASS] [4] Basic event tracing check [PASS] [5] Change the ringbuffer size[PASS] [6] Snapshot and tracing setting [PASS] [7] trace_pipe and trace_marker [PASS] [8] Generic dynamic event - add/remove kprobe events [PASS] [9] Generic dynamic event - add/remove synthetic events [PASS] [10] Generic dynamic event - selective clear (compatibility) [PASS] [11] Generic dynamic event - generic clear event [PASS] [12] event tracing - enable/disable with event level files[PASS] [13] event tracing - restricts events based on pid[PASS] [14] event tracing - enable/disable with subsystem level files[PASS] [15] event tracing - enable/disable with top level files [PASS] [16] Test trace_printk from module[PASS] [17] ftrace - function graph filters with stack tracer[PASS] [18] ftrace - function graph filters [PASS] [19] ftrace - function glob filters [PASS] [20] ftrace - function pid filters[PASS] [21] ftrace - stacktrace filter command [PASS] [22] ftrace - function trace with cpumask [PASS] [23] ftrace - test for function event triggers[PASS] [24] ftrace - function trace on module[PASS] [25] ftrace - function profiling [PASS] [26] ftrace - function profiler with function tracing [PASS] [27] ftrace - test reading of set_ftrace_filter [PASS] [28] ftrace - Max stack tracer[PASS] [29] ftrace - test for function traceon/off triggers [FAIL] [30] Test creation and deletion of trace instances while setting an event [PASS] [31] Test creation and deletion of trace instances[PASS] [32] Kprobe dynamic event - adding and removing [PASS] [33] Kprobe dynamic event - busy event check [PASS] [34] Kprobe dynamic event with arguments [PASS] [35] Kprobe event with comm arguments [PASS] [36] Kprobe event string type argument[PASS] [37] Kprobe event symbol argument [PASS] [38] Kprobe event argument syntax [PASS] [39] Kprobes event arguments with types [PASS] [40] Kprobe event auto/manual naming [PASS] [41] Kprobe dynamic event with function tracer[PASS] [42] Kprobe dynamic event - probing module[PASS] [43] Kretprobe dynamic event with arguments [PASS] [44] Kretprobe dynamic event with maxactive [PASS] [45] Register/unregister many kprobe events [PASS] [46] Kprobe events - probe points [PASS] [47] Kprobe dynamic event - adding and removing [PASS] [48] test for the preemptirqsoff tracer [UNSUPPORTED] [49] Test wakeup tracer [PASS] [50] Test wakeup RT tracer[PASS] [51] event trigger - test extended error support [PASS] [52] event trigger - test field variable support [PASS] [53] event trigger - test inter-event combined histogram trigger [PASS] [54] event trigger - test multiple actions on hist trigger[PASS] [55] event trigger - test inter-event histogram trigger onmatch action [PASS] [56] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [57] event trigger - test inter-event histogram trigger onmax action [PASS] [58] event trigger - test synthetic event create remove [PASS] [59] event trigger - test synthetic_events syntax parser [PASS] [60] event trigger - test event enable/disable trigger[PASS] [61] event trigger - test trigger filter [PASS] [62] event trigger - test histogram modifiers [PASS] [63] event trigger - test histogram trigger [PASS] [64] event trigger - test multiple histogram triggers [PASS] [65] event trigger - test snapshot-trigger[PASS] [66] event trigger - test stacktrace-trigger [PASS] [67] trace_marker trigger - test histogram trigger[PASS] [68] trace_marker trigger - test snapshot trigger [PASS] [69] trace_marker trigger - test histogram with synthetic event against kernel event [PASS] [70] trace_marker trigger - test histogram with synthetic event [PASS] [71] event trigger - test traceon/off trigger [PASS] [72] (instance) Basic
[Kernel-packages] [Bug 1923683] Re: ftrace from ubuntu_kernel_selftests failed with "test for function event triggers" on F/G/H
Found on Impish 5.13.0-23.23
** Summary changed:
- ftrace from ubuntu_kernel_selftests failed with "test for function event
triggers" on F/G/H
+ ftrace from ubuntu_kernel_selftests failed with "test for function event
triggers" on F/G/H/I
--
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/1923683
Title:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on F/G/H/I
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Confirmed
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Confirmed
Status in linux source package in Impish:
New
Bug description:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on Groovy riscv 5.8.0-21.23
This test was recently added, not considering a regression
Log is getting cut off from regression test report. the below is all
that could be retrieved at the moment:
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 >
/proc/sys/net/ipv4/conf/all/accept_local''
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo make -C
linux/tools/testing/selftests TARGETS=ftrace run_tests'
04/13 23:48:00 DEBUG| utils:0153| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
04/13 23:48:01 DEBUG| utils:0153| [stdout] make --no-builtin-rules
ARCH=riscv -C ../../.. headers_install
04/13 23:48:01 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:14 DEBUG| utils:0153| [stdout] INSTALL ./usr/include
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done
for 'all'.
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] TAP version 13
04/13 23:48:16 DEBUG| utils:0153| [stdout] 1..1
04/13 23:48:16 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Setting locale
failed.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Please check
that your locale settings:
04/13 23:48:16 ERROR| utils:0153| [stderr]LANGUAGE = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_ALL = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_CTYPE = "C.UTF-8",
04/13 23:48:16 ERROR| utils:0153| [stderr]LANG = "en_US.UTF-8"
04/13 23:48:16 ERROR| utils:0153| [stderr] are supported and
installed on your system.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Falling back to
the standard locale ("C").
04/13 23:48:17 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
04/13 23:48:21 DEBUG| utils:0153| [stdout] # [1] Basic trace file check
[PASS]
04/13 23:49:02 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers
[PASS]
04/13 23:49:09 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test
[PASS]
04/13 23:49:13 DEBUG| utils:0153| [stdout] # [4] Basic event tracing
check[PASS]
04/13 23:49:18 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer
size [PASS]
04/13 23:49:23 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing
setting [PASS]
04/13 23:49:27 DEBUG| utils:0153| [stdout] # [7] trace_pipe and
trace_marker [PASS]
04/13 23:49:32 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct
functions against tracers [UNRESOLVED]
04/13 23:49:33 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct
functions against kprobes [UNSUPPORTED]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event -
add/remove kprobe events[FAIL]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event -
add/remove synthetic events [UNSUPPORTED]
04/13 23:49:38 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event -
selective clear (compatibility) [UNSUPPORTED]
04/13 23:49:39 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event -
generic clear event [UNSUPPORTED]
04/13 23:49:44
[Kernel-packages] [Bug 1923683] Re: ftrace from ubuntu_kernel_selftests failed with "test for function event triggers" on F/G/H
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Tags added: sru-20211129
--
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/1923683
Title:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on F/G/H
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Confirmed
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Confirmed
Status in linux source package in Impish:
New
Bug description:
ftrace from ubuntu_kernel_selftests failed with "test for function
event triggers" on Groovy riscv 5.8.0-21.23
This test was recently added, not considering a regression
Log is getting cut off from regression test report. the below is all
that could be retrieved at the moment:
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 >
/proc/sys/net/ipv4/conf/all/accept_local''
04/13 23:48:00 DEBUG| utils:0116| Running 'sudo make -C
linux/tools/testing/selftests TARGETS=ftrace run_tests'
04/13 23:48:00 DEBUG| utils:0153| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
04/13 23:48:01 DEBUG| utils:0153| [stdout] make --no-builtin-rules
ARCH=riscv -C ../../.. headers_install
04/13 23:48:01 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:14 DEBUG| utils:0153| [stdout] INSTALL ./usr/include
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done
for 'all'.
04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
04/13 23:48:16 DEBUG| utils:0153| [stdout] TAP version 13
04/13 23:48:16 DEBUG| utils:0153| [stdout] 1..1
04/13 23:48:16 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Setting locale
failed.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Please check
that your locale settings:
04/13 23:48:16 ERROR| utils:0153| [stderr]LANGUAGE = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_ALL = (unset),
04/13 23:48:16 ERROR| utils:0153| [stderr]LC_CTYPE = "C.UTF-8",
04/13 23:48:16 ERROR| utils:0153| [stderr]LANG = "en_US.UTF-8"
04/13 23:48:16 ERROR| utils:0153| [stderr] are supported and
installed on your system.
04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Falling back to
the standard locale ("C").
04/13 23:48:17 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
04/13 23:48:21 DEBUG| utils:0153| [stdout] # [1] Basic trace file check
[PASS]
04/13 23:49:02 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers
[PASS]
04/13 23:49:09 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test
[PASS]
04/13 23:49:13 DEBUG| utils:0153| [stdout] # [4] Basic event tracing
check[PASS]
04/13 23:49:18 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer
size [PASS]
04/13 23:49:23 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing
setting [PASS]
04/13 23:49:27 DEBUG| utils:0153| [stdout] # [7] trace_pipe and
trace_marker [PASS]
04/13 23:49:32 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct
functions against tracers [UNRESOLVED]
04/13 23:49:33 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct
functions against kprobes [UNSUPPORTED]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event -
add/remove kprobe events[FAIL]
04/13 23:49:37 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event -
add/remove synthetic events [UNSUPPORTED]
04/13 23:49:38 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event -
selective clear (compatibility) [UNSUPPORTED]
04/13 23:49:39 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event -
generic clear event [UNSUPPORTED]
04/13 23:49:44 DEBUG| utils:0153| [stdout] # [14] event tracing -
enable/disable with event level files [PASS]
04/13 23:49:50 DEBUG|
[Kernel-packages] [Bug 1953202] Re: Bionic update: upstream stable patchset 2021-12-03
** Changed in: linux (Ubuntu Bionic) 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/1953202 Title: Bionic update: upstream stable patchset 2021-12-03 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-12-03 Ported from the following upstream stable releases: v4.14.254, v4.19.215 v4.19.216 v4.14.255, v4.19.217 from git://git.kernel.org/ ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned ARM: 9134/1: remove duplicate memcpy() definition ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype ARM: 8819/1: Remove '-p' from LDFLAGS usbnet: sanity check for maxpacket usbnet: fix error return code in usbnet_probe() ata: sata_mv: Fix the error handling of mv_chip_id() nfc: port100: fix using -ERRNO as command type mask ipv4: use siphash instead of Jenkins in fnhe_hashfun() mmc: vub300: fix control-message timeouts mmc: dw_mmc: exynos: fix the finding clock sample value mmc: sdhci: Map more voltage level to SDHCI_POWER_330 mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit net: lan78xx: fix division by zero in send path regmap: Fix possible double-free in regcache_rbtree_exit() net: batman-adv: fix error handling nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST net: nxp: lpc_eth.c: avoid hang when bringing interface down sctp: use init_tag from inithdr for ABORT chunk sctp: fix the processing for COOKIE_ECHO chunk sctp: add vtag check in sctp_sf_violation sctp: add vtag check in sctp_sf_do_8_5_1_E_sa sctp: add vtag check in sctp_sf_ootb ARM: 9141/1: only warn about XIP address when not compile testing arm64: Avoid premature usercopy failure ipv6: use siphash in rt6_exception_hash() ipv6: make exception cache less predictible arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node UBUNTU: upstream stable to v4.14.254, v4.19.215 scsi: core: Put LLD module refcnt after SCSI device is released media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() sfc: Fix reading non-legacy supported link modes ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" UBUNTU: upstream stable to v4.19.216 mm/zsmalloc: Prepare to variable MAX_PHYSMEM_BITS arch: pgtable: define MAX_POSSIBLE_PHYSMEM_BITS where needed block: introduce multi-page bvec helpers Revert "x86/kvm: fix vcpu-id indexed array sizes" usb: gadget: Mark USB_FSL_QE broken on 64-bit usb: musb: Balance list entry in musb_gadget_queue usb-storage: Add compatibility quirk flags for iODD 2531/2541 printk/console: Allow to disable console output by using console="" or console=null isofs: Fix out of bound access for corrupted isofs image comedi: dt9812: fix DMA buffers on stack comedi: ni_usb6501: fix NULL-deref in command paths comedi: vmk80xx: fix transfer-buffer overflows comedi: vmk80xx: fix bulk-buffer overflow comedi: vmk80xx: fix bulk and interrupt message timeouts staging: r8712u: fix control-message timeout staging: rtl8192u: fix control-message timeouts rsi: fix control-message timeout usb: ehci: handshake CMD_RUN instead of STS_HALT UBUNTU: upstream stable to v4.14.255, v4.19.217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953202/+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 1952665] Re: Impish update: upstream stable patchset 2021-11-29
** Changed in: linux (Ubuntu Impish) 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/1952665 Title: Impish update: upstream stable patchset 2021-11-29 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-29 Ported from the following upstream stable releases: v5.10.77, v5.14.16 v5.10.78, v5.14.17 v5.10.79, v5.14.18 from git://git.kernel.org/ ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned ARM: 9134/1: remove duplicate memcpy() definition ARM: 9138/1: fix link warning with XIP + frame-pointer ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype ARM: 9141/1: only warn about XIP address when not compile testing usbnet: sanity check for maxpacket usbnet: fix error return code in usbnet_probe() Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" pinctrl: amd: disable and mask interrupts on probe ata: sata_mv: Fix the error handling of mv_chip_id() nfc: port100: fix using -ERRNO as command type mask net/tls: Fix flipped sign in tls_err_abort() calls mmc: vub300: fix control-message timeouts mmc: cqhci: clear HALT state after CQE enable mmc: mediatek: Move cqhci init behind ungate clock mmc: dw_mmc: exynos: fix the finding clock sample value mmc: sdhci: Map more voltage level to SDHCI_POWER_330 mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit ocfs2: fix race between searching chunks and release journal_head from buffer_head nvme-tcp: fix H2CData PDU send accounting (again) cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() cfg80211: fix management registrations locking net: lan78xx: fix division by zero in send path mm, thp: bail out early in collapse_file for writeback page drm/amdgpu: fix out of bounds write cgroup: Fix memory leak caused by missing cgroup_bpf_offline riscv, bpf: Fix potential NULL dereference tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function bpf: Fix potential race in tail call compatibility check bpf: Fix error usage of map_fd and fdget() in generic_map_update_batch() IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields IB/hfi1: Fix abba locking issue with sc_disable() nvmet-tcp: fix data digest pointer calculation nvme-tcp: fix data digest pointer calculation nvme-tcp: fix possible req->offset corruption octeontx2-af: Display all enabled PF VF rsrc_alloc entries. RDMA/mlx5: Set user priority for DCT arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node reset: brcmstb-rescal: fix incorrect polarity of status bit regmap: Fix possible double-free in regcache_rbtree_exit() net: batman-adv: fix error handling net-sysfs: initialize uid and gid before calling net_ns_get_ownership cfg80211: correct bridge/4addr mode check net: Prevent infinite while loop in skb_tx_hash() RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string gpio: xgs-iproc: fix parsing of ngpios property nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST mlxsw: pci: Recycle received packet upon allocation failure net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent net: nxp: lpc_eth.c: avoid hang when bringing interface down net/tls: Fix flipped sign in async_wait.err assignment phy: phy_ethtool_ksettings_get: Lock the phy for consistency phy: phy_ethtool_ksettings_set: Move after phy_start_aneg phy: phy_start_aneg: Add an unlocked version phy: phy_ethtool_ksettings_set: Lock the PHY while changing settings sctp: use init_tag from inithdr for ABORT chunk sctp: fix the processing for INIT_ACK chunk sctp: fix the processing for COOKIE_ECHO chunk sctp: add vtag check in sctp_sf_violation sctp: add vtag check in sctp_sf_do_8_5_1_E_sa sctp: add vtag check in sctp_sf_ootb KVM: s390: clear kicked_mask before sleeping again KVM: s390: preserve deliverable_mask in __airqs_kick_single_vcpu scsi: ufs: ufs-exynos: Correct timeout value setting registers riscv:
[Kernel-packages] [Bug 1953071] Re: Focal update: v5.4.159 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1953071 Title: Focal update: v5.4.159 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.159 upstream stable release from git://git.kernel.org/ Revert "x86/kvm: fix vcpu-id indexed array sizes" usb: ehci: handshake CMD_RUN instead of STS_HALT usb: gadget: Mark USB_FSL_QE broken on 64-bit usb: musb: Balance list entry in musb_gadget_queue usb-storage: Add compatibility quirk flags for iODD 2531/2541 binder: don't detect sender/target during buffer cleanup printk/console: Allow to disable console output by using console="" or console=null isofs: Fix out of bound access for corrupted isofs image comedi: dt9812: fix DMA buffers on stack comedi: ni_usb6501: fix NULL-deref in command paths comedi: vmk80xx: fix transfer-buffer overflows comedi: vmk80xx: fix bulk-buffer overflow comedi: vmk80xx: fix bulk and interrupt message timeouts staging: r8712u: fix control-message timeout staging: rtl8192u: fix control-message timeouts media: staging/intel-ipu3: css: Fix wrong size comparison imgu_css_fw_init rsi: fix control-message timeout Linux 5.4.159 UBUNTU: upstream stable to v5.4.159 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953071/+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 1953066] Re: Focal update: v5.4.158 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1953066 Title: Focal update: v5.4.158 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.158 upstream stable release from git://git.kernel.org/ scsi: core: Put LLD module refcnt after SCSI device is released vrf: Revert "Reset skb conntrack connection..." net: ethernet: microchip: lan743x: Fix skb allocation failure media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() Revert "xhci: Set HCD flag to defer primary roothub registration" Revert "usb: core: hcd: Add support for deferring roothub registration" sfc: Fix reading non-legacy supported link modes ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" Linux 5.4.158 UBUNTU: upstream stable to v5.4.158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953066/+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 1953387] Re: Focal update: v5.4.160 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1953387 Title: Focal update: v5.4.160 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.160 upstream stable release from git://git.kernel.org/ xhci: Fix USB 3.1 enumeration issues by increasing roothub power-on-good delay usb: xhci: Enable runtime-pm by default on AMD Yellow Carp platform binder: use euid from cred instead of using task binder: use cred instead of task for selinux checks binder: use cred instead of task for getsecid Input: iforce - fix control-message timeout Input: elantench - fix misreporting trackpoint coordinates Input: i8042 - Add quirk for Fujitsu Lifebook T725 libata: fix read log timeout value ocfs2: fix data corruption on truncate scsi: qla2xxx: Fix kernel crash when accessing port_speed sysfs file scsi: qla2xxx: Fix use after free in eh_abort path mmc: dw_mmc: Dont wait for DRTO on Write RSP error parisc: Fix ptrace check on syscall return tpm: Check for integer overflow in tpm2_map_response_body() firmware/psci: fix application of sizeof to pointer crypto: s5p-sss - Add error handling in s5p_aes_probe() media: ite-cir: IR receiver stop working after receive overflow media: ir-kbd-i2c: improve responsiveness of hauppauge zilog receivers media: v4l2-ioctl: Fix check_ext_ctrls ALSA: hda/realtek: Add quirk for Clevo PC70HS ALSA: hda/realtek: Add a quirk for Acer Spin SP513-54N ALSA: hda/realtek: Add quirk for ASUS UX550VE ALSA: hda/realtek: Add quirk for HP EliteBook 840 G7 mute LED ALSA: ua101: fix division by zero at probe ALSA: 6fire: fix control and bulk message timeouts ALSA: line6: fix control and interrupt message timeouts ALSA: usb-audio: Add registration quirk for JBL Quantum 400 ALSA: synth: missing check for possible NULL after the call to kstrdup ALSA: timer: Fix use-after-free problem ALSA: timer: Unconditionally unlink slave instances, too fuse: fix page stealing x86/sme: Use #define USE_EARLY_PGTABLE_L5 in mem_encrypt_identity.c x86/cpu: Fix migration safety with X86_BUG_NULL_SEL x86/irq: Ensure PI wakeup handler is unregistered before module unload cavium: Return negative value when pci_alloc_irq_vectors() fails scsi: qla2xxx: Return -ENOMEM if kzalloc() fails scsi: qla2xxx: Fix unmap of already freed sgl cavium: Fix return values of the probe function sfc: Don't use netif_info before net_device setup hyperv/vmbus: include linux/bitops.h ARM: dts: sun7i: A20-olinuxino-lime2: Fix ethernet phy-mode reset: socfpga: add empty driver allowing consumers to probe mmc: winbond: don't build on M68K drm: panel-orientation-quirks: Add quirk for Aya Neo 2021 bpf: Define bpf_jit_alloc_exec_limit for arm64 JIT bpf: Prevent increasing bpf_jit_limit above max xen/netfront: stop tx queues during live migration nvmet-tcp: fix a memory leak when releasing a queue spi: spl022: fix Microwire full duplex mode net: multicast: calculate csum of looped-back and forwarded packets watchdog: Fix OMAP watchdog early handling drm: panel-orientation-quirks: Add quirk for GPD Win3 nvmet-tcp: fix header digest verification r8169: Add device 10ec:8162 to driver r8169 vmxnet3: do not stop tx queues after netif_device_detach() nfp: bpf: relax prog rejection for mtu check through max_pkt_offset net/smc: Correct spelling mistake to TCPF_SYN_RECV btrfs: clear MISSING device status bit in btrfs_close_one_device btrfs: fix lost error handling when replaying directory deletes btrfs: call btrfs_check_rw_degradable only if there is a missing device ia64: kprobes: Fix to pass correct trampoline address to the handler hwmon: (pmbus/lm25066) Add offset coefficients regulator: s5m8767: do not use reset value as DVS voltage if GPIO DVS is disabled regulator: dt-bindings: samsung,s5m8767: correct s5m8767,pmic-buck-default-dvs-idx property EDAC/sb_edac: Fix top-of-high-memory value for Broadwell/Haswell mwifiex: fix division by zero in fw download path ath6kl: fix division by zero in send path ath6kl: fix control-message timeout ath10k: fix control-message timeout ath10k: fix division by zero in send path PCI: Mark Atheros QCA6174 to avoid bus reset rtl8187: fix
[Kernel-packages] [Bug 1954337] Re: Impish update: upstream stable patchset 2021-12-09
** Changed in: linux (Ubuntu Impish) 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/1954337 Title: Impish update: upstream stable patchset 2021-12-09 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-12-09 Ported from the following upstream stable releases: v5.10.80, v5.14.19, v5.14.20 from git://git.kernel.org/ Note: This patch set includes patches from v5.10.80 and v5.14.19. v5.14.20 was comprised entirely of a handful of reverts to patches we never carried in Impish. xhci: Fix USB 3.1 enumeration issues by increasing roothub power-on-good delay usb: xhci: Enable runtime-pm by default on AMD Yellow Carp platform Input: iforce - fix control-message timeout Input: elantench - fix misreporting trackpoint coordinates Input: i8042 - Add quirk for Fujitsu Lifebook T725 libata: fix read log timeout value ocfs2: fix data corruption on truncate scsi: core: Remove command size deduction from scsi_setup_scsi_cmnd() scsi: qla2xxx: Fix kernel crash when accessing port_speed sysfs file scsi: qla2xxx: Fix use after free in eh_abort path mmc: mtk-sd: Add wait dma stop done flow mmc: dw_mmc: Dont wait for DRTO on Write RSP error exfat: fix incorrect loading of i_blocks for large files parisc: Fix set_fixmap() on PA1.x CPUs parisc: Fix ptrace check on syscall return tpm: Check for integer overflow in tpm2_map_response_body() firmware/psci: fix application of sizeof to pointer crypto: s5p-sss - Add error handling in s5p_aes_probe() media: rkvdec: Do not override sizeimage for output format media: ite-cir: IR receiver stop working after receive overflow media: rkvdec: Support dynamic resolution changes media: ir-kbd-i2c: improve responsiveness of hauppauge zilog receivers media: v4l2-ioctl: Fix check_ext_ctrls ALSA: hda/realtek: Fix mic mute LED for the HP Spectre x360 14 ALSA: hda/realtek: Add a quirk for HP OMEN 15 mute LED ALSA: hda/realtek: Add quirk for Clevo PC70HS ALSA: hda/realtek: Headset fixup for Clevo NH77HJQ ALSA: hda/realtek: Add a quirk for Acer Spin SP513-54N ALSA: hda/realtek: Add quirk for ASUS UX550VE ALSA: hda/realtek: Add quirk for HP EliteBook 840 G7 mute LED ALSA: ua101: fix division by zero at probe ALSA: 6fire: fix control and bulk message timeouts ALSA: line6: fix control and interrupt message timeouts ALSA: usb-audio: Line6 HX-Stomp XL USB_ID for 48k-fixed quirk ALSA: usb-audio: Add registration quirk for JBL Quantum 400 ALSA: hda: Free card instance properly at probe errors ALSA: synth: missing check for possible NULL after the call to kstrdup ALSA: timer: Fix use-after-free problem ALSA: timer: Unconditionally unlink slave instances, too ext4: fix lazy initialization next schedule time computation in more granular unit ext4: ensure enough credits in ext4_ext_shift_path_extents ext4: refresh the ext4_ext_path struct after dropping i_data_sem. fuse: fix page stealing x86/sme: Use #define USE_EARLY_PGTABLE_L5 in mem_encrypt_identity.c x86/cpu: Fix migration safety with X86_BUG_NULL_SEL x86/irq: Ensure PI wakeup handler is unregistered before module unload ASoC: soc-core: fix null-ptr-deref in snd_soc_del_component_unlocked() ALSA: hda/realtek: Fixes HP Spectre x360 15-eb1xxx speakers cavium: Return negative value when pci_alloc_irq_vectors() fails scsi: qla2xxx: Return -ENOMEM if kzalloc() fails scsi: qla2xxx: Fix unmap of already freed sgl mISDN: Fix return values of the probe function cavium: Fix return values of the probe function sfc: Export fibre-specific supported link modes sfc: Don't use netif_info before net_device setup hyperv/vmbus: include linux/bitops.h ARM: dts: sun7i: A20-olinuxino-lime2: Fix ethernet phy-mode reset: socfpga: add empty driver allowing consumers to probe mmc: winbond: don't build on M68K drm: panel-orientation-quirks: Add quirk for Aya Neo 2021 fcnal-test: kill hanging ping/nettest binaries on cleanup bpf: Define bpf_jit_alloc_exec_limit for arm64 JIT bpf: Prevent increasing bpf_jit_limit above max gpio: mlxbf2.c: Add check for bgpio_init failure xen/netfront: stop tx queues during live migration nvmet-tcp: fix
[Kernel-packages] [Bug 1950042] Re: Let NVMe with HMB use native power control again
Hi Kai-Heng. May you please verify this bug is fixed in the Hirsute and Impish kernels in -proposed? Thank you! -- 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/1950042 Title: Let NVMe with HMB use native power control again Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 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: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 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: Impact] NVMe with HMB may still do DMA during suspend, so there was a commit that put the NVMe to PCI D3 during suspend to prevent DMA activities. However, this makes them consumes much more power because modern NVMe requires to stay at PCI D0 to make its natve power control work. [Fix] Instead of put the NVMe to PCI D3 and reset it afterward, simply disable HMB and re-enable HMB, for suspend and resume respectively. [Test] On affected system, Intel SoC can only reach PC3 during suspend. With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use significant less power. [Where problems could occur] The original approach, i.e. disable NVMe and put it to PCI D3 to prevent DMA activies, was just a precaution. There wasn't any case that indicates it happens in practice. This is a different approach to the same problem, which is a theoretical problem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950042/+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 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. + + This test was previously being skipped. After recent test changes, it's + now showing up as a failure. Not a regression. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: - Impish/linux 5.13.0-23.23 - Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) - Foal/hwe-5.13 5.13.0-23.23~20.04.1 - Focal/hwe-5.11 5.11.0-42.46~20.04.1 - + Impish/linux 5.13.0-23.23 + Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) + Foal/hwe-5.13 5.13.0-23.23~20.04.1 + Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' - Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz -- 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. This test was previously being skipped. After recent test changes, it's now showing up as a failure. Not a regression. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953366/+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 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
** Summary changed: - spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el + spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el ** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. + ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing + on 5.13 and 5.11 + + Found failing on: + Impish/linux 5.13.0-23.23 + Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) + Foal/hwe-5.13 5.13.0-23.23~20.04.1 + Focal/hwe-5.11 5.11.0-42.46~20.04.1 + + + 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 + 23:45:31 DEBUG| [stdout] # test: spectre_v2 + 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty + 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' + 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 + 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 + 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 + 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 + 23:45:50 DEBUG| [stdout] # Miss percent 99 % + 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! + 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation + 23:45:50 DEBUG| [stdout] # failure: spectre_v2 + 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 + 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' + + Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211129_233258_23074@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/l/linux/20211204_001958_634a0@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211129_205509_9a143@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz -- 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953366/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el
** Tags added: hirsute 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211129_233258_23074@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/l/linux/20211204_001958_634a0@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211129_205509_9a143@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953366/+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 1953366] [NEW] spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211129_233258_23074@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/l/linux/20211204_001958_634a0@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211129_205509_9a143@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute impish kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux ADT test failure with linux/5.13.0-23.23 + spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el -- 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/1953366 Title: spectre_v2 from ubuntu_kernel_selftests failure with Impish/Hirsute ppc64el Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211129_233258_23074@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/l/linux/20211204_001958_634a0@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211129_205509_9a143@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953366/+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 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0
confirmed fixed on impish 5.13.0-22.22 and focal 5.4.0-91.102
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211109_160610_20083@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/ppc64el/l/linux/2029_042322_b4551@/log.gz
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1948351
Title:
ppc64 BPF JIT mod by 1 will not return 0
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will
produce code that returns the dividend, just like a division, instead of 0.
Both eBPF and cBPF will fail as well when doing such operations.
[Test case]
$ cat bpf-mod1.c
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))
static int pair[2];
static int attach()
{
int r;
struct sock_filter insn[] = {
{ BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
{ BPF_ALU | BPF_MOD, 0, 0, 1 },
{ BPF_RET | BPF_A, 0, 0, 0 },
};
struct sock_fprog prog = {};
prog.filter = insn;
prog.len = ARRAY_SIZE(insn);
socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, ,
sizeof(prog));
return 0;
}
int main(int argc, char **argv)
{
int buf[5];
int r;
r = attach();
if (r < 0) {
err(1, "function will error out already");
}
write(pair[0], "hello", 5);
r = recv(pair[1], buf, 5, MSG_DONTWAIT);
if (r != -1 || errno != EAGAIN) {
err(1, "program failed");
}
return 0;
}
$ gcc -o bpf-mod1 bpf-mod1.c
$ ./bpf-mod1
cbpf-mod1: program failed: Success
After fix:
$ ./bpf-mod1
$ echo $?
0
[Potential regression]
BPF programs might be misbehave on ppc64el.
This is a scripted bug report about ADT failures while running linux
tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be
determined.
Consistently failing on Focal/linux 5.4.0-90.101
13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1
Testing failed on:
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+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 1943732] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4
** Tags added: sru-20211018 -- 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/1943732 Title: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: Testcase cpufreq_boost from ubuntu_ltp.kernel_misc failed with focal/linux 5.4.0-85.95 on the P9 node baltar. 13:50:50 DEBUG| [stdout] startup='Wed Sep 8 13:42:39 2021' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : found 'acpi_cpufreq' driver, sysfs knob '/sys /devices/system/cpu/cpufreq/boost' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : maximum speed is 380 KHz 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost enabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2006 ms 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost disabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2027 ms 13:50:50 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189: compare time spent with and without boost (-2%) 13:50:50 DEBUG| [stdout] tag=cpufreq_boost stime=1631108559 dur=4 exit=exited stat=1 core=no cu=404 cs=2 This is not a regression as it has been failing since older versions (at least since 5.4.0-75.84). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943732/+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 1947709] Re: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active"
verified the same revert is on Impish/Focal/Bionic. switching verification completed for those ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-impish ** Tags added: verification-done-bionic verification-done-focal 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/1947709 Title: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" has been applied to fix a page leaking issue. However a slightly different fix has been applied upstream: 9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page leak in cachefiles_read_backing_file while vmscan is active Basically we are fixing the same issue in two different ways at the same time, but even worse our patch an introduce a potential NULL pointer dereference: we do a put_page(newpage) and set newpage = NULL in the main for() loop and then we may do additional put_page(newpage) after the main for loop if ret == -EEXIST, that would trigger the NULL pointer dereference. [Test case] No test case or reproducer is available at the moment, this issue has been found simply by reviewing the code. [Fix] Drop the SAUCE patch and rely on the upstream fix. [Regression potential] If the analysis is not correct we may re-introduce a page leak in cachefiles (NFS for example), but it seems unlikely to happen, since the upstream fix is addressing the page leaking already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947709/+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 1948436] Re: Add RevID field to VPD info in EEPROM
** 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/1948436 Title: Add RevID field to VPD info in EEPROM Status in linux-bluefield package in Ubuntu: Fix Committed Bug description: SRU Justification: [Impact] Currently, the VPD info stored in the EEPROM does not include a Rev ID. This field is incremented when a PN goes through minor HW changes. Sometimes, SW needs to differentiate the two versions of the card. Hence, this field should be supported in the EEPROM MFG partition. [Fix] EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add it to the EEPROM MFG and provide a sysfs entry to access the same via mlx-bootctl. [Test Case] This field is typically programmed at the manufacturing step using the bfcfg tool which uses the write mechanism in the driver and then the MFG partition is locked. Reading the "rev" sysfs will show the current value. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948436/+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 1944586] Re: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47"
Thank you, Eric! :) -- 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/1944586 Title: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47" Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] It has been brought to my attention the following: " We have been experiencing node lockups and degradation when testing fiber channel fail over for multi-path PURESTORAGE drives. Testing usually consists of either failing over the fabric or the local I/O module for the Cisco chassis which houses a number of individual blades. After rebooting a local Chassis I/O module we see commands like multipath -ll hanging. Resetting the blades individual fiber channel interface results in the following messages. " 6051160.241383] rport-9:0-1: blocked FC remote port time out: removing target and saving binding [6051160.252901] BUG: kernel NULL pointer dereference, address: 0040 [6051160.262267] #PF: supervisor read access in kernel mode [6051160.269314] #PF: error_code(0x) - not-present page [6051160.276016] PGD 0 P4D 0 [6051160.279807] Oops: [#1] SMP NOPTI [6051160.284642] CPU: 10 PID: 49346 Comm: kworker/10:2 Tainted: P O 5.4.0-77-generic #86-Ubuntu [6051160.295967] Hardware name: Cisco Systems Inc UCSB-B200-M5/UCSB-B200-M5, BIOS B200M5.4.1.1d.0.0609200543 06/09/2020 [6051160.308199] Workqueue: fc_dl_9 fc_timeout_deleted_rport [scsi_transport_fc] [6051160.316640] RIP: 0010:fnic_terminate_rport_io+0x10f/0x510 [fnic] [6051160.324050] Code: 48 89 c3 48 85 c0 0f 84 7b 02 00 00 48 05 20 01 00 00 48 89 45 b0 0f 84 6b 02 00 00 48 8b 83 58 01 00 00 48 8b 80 b8 01 00 00 <48> 8b 78 40 e8 68 e6 06 00 85 c0 0f 84 4c 02 00 00 48 8b 83 58 01 [6051160.346553] RSP: 0018:bc224f297d90 EFLAGS: 00010082 [6051160.353115] RAX: RBX: 90abdd4c4b00 RCX: 90d8ab2c2bb0 [6051160.361983] RDX: 90d8b5467400 RSI: RDI: 90d8ab3b4b40 [6051160.370812] RBP: bc224f297df8 R08: 90d8c08978c8 R09: 90d8b8850800 [6051160.379518] R10: 90d8a59d64c0 R11: 0001 R12: 90d8ab2c31f8 [6051160.388242] R13: R14: 0246 R15: 90d8ab2c27b8 [6051160.396953] FS: () GS:90d8c088() knlGS: [6051160.406838] CS: 0010 DS: ES: CR0: 80050033 [6051160.414168] CR2: 0040 CR3: 000fc1c0a004 CR4: 007626e0 [6051160.423146] DR0: DR1: DR2: [6051160.431884] DR3: DR6: fffe0ff0 DR7: 0400 [6051160.440615] PKRU: 5554 [6051160.444337] Call Trace: [6051160.447841] fc_terminate_rport_io+0x56/0x70 [scsi_transport_fc] [6051160.455263] fc_timeout_deleted_rport.cold+0x1bc/0x2c7 [scsi_transport_fc] [6051160.463623] process_one_work+0x1eb/0x3b0 [6051160.468784] worker_thread+0x4d/0x400 [6051160.473660] kthread+0x104/0x140 [6051160.478102] ? process_one_work+0x3b0/0x3b0 [6051160.483439] ? kthread_park+0x90/0x90 [6051160.488213] ret_from_fork+0x1f/0x40 [6051160.492901] Modules linked in: dm_service_time zfs(PO) zunicode(PO) zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_nat vhost_vsock vmw_vsock_virtio_transport_common vsock unix_diag nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net vhost tap 8021q garp mrp bluetooth ecdh_generic ecc tcp_diag inet_diag sctp nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nls_iso8859_1 dm_queue_length dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common isst_if_common skx_edac nfit x86_pkg_temp_thermal intel_powerclamp ipmi_ssif coretemp kvm_intel kvm rapl input_leds joydev intel_cstate mei_me ioatdma mei dca ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [6051160.492928] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear fnic mgag200 drm_vram_helper i2c_algo_bit ttm drm_kms_helper crct10dif_pclmul syscopyarea hid_generic crc32_pclmul libfcoe sysfillrect ghash_clmulni_intel sysimgblt aesni_intel fb_sys_fops crypto_simd libfc usbhid cryptd scsi_transport_fc hid drm glue_helper enic ahci lpc_ich libahci wmi [6051160.632623] CR2: 0040 [6051160.637043] ---[ end trace 236e6f4850146477 ]--- [Test Plan] There are two ways to replicate the bug: Reset a single chassis I/O module or fail over a
[Kernel-packages] [Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves
Thank you, Samuel! :)
--
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/1945180
Title:
vrf: fix refcnt leak with vxlan slaves
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
There are cases, where deleting a VRF device can hang waiting for the refcnt
to drop to 0, with the message:
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1
This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
used for dst_alloc with local routes"), included in linux v5.13. The
original patch, which has introduced the bug, is included in linux
v4.10.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b87b04f5019e
[Test Case]
The upstream patch includes a test case, which describe how to
reproduce the bug.
[Regression Potential]
The patch affects ipv4 routing. It is straightforward, it links new
dst to a vrf device instead of the loopback if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+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 1949397] Re: Hirsute update: upstream stable patchset 2021-11-01
** Changed in: linux (Ubuntu Hirsute) 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/1949397 Title: Hirsute update: upstream stable patchset 2021-11-01 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-01 Ported from the following upstream stable releases: v5.10.69, v5.14.8 from git://git.kernel.org/ PCI: pci-bridge-emul: Add PCIe Root Capabilities Register PCI: aardvark: Fix reporting CRS value console: consume APC, DM, DCS ARM: Qualify enabling of swiotlb_init() ARM: 9077/1: PLT: Move struct plt_entries definition to header ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link() ARM: 9079/1: ftrace: Add MODULE_PLTS support ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE sctp: validate chunk size in __rcv_asconf_lookup sctp: add param size validation for SCTP_PARAM_SET_PRIMARY staging: rtl8192u: Fix bitwise vs logical operator in TranslateRxSignalStuff819xUsb() coredump: fix memleak in dump_vma_snapshot() um: virtio_uml: fix memory leak on init failures dmaengine: acpi: Avoid comparison GSI with Linux vIRQ perf test: Fix bpf test sample mismatch reporting perf tools: Allow build-id with trailing zeros thermal/drivers/exynos: Fix an error code in exynos_tmu_probe() 9p/trans_virtio: Remove sysfs file on probe failure prctl: allow to setup brk for et_dyn executables nilfs2: use refcount_dec_and_lock() to fix potential UAF profiling: fix shift-out-of-bounds bugs PM: sleep: core: Avoid setting power.must_resume to false pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was registered pwm: mxs: Don't modify HW state in .probe() after the PWM chip was registered dmaengine: idxd: fix wq slot allocation index check platform/chrome: sensorhub: Add trace events for sample platform/chrome: cros_ec_trace: Fix format warnings ceph: allow ceph_put_mds_session to take NULL or ERR_PTR ceph: cancel delayed work instead of flushing on mdsc teardown Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH tools/bootconfig: Fix tracing_on option checking in ftrace2bconf.sh thermal/core: Fix thermal_cooling_device_register() prototype drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION() dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER parisc: Move pci_dev_is_behind_card_dino to where it is used iommu/amd: Relocate GAMSup check to early_enable_iommus dmaengine: idxd: depends on !UML dmaengine: sprd: Add missing MODULE_DEVICE_TABLE dmaengine: ioat: depends on !UML dmaengine: xilinx_dma: Set DMA mask for coherent APIs ceph: request Fw caps before updating the mtime in ceph_write_iter ceph: remove the capsnaps when removing caps ceph: lockdep annotations for try_nonblocking_invalidate btrfs: update the bdev time directly when closing btrfs: fix lockdep warning while mounting sprout fs nilfs2: fix memory leak in nilfs_sysfs_create_device_group nilfs2: fix NULL pointer in nilfs_##name##_attr_release nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group habanalabs: add validity check for event ID received from F/W pwm: img: Don't modify HW state in .remove() callback pwm: rockchip: Don't modify HW state in .remove() callback pwm: stm32-lp: Don't modify HW state in .remove() callback blk-throttle: fix UAF by deleteing timer in blk_throtl_exit() blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for multiple_queues rtc: rx8010: select REGMAP_I2C sched/idle: Make the idle timer expire in hard interrupt context drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV RDMA/mlx5: Fix xlt_chunk_align calculation staging: rtl8723bs: fix wpa_set_auth_algs() function dmaengine: idxd: have command status always set dmaengine: idxd: clear block on fault flag when clear wq arm64: mm: limit linear region to 51 bits for KVM in nVHE mode s390: add kmemleak annotation in stack_alloc() ceph: fix memory leak on decode
[Kernel-packages] [Bug 1944390] Re: Fix ignoring ct state match of OVS offload to TC/HW
Hi Bodong, may you please verify the focal/bluefield kernel in -proposed resolves this bug? You can find more instructions in comment #1. Thank you! -- 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/1944390 Title: Fix ignoring ct state match of OVS offload to TC/HW Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug When using OVS with tc to offload connection tracking flows, if user matches on ct_state other then trk and est, such as ct_state +rpl, it will be silently ignored by TC/HW and might result in wrong actions being executed. * How to test Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices) Enable HW offload and configure connection tracking OpenFlow rules which match on ct_state +rpl and do different actions based on that match. e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est-rpl, actions=$dev1" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est+rpl, actions=$dev2" With commits, ovs dump-flows (or tc show on devs) will have ct_state +rpl match, and without they don't have, meaning the match is ignored. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1944390/+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 1946266] Re: Add psample tunnel support and also two fixes for psample issues.
Hi Bodong, may you please verify the Focal kernel in -proposed resolves this bug? You can find more instructions in comment #1. Thank you! -- 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/1946266 Title: Add psample tunnel support and also two fixes for psample issues. Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) Fix psample compilation issue and add tunnel support * brief explanation of fixes Enhance psample * How to test Add tc rule with tunnel and sample actions and run traffic. Verify sample traffic on the sample interface. * What it could break. psample could be broke as new function is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946266/+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 1946393] Re: Fix byte count on fragmented packets in tc ct action
Hi Bodong, may you please verify the Focal/bluefield kernel in -proposed resolves this bug? You can find more instructions in comment #1. Thank you! -- 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/1946393 Title: Fix byte count on fragmented packets in tc ct action Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug First fragmented packets (frag offset = 0) byte len is zeroed when stolen by ip_defrag(). And since act_ct update the stats only afterwards (at end of execute), bytes aren't correctly accounted for such packets. * How to test Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices) Enable HW offload and configure connection tracking OpenFlow rules as below e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run fragmented icmp ping traffic (e.g ping -s 2000) dump ovs rules (ovs-appctl dpctl/dump-flows), observe byte count on frag=first rule: ct_state(-trk),recirc_id(0),in_port(2),eth_type(0x0800),ipv4(proto=1,frag=first), packets:10, bytes:13960, used:1.370s, actions:ct(zone=1),recirc(0x1) bytes would be zero if bug occurs. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946393/+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 1944586] Re: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47"
Hi Eric, may you please verify the focal kernel in -proposed resolves this bug? You can find more instructions for this in comment #4. Thank you! -- 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/1944586 Title: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47" Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] It has been brought to my attention the following: " We have been experiencing node lockups and degradation when testing fiber channel fail over for multi-path PURESTORAGE drives. Testing usually consists of either failing over the fabric or the local I/O module for the Cisco chassis which houses a number of individual blades. After rebooting a local Chassis I/O module we see commands like multipath -ll hanging. Resetting the blades individual fiber channel interface results in the following messages. " 6051160.241383] rport-9:0-1: blocked FC remote port time out: removing target and saving binding [6051160.252901] BUG: kernel NULL pointer dereference, address: 0040 [6051160.262267] #PF: supervisor read access in kernel mode [6051160.269314] #PF: error_code(0x) - not-present page [6051160.276016] PGD 0 P4D 0 [6051160.279807] Oops: [#1] SMP NOPTI [6051160.284642] CPU: 10 PID: 49346 Comm: kworker/10:2 Tainted: P O 5.4.0-77-generic #86-Ubuntu [6051160.295967] Hardware name: Cisco Systems Inc UCSB-B200-M5/UCSB-B200-M5, BIOS B200M5.4.1.1d.0.0609200543 06/09/2020 [6051160.308199] Workqueue: fc_dl_9 fc_timeout_deleted_rport [scsi_transport_fc] [6051160.316640] RIP: 0010:fnic_terminate_rport_io+0x10f/0x510 [fnic] [6051160.324050] Code: 48 89 c3 48 85 c0 0f 84 7b 02 00 00 48 05 20 01 00 00 48 89 45 b0 0f 84 6b 02 00 00 48 8b 83 58 01 00 00 48 8b 80 b8 01 00 00 <48> 8b 78 40 e8 68 e6 06 00 85 c0 0f 84 4c 02 00 00 48 8b 83 58 01 [6051160.346553] RSP: 0018:bc224f297d90 EFLAGS: 00010082 [6051160.353115] RAX: RBX: 90abdd4c4b00 RCX: 90d8ab2c2bb0 [6051160.361983] RDX: 90d8b5467400 RSI: RDI: 90d8ab3b4b40 [6051160.370812] RBP: bc224f297df8 R08: 90d8c08978c8 R09: 90d8b8850800 [6051160.379518] R10: 90d8a59d64c0 R11: 0001 R12: 90d8ab2c31f8 [6051160.388242] R13: R14: 0246 R15: 90d8ab2c27b8 [6051160.396953] FS: () GS:90d8c088() knlGS: [6051160.406838] CS: 0010 DS: ES: CR0: 80050033 [6051160.414168] CR2: 0040 CR3: 000fc1c0a004 CR4: 007626e0 [6051160.423146] DR0: DR1: DR2: [6051160.431884] DR3: DR6: fffe0ff0 DR7: 0400 [6051160.440615] PKRU: 5554 [6051160.444337] Call Trace: [6051160.447841] fc_terminate_rport_io+0x56/0x70 [scsi_transport_fc] [6051160.455263] fc_timeout_deleted_rport.cold+0x1bc/0x2c7 [scsi_transport_fc] [6051160.463623] process_one_work+0x1eb/0x3b0 [6051160.468784] worker_thread+0x4d/0x400 [6051160.473660] kthread+0x104/0x140 [6051160.478102] ? process_one_work+0x3b0/0x3b0 [6051160.483439] ? kthread_park+0x90/0x90 [6051160.488213] ret_from_fork+0x1f/0x40 [6051160.492901] Modules linked in: dm_service_time zfs(PO) zunicode(PO) zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_nat vhost_vsock vmw_vsock_virtio_transport_common vsock unix_diag nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net vhost tap 8021q garp mrp bluetooth ecdh_generic ecc tcp_diag inet_diag sctp nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nls_iso8859_1 dm_queue_length dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common isst_if_common skx_edac nfit x86_pkg_temp_thermal intel_powerclamp ipmi_ssif coretemp kvm_intel kvm rapl input_leds joydev intel_cstate mei_me ioatdma mei dca ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [6051160.492928] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear fnic mgag200 drm_vram_helper i2c_algo_bit ttm drm_kms_helper crct10dif_pclmul syscopyarea hid_generic crc32_pclmul libfcoe sysfillrect ghash_clmulni_intel sysimgblt aesni_intel fb_sys_fops crypto_simd libfc usbhid cryptd scsi_transport_fc hid drm glue_helper enic ahci lpc_ich libahci wmi [6051160.632623] CR2: 0040 [6051160.637043] ---[ end trace
[Kernel-packages] [Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves
Hi Nicolas or Samuel, may you please verify the Bionic kernel in
-proposed resolves this bug? You can find more instructions in comment
#4. Thank you!
--
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/1945180
Title:
vrf: fix refcnt leak with vxlan slaves
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
There are cases, where deleting a VRF device can hang waiting for the refcnt
to drop to 0, with the message:
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1
This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
used for dst_alloc with local routes"), included in linux v5.13. The
original patch, which has introduced the bug, is included in linux
v4.10.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b87b04f5019e
[Test Case]
The upstream patch includes a test case, which describe how to
reproduce the bug.
[Regression Potential]
The patch affects ipv4 routing. It is straightforward, it links new
dst to a vrf device instead of the loopback if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+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 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during s2idle
Hi Chris, may you please verify the Impish kernel in -proposed resolves this bug? You can find further instructions for this in comment #8. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931072 Title: USB Type-C hotplug event not handled properly in TGL-H system during s2idle Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] The system will be hold by the infinite loop in ACPI method IPCS after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. It's because the system is unaware of the unplug event and it seems keep something asserted which will never be released while the system trying to exit s2idle. [Fix] Disconnect TypeC PHYs during system suspend and shutdown, even with the corresponding TypeC sink still plugged to its connector. The HPD event is no longer triggered when the system is in s2idle so the resume process will not be hindered. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Where problems could occur] Low. This will only make a difference in the TypeC DP alternate mode, and the display driver will detect the display connector after resume. == Original Bug Description == [Summary] As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the USB Type-C docking/dongle with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. It's because the display connector hotplug event not handled properly in graphics drivers and the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit. [ 154.446781] [ 154.446783] [ 154.446783] Initialized Local Variables for Method [IPCS]: [ 154.446784] Local0: 9863e365 Integer 09C5 [ 154.446790] [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments defined for method invocation) [ 154.446792] Arg0: 25568fbd Integer 00AC [ 154.446795] Arg1: 9ef30e76 Integer [ 154.446798] Arg2: fdf820f0 Integer 0010 [ 154.446801] Arg3: 9fc2a088 Integer 0001 [ 154.446804] Arg4: 3a3418f7 Integer 0001 [ 154.446807] Arg5: 20c4b87c Integer [ 154.446810] Arg6: 8b965a8a Integer [ 154.446813] [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446852] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446860] acpi device:02: Failed to change power state to D0 [ 154.690760] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) [Reproduce Steps] 1. Connect either Dell WD19SC/DC/TB docking station(USB Type-C) to the system. 2. Connect to external display to HDMI/DisplayPort of the
[Kernel-packages] [Bug 1947885] Re: Focal update: v5.4.149 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1947885 Title: Focal update: v5.4.149 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.149 upstream stable release from git://git.kernel.org/ PCI: pci-bridge-emul: Fix big-endian support PCI: aardvark: Indicate error in 'val' when config read fails PCI: pci-bridge-emul: Add PCIe Root Capabilities Register PCI: aardvark: Fix reporting CRS value PCI/ACPI: Add Ampere Altra SOC MCFG quirk KVM: remember position in kvm->vcpus array console: consume APC, DM, DCS s390/pci_mmio: fully validate the VMA before calling follow_pte() ARM: Qualify enabling of swiotlb_init() apparmor: remove duplicate macro list_entry_is_head() ARM: 9077/1: PLT: Move struct plt_entries definition to header ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link() ARM: 9079/1: ftrace: Add MODULE_PLTS support ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE sctp: validate chunk size in __rcv_asconf_lookup sctp: add param size validation for SCTP_PARAM_SET_PRIMARY staging: rtl8192u: Fix bitwise vs logical operator in TranslateRxSignalStuff819xUsb() um: virtio_uml: fix memory leak on init failures dmaengine: acpi: Avoid comparison GSI with Linux vIRQ thermal/drivers/exynos: Fix an error code in exynos_tmu_probe() 9p/trans_virtio: Remove sysfs file on probe failure prctl: allow to setup brk for et_dyn executables nilfs2: use refcount_dec_and_lock() to fix potential UAF profiling: fix shift-out-of-bounds bugs pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was registered phy: avoid unnecessary link-up delay in polling mode net: stmmac: reset Tx desc base address before restarting Tx Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH thermal/core: Fix thermal_cooling_device_register() prototype drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION() parisc: Move pci_dev_is_behind_card_dino to where it is used dmaengine: sprd: Add missing MODULE_DEVICE_TABLE dmaengine: ioat: depends on !UML dmaengine: xilinx_dma: Set DMA mask for coherent APIs ceph: request Fw caps before updating the mtime in ceph_write_iter ceph: lockdep annotations for try_nonblocking_invalidate btrfs: fix lockdep warning while mounting sprout fs nilfs2: fix memory leak in nilfs_sysfs_create_device_group nilfs2: fix NULL pointer in nilfs_##name##_attr_release nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group pwm: img: Don't modify HW state in .remove() callback pwm: rockchip: Don't modify HW state in .remove() callback pwm: stm32-lp: Don't modify HW state in .remove() callback blk-throttle: fix UAF by deleteing timer in blk_throtl_exit() rtc: rx8010: select REGMAP_I2C drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV Linux 5.4.149 UBUNTU: upstream stable to v5.4.149 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947885/+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 1947886] Re: Focal update: v5.4.150 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1947886 Title: Focal update: v5.4.150 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.150 upstream stable release from git://git.kernel.org/ ocfs2: drop acl cache for directories too usb: gadget: r8a66597: fix a loop in set_feature() usb: dwc2: gadget: Fix ISOC flow for BDMA and Slave usb: dwc2: gadget: Fix ISOC transfer complete handling for DDMA usb: musb: tusb6010: uninitialized data in tusb_fifo_write_unaligned() cifs: fix incorrect check for null pointer in header_assemble xen/x86: fix PV trap handling on secondary processors usb-storage: Add quirk for ScanLogic SL11R-IDE older than 2.6c USB: serial: cp210x: add ID for GW Instek GDM-834x Digital Multimeter USB: cdc-acm: fix minor-number release binder: make sure fd closes complete staging: greybus: uart: fix tty use after free Re-enable UAS for LaCie Rugged USB3-FW with fk quirk USB: serial: mos7840: remove duplicated 0xac24 device ID USB: serial: option: add Telit LN920 compositions USB: serial: option: remove duplicate USB device ID USB: serial: option: add device id for Foxconn T99W265 mcb: fix error handling in mcb_alloc_bus() erofs: fix up erofs_lookup tracepoint btrfs: prevent __btrfs_dump_space_info() to underflow its free space serial: mvebu-uart: fix driver's tx_empty callback net: hso: fix muxed tty registration afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR() enetc: Fix illegal access when reading affinity_hint bnxt_en: Fix TX timeout when TX ring size is set to the smallest net/smc: add missing error check in smc_clc_prfx_set() gpio: uniphier: Fix void functions to remove return value qed: rdma - don't wait for resources under hw error recovery flow net/mlx4_en: Don't allow aRFS for encapsulated packets scsi: iscsi: Adjust iface sysfs attr detection tty: synclink_gt, drop unneeded forward declarations tty: synclink_gt: rename a conflicting function name fpga: machxo2-spi: Return an error on failure fpga: machxo2-spi: Fix missing error code in machxo2_write_complete() thermal/core: Potential buffer overflow in thermal_build_list_of_policies() cifs: fix a sign extension bug scsi: qla2xxx: Restore initiator in dual mode scsi: lpfc: Use correct scnprintf() limit irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build irqchip/gic-v3-its: Fix potential VPE leak on error md: fix a lock order reversal in md_alloc blktrace: Fix uaf in blk_trace access after removing by sysfs net: macb: fix use after free on rmmod net: stmmac: allow CSR clock of 300MHz m68k: Double cast io functions to unsigned long ipv6: delay fib6_sernum increase in fib6_add bpf: Add oversize check before call kvcalloc() xen/balloon: use a kernel thread instead a workqueue nvme-multipath: fix ANA state updates when a namespace is not present sparc32: page align size in arch_dma_alloc blk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg pd compiler.h: Introduce absolute_pointer macro net: i825xx: Use absolute_pointer for memcpy from fixed memory location sparc: avoid stringop-overread errors qnx4: avoid stringop-overread errors parisc: Use absolute_pointer() to define PAGE0 arm64: Mark __stack_chk_guard as __ro_after_init alpha: Declare virt_to_phys and virt_to_bus parameter as pointer to volatile net: 6pack: Fix tx timeout and slot time spi: Fix tegra20 build with CONFIG_PM=n EDAC/synopsys: Fix wrong value type assignment for edac_mode thermal/drivers/int340x: Do not set a wrong tcc offset on resume arm64: dts: marvell: armada-37xx: Extend PCIe MEM space xen/balloon: fix balloon kthread freezing qnx4: work around gcc false positive warning bug Linux 5.4.150 UBUNTU: upstream stable to v5.4.150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947886/+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 1947888] Re: Focal update: v5.4.151 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1947888 Title: Focal update: v5.4.151 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.151 upstream stable release from git://git.kernel.org/ tty: Fix out-of-bound vmalloc access in imageblit cpufreq: schedutil: Use kobject release() method to free sugov_tunables cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory usb: cdns3: fix race condition before setting doorbell fs-verity: fix signed integer overflow with i_size near S64_MAX hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field scsi: ufs: Fix illegal offset in UPIU event trace mac80211: fix use-after-free in CCMP/GCMP RX x86/kvmclock: Move this_cpu_pvti into kvmclock.h drm/amd/display: Pass PCI deviceid into DC ipvs: check that ip_vs_conn_tab_bits is between 8 and 20 hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap mac80211: mesh: fix potentially unaligned access mac80211-hwsim: fix late beacon hrtimer handling sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb hwmon: (tmp421) report /PVLD condition as fault hwmon: (tmp421) fix rounding for negative values net: ipv4: Fix rtnexthop len when RTA_FLOW is present e100: fix length calculation in e100_get_regs_len e100: fix buffer overrun in e100_get_regs selftests, bpf: test_lwt_ip_encap: Really disable rp_filter scsi: csiostor: Add module softdep on cxgb4 net: hns3: do not allow call hns3_nic_net_open repeatedly net: sched: flower: protect fl_walk() with rcu af_unix: fix races in sk_peer_pid and sk_peer_cred accesses perf/x86/intel: Update event constraints for ICX elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings debugfs: debugfs_create_file_size(): use IS_ERR to check for error ipack: ipoctal: fix stack information leak ipack: ipoctal: fix tty registration race ipack: ipoctal: fix tty-registration error handling ipack: ipoctal: fix missing allocation-failure check ipack: ipoctal: fix module reference leak ext4: fix loff_t overflow in ext4_max_bitmap_size() ext4: fix reserved space counter leakage ext4: fix potential infinite loop in ext4_dx_readdir() HID: u2fzero: ignore incomplete packets without data net: udp: annotate data race around udp_sk(sk)->corkflag net: stmmac: don't attach interface until resume finishes PCI: Fix pci_host_bridge struct device release/free handling libnvdimm/pmem: Fix crash triggered when I/O in-flight during unbind hso: fix bailout in error case of probe usb: hso: fix error handling code of hso_create_net_device usb: hso: remove the bailout parameter crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() HID: betop: fix slab-out-of-bounds Write in betop_probe netfilter: ipset: Fix oversized kvmalloc() calls HID: usbhid: free raw_report buffers in usbhid_stop Linux 5.4.151 UBUNTU: upstream stable to v5.4.151 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947888/+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 1947781] Re: Hirsute update: upstream stable patchset 2021-10-19
** Changed in: linux (Ubuntu Hirsute) 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/1947781 Title: Hirsute update: upstream stable patchset 2021-10-19 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-10-19 Ported from the following upstream stable releases: v5.10.67, v5.13.19 from git://git.kernel.org/ rtc: tps65910: Correct driver module alias io_uring: place fixed tables under memcg limits io_uring: add ->splice_fd_in checks io_uring: fail links of cancelled timeouts io-wq: fix wakeup race when adding new work btrfs: wake up async_delalloc_pages waiters after submit btrfs: reset replace target device to allocation state on close blk-zoned: allow zone management send operations without CAP_SYS_ADMIN blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN PCI/MSI: Skip masking MSI-X on Xen PV powerpc/perf/hv-gpci: Fix counter value parsing xen: fix setting of max_pfn in shared_info 9p/xen: Fix end of loop tests for list_for_each_entry ceph: fix dereference of null pointer cf selftests/ftrace: Fix requirement check of README file tools/thermal/tmon: Add cross compiling support clk: socfpga: agilex: fix the parents of the psi_ref_clk clk: socfpga: agilex: fix up s2f_user0_clk representation clk: socfpga: agilex: add the bypass register for s2f_usr0 clock pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast pinctrl: ingenic: Fix incorrect pull up/down info soc: qcom: aoss: Fix the out of bound usage of cooling_devs soc: aspeed: lpc-ctrl: Fix boundary check for mmap soc: aspeed: p2a-ctrl: Fix boundary check for mmap arm64: mm: Fix TLBI vs ASID rollover arm64: head: avoid over-mapping in map_memory iio: ltc2983: fix device probe wcn36xx: Ensure finish scan is not requested before start scan crypto: public_key: fix overflow during implicit conversion block: bfq: fix bfq_set_next_ioprio_data() power: supply: max17042: handle fails of reading status register dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc() crypto: ccp - shutdown SEV firmware on kexec VMCI: fix NULL pointer dereference when unmapping queue pair media: uvc: don't do DMA on stack media: rc-loopback: return number of emitters rather than error s390/qdio: fix roll-back after timeout on ESTABLISH ccw s390/qdio: cancel the ESTABLISH ccw after timeout Revert "dmaengine: imx-sdma: refine to load context only once" dmaengine: imx-sdma: remove duplicated sdma_load_context libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs ARM: 9105/1: atags_to_fdt: don't warn about stack size f2fs: fix to do sanity check for sb/cp fields correctly PCI/portdrv: Enable Bandwidth Notification only if port supports it PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure PCI: xilinx-nwl: Enable the clock through CCF PCI: aardvark: Configure PCIe resources from 'ranges' DT property PCI: Export pci_pio_to_address() for module use PCI: aardvark: Fix checking for PIO status PCI: aardvark: Fix masking and unmasking legacy INTx interrupts HID: input: do not report stylus battery state as "full" f2fs: quota: fix potential deadlock pinctrl: remove empty lines in pinctrl subsystem pinctrl: armada-37xx: Correct PWM pins definitions scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND clk: rockchip: drop GRF dependency for rk3328/rk3036 pll types IB/hfi1: Adjust pkey entry in index 0 RDMA/iwcm: Release resources if iw_cm module initialization fails docs: Fix infiniband uverbs minor number scsi: BusLogic: Use %X for u32 sized integer rather than %lX pinctrl: samsung: Fix pinctrl bank pin count vfio: Use config not menuconfig for VFIO_NOIOMMU scsi: ufs: Fix memory corruption by ufshcd_read_desc_param() cpuidle: pseries: Fixup CEDE0 latency only for POWER10 onwards powerpc/stacktrace: Include linux/delay.h RDMA/efa: Remove double QP type assignment RDMA/mlx5: Delete not-available udata check cpuidle: pseries: Mark pseries_idle_proble() as __init f2fs: reduce the scope of setting fsck tag when de->name_len is zero openrisc: don't printk() unconditionally dma-debug: fix
[Kernel-packages] [Bug 1948873] Re: Hirsute update: upstream stable patchset 2021-10-26
** Changed in: linux (Ubuntu Hirsute)
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/1948873
Title:
Hirsute update: upstream stable patchset 2021-10-26
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Hirsute:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2021-10-26
Ported from the following upstream stable releases:
v5.10.68, v5.14.7
from git://git.kernel.org/
drm/bridge: lt9611: Fix handling of 4k panels
xen: reset legacy rtc flag for PV domU
arm64/sve: Use correct size when reinitialising SVE state
PM: base: power: don't try to use non-existing RTC for storing data
PCI: Add AMD GPU multi-function power dependencies
drm/amd/amdgpu: Increase HWIP_MAX_INSTANCE to 10
drm/etnaviv: return context from etnaviv_iommu_context_get
drm/etnaviv: put submit prev MMU context when it exists
drm/etnaviv: stop abusing mmu_context as FE running marker
drm/etnaviv: keep MMU context across runtime suspend/resume
drm/etnaviv: exec and MMU state is lost when resetting the GPU
drm/etnaviv: fix MMU context leak on GPU reset
drm/etnaviv: reference MMU context when setting up hardware state
drm/etnaviv: add missing MMU context put when reaping MMU mapping
s390/sclp: fix Secure-IPL facility detection
x86/pat: Pass valid address to sanitize_phys()
x86/mm: Fix kern_addr_valid() to cope with existing but not present entries
tipc: fix an use-after-free issue in tipc_recvmsg
ethtool: Fix rxnfc copy to user buffer overflow
net/{mlx5|nfp|bnxt}: Remove unnecessary RTNL lock assert
net-caif: avoid user-triggerable WARN_ON(1)
ptp: dp83640: don't define PAGE0
net/l2tp: Fix reference count leak in l2tp_udp_recv_core
r6040: Restore MDIO clock frequency after MAC reset
tipc: increase timeout in tipc_sk_enqueue()
drm/rockchip: cdn-dp-core: Make cdn_dp_core_resume __maybe_unused
perf machine: Initialize srcline string member in add_location struct
net/mlx5: FWTrace, cancel work on alloc pd error flow
net/mlx5: Fix potential sleeping in atomic context
nvme-tcp: fix io_work priority inversion
events: Reuse value read using READ_ONCE instead of re-reading it
net: ipa: initialize all filter table slots
gen_compile_commands: fix missing 'sys' package
vhost_net: fix OoB on sendmsg() failure.
net/af_unix: fix a data-race in unix_dgram_poll
net: dsa: destroy the phylink instance on any error in dsa_slave_phy_setup
x86/uaccess: Fix 32-bit __get_user_asm_u64() when CC_HAS_ASM_GOTO_OUTPUT=y
tcp: fix tp->undo_retrans accounting in tcp_sacktag_one()
selftest: net: fix typo in altname test
qed: Handle management FW error
udp_tunnel: Fix udp_tunnel_nic work-queue type
dt-bindings: arm: Fix Toradex compatible typo
ibmvnic: check failover_pending in login response
KVM: PPC: Book3S HV: Tolerate treclaim. in fake-suspend mode changing
registers
bnxt_en: make bnxt_free_skbs() safe to call after bnxt_free_mem()
net: hns3: pad the short tunnel frame before sending to hardware
net: hns3: change affinity_mask to numa node range
net: hns3: disable mac in flr process
net: hns3: fix the timing issue of VF clearing interrupt sources
dt-bindings: mtd: gpmc: Fix the ECC bytes vs. OOB bytes equation
mfd: db8500-prcmu: Adjust map to reality
PCI: Add ACS quirks for NXP LX2xx0 and LX2xx2 platforms
fuse: fix use after free in fuse_read_interrupt()
PCI: tegra194: Fix handling BME_CHGED event
PCI: tegra194: Fix MSI-X programming
PCI: tegra: Fix OF node reference leak
mfd: Don't use irq_create_mapping() to resolve a mapping
PCI: rcar: Fix runtime PM imbalance in rcar_pcie_ep_probe()
tracing/probes: Reject events which have the same name of existing one
PCI: cadence: Use bitfield for *quirk_retrain_flag* instead of bool
PCI: cadence: Add quirk flag to set minimum delay in LTSSM Detect.Quiet state
PCI: j721e: Add PCIe support for J7200
PCI: j721e: Add PCIe support for AM64
PCI: Add ACS quirks for Cavium multi-function devices
watchdog: Start watchdog in watchdog_set_last_hw_keepalive only if appropriate
octeontx2-af: Add additional register check to rvu_poll_reg()
Set fc_nlinfo in nh_create_ipv4, nh_create_ipv6
net: usb: cdc_mbim: avoid altsetting toggling for Telit LN920
PCI: ibmphp: Fix double unmap of io_mem
ethtool: Fix an
[Kernel-packages] [Bug 1947191] Re: Impish update: v5.13.19 upstream stable release
** Changed in: linux (Ubuntu Impish) 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/1947191 Title: Impish update: v5.13.19 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.19 upstream stable release from git://git.kernel.org/ rtc: tps65910: Correct driver module alias btrfs: wake up async_delalloc_pages waiters after submit btrfs: wait on async extents when flushing delalloc btrfs: reduce the preemptive flushing threshold to 90% btrfs: zoned: fix block group alloc_offset calculation btrfs: zoned: suppress reclaim error message on EAGAIN btrfs: fix upper limit for max_inline for page size 64K btrfs: reset replace target device to allocation state on close btrfs: zoned: fix double counting of split ordered extent blk-zoned: allow zone management send operations without CAP_SYS_ADMIN blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN PCI/MSI: Skip masking MSI-X on Xen PV powerpc/perf/hv-gpci: Fix counter value parsing xen: fix setting of max_pfn in shared_info 9p/xen: Fix end of loop tests for list_for_each_entry ceph: fix dereference of null pointer cf Input: elan_i2c - reduce the resume time for controller in Whitebox selftests/ftrace: Fix requirement check of README file tools/thermal/tmon: Add cross compiling support clk: socfpga: agilex: fix the parents of the psi_ref_clk clk: socfpga: agilex: fix up s2f_user0_clk representation clk: socfpga: agilex: add the bypass register for s2f_usr0 clock pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast pinctrl: ingenic: Fix incorrect pull up/down info pinctrl: ingenic: Fix bias config for X2000(E) soc: mediatek: mmsys: Fix missing UFOE component in mt8173 table routing soc: qcom: aoss: Fix the out of bound usage of cooling_devs soc: aspeed: lpc-ctrl: Fix boundary check for mmap soc: aspeed: p2a-ctrl: Fix boundary check for mmap arm64: Move .hyp.rodata outside of the _sdata.._edata range arm64: mm: Fix TLBI vs ASID rollover arm64: head: avoid over-mapping in map_memory arm64: Do not trap PMSNEVFR_EL1 iio: ltc2983: fix device probe wcn36xx: Ensure finish scan is not requested before start scan crypto: public_key: fix overflow during implicit conversion block: bfq: fix bfq_set_next_ioprio_data() power: supply: max17042: handle fails of reading status register dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc() crypto: ccp - shutdown SEV firmware on kexec spi: fsi: Reduce max transfer size to 8 bytes VMCI: fix NULL pointer dereference when unmapping queue pair media: uvc: don't do DMA on stack media: rc-loopback: return number of emitters rather than error nvmem: core: fix error handling while validating keepout regions s390/qdio: fix roll-back after timeout on ESTABLISH ccw s390/qdio: cancel the ESTABLISH ccw after timeout Revert "dmaengine: imx-sdma: refine to load context only once" dmaengine: imx-sdma: remove duplicated sdma_load_context io_uring: place fixed tables under memcg limits io_uring: add ->splice_fd_in checks io_uring: fix io_try_cancel_userdata race for iowq io-wq: fix wakeup race when adding new work io-wq: fix race between adding work and activating a free worker io_uring: fail links of cancelled timeouts libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs ARM: 9105/1: atags_to_fdt: don't warn about stack size f2fs: fix to do sanity check for sb/cp fields correctly PCI/portdrv: Enable Bandwidth Notification only if port supports it PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure PCI: xilinx-nwl: Enable the clock through CCF PCI: aardvark: Configure PCIe resources from 'ranges' DT property PCI: aardvark: Fix checking for PIO status PCI: aardvark: Increase polling delay to 1.5s while waiting for PIO response PCI: aardvark: Fix masking and unmasking legacy INTx interrupts f2fs: compress: fix to set zstd compress level correctly HID: input: do not report stylus battery state as "full" f2fs: quota: fix potential deadlock pinctrl: armada-37xx: Correct PWM pins definitions scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND clk: rockchip: drop GRF dependency for
[Kernel-packages] [Bug 1948485] Re: Impish update: upstream stable patchset 2021-10-22
** Changed in: linux (Ubuntu Impish)
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/1948485
Title:
Impish update: upstream stable patchset 2021-10-22
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2021-10-22
Ported from the following upstream stable releases:
v5.10.68, v5.14.7
from git://git.kernel.org/
xen: reset legacy rtc flag for PV domU
arm64/sve: Use correct size when reinitialising SVE state
PM: base: power: don't try to use non-existing RTC for storing data
PCI: Add AMD GPU multi-function power dependencies
drm/amd/amdgpu: Increase HWIP_MAX_INSTANCE to 10
drm/etnaviv: return context from etnaviv_iommu_context_get
drm/etnaviv: put submit prev MMU context when it exists
drm/etnaviv: stop abusing mmu_context as FE running marker
drm/etnaviv: keep MMU context across runtime suspend/resume
drm/etnaviv: exec and MMU state is lost when resetting the GPU
drm/etnaviv: fix MMU context leak on GPU reset
drm/etnaviv: reference MMU context when setting up hardware state
drm/etnaviv: add missing MMU context put when reaping MMU mapping
s390/sclp: fix Secure-IPL facility detection
x86/pat: Pass valid address to sanitize_phys()
x86/mm: Fix kern_addr_valid() to cope with existing but not present entries
tipc: fix an use-after-free issue in tipc_recvmsg
ethtool: Fix rxnfc copy to user buffer overflow
net/{mlx5|nfp|bnxt}: Remove unnecessary RTNL lock assert
net-caif: avoid user-triggerable WARN_ON(1)
ptp: dp83640: don't define PAGE0
net/l2tp: Fix reference count leak in l2tp_udp_recv_core
r6040: Restore MDIO clock frequency after MAC reset
tipc: increase timeout in tipc_sk_enqueue()
drm/rockchip: cdn-dp-core: Make cdn_dp_core_resume __maybe_unused
perf machine: Initialize srcline string member in add_location struct
net/mlx5: FWTrace, cancel work on alloc pd error flow
net/mlx5: Fix potential sleeping in atomic context
nvme-tcp: fix io_work priority inversion
events: Reuse value read using READ_ONCE instead of re-reading it
net: ipa: initialize all filter table slots
gen_compile_commands: fix missing 'sys' package
vhost_net: fix OoB on sendmsg() failure.
net/af_unix: fix a data-race in unix_dgram_poll
net: dsa: destroy the phylink instance on any error in dsa_slave_phy_setup
x86/uaccess: Fix 32-bit __get_user_asm_u64() when CC_HAS_ASM_GOTO_OUTPUT=y
tcp: fix tp->undo_retrans accounting in tcp_sacktag_one()
selftest: net: fix typo in altname test
qed: Handle management FW error
udp_tunnel: Fix udp_tunnel_nic work-queue type
dt-bindings: arm: Fix Toradex compatible typo
ibmvnic: check failover_pending in login response
KVM: PPC: Book3S HV: Tolerate treclaim. in fake-suspend mode changing
registers
bnxt_en: make bnxt_free_skbs() safe to call after bnxt_free_mem()
net: hns3: pad the short tunnel frame before sending to hardware
net: hns3: change affinity_mask to numa node range
net: hns3: disable mac in flr process
net: hns3: fix the timing issue of VF clearing interrupt sources
dt-bindings: mtd: gpmc: Fix the ECC bytes vs. OOB bytes equation
mfd: db8500-prcmu: Adjust map to reality
PCI: Add ACS quirks for NXP LX2xx0 and LX2xx2 platforms
fuse: fix use after free in fuse_read_interrupt()
PCI: tegra194: Fix handling BME_CHGED event
PCI: tegra194: Fix MSI-X programming
PCI: tegra: Fix OF node reference leak
mfd: Don't use irq_create_mapping() to resolve a mapping
PCI: rcar: Fix runtime PM imbalance in rcar_pcie_ep_probe()
tracing/probes: Reject events which have the same name of existing one
PCI: cadence: Use bitfield for *quirk_retrain_flag* instead of bool
PCI: cadence: Add quirk flag to set minimum delay in LTSSM Detect.Quiet state
PCI: j721e: Add PCIe support for J7200
PCI: j721e: Add PCIe support for AM64
PCI: Add ACS quirks for Cavium multi-function devices
watchdog: Start watchdog in watchdog_set_last_hw_keepalive only if appropriate
octeontx2-af: Add additional register check to rvu_poll_reg()
Set fc_nlinfo in nh_create_ipv4, nh_create_ipv6
net: usb: cdc_mbim: avoid altsetting toggling for Telit LN920
PCI: ibmphp: Fix double unmap of io_mem
ethtool: Fix an error code in cxgb2.c
NTB: Fix an error code in
[Kernel-packages] [Bug 1948977] Re: Impish update: upstream stable patchset 2021-10-27
** Changed in: linux (Ubuntu Impish) 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/1948977 Title: Impish update: upstream stable patchset 2021-10-27 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-10-27 Ported from the following upstream stable releases: v5.10.69, v5.14.8 from git://git.kernel.org/ PCI: pci-bridge-emul: Add PCIe Root Capabilities Register PCI: aardvark: Fix reporting CRS value console: consume APC, DM, DCS ARM: 9077/1: PLT: Move struct plt_entries definition to header ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link() ARM: 9079/1: ftrace: Add MODULE_PLTS support ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE sctp: validate chunk size in __rcv_asconf_lookup sctp: add param size validation for SCTP_PARAM_SET_PRIMARY staging: rtl8192u: Fix bitwise vs logical operator in TranslateRxSignalStuff819xUsb() coredump: fix memleak in dump_vma_snapshot() um: virtio_uml: fix memory leak on init failures dmaengine: acpi: Avoid comparison GSI with Linux vIRQ perf test: Fix bpf test sample mismatch reporting perf tools: Allow build-id with trailing zeros thermal/drivers/exynos: Fix an error code in exynos_tmu_probe() 9p/trans_virtio: Remove sysfs file on probe failure prctl: allow to setup brk for et_dyn executables nilfs2: use refcount_dec_and_lock() to fix potential UAF profiling: fix shift-out-of-bounds bugs PM: sleep: core: Avoid setting power.must_resume to false pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was registered pwm: mxs: Don't modify HW state in .probe() after the PWM chip was registered dmaengine: idxd: fix wq slot allocation index check platform/chrome: sensorhub: Add trace events for sample platform/chrome: cros_ec_trace: Fix format warnings ceph: allow ceph_put_mds_session to take NULL or ERR_PTR ceph: cancel delayed work instead of flushing on mdsc teardown Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH tools/bootconfig: Fix tracing_on option checking in ftrace2bconf.sh thermal/core: Fix thermal_cooling_device_register() prototype drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION() dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER parisc: Move pci_dev_is_behind_card_dino to where it is used iommu/amd: Relocate GAMSup check to early_enable_iommus dmaengine: idxd: depends on !UML dmaengine: sprd: Add missing MODULE_DEVICE_TABLE dmaengine: ioat: depends on !UML dmaengine: xilinx_dma: Set DMA mask for coherent APIs ceph: request Fw caps before updating the mtime in ceph_write_iter ceph: remove the capsnaps when removing caps ceph: lockdep annotations for try_nonblocking_invalidate btrfs: update the bdev time directly when closing btrfs: fix lockdep warning while mounting sprout fs nilfs2: fix memory leak in nilfs_sysfs_create_device_group nilfs2: fix NULL pointer in nilfs_##name##_attr_release nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group habanalabs: add validity check for event ID received from F/W pwm: img: Don't modify HW state in .remove() callback pwm: rockchip: Don't modify HW state in .remove() callback pwm: stm32-lp: Don't modify HW state in .remove() callback blk-throttle: fix UAF by deleteing timer in blk_throtl_exit() blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for multiple_queues rtc: rx8010: select REGMAP_I2C sched/idle: Make the idle timer expire in hard interrupt context drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV um: fix stub location calculation RDMA/mlx5: Fix xlt_chunk_align calculation perf symbol: Look for ImageBase in PE file to compute .text offset staging: rtl8723bs: fix wpa_set_auth_algs() function n64cart: fix return value check in n64cart_probe() pwm: ab8500: Fix register offset calculation to not depend on probe order thermal/drivers/qcom/spmi-adc-tm5: Don't abort probing if a sensor
[Kernel-packages] [Bug 1948724] [NEW] udpgro_fwd from selftests/net fails ADT test failure with impish
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-21.21 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. This is not a regression; found previously on 5.13.0-19.19 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211021_221027_e5903@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211023_154712_826b9@/log.gz 21:21:14 DEBUG| [stdout] # selftests: net: udpgro_fwd.sh 21:21:14 DEBUG| [stdout] # IPv4 21:21:14 DEBUG| [stdout] # No GRO ok 21:21:14 DEBUG| [stdout] # GRO frag listok 21:21:15 DEBUG| [stdout] # GRO fwd ok 21:21:16 DEBUG| [stdout] # UDP fwd perfudp rx: 219 MB/s 178766 calls/s 21:21:16 DEBUG| [stdout] # udp tx:290 MB/s 4927 calls/s 4927 msg/s 21:21:17 DEBUG| [stdout] # udp rx:280 MB/s 228627 calls/s 21:21:17 DEBUG| [stdout] # udp tx:284 MB/s 4828 calls/s 4828 msg/s 21:21:18 DEBUG| [stdout] # udp rx:263 MB/s 214183 calls/s 21:21:18 DEBUG| [stdout] # udp tx:281 MB/s 4775 calls/s 4775 msg/s 21:21:19 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 238 MB/s 194146 calls/s 21:21:19 DEBUG| [stdout] # udp tx:271 MB/s 4598 calls/s 4598 msg/s 21:21:20 DEBUG| [stdout] # ./udpgso_bench_tx: sendmsg: Connection refused 21:21:20 DEBUG| [stdout] # fail client exit code 1, server 0 21:21:20 DEBUG| [stdout] # GRO frag list over UDP tunnelok 21:21:21 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 21:21:22 DEBUG| [stdout] # UDP tunnel fwd perf udp rx: 122 MB/s99319 calls/s 21:21:22 DEBUG| [stdout] # udp tx:222 MB/s 3782 calls/s 3782 msg/s 21:21:23 DEBUG| [stdout] # udp rx:161 MB/s 131528 calls/s 21:21:23 DEBUG| [stdout] # udp tx:228 MB/s 3868 calls/s 3868 msg/s 21:21:24 DEBUG| [stdout] # udp rx:197 MB/s 160785 calls/s 21:21:24 DEBUG| [stdout] # udp tx:218 MB/s 3698 calls/s 3698 msg/s 21:21:25 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 200 MB/s 163194 calls/s 21:21:25 DEBUG| [stdout] # udp tx:231 MB/s 3921 calls/s 3921 msg/s 21:21:26 DEBUG| [stdout] # udp rx:193 MB/s 157637 calls/s 21:21:26 DEBUG| [stdout] # udp tx:220 MB/s 3744 calls/s 3744 msg/s 21:21:27 DEBUG| [stdout] # udp rx:226 MB/s 184120 calls/s 21:21:27 DEBUG| [stdout] # udp tx:240 MB/s 4073 calls/s 4073 msg/s 21:21:27 DEBUG| [stdout] # IPv6 21:21:28 DEBUG| [stdout] # No GRO ok 21:21:28 DEBUG| [stdout] # GRO frag listok 21:21:28 DEBUG| [stdout] # GRO fwd ok 21:21:30 DEBUG| [stdout] # UDP fwd perfudp rx: 174 MB/s 142456 calls/s 21:21:30 DEBUG| [stdout] # udp tx:299 MB/s 5076 calls/s 5076 msg/s 21:21:31 DEBUG| [stdout] # udp rx:239 MB/s 195356 calls/s 21:21:31 DEBUG| [stdout] # udp tx:311 MB/s 5276 calls/s 5276 msg/s 21:21:32 DEBUG| [stdout] # udp rx:301 MB/s 245849 calls/s 21:21:32 DEBUG| [stdout] # udp tx:307 MB/s 5213 calls/s 5213 msg/s 21:21:33 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 196 MB/s 160372 calls/s 21:21:33 DEBUG| [stdout] # udp tx:228 MB/s 3876 calls/s 3876 msg/s 21:21:34 DEBUG| [stdout] # udp rx:341 MB/s 278286 calls/s 21:21:34 DEBUG| [stdout] # udp tx:339 MB/s 5760 calls/s 5760 msg/s 21:21:35 DEBUG| [stdout] # udp rx:272 MB/s 221441 calls/s 21:21:35 DEBUG| [stdout] # udp tx:304 MB/s 5160 calls/s 5160 msg/s 21:21:35 DEBUG| [stdout] # GRO frag list over UDP tunnelok 21:21:36 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 21:21:37 DEBUG| [stdout] # UDP tunnel fwd perf ./udpgso_bench_tx: sendmsg: Connection refused 21:21:37 DEBUG| [stdout] # fail client exit code 1, server 0 21:21:38 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 201 MB/s 164027 calls/s 21:21:38 DEBUG| [stdout] # udp tx:234 MB/s 3973 calls/s 3973 msg/s 21:21:39 DEBUG| [stdout] # udp rx:227 MB/s 185123 calls/s 21:21:39 DEBUG| [stdout] # udp tx:237 MB/s 4032 calls/s 4032 msg/s 21:21:40 DEBUG| [stdout] # ./udpgso_bench_tx: sendmsg: Connection refused 21:21:40 DEBUG| [stdout] # fail client exit code 1, server 0 21:21:40 DEBUG| [stdout] not ok 48 selftests: net: udpgro_fwd.sh # exit=1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: impish kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux ADT test failure with linux/5.13.0-21.21 + udpgro_fwd from selftests/net
[Kernel-packages] [Bug 1948351] [NEW] linux ADT test_bpf failure with linux/5.4.0-90.101
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/5.4.0-90.101 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Consistently failing on Focal/linux 5.4.0-90.101 13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh 13:15:27 DEBUG| [stdout] # test_bpf: [FAIL] 13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1 Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: focal kernel-adt-failure ** Tags added: kernel-adt-failure ** Tags added: focal ** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/5.4.0-90.101 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. + + Consistently failing on Focal/linux 5.4.0-90.101 + + 13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh + 13:15:27 DEBUG| [stdout] # test_bpf: [FAIL] + 13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1 + + Testing failed on: - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz ** Summary changed: - linux ADT test failure with linux/5.4.0-90.101 + linux ADT test_bpf failure with linux/5.4.0-90.101 -- 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/1948351 Title: linux ADT test_bpf failure with linux/5.4.0-90.101 Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.4.0-90.101 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Consistently failing on Focal/linux 5.4.0-90.101 13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh 13:15:27 DEBUG| [stdout] # test_bpf: [FAIL] 13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1 Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+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 1945553] Re: It hangs while booting up with AMD W6800 [1002:73A3]
** Changed in: linux (Ubuntu Impish) 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.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945553 Title: It hangs while booting up with AMD W6800 [1002:73A3] Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] It hangs when booting up with AMD W6800 [1002:73A3] graphics card. [Fix] Bisect the kernel and found below fix from v5.15-rc1 mainline kernel 5810323ba692 drm/amd/pm: Fix a bug communicating with the SMU (v5) [Test] Verified the patch on a Dell workstation with AMD W6800 graphics card [Where problems could occur] The code flow doesn't change much, but with better return codes handling and print out more meaningful messages. So it should not impact the already working devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945553/+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 1928679] Re: Support importing mokx keys into revocation list from the mok table
** Changed in: linux (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-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-azure-5.8 source package in Focal: New Status in linux-hwe-5.8 source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. * $ sudo ls /sys/firmware/efi/mok-variables MokListRT MokListXRT SbatLevelRT When booted with shim, the mok-variables directory above should exist, and contain at least `MokListRT MokListXRT SbatLevelRT` files. In kernel messages, the CA certificate should be loaded via MOKvar table i.e: * $ sudo journalctl -b -k | grep -A1 'MOKvar table' Sep 27 13:11:04 champion-spaniel kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Sep 27 13:11:04 champion-spaniel kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63 [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+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 1932029] Re: Support builtin revoked certificates
** Changed in: linux (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-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-azure-5.8 source package in Focal: New Status in linux-hwe-5.8 source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains asymmetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html * Previous reviews Unstable & v5.13: https://lists.ubuntu.com/archives/kernel- team/2021-June/121362.html Hirsute & v5.11: https://lists.ubuntu.com/archives/kernel- team/2021-August/122996.html Focal & v5.10 (oem): https://lists.ubuntu.com/archives/kernel- team/2021-August/123470.html Focal & v5.8 (azure): https://lists.ubuntu.com/archives/kernel- team/2021-September/124336.html Focal & v5.4: https://lists.ubuntu.com/archives/kernel- team/2021-October/124497.html Bionic & v4.15: TODO Xenial & v4.4: TODO Trusty & v3.13: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+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 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1913442 Title: [Ubuntu 20.04] Problem leading IUCV service down (on s390x) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification: == [Impact] * Problems occur in IBM z/VM's IUCV (Inter User Communication Vehicle) environments and its communication. * Errors like "usercopy: Kernel memory overwrite attempt detected to SLUB object 'dma-kmalloc-1 k' (offset 0, size 11)!" pop up and cause failures. * This is because IUCV uses kmalloc() with __GFP_DMA because of memory address restrictions. * The solution is to mark dma-kmalloc caches as usercopy caches. [Fix] * 49f2d2419d60a103752e5fbaf158cf8d07c0d884 49f2d2419d60 "usercopy: mark dma-kmalloc caches as usercopy caches" * Due to changes in the context of the upstream patch, a cherry-pick was not possible and the following backport was created: https://bugs.launchpad.net/bugs/1913442/+attachment/5457885/+files/commit_49f2d2419d60_backport.patch [Test Case] * Setup Ubuntu Server 20.04 on s390x system as IBM z/VM guest aka virtual machine. * Setup IUCV on z/VM: Setting up the (IUCV TCPIP) service machine: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_tcpservice.html * Set up a Linux IUCV instance: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_scen1_guest.html * Set up an IUCV direct: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_c_iucv_connect.html * Make use of IUCV, for example using ssh on a direct connection. * Verify if the connections is stable and watch out for messages starting with "usercopy". [Regression Potential] * Problems could occur in case the create_kmalloc_cache call is done wrong, for example with wrong index, wrong size or just wrong comma separations. * Wrong size or index will probably lead to similar instability problems that exist today. * Problems in the syntax (commas etc.) will be detected at compile time. * But it's just a single line modification in function create_kmalloc_caches of /mm/slab_common.c, * so the change is very limited and quite traceable. * And it was in depth discussed here: https://lore.kernel.org/kernel-hardening/1515636190-24061-2-git-send-email-keesc...@chromium.org/ * a reviewed by a lot of kernel engineers (see provenance) * and it was already upstream accepted with kernel 5.8. [Other] * Since the commit is upstream accepted with 5.8, so it's already in impish and hirsute (and groovy). * Hence this kernel SRU submission is for Focal only and covers only the above single but common code commit/patch. __ When I deployed a Ubuntu20.04 instance with kernel version of 5.4.0-58-generic under z/VM, I saw below messages from kernel and the iucvserv program malfunctioned. Hence it caused some devices like network device configuration failure and deployment failure. Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check authorization. Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, len=7 Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded version is 0.0.0.1 Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd 2>&1; echo iucvcmdrc=$? sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message length=14,#012 /#012iucvcmdrc=0 Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here ] Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'dma-kmalloc-1k' (offset 0, size 20)! Dec 14 22:02:26 ub2004img kernel: [63084.184680] WARNING: CPU: 1 PID: 697 at mm/usercopy.c:75 usercopy_warn+0xa0/0xd0 Dec 14 22:02:26 ub2004img kernel: [63084.184681] Modules linked in: tcp_diag udp_diag raw_diag inet_diag unix_diag xt_CT iptable_raw ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_conntrack nf_conntrack nf_defr ag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter af_iucv nls_utf8 isofs dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmur vfio_ccw vfio_mdev mdev s390_trng vfio_iommu_type1 vfio sch_fq_codel drm drm _panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov
[Kernel-packages] [Bug 1947011] Re: Bionic update: upstream stable patchset 2021-10-13
** Changed in: linux (Ubuntu Bionic) 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/1947011 Title: Bionic update: upstream stable patchset 2021-10-13 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-10-13 Ported from the following upstream stable releases: v4.14.248, v4.19.208 from git://git.kernel.org/ rcu: Fix missed wakeup of exp_wq waiters apparmor: remove duplicate macro list_entry_is_head() crypto: talitos - fix max key size for sha384 and sha512 sctp: validate chunk size in __rcv_asconf_lookup sctp: add param size validation for SCTP_PARAM_SET_PRIMARY dmaengine: acpi: Avoid comparison GSI with Linux vIRQ thermal/drivers/exynos: Fix an error code in exynos_tmu_probe() 9p/trans_virtio: Remove sysfs file on probe failure prctl: allow to setup brk for et_dyn executables profiling: fix shift-out-of-bounds bugs pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was registered Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH parisc: Move pci_dev_is_behind_card_dino to where it is used dmaengine: ioat: depends on !UML dmaengine: xilinx_dma: Set DMA mask for coherent APIs ceph: lockdep annotations for try_nonblocking_invalidate nilfs2: fix memory leak in nilfs_sysfs_create_device_group nilfs2: fix NULL pointer in nilfs_##name##_attr_release nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group pwm: rockchip: Don't modify HW state in .remove() callback blk-throttle: fix UAF by deleteing timer in blk_throtl_exit() drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV nilfs2: use refcount_dec_and_lock() to fix potential UAF drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION() UBUNTU: upstream stable to v4.14.248, v4.19.208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947011/+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 1946464] Re: Invalid backport to v4.15: missing pgtable_l5_enabled
** Changed in: linux (Ubuntu Bionic)
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/1946464
Title:
Invalid backport to v4.15: missing pgtable_l5_enabled
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Commit 5047ef5725ed ("x86/mm: Don't free P4D table when it is folded at
runtime") should not be backported to v4.15 because:
1. It adds pgtable_l5_enabled which does not exist in v4.15,
2. It is marked as v4.17+
3. It is marked as fixing commit which does not exist in v4.15 and was not
backported there.
allyesconfig in x86_64 fails to build:
---
In file included from ../arch/x86/include/asm/mmu_context.h:12,
from ../include/linux/mmu_context.h:5,
from ../arch/x86/kvm/../../../virt/kvm/async_pf.c:26:
../arch/x86/include/asm/pgalloc.h: In function ‘p4d_free’:
../arch/x86/include/asm/pgalloc.h:185:7: error: ‘pgtable_l5_enabled’
undeclared (first use in this function); did you mean ‘movable_node_enabled’?
185 | if (!pgtable_l5_enabled)
| ^~
| movable_node_enabled
---
[Test Plan]
Compile the x86_64 KVM code.
[Where problems could occur]
If backport commit is actually needed, e.g. when we backport 5-level
page tables and commit 98219dda2ab5 ("x86/mm: Fold p4d page table
layer at runtime"), this could cause double-free and memory
corruption.
When backporting x86_64 5-level pages, we need to bring this commit as
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946464/+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 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4
** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1896448
Title:
ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of
ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle
/ B-5.4-azure / B-5.4
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Bug description:
[ Impact ]
When running the net/rtnetlink.sh selftest from v5.4 on older Ubuntu releases
(e.g. Bionic 18.04), some of the iproute2 CLI options are not available causing
the testcase to fail.
[ Fix ]
SAUCE patch to detect whether some options not present on older iproute2
versions are available, skipping or adapting the tests.
[ Test ]
Run net/rtnetlink.sh on 5.4 kernels with both Focal and Bionic userspace. The
test should complete without introducing regressions on Focal and without
breaking on Bionic.
[ Where problems could occur ]
If the checks for the available interfaces are not done correctly, we could
end up having a smaller coverage on Focal or the tests would still break in
Bionic.
[ Original bug description ]
Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted before
fixing the false-negative return value of this rtnetlink.sh test (bug 1890136)
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ hoplimit TTL ]
# [ encaplimit ELIM ]
# [ tclass TCLASS ]
# [ flowlabel FLOWLABEL ]
# [ dscp inherit ]
# [ fwmark MARK ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ erspan IDX ]
#
# Where: ADDR := IPV6_ADDRESS
# TTL := { 0..255 } (default=64)
# KEY := { DOTTED_QUAD | NUMBER }
# ELIM := { none | 0..255 }(default=4)
# TCLASS := { 0x0..0xff | inherit }
# FLOWLABEL := { 0x0..0xf | inherit }
# MARK := { 0x0..0x | inherit }
# Cannot find device "ip6gretap00"
# FAIL: ip6gretap
# Usage: ... { gre | gretap | erspan } [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ ttl TTL ]
# [ tos TOS ]
# [ [no]pmtudisc ]
# [ [no]ignore-df ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ external ]
# [ fwmark MARK ]
# [ erspan IDX ]
#
# Where: ADDR := { IP_ADDRESS | any }
# TOS := { NUMBER | inherit }
# TTL := { 1..255 | inherit }
# KEY := { DOTTED_QUAD | NUMBER }
# MARK := { 0x0..0x }
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# Usage: ... { gre | gretap | erspan } [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ ttl TTL ]
# [ tos TOS ]
# [ [no]pmtudisc ]
# [ [no]ignore-df ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ external ]
# [ fwmark MARK ]
# [ erspan IDX ]
#
# Where: ADDR := { IP_ADDRESS | any }
# TOS := { NUMBER | inherit }
# TTL := { 1..255 | inherit }
# KEY := { DOTTED_QUAD | NUMBER }
# MARK := { 0x0..0x }
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# Cannot find device "erspan00"
# FAIL: erspan
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ hoplimit TTL ]
# [ encaplimit ELIM ]
# [ tclass TCLASS ]
# [ flowlabel FLOWLABEL ]
# [ dscp inherit ]
# [ fwmark MARK ]
# [ dev PHYS_DEV ]
# [ noencap ]
# [ encap { fou | gue | none } ]
# [ encap-sport PORT ]
# [ encap-dport PORT ]
# [ [no]encap-csum ]
# [ [no]encap-csum6 ]
# [ [no]encap-remcsum ]
# [ erspan IDX ]
#
# Where: ADDR := IPV6_ADDRESS
# TTL := { 0..255 } (default=64)
# KEY := { DOTTED_QUAD | NUMBER }
# ELIM := { none | 0..255 }(default=4)
# TCLASS := { 0x0..0xff | inherit }
# FLOWLABEL := { 0x0..0xf | inherit }
# MARK := { 0x0..0x | inherit }
# Cannot find device "ip6erspan00"
# Cannot find device "ip6erspan00"
# Cannot find device "ip6erspan00"
# Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
# [ local ADDR ]
# [ [i|o]seq ]
# [ [i|o]key KEY ]
# [ [i|o]csum ]
# [ hoplimit TTL ]
# [ encaplimit ELIM ]
# [ tclass
[Kernel-packages] [Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu Focal)
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/1945180
Title:
vrf: fix refcnt leak with vxlan slaves
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
There are cases, where deleting a VRF device can hang waiting for the refcnt
to drop to 0, with the message:
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1
This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
used for dst_alloc with local routes"), included in linux v5.13. The
original patch, which has introduced the bug, is included in linux
v4.10.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b87b04f5019e
[Test Case]
The upstream patch includes a test case, which describe how to
reproduce the bug.
[Regression Potential]
The patch affects ipv4 routing. It is straightforward, it links new
dst to a vrf device instead of the loopback if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+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 1945989] Re: Check for changes relevant for security certifications
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Incomplete => 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/1945989 Title: Check for changes relevant for security certifications Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Incomplete Bug description: [Impact] When producing a new version of some kernels, we need to check for changes that might affect FIPS or other certs and justify why a commit was kept or removed. To simplify this process we can add an automated check that will abort the kernel preparation and build when such changes exist without a justification. [Test Plan] Check if the kernel preparation fails (cranky close) when one of a security certification changes is added. [Where problems could occur] No kernels should be affected until we enable this check on each one. Even when enabled, that only affects the kernel preparation and not the resulting kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945989/+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 1944613] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’)
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1944613 Title: memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.4 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-5.4 source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux-hwe-5.4 source package in Focal: Invalid Bug description: [Impact] BugLink: https://bugs.launchpad.net/bugs/1944613 There are build issues in selftests/memfd/fuse_test.c where __u64 is not defined. This is issue is probably due to the fact that in 5.4 there is a type include in one of the includes in the file, however this include probably was not there for 4.15. Regardless we fix this by including the type file directly. [Fix] * selftests/memfd: fix __u64 not defined build issue Add #include to define the type [Test Plan] Recompile tests to make sure they build and tests pass. [Where problems could occur] Should be no problems since we are adding an include file that userspace files always have access to. -- Failed to build on B/linux-hwe-5.4 5.4.0-85.95~18.04.1. This was observed in previous cycles. I am working on a fix for it right now. 13203 fuse_test.c:63:8: error: unknown type name ‘__u64’ 13204static __u64 mfd_assert_get_seals(int fd) 13205 ^ 13206 fuse_test.c:76:42: error: unknown type name ‘__u64’; did you mean ‘__f64’? 13207static void mfd_assert_has_seals(int fd, __u64 seals) 13208 ^ 13209 __f64 13210 fuse_test.c:88:42: error: unknown type name ‘__u64’; did you mean ‘__f64’? 13211static void mfd_assert_add_seals(int fd, __u64 seals) 13212 ^ 13213 __f64 13214 fuse_test.c:102:39: error: unknown type name ‘__u64’; did you mean ‘__f64’? 13215static int mfd_busy_add_seals(int fd, __u64 seals) 13216 ^ 13217 __f64 13218 fuse_test.c: In function ‘sealing_thread_fn’: 13219 fuse_test.c:185:6: warning: implicit declaration of function ‘mfd_busy_add_seals’; did you mean ‘mfd_assert_get_seals’? [-Wimplicit-function-declaration] 13220 r = mfd_busy_add_seals(global_mfd, F_SEAL_WRITE); 13221 ^~ 13222 mfd_assert_get_seals 13223 fuse_test.c:193:3: warning: implicit declaration of function ‘mfd_assert_add_seals’; did you mean ‘mfd_assert_get_seals’? [-Wimplicit-function-declaration] 13224 mfd_assert_add_seals(global_mfd, F_SEAL_WRITE); 13225 ^~~~ 13226 mfd_assert_get_seals 13227 fuse_test.c: In function ‘main’: 13228 fuse_test.c:302:2: warning: implicit declaration of function ‘mfd_assert_has_seals’; did you mean ‘mfd_assert_get_seals’? [-Wimplicit-function-declaration] 13229 mfd_assert_has_seals(mfd, F_SEAL_WRITE); 13230 ^~~~ 13231 mfd_assert_get_seals 13232 make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/fuse_test] Error 1 13233 make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1944613/+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 1944586] Re: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47"
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1944586 Title: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47" Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] It has been brought to my attention the following: " We have been experiencing node lockups and degradation when testing fiber channel fail over for multi-path PURESTORAGE drives. Testing usually consists of either failing over the fabric or the local I/O module for the Cisco chassis which houses a number of individual blades. After rebooting a local Chassis I/O module we see commands like multipath -ll hanging. Resetting the blades individual fiber channel interface results in the following messages. " 6051160.241383] rport-9:0-1: blocked FC remote port time out: removing target and saving binding [6051160.252901] BUG: kernel NULL pointer dereference, address: 0040 [6051160.262267] #PF: supervisor read access in kernel mode [6051160.269314] #PF: error_code(0x) - not-present page [6051160.276016] PGD 0 P4D 0 [6051160.279807] Oops: [#1] SMP NOPTI [6051160.284642] CPU: 10 PID: 49346 Comm: kworker/10:2 Tainted: P O 5.4.0-77-generic #86-Ubuntu [6051160.295967] Hardware name: Cisco Systems Inc UCSB-B200-M5/UCSB-B200-M5, BIOS B200M5.4.1.1d.0.0609200543 06/09/2020 [6051160.308199] Workqueue: fc_dl_9 fc_timeout_deleted_rport [scsi_transport_fc] [6051160.316640] RIP: 0010:fnic_terminate_rport_io+0x10f/0x510 [fnic] [6051160.324050] Code: 48 89 c3 48 85 c0 0f 84 7b 02 00 00 48 05 20 01 00 00 48 89 45 b0 0f 84 6b 02 00 00 48 8b 83 58 01 00 00 48 8b 80 b8 01 00 00 <48> 8b 78 40 e8 68 e6 06 00 85 c0 0f 84 4c 02 00 00 48 8b 83 58 01 [6051160.346553] RSP: 0018:bc224f297d90 EFLAGS: 00010082 [6051160.353115] RAX: RBX: 90abdd4c4b00 RCX: 90d8ab2c2bb0 [6051160.361983] RDX: 90d8b5467400 RSI: RDI: 90d8ab3b4b40 [6051160.370812] RBP: bc224f297df8 R08: 90d8c08978c8 R09: 90d8b8850800 [6051160.379518] R10: 90d8a59d64c0 R11: 0001 R12: 90d8ab2c31f8 [6051160.388242] R13: R14: 0246 R15: 90d8ab2c27b8 [6051160.396953] FS: () GS:90d8c088() knlGS: [6051160.406838] CS: 0010 DS: ES: CR0: 80050033 [6051160.414168] CR2: 0040 CR3: 000fc1c0a004 CR4: 007626e0 [6051160.423146] DR0: DR1: DR2: [6051160.431884] DR3: DR6: fffe0ff0 DR7: 0400 [6051160.440615] PKRU: 5554 [6051160.444337] Call Trace: [6051160.447841] fc_terminate_rport_io+0x56/0x70 [scsi_transport_fc] [6051160.455263] fc_timeout_deleted_rport.cold+0x1bc/0x2c7 [scsi_transport_fc] [6051160.463623] process_one_work+0x1eb/0x3b0 [6051160.468784] worker_thread+0x4d/0x400 [6051160.473660] kthread+0x104/0x140 [6051160.478102] ? process_one_work+0x3b0/0x3b0 [6051160.483439] ? kthread_park+0x90/0x90 [6051160.488213] ret_from_fork+0x1f/0x40 [6051160.492901] Modules linked in: dm_service_time zfs(PO) zunicode(PO) zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_nat vhost_vsock vmw_vsock_virtio_transport_common vsock unix_diag nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net vhost tap 8021q garp mrp bluetooth ecdh_generic ecc tcp_diag inet_diag sctp nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nls_iso8859_1 dm_queue_length dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common isst_if_common skx_edac nfit x86_pkg_temp_thermal intel_powerclamp ipmi_ssif coretemp kvm_intel kvm rapl input_leds joydev intel_cstate mei_me ioatdma mei dca ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [6051160.492928] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear fnic mgag200 drm_vram_helper i2c_algo_bit ttm drm_kms_helper crct10dif_pclmul syscopyarea hid_generic crc32_pclmul libfcoe sysfillrect ghash_clmulni_intel sysimgblt aesni_intel fb_sys_fops crypto_simd libfc usbhid cryptd scsi_transport_fc hid drm glue_helper enic ahci lpc_ich libahci wmi [6051160.632623] CR2: 0040 [6051160.637043] ---[ end trace 236e6f4850146477 ]--- [Test Plan] There are two ways to replicate
[Kernel-packages] [Bug 1946795] Re: Focal update: v5.4.147 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1946795 Title: Focal update: v5.4.147 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.147 upstream stable release from git://git.kernel.org/ Note: v5.4.147 contained only reverts for commits omitted from our application of prior sets, so v5.4.147 suppplies new commits for Focal Linux 5.4.147 UBUNTU: upstream stable to v5.4.147 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946795/+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 1909814] Re: Medion Notebook Keyboard not working
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1909814 Title: Medion Notebook Keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Bug description: [Impact] The keyboard of some medion laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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 1946802] Re: Focal update: v5.4.148 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1946802 Title: Focal update: v5.4.148 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.148 upstream stable release from git://git.kernel.org/ rtc: tps65910: Correct driver module alias btrfs: wake up async_delalloc_pages waiters after submit btrfs: reset replace target device to allocation state on close blk-zoned: allow zone management send operations without CAP_SYS_ADMIN blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN PCI/MSI: Skip masking MSI-X on Xen PV powerpc/perf/hv-gpci: Fix counter value parsing xen: fix setting of max_pfn in shared_info include/linux/list.h: add a macro to test if entry is pointing to the head 9p/xen: Fix end of loop tests for list_for_each_entry tools/thermal/tmon: Add cross compiling support pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast pinctrl: ingenic: Fix incorrect pull up/down info soc: qcom: aoss: Fix the out of bound usage of cooling_devs soc: aspeed: lpc-ctrl: Fix boundary check for mmap soc: aspeed: p2a-ctrl: Fix boundary check for mmap arm64: head: avoid over-mapping in map_memory crypto: public_key: fix overflow during implicit conversion block: bfq: fix bfq_set_next_ioprio_data() power: supply: max17042: handle fails of reading status register dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc() VMCI: fix NULL pointer dereference when unmapping queue pair media: uvc: don't do DMA on stack media: rc-loopback: return number of emitters rather than error Revert "dmaengine: imx-sdma: refine to load context only once" dmaengine: imx-sdma: remove duplicated sdma_load_context libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs ARM: 9105/1: atags_to_fdt: don't warn about stack size PCI/portdrv: Enable Bandwidth Notification only if port supports it PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure PCI: xilinx-nwl: Enable the clock through CCF PCI: aardvark: Fix checking for PIO status PCI: aardvark: Increase polling delay to 1.5s while waiting for PIO response PCI: aardvark: Fix masking and unmasking legacy INTx interrupts HID: input: do not report stylus battery state as "full" f2fs: quota: fix potential deadlock scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND IB/hfi1: Adjust pkey entry in index 0 RDMA/iwcm: Release resources if iw_cm module initialization fails docs: Fix infiniband uverbs minor number pinctrl: samsung: Fix pinctrl bank pin count vfio: Use config not menuconfig for VFIO_NOIOMMU powerpc/stacktrace: Include linux/delay.h RDMA/efa: Remove double QP type assignment f2fs: show f2fs instance in printk_ratelimited f2fs: reduce the scope of setting fsck tag when de->name_len is zero openrisc: don't printk() unconditionally dma-debug: fix debugfs initialization order SUNRPC: Fix potential memory corruption scsi: fdomain: Fix error return code in fdomain_probe() pinctrl: single: Fix error return code in pcs_parse_bits_in_pinctrl_entry() scsi: smartpqi: Fix an error code in pqi_get_raid_map() scsi: qedi: Fix error codes in qedi_alloc_global_queues() scsi: qedf: Fix error codes in qedf_alloc_global_queues() powerpc/config: Renable MTD_PHYSMAP_OF scsi: target: avoid per-loop XCOPY buffer allocations HID: i2c-hid: Fix Elan touchpad regression KVM: PPC: Book3S HV Nested: Reflect guest PMU in-use to L0 when guest SPRs are live platform/x86: dell-smbios-wmi: Add missing kfree in error-exit from run_smbios_call fscache: Fix cookie key hashing clk: at91: sam9x60: Don't use audio PLL clk: at91: clk-generated: pass the id of changeable parent at registration clk: at91: clk-generated: Limit the requested rate to our range KVM: PPC: Fix clearing never mapped TCEs in realmode f2fs: fix to account missing .skipped_gc_rwsem f2fs: fix unexpected ENOENT comes from f2fs_map_blocks() f2fs: fix to unmap pages from userspace process in punch_hole() MIPS: Malta: fix alignment of the devicetree buffer kbuild: Fix 'no symbols' warning when CONFIG_TRIM_UNUSD_KSYMS=y userfaultfd: prevent concurrent API initialization
[Kernel-packages] [Bug 1945211] Re: Fix cold plugged USB device on certain PCIe USB cards
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) 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/1945211 Title: Fix cold plugged USB device on certain PCIe USB cards Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [SRU Justification] [Impact] Cold plugged USB device was not detected on certain PCIe USB cards (like Inateck card connected to AM64 EVM or connected to J7200 EVM). And also the root hub mentioned in https://bugs.launchpad.net/bugs/1939638. Re-plugging the USB device always gets it enumerated. [Fix] As soonprimary roothub is registered, port status change is handled even before xHC is running and leads to cold plug USB devices not detected. Register both root hubs along with the secondary hcd for xhci. [Test Case] 1. Plug the USB device to the ports of problematic root hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Regression Potential] Low. It simply make sure both primary and secondary roothubs are registered along with the second HCD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945211/+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 1946788] Re: Hirsute update: upstream stable patchset 2021-10-12
** Changed in: linux (Ubuntu Hirsute) 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/1946788 Title: Hirsute update: upstream stable patchset 2021-10-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-10-12 Ported from the following upstream stable releases: v5.10.65, v5.13.17 v5.10.66, v5.13.18 from git://git.kernel.org/ locking/mutex: Fix HANDOFF condition regmap: fix the offset of register error log regulator: tps65910: Silence deferred probe error crypto: mxs-dcp - Check for DMA mapping errors sched/deadline: Fix reset_on_fork reporting of DL tasks power: supply: axp288_fuel_gauge: Report register-address on readb / writeb errors crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop() sched/deadline: Fix missing clock update in migrate_task_rq_dl() rcu/tree: Handle VM stoppage in stall detection EDAC/mce_amd: Do not load edac_mce_amd module on guests hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns() hrtimer: Ensure timerfd notification for HIGHRES=n udf: Check LVID earlier udf: Fix iocharset=utf8 mount option isofs: joliet: Fix iocharset=utf8 mount option bcache: add proper error unwinding in bcache_device_init blk-throtl: optimize IOPS throttle for large IO scenarios nvme-tcp: don't update queue count when failing to set io queues nvme-rdma: don't update queue count when failing to set io queues nvmet: pass back cntlid on successful completion power: supply: smb347-charger: Add missing pin control activation power: supply: max17042_battery: fix typo in MAx17042_TOFF s390/cio: add dev_busid sysfs entry for each subchannel s390/zcrypt: fix wrong offset index for APKA master key valid state libata: fix ata_host_start() crypto: omap - Fix inconsistent locking of device lists crypto: qat - do not ignore errors from enable_vf2pf_comms() crypto: qat - handle both source of interrupt in VF ISR crypto: qat - fix reuse of completion variable crypto: qat - fix naming for init/shutdown VF to PF notifications crypto: qat - do not export adf_iov_putmsg() fcntl: fix potential deadlock for _struct.fa_lock udf_get_extendedattr() had no boundary checks. s390/kasan: fix large PMD pages address alignment check s390/pci: fix misleading rc in clp_set_pci_fn() s390/debug: keep debug data on resize s390/debug: fix debug area life cycle s390/ap: fix state machine hang after failure to enable irq power: supply: cw2015: use dev_err_probe to allow deferred probe m68k: emu: Fix invalid free in nfeth_cleanup() sched/numa: Fix is_core_idle() sched: Fix UCLAMP_FLAG_IDLE setting rcu: Fix to include first blocked task in stall warning rcu: Add lockdep_assert_irqs_disabled() to rcu_sched_clock_irq() and callees rcu: Fix stall-warning deadlock due to non-release of rcu_node ->lock m68k: Fix invalid RMW_INSNS on CPUs that lack CAS block: return ELEVATOR_DISCARD_MERGE if possible spi: spi-fsl-dspi: Fix issue with uninitialized dma_slave_config spi: spi-pic32: Fix issue with uninitialized dma_slave_config genirq/timings: Fix error return code in irq_timings_test_irqs() irqchip/loongson-pch-pic: Improve edge triggered interrupt support lib/mpi: use kcalloc in mpi_resize clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock source channel spi: coldfire-qspi: Use clk_disable_unprepare in the remove function irqchip/gic-v3: Fix priority comparison when non-secure priorities are used crypto: qat - use proper type for vf_mask certs: Trigger creation of RSA module signing key if it's not an RSA key tpm: ibmvtpm: Avoid error message when process gets signal while waiting x86/mce: Defer processing of early errors spi: davinci: invoke chipselect callback blk-crypto: fix check for too-large dun_bytes regulator: vctrl: Use locked regulator_get_voltage in probe path regulator: vctrl: Avoid lockdep warning in enable/disable ops spi: sprd: Fix the wrong WDG_LOAD_VAL spi: spi-zynq-qspi: use wait_for_completion_timeout to make zynq_qspi_exec_mem_op not interruptible EDAC/i10nm: Fix NVDIMM detection drm/panfrost: Fix missing clk_disable_unprepare() on error in
[Kernel-packages] [Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] bnx2x driver won't add all devices ports/interfaces. [Test case] Boot system with bnx2x device and verify all ports/interfaces have been added. [Potential regression] bnx2x devices won't be properly probed. Devices won't be added or SR-IOV won't be correctly supported. --- Original Description --- Works with focal kernel 5.4.0-80 Broken with focal kernel 5.4.0-88 On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network cards Kernel 5.11.22-3 causes half of the network interfaces to disappear specifically the 1gb ports. Commands like "ip link show" and "dmesg" no longer show eno3 and eno4 nor any other interface name for these ports. I've read the note in the release notes and this does not appear to be a case of the interface changing names, the 3rd and 4th interface don't show up at all. The card is based on the BCM57800 chipset and has two SFP+ and two gigabit ports on the same card. Commands like "ip link show" no longer show ports 3 and 4. "lspci" still shows four items. dmesg only shows the first two interfaces. This problem seems to be known upstream, and seems to be a regression. More information at https://bugzilla.proxmox.com/show_bug.cgi?id=3558 This is being seen at a customer during an openstack install. It would be appreciated if a workaround could be provided or the fix could be prioritized. Using standard Focal 20.04 LTS kernel (it installs ok with the working kernel then upgrades to the non-working one -- this is done through maas and is difficult to control). Tested other kernels like hwe-* and all seem to be affected too. Client does not want to disable SRIOV on whole card and also cannot disable only ports 3/4 (the bios will not allow it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+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 1946024] Re: Focal update: v5.4.146 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1946024 Title: Focal update: v5.4.146 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.146 upstream stable release from git://git.kernel.org/ locking/mutex: Fix HANDOFF condition regmap: fix the offset of register error log crypto: mxs-dcp - Check for DMA mapping errors sched/deadline: Fix reset_on_fork reporting of DL tasks power: supply: axp288_fuel_gauge: Report register-address on readb / writeb errors crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop() sched/deadline: Fix missing clock update in migrate_task_rq_dl() rcu/tree: Handle VM stoppage in stall detection hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns() hrtimer: Ensure timerfd notification for HIGHRES=n udf: Check LVID earlier udf: Fix iocharset=utf8 mount option isofs: joliet: Fix iocharset=utf8 mount option bcache: add proper error unwinding in bcache_device_init nvme-tcp: don't update queue count when failing to set io queues nvme-rdma: don't update queue count when failing to set io queues nvmet: pass back cntlid on successful completion power: supply: max17042_battery: fix typo in MAx17042_TOFF s390/cio: add dev_busid sysfs entry for each subchannel libata: fix ata_host_start() crypto: qat - do not ignore errors from enable_vf2pf_comms() crypto: qat - handle both source of interrupt in VF ISR crypto: qat - fix reuse of completion variable crypto: qat - fix naming for init/shutdown VF to PF notifications crypto: qat - do not export adf_iov_putmsg() fcntl: fix potential deadlock for _struct.fa_lock udf_get_extendedattr() had no boundary checks. s390/kasan: fix large PMD pages address alignment check s390/debug: fix debug area life cycle m68k: emu: Fix invalid free in nfeth_cleanup() sched: Fix UCLAMP_FLAG_IDLE setting spi: spi-fsl-dspi: Fix issue with uninitialized dma_slave_config spi: spi-pic32: Fix issue with uninitialized dma_slave_config genirq/timings: Fix error return code in irq_timings_test_irqs() lib/mpi: use kcalloc in mpi_resize clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock source channel crypto: qat - use proper type for vf_mask certs: Trigger creation of RSA module signing key if it's not an RSA key regulator: vctrl: Use locked regulator_get_voltage in probe path regulator: vctrl: Avoid lockdep warning in enable/disable ops spi: sprd: Fix the wrong WDG_LOAD_VAL spi: spi-zynq-qspi: use wait_for_completion_timeout to make zynq_qspi_exec_mem_op not interruptible EDAC/i10nm: Fix NVDIMM detection drm/panfrost: Fix missing clk_disable_unprepare() on error in panfrost_clk_init() media: TDA1997x: enable EDID support soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally media: cxd2880-spi: Fix an error handling path bpf: Fix a typo of reuseport map in bpf.h. bpf: Fix potential memleak and UAF in the verifier. ARM: dts: aspeed-g6: Fix HVI3C function-group in pinctrl dtsi arm64: dts: renesas: r8a77995: draak: Remove bogus adv7511w properties soc: qcom: rpmhpd: Use corner in power_off media: dvb-usb: fix uninit-value in dvb_usb_adapter_dvb_init media: dvb-usb: fix uninit-value in vp702x_read_mac_addr media: dvb-usb: Fix error handling in dvb_usb_i2c_init media: go7007: remove redundant initialization media: coda: fix frame_mem_ctrl for YUV420 and YVU420 formats Bluetooth: sco: prevent information leak in sco_conn_defer_accept() 6lowpan: iphc: Fix an off-by-one check of array index netns: protect netns ID lookups with RCU drm/amdgpu/acp: Make PM domain really work tcp: seq_file: Avoid skipping sk during tcp_seek_last_pos ARM: dts: meson8: Use a higher default GPU clock frequency ARM: dts: meson8b: odroidc1: Fix the pwm regulator supply properties ARM: dts: meson8b: mxq: Fix the pwm regulator supply properties ARM: dts: meson8b: ec100: Fix the pwm regulator supply properties net/mlx5e: Prohibit inner indir TIRs in IPoIB cgroup/cpuset: Fix a partition bug with hotplug net: cipso: fix warnings in netlbl_cipsov4_add_std i2c: highlander: add IRQ check leds: lt3593: Put fwnode in any case during ->probe()
[Kernel-packages] [Bug 1942932] Re: oob_net0 up but stops processing Rx packets
Hi David, may you please verify this is resolved in the kernel sitting in proposed? You can find instructions for how to do this in comment #1. thank you! -- 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/1942932 Title: oob_net0 up but stops processing Rx packets Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The oob_net0 interface, managed by the mlxbf_gige driver, will be up and enabled but can stop processing received packets if three specific conditions occur: 1) driver has received more than (N * RxRingSize) packets but less than (N+1 * RxRingSize) packets where N is an odd number. Note: the command "ethtool -g oob_net0" will display the current receive ring size, which currently defaults to 128. 2) the driver's interface was disabled via "ifconfig oob_net0 down" during the window described in #1. 3) the driver's interface is re-enabled via "ifconfig oob_net0 up" Without this fix, the driver needs to be unloaded and re-loaded to correct this condition. [Fix] * The fix is to ensure that the driver's "valid_polarity" field is cleared during the open() method so that it always matches the receive polarity used by hardware. [Test Case] * To test this fix, need to send in a specific number of packets to the "oob_net0" interface, then issue "ifconfig oob_net0 down" to disable the interface. A subsequent "ifconfig oob_net0 up" command will succesfully bring up the "oob_net0" interface and start the processing of received packets. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942932/+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 1942931] Re: "ethtool -S oob_net0" does not report interrupt counts
Hi David, may you please verify this bug is resolved in the kernel sitting in proposed? You can find instructions for how to complete that in comment #1. Thank you! -- 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/1942931 Title: "ethtool -S oob_net0" does not report interrupt counts Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The command "ethtool -S oob_net0" displays a set of statistics related to mlxbf_gige driver. This set of statistics does not include the driver's interrupt counts. [Fix] * The fix is to extend the statistics list supported by "ethtool -S" so that it includes MAC, receive packet, and LLU/PLU interrupt counts. [Test Case] * The command "ethtool -S oob_net0" should be executed before and after this fix to verify that three new fields are displayed: mac_intr_count rx_intr_count llu_plu_intr_count [Regression Potential] * There is low risk of this fix causing any problems. [Other] * n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942931/+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 1943065] Re: mlxbf_gige: update driver version to 1.25
Hi David, may you please verify this bug is resolved in the kernel in proposed? You can find instructions in comment #2 https://bugs.launchpad.net/ubuntu/+source/linux- bluefield/+bug/1943065/comments/2 Thank you! -- 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/1943065 Title: mlxbf_gige: update driver version to 1.25 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The mlxbf_gige driver needs a version increase to identify a driver containing recent important bug fixes. [Fix] * The driver version implemented by the DRV_VERSION define and MODULE_VERSION macro will be incremented from 1.24 to 1.25 [Test Case] * To test this fix, need to check the driver version shown in the output of "modinfo mlxbf_gige" command. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1943065/+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 1943065] Re: mlxbf_gige: update driver version to 1.25
Hi Meriton, the fix is currently in linux-bluefield/5.4.0-1020.23 which is in proposed. As long as test reviews continue to go well, this will be scheduled to release next week. Schedule can be found here: https://kernel.ubuntu.com/ If you are able to complete the verification mentioned in comment #2, it would be very helpful. :) -- 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/1943065 Title: mlxbf_gige: update driver version to 1.25 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The mlxbf_gige driver needs a version increase to identify a driver containing recent important bug fixes. [Fix] * The driver version implemented by the DRV_VERSION define and MODULE_VERSION macro will be incremented from 1.24 to 1.25 [Test Case] * To test this fix, need to check the driver version shown in the output of "modinfo mlxbf_gige" command. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1943065/+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 1942902] Re: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
** Tags removed: verification-needed-focal
** Tags added: verification-done-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/1942902
Title:
Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption"
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
In order to address https://bugs.launchpad.net/bugs/1933074 the following
SAUCE patch was introduced.
Colin Ian King (1):
UBUNTU: SAUCE: ext4: fix directory index node split corruption
fs/ext4/namei.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
Meanwhile the issue addressed by this patch was fixed upstream with
commit 877ba3f729fd ("ext4: fix potential htree corruption when
growing large_dir directories").
The upstream patch was already cherry-picked to hirsute with "upstream
stable patchset 2021-08-30" [1] commit ffcc845ec245) and focal with
"v5.4.140 upstream stable release" [2] (commit 93ad4c3f59c6).
[1] BugLink: https://bugs.launchpad.net/bugs/1942123
[2] BugLink: https://bugs.launchpad.net/bugs/1941798
Therefore the SAUCE patch is obsolete and can be either dropped or
reverted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+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 1946219] Re: liburing stops working after upgrading to 5.4.0-1012
** Changed in: linux-bluefield (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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1946219 Title: liburing stops working after upgrading to 5.4.0-1012 Status in HWE Next: New Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: Fix Committed Bug description: == Impact == After configuration multipath with io uring virtio_blk module is stuck == Fix == The issue was introduced by one of the stable updates merged in the base kernel Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be reproduced any more. commit d6757b3e34831b7615edd3268b878536761f8b2e Author: Pavel Begunkov Date: Fri Nov 20 17:10:28 2020 + block: don't ignore REQ_NOWAIT for direct IO BugLink: https://bugs.launchpad.net/bugs/1926490 [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocking on eg request allocation on the storage side. Signed-off-by: Pavel Begunkov Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader == Risk of Regression == Medium. The commit has a good reason to be part of the stable updates. However the kernel passes Cert and Nvidia tests without the commit so reverting the commit should be an acceptable approach for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946219/+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 1929247] Re: kernel/selftests: seccomp_benchmark fails with timeout in H/KVM
** Tags added: sru-20210927 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1929247 Title: kernel/selftests: seccomp_benchmark fails with timeout in H/KVM Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Hirsute: New Bug description: Found that on cycle sru-20210510, on H/KVM 5.11.0-1008.8 : 02:36:23 DEBUG| [stdout] # selftests: seccomp: seccomp_benchmark 02:36:23 DEBUG| [stdout] # sysctl: cannot stat /proc/sys/net/core/bpf_jit_enable: No such file or directory 02:36:23 DEBUG| [stdout] # sysctl: cannot stat /proc/sys/net/core/bpf_jit_harden: No such file or directory 02:38:23 DEBUG| [stdout] # 02:38:23 DEBUG| [stdout] not ok 2 selftests: seccomp: seccomp_benchmark # TIMEOUT 120 seconds In the previous cycle this test worked, but this one failed due to timeout - I've manually executed in my Hirsute VM and it succeeded in ~100 seconds. Maybe we need to just bump the timeout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1929247/+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 1748103] Re: apic test in kvm-unit-test failed with timeout
** Tags added: sru-20210906 -- 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/1748103 Title: apic test in kvm-unit-test failed with timeout Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-azure-edge source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-azure-edge source package in Bionic: New Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test apic will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the apic test as root: # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7 enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id FAIL: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand PASS: nmi-after-sti qemu-system-x86_64: terminating on signal 15 from pid 7246 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:00:55 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DistroRelease: Ubuntu 16.04 Package: linux-azure-edge PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13 Tags: xenial uec-images Uname: Linux 4.13.0-1009-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+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 1831449] Re: memory in ubuntu_kvm_unit_tests fails (clflushopt / clwb ABSENT)
** Tags added: sru-20210906 -- 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/1831449 Title: memory in ubuntu_kvm_unit_tests fails (clflushopt / clwb ABSENT) Status in ubuntu-kernel-tests: Triaged Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: FAIL: clflushopt (ABSENT) FAIL: clwb (ABSENT) Test output: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/memory' BUILD_HEAD=32db322d 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.SOyUkPCNxP -smp 1 -cpu max # -initrd /tmp/tmp.DiAWwvk2jC enabling apic PASS: clflush (present) PASS: sfence (present) PASS: lfence (present) PASS: mfence (present) FAIL: clflushopt (ABSENT) FAIL: clwb (ABSENT) PASS: invalid clwb PASS: pcommit (ABSENT) SUMMARY: 8 tests, 2 unexpected failures FAIL memory (8 tests, 2 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+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 1933248] Re: please drop virtualbox-guest-dkms virtualbox-guest-source
Removing tags `block-proposed-focal verification-failed-focal`. Commit in Focal was reverted. ** Tags removed: block-proposed-focal verification-failed-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/1933248 Title: please drop virtualbox-guest-dkms virtualbox-guest-source Status in linux package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in virtualbox source package in Focal: Invalid Status in virtualbox-hwe source package in Focal: Invalid Bug description: [Impact] * virtualbox guest modules have graduated into the upstream vanilla kernel, since at least v5.4 / Ubuntu 20.04 * These guest modules are no longer needed in dkms or source form, as they are always available from all kernel flavours, including when the packages are backported to Ubuntu 20.04. * Thus we should stop shipping them, and instead rely on the upstream ones. [Test Plan] * Boot virtualbox images * Check that guest-modules based integration still works. [Where problems could occur] * There might be differences between the linux kernel provided modules, guest userspace & host userspace tooling. If there are any differences, we would have to resolve the issues as needed to maintain backwards & forwards compatibility. [Other Info] * virtualbox guest modules fail to build from source with recent kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933248/+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 1847340] Re: ext4 journal recovery fails w/ data=journal + mmap
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. And the stress-ng test-case as well. (Numbers/details in the LP bug.) [Other info] The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; only Focal and Bionic need it. There are little changes in the patches between Focal and Bionic (mostly minor backport adjustments, mainly due to no vm_fault_t) but unfortunately that needs separate versions for most patches. ... [Original Bug Description] [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+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 1942902] Re: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1942902
Title:
Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption"
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
In order to address https://bugs.launchpad.net/bugs/1933074 the following
SAUCE patch was introduced.
Colin Ian King (1):
UBUNTU: SAUCE: ext4: fix directory index node split corruption
fs/ext4/namei.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
Meanwhile the issue addressed by this patch was fixed upstream with
commit 877ba3f729fd ("ext4: fix potential htree corruption when
growing large_dir directories").
The upstream patch was already cherry-picked to hirsute with "upstream
stable patchset 2021-08-30" [1] commit ffcc845ec245) and focal with
"v5.4.140 upstream stable release" [2] (commit 93ad4c3f59c6).
[1] BugLink: https://bugs.launchpad.net/bugs/1942123
[2] BugLink: https://bugs.launchpad.net/bugs/1941798
Therefore the SAUCE patch is obsolete and can be either dropped or
reverted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+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 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Changed in: linux (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/1892213
Title:
psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
focal/groovy/hirsute/impish
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 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:
Fix Committed
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Bug description:
[Impact]
The expected to fail 'raw gso min size - 1' test in psock_snd.sh is
not failing as expected, and thus this test will fail with:
raw gso min size - 1 (expected to fail)
tx: 1524
rx: 1472
OK
This is because after commit 7c6d2ec ("net: be more gentle about silly
gso requests coming from user"), we relaxed the min gso_size check in
virtio_net_hdr_to_skb().
So when a packet which is smaller then the gso_size, GSO for this
packet will not be set, the packet will be send/recv successfully.
[Fix]
* cfba3fb68960b4 selftests/net: remove min gso test in packet_snd
This patch can be cherry-picked into all affected kernels.
I decided to skip those 5.8 variants, as the current cycle
(2021-09-06) might be the last cycle for them.
[Test]
Run this psock_snd.sh script, this test will no longer exist and the
script can proceed with the next test.
[Where problems could occur]
Removing this broken test should not have any negative impact to our
tests. We will need to update our hints later.
[Original Bug Report]
Testing failed on focal/linux 5.4.0-44.48:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz
psock_snd.sh output:
16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
16:28:31 DEBUG| [stdout] # dgram
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # dgram bind
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw bind
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw qdisc bypass
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vlan
16:28:31 DEBUG| [stdout] # tx: 146
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vnet hdr
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
16:28:31 DEBUG| [stdout] # raw min size
16:28:31 DEBUG| [stdout] # tx: 42
16:28:31 DEBUG| [stdout] # rx: 0
[Kernel-packages] [Bug 1944212] Re: Focal update: v5.4.143 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1944212 Title: Focal update: v5.4.143 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.143 upstream stable release from git://git.kernel.org/ ext4: fix EXT4_MAX_LOGICAL_BLOCK macro x86/fpu: Make init_fpstate correct with optimized XSAVE ath: Use safer key clearing with key cache entries ath9k: Clear key cache explicitly on disabling hardware ath: Export ath_hw_keysetmac() ath: Modify ath_key_delete() to not need full key entry ath9k: Postpone key cache entry deletion for TXQ frames reference it mtd: cfi_cmdset_0002: fix crash when erasing/writing AMD cards media: zr364xx: propagate errors from zr364xx_start_readpipe() media: zr364xx: fix memory leaks in probe() media: drivers/media/usb: fix memory leak in zr364xx_probe USB: core: Avoid WARNings for 0-length descriptor requests dmaengine: xilinx_dma: Fix read-after-free bug when terminating transfers dmaengine: usb-dmac: Fix PM reference leak in usb_dmac_probe() ARM: dts: am43x-epos-evm: Reduce i2c0 bus speed for tps65218 dmaengine: of-dma: router_xlate to return -EPROBE_DEFER if controller is not yet available scsi: megaraid_mm: Fix end of loop tests for list_for_each_entry() scsi: scsi_dh_rdac: Avoid crash during rdac_bus_attach() scsi: core: Avoid printing an error if target_alloc() returns -ENXIO scsi: core: Fix capacity set to zero after offlinining device ARM: dts: nomadik: Fix up interrupt controller node names net: usb: lan78xx: don't modify phy_device state concurrently drm/amd/display: Fix Dynamic bpp issue with 8K30 with Navi 1X Bluetooth: hidp: use correct wait queue when removing ctrl_wait iommu: Check if group is NULL before remove device cpufreq: armada-37xx: forbid cpufreq for 1.2 GHz variant dccp: add do-while-0 stubs for dccp_pr_debug macros virtio: Protect vqs list access vhost: Fix the calculation in vhost_overflow() bpf: Clear zext_dst of dead insns bnxt: don't lock the tx queue from napi poll bnxt: disable napi before canceling DIM net: 6pack: fix slab-out-of-bounds in decode_data ptp_pch: Restore dependency on PCI bnxt_en: Add missing DMA memory barriers vrf: Reset skb conntrack connection on VRF rcv virtio-net: support XDP when not more queues virtio-net: use NETIF_F_GRO_HW instead of NETIF_F_LRO net: qlcnic: add missed unlock in qlcnic_83xx_flash_read32 net: mdio-mux: Don't ignore memory allocation errors net: mdio-mux: Handle -EPROBE_DEFER correctly ovs: clear skb->tstamp in forwarding path i40e: Fix ATR queue selection iavf: Fix ping is lost after untrusted VF had tried to change MAC ovl: add splice file read write helper mmc: dw_mmc: Fix hang on data CRC error ALSA: hda - fix the 'Capture Switch' value change notifications tracing / histogram: Fix NULL pointer dereference on strcmp() on NULL event name slimbus: messaging: start transaction ids from 1 instead of zero slimbus: messaging: check for valid transaction id slimbus: ngd: reset dma setup during runtime pm ipack: tpci200: fix many double free issues in tpci200_pci_probe ipack: tpci200: fix memory leak in the tpci200_register btrfs: prevent rename2 from exchanging a subvol with a directory from different parents PCI: Increase D3 delay for AMD Renoir/Cezanne XHCI ASoC: intel: atom: Fix breakage for PCM buffer address setup mm, memcg: avoid stale protection values when cgroup is above protection mm: memcontrol: fix occasional OOMs due to proportional memory.low reclaim fs: warn about impending deprecation of mandatory locks netfilter: nft_exthdr: fix endianness of tcp option cast Linux 5.4.143 UBUNTU: upstream stable to v5.4.143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944212/+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 1944202] Re: Focal update: v5.4.142 upstream stable release
** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1944202
Title:
Focal update: v5.4.142 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.142 upstream stable release
from git://git.kernel.org/
iio: adc: ti-ads7950: Ensure CS is deasserted after reading channels
iio: humidity: hdc100x: Add margin to the conversion time
iio: adc: Fix incorrect exit of for-loop
ASoC: xilinx: Fix reference to PCM buffer address
ASoC: intel: atom: Fix reference to PCM buffer address
i2c: dev: zero out array used for i2c reads from userspace
ceph: reduce contention in ceph_check_delayed_caps()
ACPI: NFIT: Fix support for virtual SPA ranges
libnvdimm/region: Fix label activation vs errors
ieee802154: hwsim: fix GPF in hwsim_set_edge_lqi
ieee802154: hwsim: fix GPF in hwsim_new_edge_nl
ASoC: cs42l42: Correct definition of ADC Volume control
ASoC: cs42l42: Don't allow SND_SOC_DAIFMT_LEFT_J
ASoC: cs42l42: Fix inversion of ADC Notch Switch control
ASoC: cs42l42: Remove duplicate control for WNF filter frequency
netfilter: nf_conntrack_bridge: Fix memory leak when error
ASoC: cs42l42: Fix LRCLK frame start edge
net: dsa: mt7530: add the missing RxUnicast MIB counter
platform/x86: pcengines-apuv2: revert wiring up simswitch GPIO as LED
platform/x86: pcengines-apuv2: Add missing terminating entries to gpio-lookup
tables
net: phy: micrel: Fix link detection on ksz87xx switch"
ppp: Fix generating ifname when empty IFLA_IFNAME is specified
net: sched: act_mirred: Reset ct info when mirror/redirect skb
iavf: Set RSS LUT and key in reset handle path
psample: Add a fwd declaration for skbuff
net/mlx5: Fix return value from tracer initialization
drm/meson: fix colour distortion from HDR set during vendor u-boot
net: dsa: microchip: Fix ksz_read64()
net: Fix memory leak in ieee802154_raw_deliver
net: igmp: fix data-race in igmp_ifc_timer_expire()
net: dsa: lan9303: fix broken backpressure in .port_fdb_dump
net: dsa: lantiq: fix broken backpressure in .port_fdb_dump
net: dsa: sja1105: fix broken backpressure in .port_fdb_dump
net: bridge: fix memleak in br_add_if()
net: linkwatch: fix failure to restore device state across suspend/resume
tcp_bbr: fix u32 wrap bug in round logic if bbr_init() called after 2B packets
net: igmp: increase size of mr_ifc_count
xen/events: Fix race in set_evtchn_to_irq
vsock/virtio: avoid potential deadlock when vsock device remove
nbd: Aovid double completion of a request
powerpc/kprobes: Fix kprobe Oops happens in booke
x86/tools: Fix objdump version check again
genirq: Provide IRQCHIP_AFFINITY_PRE_STARTUP
x86/msi: Force affinity setup before startup
x86/ioapic: Force affinity setup before startup
x86/resctrl: Fix default monitoring groups reporting
genirq/msi: Ensure deactivation on teardown
genirq/timings: Prevent potential array overflow in __irq_timings_store()
PCI/MSI: Enable and mask MSI-X early
PCI/MSI: Mask all unused MSI-X entries
PCI/MSI: Enforce that MSI-X table entry is masked for update
PCI/MSI: Enforce MSI[X] entry updates to be visible
PCI/MSI: Do not set invalid bits in MSI mask
PCI/MSI: Correct misleading comments
PCI/MSI: Use msi_mask_irq() in pci_msi_shutdown()
PCI/MSI: Protect msi_desc::masked for multi-MSI
KVM: VMX: Use current VMCS to query WAITPKG support for MSR emulation
ceph: add some lockdep assertions around snaprealm handling
ceph: clean up locking annotation for ceph_get_snap_realm and
__lookup_snap_realm
ceph: take snap_empty_lock atomically with snaprealm refcount change
vmlinux.lds.h: Handle clang's module.{c,d}tor sections
iommu/vt-d: Fix agaw for a supported 48 bit guest address width
Linux 5.4.142
UBUNTU: upstream stable to v5.4.142
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944202/+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 1934923] Re: Sync up mlxbf-gige driver with upstreamed version
F/bluefield 5.4.0-1019.22 is currently in -proposed and ready to test. Thank you, Meriton :) -- 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/1934923 Title: Sync up mlxbf-gige driver with upstreamed version Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf-gige driver has just been upstreamed so linux-bluefield needs to be synced up with what we have upstreamed. IMPORTANT: during testing, make sure the latest UEFI (bootloader) is loaded on top of these changes, otherwise both the gpio driver and mlxbf-gige driver will fail to load. [Fix] * reverted 20 commits related to the mlxbf-gige driver and 1 commit related to gpio-mlxbf2 driver since there are dependencies between them. * Cherry-picked f92e1869d74e1acc6551256eb084a1c14a054e19 from net-next branch. The upstreamed version of the GPIO driver removed the dependency between the mlxbf-gige driver and gpio-mlxbf2 driver. * added code that was left out of the upstreamed version. and added code that got reverted in gpio-mlxbf2.c * updated the UEFI ACPI table to reflect the above changes (so the bootloader and the linux drivers need to be in sync) [Test Case] * oob_net0 coming up after several SW_RESET or reboot * oob_net0 coming up after several powercycles * oob_net0 coming up after pushing a new Ubuntu/CentOS/Yocto * rmmod/modprove mlxbf_gige several times * OOB PXE boot multiple times from UEFI menu * automate OOB PXE boot and do reboot * automate OOB PXE boot and do powercycle * Test that GPIO7 reset still works on BlueSphere like boards [Regression Potential] Any of the test cases above could be impacted due to these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934923/+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 1933248] Re: please drop virtualbox-guest-dkms virtualbox-guest-source
** Changed in: linux (Ubuntu Focal) Status: Triaged => 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/1933248 Title: please drop virtualbox-guest-dkms virtualbox-guest-source Status in linux package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in virtualbox source package in Focal: Invalid Status in virtualbox-hwe source package in Focal: Invalid Bug description: [Impact] * virtualbox guest modules have graduated into the upstream vanilla kernel, since at least v5.4 / Ubuntu 20.04 * These guest modules are no longer needed in dkms or source form, as they are always available from all kernel flavours, including when the packages are backported to Ubuntu 20.04. * Thus we should stop shipping them, and instead rely on the upstream ones. [Test Plan] * Boot virtualbox images * Check that guest-modules based integration still works. [Where problems could occur] * There might be differences between the linux kernel provided modules, guest userspace & host userspace tooling. If there are any differences, we would have to resolve the issues as needed to maintain backwards & forwards compatibility. [Other Info] * virtualbox guest modules fail to build from source with recent kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933248/+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 1938818] Re: Add support for packet-per-second policing
Marking verification completed. Thank you, Bodong! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1938818 Title: Add support for packet-per-second policing Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) It’s a missing feature in current kernel. * brief explanation of fixes Cherry-pick and backport the related patches from upstream kernel. * How to test Add tc filter rule with police action, and check it is offloaded. For example: tc filter add dev enp8s0f0_0 ingress protocol ip flower \ dst_mac b8:ce:f6:7b:d9:24 \ action police pkts_rate 1000 pkts_burst 100 conform-exceed drop/pipe \ action mirred egress redirect dev enp8s0f0 * What it could break. New feature, doesn't break existing features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1938818/+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
