[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
** Changed in: ideapad-laptop Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: Invalid Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2039816] Re: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel
Try ‘s/sha1/md5’ and ‘s/aes/des3_ede’ on vrf-xfrm-tests.sh, either way it can passes. I will read more about this test and find out how it fails. Bug against kunpeng920 is also filed. https://bugs.launchpad.net/kunpeng920/+bug/2043365 ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039816 Title: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: Issue found on ARM64 node scobee-kernel with: * J-5.15.0-86.95 lowlatency * 5.15.0-85.95~20.04.2 generic * F-5.15.0-86.95~20.04.1 lowlatency * F-5.15.0-87.96~20.04.1 lowlatency-64k Test failed with: $ sudo ./vrf-xfrm-tests.sh No qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] netem qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] Tests passed: 6 Tests failed: 8 And this issue does not exist with the following combination: * F-generic-5.15.0-86.96~20.04.1 howzit-kernel * F-generic-5.15.0-86.96~20.04.1 wright-kernel * F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel * F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel * F-lowlatency-5.15.0-85.94 starmie-kernel * F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel * J-lowlatency-64k-5.15.0-85.94 starmie-kernel * J-lowlatency-64k-5.15.0-86.95 howzit-kernel So it looks like this is hardware related. And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests: change authentication and encryption algos"), which lands on the Jammy tree since: * Ubuntu-5.15.0-85.95 * Ubuntu-lowlatency-5.15.0-85.94 With this commit reverted, this test can pass on node scobee-kernel with 5.15.0-87-lowlatency-64k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2039816/+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 2039816] Re: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel
After `rmmod hisi_sec2`, 5.15.0-87.97 kernel passes all tests. In conclusion, after vrf-xfrm-tests algorithms switched since v6.4 kernel, it fails with hisi_sec2 loaded. -- 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/2039816 Title: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on ARM64 node scobee-kernel with: * J-5.15.0-86.95 lowlatency * 5.15.0-85.95~20.04.2 generic * F-5.15.0-86.95~20.04.1 lowlatency * F-5.15.0-87.96~20.04.1 lowlatency-64k Test failed with: $ sudo ./vrf-xfrm-tests.sh No qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] netem qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] Tests passed: 6 Tests failed: 8 And this issue does not exist with the following combination: * F-generic-5.15.0-86.96~20.04.1 howzit-kernel * F-generic-5.15.0-86.96~20.04.1 wright-kernel * F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel * F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel * F-lowlatency-5.15.0-85.94 starmie-kernel * F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel * J-lowlatency-64k-5.15.0-85.94 starmie-kernel * J-lowlatency-64k-5.15.0-86.95 howzit-kernel So it looks like this is hardware related. And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests: change authentication and encryption algos"), which lands on the Jammy tree since: * Ubuntu-5.15.0-85.95 * Ubuntu-lowlatency-5.15.0-85.94 With this commit reverted, this test can pass on node scobee-kernel with 5.15.0-87-lowlatency-64k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2039816/+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 2039816] Re: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel
Using 5.15.0-25.25 and the results are the same, vrf-xfrm-tests.sh in linux v6.3 passes and v6.4 fails. Good news is this is not because of any kernel upgrade, and the next step is to look if any function missing/broken in Ubuntu 5.15 kernels. -- 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/2039816 Title: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on ARM64 node scobee-kernel with: * J-5.15.0-86.95 lowlatency * 5.15.0-85.95~20.04.2 generic * F-5.15.0-86.95~20.04.1 lowlatency * F-5.15.0-87.96~20.04.1 lowlatency-64k Test failed with: $ sudo ./vrf-xfrm-tests.sh No qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] netem qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] Tests passed: 6 Tests failed: 8 And this issue does not exist with the following combination: * F-generic-5.15.0-86.96~20.04.1 howzit-kernel * F-generic-5.15.0-86.96~20.04.1 wright-kernel * F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel * F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel * F-lowlatency-5.15.0-85.94 starmie-kernel * F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel * J-lowlatency-64k-5.15.0-85.94 starmie-kernel * J-lowlatency-64k-5.15.0-86.95 howzit-kernel So it looks like this is hardware related. And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests: change authentication and encryption algos"), which lands on the Jammy tree since: * Ubuntu-5.15.0-85.95 * Ubuntu-lowlatency-5.15.0-85.94 With this commit reverted, this test can pass on node scobee-kernel with 5.15.0-87-lowlatency-64k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2039816/+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 2039816] Re: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel
Between v6.3 and v6.4 some algorithms has been replaced. commit cb43c60e64ca67fcc9d23bd08f51d2ab8209d9d7 Author: Magali Lemes Date: Tue Jun 13 09:32:21 2023 -0300 selftests: net: vrf-xfrm-tests: change authentication and encryption algos The vrf-xfrm-tests tests use the hmac(md5) and cbc(des3_ede) algorithms for performing authentication and encryption, respectively. This causes the tests to fail when fips=1 is set, since these algorithms are not allowed in FIPS mode. Therefore, switch from hmac(md5) and cbc(des3_ede) to hmac(sha1) and cbc(aes), which are FIPS compliant. -- 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/2039816 Title: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on ARM64 node scobee-kernel with: * J-5.15.0-86.95 lowlatency * 5.15.0-85.95~20.04.2 generic * F-5.15.0-86.95~20.04.1 lowlatency * F-5.15.0-87.96~20.04.1 lowlatency-64k Test failed with: $ sudo ./vrf-xfrm-tests.sh No qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] netem qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] Tests passed: 6 Tests failed: 8 And this issue does not exist with the following combination: * F-generic-5.15.0-86.96~20.04.1 howzit-kernel * F-generic-5.15.0-86.96~20.04.1 wright-kernel * F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel * F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel * F-lowlatency-5.15.0-85.94 starmie-kernel * F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel * J-lowlatency-64k-5.15.0-85.94 starmie-kernel * J-lowlatency-64k-5.15.0-86.95 howzit-kernel So it looks like this is hardware related. And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests: change authentication and encryption algos"), which lands on the Jammy tree since: * Ubuntu-5.15.0-85.95 * Ubuntu-lowlatency-5.15.0-85.94 With this commit reverted, this test can pass on node scobee-kernel with 5.15.0-87-lowlatency-64k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2039816/+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 2039816] Re: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel
Checked with vrf-xfrm-tests.sh in mainline kernel. With 5.15.0-87.97 kernel v6.3 passes and v6.4 failed. -- 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/2039816 Title: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on ARM64 node scobee-kernel with: * J-5.15.0-86.95 lowlatency * 5.15.0-85.95~20.04.2 generic * F-5.15.0-86.95~20.04.1 lowlatency * F-5.15.0-87.96~20.04.1 lowlatency-64k Test failed with: $ sudo ./vrf-xfrm-tests.sh No qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] netem qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] Tests passed: 6 Tests failed: 8 And this issue does not exist with the following combination: * F-generic-5.15.0-86.96~20.04.1 howzit-kernel * F-generic-5.15.0-86.96~20.04.1 wright-kernel * F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel * F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel * F-lowlatency-5.15.0-85.94 starmie-kernel * F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel * J-lowlatency-64k-5.15.0-85.94 starmie-kernel * J-lowlatency-64k-5.15.0-86.95 howzit-kernel So it looks like this is hardware related. And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests: change authentication and encryption algos"), which lands on the Jammy tree since: * Ubuntu-5.15.0-85.95 * Ubuntu-lowlatency-5.15.0-85.94 With this commit reverted, this test can pass on node scobee-kernel with 5.15.0-87-lowlatency-64k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2039816/+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 2039816] Re: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel
Interested. I can reproduce this issue with latest vrf-xfrm-tests.sh on 5.15.0-87.97 but can not reproduce with linux v6.3 vrf-xfrm-tests.sh. This might be a testcase issue. -- 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/2039816 Title: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on ARM64 node scobee-kernel with: * J-5.15.0-86.95 lowlatency * 5.15.0-85.95~20.04.2 generic * F-5.15.0-86.95~20.04.1 lowlatency * F-5.15.0-87.96~20.04.1 lowlatency-64k Test failed with: $ sudo ./vrf-xfrm-tests.sh No qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] netem qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] Tests passed: 6 Tests failed: 8 And this issue does not exist with the following combination: * F-generic-5.15.0-86.96~20.04.1 howzit-kernel * F-generic-5.15.0-86.96~20.04.1 wright-kernel * F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel * F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel * F-lowlatency-5.15.0-85.94 starmie-kernel * F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel * J-lowlatency-64k-5.15.0-85.94 starmie-kernel * J-lowlatency-64k-5.15.0-86.95 howzit-kernel So it looks like this is hardware related. And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests: change authentication and encryption algos"), which lands on the Jammy tree since: * Ubuntu-5.15.0-85.95 * Ubuntu-lowlatency-5.15.0-85.94 With this commit reverted, this test can pass on node scobee-kernel with 5.15.0-87-lowlatency-64k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2039816/+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 2039816] Re: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel
** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/2039816 Title: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on ARM64 node scobee-kernel with: * J-5.15.0-86.95 lowlatency * 5.15.0-85.95~20.04.2 generic * F-5.15.0-86.95~20.04.1 lowlatency * F-5.15.0-87.96~20.04.1 lowlatency-64k Test failed with: $ sudo ./vrf-xfrm-tests.sh No qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] netem qdisc on VRF device TEST: IPv4 no xfrm policy [ OK ] TEST: IPv6 no xfrm policy [ OK ] TEST: IPv4 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy based on address [FAIL] TEST: IPv6 xfrm policy with VRF in selector [ OK ] TEST: IPv4 xfrm policy with xfrm device [FAIL] TEST: IPv6 xfrm policy with xfrm device [FAIL] Tests passed: 6 Tests failed: 8 And this issue does not exist with the following combination: * F-generic-5.15.0-86.96~20.04.1 howzit-kernel * F-generic-5.15.0-86.96~20.04.1 wright-kernel * F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel * F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel * F-lowlatency-5.15.0-85.94 starmie-kernel * F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel * J-lowlatency-64k-5.15.0-85.94 starmie-kernel * J-lowlatency-64k-5.15.0-86.95 howzit-kernel So it looks like this is hardware related. And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests: change authentication and encryption algos"), which lands on the Jammy tree since: * Ubuntu-5.15.0-85.95 * Ubuntu-lowlatency-5.15.0-85.94 With this commit reverted, this test can pass on node scobee-kernel with 5.15.0-87-lowlatency-64k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2039816/+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 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
Test from 5.4.0-26.30 and looks like this issue starts from 5.4.0-31.35. I will do more test to make sure this -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702] secondary_start_kernel+0x198/0x288 Dec 2 12:17:46 appleton-kernel kernel: [ 98.829315] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Dec 2 12:17:46 appleton-kernel ker
[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
I believe it is ok to say this bug is fix already. Thanks Colin. ** Changed in: stress-ng Assignee: Ike Panhc (ikepanhc) => (unassigned) -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: Invalid Status in stress-ng package in Ubuntu: Fix Released Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1999731] Re: disk stress test failing with code 7
For more information, test V0.15.00 to V0.15.04 for 300 times each[1], I can reproduce on V0.15.00 and V0.15.01 only. console output are attached. -- [1] #!/bin/bash for i in `cat gittag.txt`; do echo $i cd /home/ubuntu/stress-ng make clean git reset --hard git checkout $i make clean make cd /home/ubuntu for j in `seq 1 300`; do ./stress-ng/stress-ng --lockofd 0 -t 240 echo == $? == done done $ cat gittag.txt V0.15.00 V0.15.01 V0.15.02 V0.15.03 V0.15.04 ** Attachment added: "screenlog.0.bz2" https://bugs.launchpad.net/stress-ng/+bug/1999731/+attachment/5654104/+files/screenlog.0.bz2 -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: Invalid Status in stress-ng package in Ubuntu: Fix Released Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
Same test in #7 for bionic and so far all 13 deploy looks good, no soft lockup. Looks this is a focal kernel issue and I will try to reboot into different focal kernel. ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702] secondary_start_kernel+0x198/0x288 Dec 2 12:
[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
Thanks Colin, For your information, I ran a loop test[1] on each of stress-ng tags since V0.12.00, with 100 times lockofd run and see the return value. This issue starts to be seen since V0.12.09 (or maybe early because the reprudce chance is very low). Full console log is attached for your information. -- #!/bin/bash for i in `cat gittag.txt`; do echo $i cd /home/ubuntu/stress-ng make clean git reset --hard git checkout $i make clean make cd /home/ubuntu for j in `seq 1 100`; do ./stress-ng/stress-ng --lockofd 0 -t 240 echo == $? == done done ** Attachment added: "screenlog.0.gz" https://bugs.launchpad.net/stress-ng/+bug/1999731/+attachment/5652313/+files/screenlog.0.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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: Invalid Status in stress-ng package in Ubuntu: Fix Released Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1999731] Re: disk stress test failing with code 7
** Changed in: linux (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: Invalid Status in stress-ng package in Ubuntu: Fix Released Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
Tried to deploy and wait for 100min to see if soft lockup shows. Deploy focal and I can reproduce 5 times in 8 deploy test. Deploy jammy and it passes 20 deploy and everything looks good. It looks more and more like a focal kernel issue to me. -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702] secondary_start_kernel+0x198/0x288 Dec 2 12:17:
[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
Thanks cking, I have trouble finding a machine stably reproducing this issue. I will run >100 times test on V0.15.04 and V0.15.03. If V0.15.04 is much more stable, we can switch to V0.15.04 to avoid this issue. Many thanks. -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1999731] Re: disk stress test failing with code 7
Here is the fail log with stress-ng 0.15.01-1~f1 on d05-5 with `--vmstat 1` ** Attachment added: "faillog.txt" https://bugs.launchpad.net/stress-ng/+bug/1999731/+attachment/5639246/+files/faillog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1999731] Re: disk stress test failing with code 7
Running 5.4.0-135.152 kernel on d05-2 with stress-ng 0.11.07-1ubuntu2 -> 10/10 passed d05-2 with stress-ng 0.14.06-0~202210291239~ubuntu20.04.1 -> 10/10 passed d05-5 with stress-ng 0.15.01-1~f1 -> 9/10 passed and on d05-5 with stress-ng 0.14.06-0~202210291239~ubuntu20.04.1 I see failure yesterday. I will run more test on d05-5 to find out. The disk on d05-2 is 4T rotary and d05-5 is 8T rotary. -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1999731] Re: disk stress test failing with code 7
Thanks cking and David, I am running 0.11.07-1ubuntu2 from archive, 0.14.06-0~202210291239~ubuntu20.04.1 from ppa:hardware- certification/public and 0.15.01-1~f1 from ppa:colin-king/stress-ng with 5.4.0-135.152 kernel to see if stress-ng version matters. If not, next step is to test on kernels. -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
For next steps, 1) Find out why I can not use maas-cli to deploy bionic-hwe on d05-3 2) Collect failure logs on appleton 3) Find out the hardware difference -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702] secondary_start_kernel+0x198/0x288 Dec 2 12:17:46 appleton-kernel kernel: [ 98.829315] rcu: INFO: rcu_sched detected stalls on CPUs
[Kernel-packages] [Bug 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
MAAS deploy/release loop with focal[1] on d05-3 and has deployed for 82 times without failure. MAAS deploy/release loop with bionic-hwe on appleton run 100 times and 10 of them are failed. Look like this issue is only happened on appleton. -- [1] For some reason I can not deploy bionic-hwe with d05-3. Working on it. -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kerne
[Kernel-packages] [Bug 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
Check log again and it looks like failure happens when reboot from deploying. I will try deploy/release cycle again and see how it goes. -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702] secondary_start_kernel+0x198/0x288 Dec 2 12:17:46 appleton-kernel kernel: [ 98.829315] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Dec 2 12:1
[Kernel-packages] [Bug 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
appleton with 5.4.0-135.152~18.04.2-generic passes 1000 reboot without any soft lockup. I will try 5.4.0-92.103~18.04.2. d05-3 with 5.4.0-135.152~18.04.2-generic passes 669 reboot without any error. ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kerne
[Kernel-packages] [Bug 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
I find 2 systems with same Mellanox NIC card and put both systems in reboot test overnight. 0005:01:00.0 Ethernet controller [0200]: Mellanox Technologies MT27710 Family [ConnectX-4 Lx] [15b3:1015] 0005:01:00.1 Ethernet controller [0200]: Mellanox Technologies MT27710 Family [ConnectX-4 Lx] [15b3:1015] -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 6
[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
So far we are not sure this is because of kernel update or stress-ng update. I am going to correct all failure information and see if there are hints within. The stress-ng we use is from ppa:hardware-certification/public and kernel is from Ubuntu archive. ** Changed in: stress-ng (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: stress-ng Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1999731] [NEW] disk stress test failing with code 7
Public bug reported: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 ** Affects: stress-ng Importance: Undecided Assignee: Ike Panhc (ikepanhc) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ike Panhc (ikepanhc) Status: In Progress ** Affects: stress-ng (Ubuntu) Importance: Undecided Assignee: Ike Panhc (ikepanhc) Status: In Progress ** Also affects: stress-ng (Ubuntu) Importance: Undecided Status: New ** Changed in: stress-ng (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Also affects: stress-ng Importance: Undecided Status: New ** Changed in: stress-ng Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
@cypressyew, I use another machine with mlx5 NIC but can not reproduce. I might need to borrow appleton for testing. -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702] secondary_start_kernel+0x198/0x288 Dec 2 12:17:46 appleton-kernel kernel: [ 98.829315] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Dec 2 12:17:46 appleton-kerne
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Tags removed: verification-needed-jammy ** Tags added: verification-donejammy ** Tags removed: verification-donejammy ** Tags added: verification-done-jammy -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler his
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This issue is already verified with -generic kernel. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq s
[Kernel-packages] [Bug 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
Tried to reproduce this issue on Ampere Altra SoC (not AltraMax) with focal grub and 5.15.0-43-generic kernel but can not reproduce. It reboot 222 times successfully. I will try to reproduce on an altramax machine. -- 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/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+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 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Changed in: kunpeng920/ubuntu-20.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
Jammy kernel 5.15.0-50.56 works for me. Thanks. ** Tags added: verification-done-jammy -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
I can not reproduce on 5.4.0-125.141-generic kernel. The only Ubuntu kernel affected is 5.15. ** Changed in: kunpeng920/ubuntu-20.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
Dig deeper with 5.4 kernels and it also support debugfs with hisi_sas but can not clean cherry-pick the mainline patch. I will try to reproduce this issue with 5.4 kernel and find out if we need to backport. -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
Patch sent. https://lists.ubuntu.com/archives/kernel- team/2022-September/132987.html -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs blake2
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
Patch hits mainline kernel since v5.16. When Kinetic kernel rolls to v5.19, this issue will be fix for 22.10. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu) Assignee: Ike Panhc (ikepanhc) => (unassigned) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.46
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Description changed: - Bug Description] - When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. + [Impact] + Trigger dump on hisi_sas in debugfs will cause kernel oops. + + [Test Plan] + 1) modprobe hisi_sas_main with "debugfs_enable=1" + 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump + 3) dmesg | grep Oops + + [Regression Risk] + Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. + + + [Bug Description] + When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core realtek hibmc_drm drm_vram_helper drm_ttm_helper ttm i2c_algo_bit drm_kms_helper syscopyarea sysfillrect crct10dif_ce hid_generi
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq
[Kernel-packages] [Bug 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Changed in: kunpeng920/ubuntu-20.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920/ubuntu-20.04 Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. It also wastes memory on arm64 systems based on other SoCs. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
Thanks. 5.15.0-32.33 works for me. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. It also wastes memory on arm64 systems based on other SoCs. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
Thanks. 5.4.0-112.126 works for me. ** 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/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. It also wastes memory on arm64 systems based on other SoCs. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
5.13.0-42.47 works for me. Thanks. ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. It also wastes memory on arm64 systems based on other SoCs. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Changed in: kunpeng920/ubuntu-20.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 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/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. It also wastes memory on arm64 systems based on other SoCs. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
Patch sent. https://lists.ubuntu.com/archives/kernel- team/2022-April/129828.html -- 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/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Also affects: kunpeng920/ubuntu-21.10 Importance: Undecided Status: New ** No longer affects: kunpeng920/ubuntu-21.10 ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Description changed: + [Impact] + We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. + + [Test Plan] + `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. + + [Regression Risk] + CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. + + = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y - [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: Ike Panhc (ikepanhc) Status: In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
** Changed in: kunpeng920/ubuntu-20.04 Status: Fix Committed => Fix Released ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1943301] Re: 【sec-0911】 fail to reset sec module
** Changed in: kunpeng920/ubuntu-20.04 Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943301 Title: 【sec-0911】 fail to reset sec module Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] The crypto accelerator in Hi1620 SoC can not be reset. [Test Plan] 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3) busybox devmem 0x200141B01018 32 0x1 4) dmesg | grep "FLR resetting" [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV(driver version): vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1943301/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Looks linux-hwe-5.4/5.4.0-107.121~18.04.1 contains security fix without patch for this issue. I will wait for testing linux-hwe-5.4/5.4.0-108 ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1943301] Re: 【sec-0911】 fail to reset sec module
Looks linux-hwe-5.4/5.4.0-107.121~18.04.1 contains security fix without patch for this issue. I will wait for testing linux-hwe-5.4/5.4.0-108 ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- 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/1943301 Title: 【sec-0911】 fail to reset sec module Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] The crypto accelerator in Hi1620 SoC can not be reset. [Test Plan] 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3) busybox devmem 0x200141B01018 32 0x1 4) dmesg | grep "FLR resetting" [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV(driver version): vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1943301/+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 1943301] Re: 【sec-0911】 fail to reset sec module
Thanks. 5.4.0-106.120 kernel works for me. ** 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/1943301 Title: 【sec-0911】 fail to reset sec module Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] The crypto accelerator in Hi1620 SoC can not be reset. [Test Plan] 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3) busybox devmem 0x200141B01018 32 0x1 4) dmesg | grep "FLR resetting" [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV(driver version): vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1943301/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Thanks, 5.4.0-106.120 kernel works for me on this issue. ** 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1943301] Re: 【sec-0911】 fail to reset sec module
** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 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/1943301 Title: 【sec-0911】 fail to reset sec module Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] The crypto accelerator in Hi1620 SoC can not be reset. [Test Plan] 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3) busybox devmem 0x200141B01018 32 0x1 4) dmesg | grep "FLR resetting" [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV(driver version): vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1943301/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Patch sent for review. https://lists.ubuntu.com/archives/kernel-team/2022-March/128419.html -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1943301] Re: 【sec-0911】 fail to reset sec module
Patch sent for review. https://lists.ubuntu.com/archives/kernel-team/2022-March/128419.html -- 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/1943301 Title: 【sec-0911】 fail to reset sec module Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: [Impact] The crypto accelerator in Hi1620 SoC can not be reset. [Test Plan] 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3) busybox devmem 0x200141B01018 32 0x1 4) dmesg | grep "FLR resetting" [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV(driver version): vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1943301/+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 1943301] Re: 【sec-0911】 fail to reset sec module
** Description changed: + [Impact] + The crypto accelerator in Hi1620 SoC can not be reset. + + [Test Plan] + 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset + 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset + 3) busybox devmem 0x200141B01018 32 0x1 + 4) dmesg | grep "FLR resetting" + + [Regression Risk] + hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. + + === + [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV(driver version): vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1943301 Title: 【sec-0911】 fail to reset sec module Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: [Impact] The crypto accelerator in Hi1620 SoC can not be reset. [Test Plan] 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3) busybox devmem 0x200141B01018 32 0x1 4) dmesg | grep "FLR resetting" [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV(driver version): vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1943301/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Working on crypto module testcase.. ** Changed in: kunpeng920/ubuntu-20.04 Status: Incomplete => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Incomplete => In Progress ** Changed in: kunpeng920 Status: Incomplete => In Progress ** Changed in: kunpeng920 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Hi Xinwei, Tested kernel debs in comment #9 and cpu and memory stress test are passed. 1302 processes in `ps aux` after cpu stress test. If the kernel debs can pass your internal test for crypto module, let me know and I will propose the patchset to kernel team. -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Hi Xinwei, I build kernel for testing on bug 1932117 and bug 1943301 with 4 patches backported. https://kernel.ubuntu.com/~ikepanhc/lp1943301.1/ d0228aeb4d65 crypto: hisilicon/sec2 - update SEC initialization and reset a13c97118749 crypto: hisilicon/sec2 - Add workqueue for SEC driver. 57ca81245f4d crypto: hisilicon - Use one workqueue per qm instead of per qp eaebf4c3b103 crypto: hisilicon - Unify hardware error init/uninit into QM Please test to see if there is any risk found. I will run full checkbox test too. -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Build the kernel with 3 patches backported, and the test looks good. https://kernel.ubuntu.com/~ikepanhc/lp1932117.2/ @Xinwei, Could you check internally if it is ok to backport these patches for Ubuntu 5.4 kernel? a13c97118749 crypto: hisilicon/sec2 - Add workqueue for SEC driver. 57ca81245f4d crypto: hisilicon - Use one workqueue per qm instead of per qp eaebf4c3b103 crypto: hisilicon - Unify hardware error init/uninit into QM ** Changed in: kunpeng920 Status: In Progress => Incomplete ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Incomplete ** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
https://lists.ubuntu.com/archives/kernel-team/2021-September/123793.html Thanks Cascardo pointing out that patch a13c97118749 ("crypto: hisilicon/sec2 - Add workqueue for SEC driver.") is also needed and in order to cherry-pick it, we need to cherry-pick eaebf4c3b103 ("crypto: hisilicon - Unify hardware error init/uninit into QM") too. I am testing patched kernel and see if any more issue shall be noted. -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
** Changed in: kunpeng920/ubuntu-20.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920/ubuntu-20.04 Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. [Test Plan] Setup soft RAID5 and wait for few seconds. Kernel will crash. [Regression Risk] CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+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 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
Thanks. 5.11.0-35.37 kernel works fine with soft RAID5 on kunpeng920. $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 57.4M 1 loop /snap/core20/1084 loop1 7:10 28.1M 1 loop /snap/snapd/12707 loop2 7:2061M 1 loop /snap/lxd/21042 loop3 7:30 28.1M 1 loop /snap/snapd/12886 loop4 7:40 65.1M 1 loop /snap/lxd/21462 sda 8:00 894.3G 0 disk ├─sda1 8:10 100G 0 part │ └─md127 9:127 0 199.9G 0 raid5 ├─sda2 8:20 100G 0 part │ └─md127 9:127 0 199.9G 0 raid5 └─sda3 8:30 100G 0 part └─md127 9:127 0 199.9G 0 raid5 sdb 8:16 0 894.3G 0 disk ├─sdb1 8:17 0 512M 0 part /boot/efi └─sdb2 8:18 0 893.8G 0 part / $ uname -a Linux segers 5.11.0-35-generic #37-Ubuntu SMP Fri Sep 3 14:00:38 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux $ sudo dmesg | grep raid | tail -3 [ 21.269566] md/raid:md127: device sda2 operational as raid disk 1 [ 21.298316] md/raid:md127: device sda1 operational as raid disk 0 [ 21.305059] md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed 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: In Progress Bug description: [Impact] Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. [Test Plan] Setup soft RAID5 and wait for few seconds. Kernel will crash. [Regression Risk] CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+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 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
Thanks. 5.4.0-85.95 kernel works fine with soft RAID5 on kunpeng920 $ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0062M 1 loop /snap/lxd/21032 loop1 7:10 48.9M 1 loop /snap/core18/2127 loop2 7:20 28.1M 1 loop /snap/snapd/12707 sda 8:00 557.9G 0 disk ├─sda18:10 512M 0 part /boot/efi └─sda28:20 557.4G 0 part / sdb 8:16 0 557.9G 0 disk ├─sdb18:17 0 100G 0 part │ └─md0 9:00 199.9G 0 raid5 ├─sdb28:18 0 100G 0 part │ └─md0 9:00 199.9G 0 raid5 └─sdb38:19 0 100G 0 part └─md0 9:00 199.9G 0 raid5 $ uname -a Linux saenger 5.4.0-85-generic #95-Ubuntu SMP Fri Sep 3 16:13:17 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux $ dmesg | tail -3 [ 531.883803] md0: detected capacity change from 0 to 214612049920 [ 531.883914] md: recovery of RAID array md0 [ 739.851754] hns3 :7d:00.0 enp125s0f0: link down ** 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/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed 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: In Progress Bug description: [Impact] Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. [Test Plan] Setup soft RAID5 and wait for few seconds. Kernel will crash. [Regression Risk] CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Patch sent. https://lists.ubuntu.com/archives/kernel- team/2021-September/123789.html -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
** Description changed: + [Impact] + hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. + + [Test Plan] + 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 + 2) ps aux | grep hisi_qm | wc -l + Expected result is less then 100 + + [Regression Risk] + hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. + + === + [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] ** Changed in: kunpeng920 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: New => In Progress ** Changed in: kunpeng920/ubuntu-20.04 Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
Patches sent. https://lists.ubuntu.com/archives/kernel- team/2021-August/123198.html -- 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/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. [Test Plan] Setup soft RAID5 and wait for few seconds. Kernel will crash. [Regression Risk] CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+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 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
** Description changed: + [Impact] + Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. + + [Test Plan] + Setup soft RAID5 and wait for few seconds. Kernel will crash. + + [Regression Risk] + CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. + + === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] -- 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/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] Setup soft RAID5 on kunpeng920 machine and system will crash because of hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with hisi_dma. [Test Plan] Setup soft RAID5 and wait for few seconds. Kernel will crash. [Regression Risk] CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+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 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: kunpeng920 Status: Incomplete => In Progress ** Changed in: kunpeng920/ubuntu-20.04-hwe Status: Incomplete => In Progress ** Changed in: kunpeng920/ubuntu-20.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-20.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920 Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1936771 Title: disable “CONFIG_HISI_DMA” config for ubuntu version Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Bug Description] disable “CONFIG_HISI_DMA” config for ubuntu version [Steps to Reproduce] 1) 2) 3) [Actual Results] this module cause some error [Expected Results] ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1936771/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Here is the kernel and the backported patch https://kernel.ubuntu.com/~ikepanhc/lp1932117/ -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04-hwe series: New Status in kunpeng920 ubuntu-20.04 series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Thanks Dann. Build the kernel and I can confirm that is the fix. Let me review it once again before sending it out. -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04-hwe series: New Status in kunpeng920 ubuntu-20.04 series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
** Changed in: kunpeng920 Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic Status in kunpeng920: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] Stack overflow in Kunpeng 920 32cores server, cause system reboot in production environment every month [Steps to Reproduce] 1)I cannot reproduce coz its a low-probability event [Actual Results] [1474521.296779] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.323300] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.349890] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.376451] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.411383] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.438042] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.455965] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.481140] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.508051] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.534519] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.561541] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.565243] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.596849] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.623516] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.659077] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.677128] Kernel panic - not syncing: corrupted stack end detected inside scheduler [1474521.685108] CPU: 7 PID: 5387 Comm: query_event Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.686201] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.689690] Unable to handle kernel paging request at virtual address 8027ce43b007 [1474521.689693] Mem abort info: [1474521.689695] ESR = 0x9605 [1474521.689698] EC = 0x25: DABT (current EL), IL = 32 bits [1474521.689700] SET = 0, FnV = 0 [1474521.689702] EA = 0, S1PTW = 0 [1474521.689703] Data abort info: [1474521.689705] ISV = 0, ISS = 0x0005 [1474521.689706] CM = 0, WnR = 0 [1474521.689710] swapper pgtable: 4k pages, 48-bit VAs, pgdp=014ac000 [1474521.689712] [8027ce43b007] pgd=2027f003, pud= [1474521.689719] Internal error: Oops: 9605 [#1] SMP [1474521.689722] Modules linked in: binfmt_misc xt_MASQUERADE iptable_nat nf_nat xt_tcpudp xt_multiport xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter rpcsec_gss_krb5 nfsv4 nfs fscache bonding nls_iso8859_1 ipmi_ssif joydev input_leds hns_roce_hw_v2 ib_uverbs ipmi_si spi_dw_mmio ipmi_devintf ipmi_msghandler spi_dw hisi_dma cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx5_ib(OE) hibmc_drm realtek drm_vram_helper ttm drm_kms_helper hid_generic crct10dif_ce syscopyarea sysfillrect ghash_ce mlx5_core(OE) sysimgblt hisi_sas_v3_hw sha2_ce hns3 hisi_sas_main sha256_arm64 fb_sys_fops mlx_compat(OE) sha1_ce hclge libsas usbhid tls drm hid hnae3 megaraid_sas ahci [1474521.689802] scsi_transport_sas mlxfw(OE) gpio_dwapb aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [1474521.689814] CPU: 14 PID: 5899 Comm: tcp_upload Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.689816] Hardware name: [About Privacy Deleted], BIOS 1.39 06/11/2020 [1474521.689819] pstate: 0049 (nzcv daif +PAN -UAO) [1474521.689831] pc : kmem_cache_alloc+0x4c/0x220 [1474521.689835] lr : kmem_cache_alloc+0x44/0x220 [1474521.689836] sp : 800010073b90 [1474521.689838] x29: 800010073b90 x28: 0001 [1474521.689841] x27: 0027b78270c0 x26: 2027cc2b [1474521.689844] x25: 05ea x24: 0040 [1474521.689847] x23: 2027d3896000 x22: 800010c11a8c [1474521.689850] x21: 0a20 x20: 0007 [1474521.689852] x19: 2027d3896000 x18: 0014 [1474521.689856] x17: ea74f425 x16: 5fe3fcbf [1474521.689859] x15: f26bfafa x14: 683f9e854da8ab18 [1474521.689862] x13: e3274a9b1fac7e1b x12: 298175ef2f49b6e3 [1474521.689864] x11: 5ac56f1f37f55ef9 x10: 0040 [1474521.689867] x9 : 000
[Kernel-packages] [Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
Hi Merlin, Thanks for the information. I will look into it. And can you provide us more information please? e.g. firmware ver, output of `lspci -vvnn`, what kind of operation you use to reproduce this issue. Thanks a lot. -- 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/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic Status in kunpeng920: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] Stack overflow in Kunpeng 920 32cores server, cause system reboot in production environment every month [Steps to Reproduce] 1)I cannot reproduce coz its a low-probability event [Actual Results] [1474521.296779] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.323300] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.349890] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.376451] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.411383] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.438042] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.455965] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.481140] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.508051] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.534519] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.561541] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.565243] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.596849] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.623516] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.659077] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.677128] Kernel panic - not syncing: corrupted stack end detected inside scheduler [1474521.685108] CPU: 7 PID: 5387 Comm: query_event Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.686201] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.689690] Unable to handle kernel paging request at virtual address 8027ce43b007 [1474521.689693] Mem abort info: [1474521.689695] ESR = 0x9605 [1474521.689698] EC = 0x25: DABT (current EL), IL = 32 bits [1474521.689700] SET = 0, FnV = 0 [1474521.689702] EA = 0, S1PTW = 0 [1474521.689703] Data abort info: [1474521.689705] ISV = 0, ISS = 0x0005 [1474521.689706] CM = 0, WnR = 0 [1474521.689710] swapper pgtable: 4k pages, 48-bit VAs, pgdp=014ac000 [1474521.689712] [8027ce43b007] pgd=2027f003, pud= [1474521.689719] Internal error: Oops: 9605 [#1] SMP [1474521.689722] Modules linked in: binfmt_misc xt_MASQUERADE iptable_nat nf_nat xt_tcpudp xt_multiport xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter rpcsec_gss_krb5 nfsv4 nfs fscache bonding nls_iso8859_1 ipmi_ssif joydev input_leds hns_roce_hw_v2 ib_uverbs ipmi_si spi_dw_mmio ipmi_devintf ipmi_msghandler spi_dw hisi_dma cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx5_ib(OE) hibmc_drm realtek drm_vram_helper ttm drm_kms_helper hid_generic crct10dif_ce syscopyarea sysfillrect ghash_ce mlx5_core(OE) sysimgblt hisi_sas_v3_hw sha2_ce hns3 hisi_sas_main sha256_arm64 fb_sys_fops mlx_compat(OE) sha1_ce hclge libsas usbhid tls drm hid hnae3 megaraid_sas ahci [1474521.689802] scsi_transport_sas mlxfw(OE) gpio_dwapb aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [1474521.689814] CPU: 14 PID: 5899 Comm: tcp_upload Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.689816] Hardware name: [About Privacy Deleted], BIOS 1.39 06/11/2020 [1474521.689819] pstate: 0049 (nzcv daif +PAN -UAO) [1474521.689831] pc : kmem_cache_alloc+0x4c/0x220 [1474521.689835] lr : kmem_cache_alloc+0x44/0x220 [1474521.689836] sp : 800010073b90 [1474521.689838] x29: 800010073b90 x28: 0001 [1474521.689841] x27: 0027b78270c0 x26: 2027cc2b [1474521.689844] x25: 05ea x24: 0040 [1474521.689847] x23: 2027d3896000 x22: 800010c11a8c [1474521.689850] x21: 0a20 x20: 0007 [1474521.689852] x19: 2027d3896000 x18: 0014 [1474521.689856] x17: ea74f425 x16: 5fe3fcbf [1474521.689859] x15: f26bfafa x14: 683f9e854da8ab18 [1474521.689862] x13: e3274a9b1fac7e1b x12: 298175ef2f49b6e3 [147
[Kernel-packages] [Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
There are many ways to corrupt stack or pointers to stack. Since this issue happens in out-of-tree mlx5 modules, it looks to me that where you shall look at. Please let us know if you can reproduce this issue without any out-of- tree module. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: kunpeng920 Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic Status in kunpeng920: Invalid Status in linux package in Ubuntu: Invalid Bug description: [Bug Description] Stack overflow in Kunpeng 920 32cores server, cause system reboot in production environment every month [Steps to Reproduce] 1)I cannot reproduce coz its a low-probability event [Actual Results] [1474521.296779] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.323300] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.349890] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.376451] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.411383] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.438042] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.455965] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.481140] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.508051] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.534519] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.561541] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.565243] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.596849] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.623516] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.659077] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.677128] Kernel panic - not syncing: corrupted stack end detected inside scheduler [1474521.685108] CPU: 7 PID: 5387 Comm: query_event Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.686201] ACPI CPPC: PCC check channel failed for ss: 0. ret=-110 [1474521.689690] Unable to handle kernel paging request at virtual address 8027ce43b007 [1474521.689693] Mem abort info: [1474521.689695] ESR = 0x9605 [1474521.689698] EC = 0x25: DABT (current EL), IL = 32 bits [1474521.689700] SET = 0, FnV = 0 [1474521.689702] EA = 0, S1PTW = 0 [1474521.689703] Data abort info: [1474521.689705] ISV = 0, ISS = 0x0005 [1474521.689706] CM = 0, WnR = 0 [1474521.689710] swapper pgtable: 4k pages, 48-bit VAs, pgdp=014ac000 [1474521.689712] [8027ce43b007] pgd=2027f003, pud= [1474521.689719] Internal error: Oops: 9605 [#1] SMP [1474521.689722] Modules linked in: binfmt_misc xt_MASQUERADE iptable_nat nf_nat xt_tcpudp xt_multiport xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter rpcsec_gss_krb5 nfsv4 nfs fscache bonding nls_iso8859_1 ipmi_ssif joydev input_leds hns_roce_hw_v2 ib_uverbs ipmi_si spi_dw_mmio ipmi_devintf ipmi_msghandler spi_dw hisi_dma cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx5_ib(OE) hibmc_drm realtek drm_vram_helper ttm drm_kms_helper hid_generic crct10dif_ce syscopyarea sysfillrect ghash_ce mlx5_core(OE) sysimgblt hisi_sas_v3_hw sha2_ce hns3 hisi_sas_main sha256_arm64 fb_sys_fops mlx_compat(OE) sha1_ce hclge libsas usbhid tls drm hid hnae3 megaraid_sas ahci [1474521.689802] scsi_transport_sas mlxfw(OE) gpio_dwapb aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [1474521.689814] CPU: 14 PID: 5899 Comm: tcp_upload Kdump: loaded Tainted: G OE 5.4.0-47-generic #51~18.04.1-Ubuntu [1474521.689816] Hardware name: [About Privacy Deleted], BIOS 1.39 06/11/2020 [1474521.689819] pstate: 0049 (nzcv daif +PAN -UAO) [1474521.689831] pc : kmem_cache_alloc+0x4c/0x220 [1474521.689835] lr : kmem_cache_alloc+0x44/0x220 [1474521.689836] sp : 800010073b90 [1474521.689838] x29: 800010073b90 x28: 0001 [1474521.689841] x27: 0027b78270c0 x26: 2027cc2b [1474521.689844] x25: 05ea x24: 0040 [1474521.689847] x23: 2027d3896000 x22: 800010c11a8c [1474521.689850] x21: 0a20 x20: 0007 [1474521.689852] x19: 2027d3896000 x18: 0014 [1474521.689856] x17: ea74f425 x16: 5fe
[Kernel-packages] [Bug 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)
Regression test on d05, kunpeng920, crb1s and crb2s all passed. Thanks. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1911376 Title: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace) Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The SSBS patch in 4.14 stable kernel, and mainline kernel adds snippet into arm64_cpufeatures but in bionic kernel, it is landed into arm64_elf_hwcaps. [Fix] Move SSBS snippet from arm64_elf_hwcaps back to arm64_features [Test] No known tool for SSB attack. Regression test only. [Regression Potential] Regression might be on all arm64 platforms. Regression test on all arm64 platform we have is recommended. = [Bug Description] ubuntu 18.04.1 fail to enable this SSBS function, this sys log will call trace as follow: [0.662089] Call trace: [0.662870] setup_elf_hwcaps+0xb8/0xd4 [0.664023] setup_cpu_features+0x60/0xf8 [0.665216] smp_cpus_done+0x34/0xa8 [0.666547] smp_init+0x120/0x138 [0.667555] kernel_init_freeable+0xf4/0x260 [0.668860] kernel_init+0x18/0x110 [0.670025] ret_from_fork+0x10/0x18 [Steps to Reproduce] 1) boot this system 2) uname -a Ubuntu 4.15.0-99.100-generic 4.15.18 [Actual Results] boot error: [0.662089] Call trace: [0.662870] setup_elf_hwcaps+0xb8/0xd4 [0.664023] setup_cpu_features+0x60/0xf8 [0.665216] smp_cpus_done+0x34/0xa8 [0.666547] smp_init+0x120/0x138 [0.667555] kernel_init_freeable+0xf4/0x260 [0.668860] kernel_init+0x18/0x110 [0.670025] ret_from_fork+0x10/0x18 [Expected Results] no error [Reproducibility] NA [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): arm64: cpufeature: Detect SSBS and advertise to userspace https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d71be2b6c0e19180b5f80a6d42039cc074a693a2 backport this following code into "static const struct arm64_cpu_capabilities arm64_elf_hwcaps[]" which will be error. 1274 #ifdef CONFIG_ARM64_SSBD 1275 { 1276 .desc = "Speculative Store Bypassing Safe (SSBS)", 1277 .capability = ARM64_SSBS, 1278 .type = ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE, 1279 .matches = has_cpuid_feature, 1280 .sys_reg = SYS_ID_AA64PFR1_EL1, 1281 .field_pos = ID_AA64PFR1_SSBS_SHIFT, 1282 .sign = FTR_UNSIGNED, 1283 .min_field_value = ID_AA64PFR1_SSBS_PSTATE_ONLY, 1284 .cpu_enable = cpu_enable_ssbs, 1285 }, [Resolution] Can you backport aboving code into "static const struct arm64_cpu_capabilities arm64_features[] = {"? To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1911376/+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 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
I can not reproduce this issue with bionic-update kernel and the patch mentioned in #6 has been merged into ubuntu-bionic since 4.15.0-125.128. I believe this issue has been fixed and am going to close this bug. Please re-open if this issue is still bothering you with bionic-update kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: kunpeng920 Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in kunpeng920: Invalid Status in linux package in Ubuntu: Invalid Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1869763/+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 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)
** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 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/1911376 Title: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace) Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The SSBS patch in 4.14 stable kernel, and mainline kernel adds snippet into arm64_cpufeatures but in bionic kernel, it is landed into arm64_elf_hwcaps. [Fix] Move SSBS snippet from arm64_elf_hwcaps back to arm64_features [Test] No known tool for SSB attack. Regression test only. [Regression Potential] Regression might be on all arm64 platforms. Regression test on all arm64 platform we have is recommended. = [Bug Description] ubuntu 18.04.1 fail to enable this SSBS function, this sys log will call trace as follow: [0.662089] Call trace: [0.662870] setup_elf_hwcaps+0xb8/0xd4 [0.664023] setup_cpu_features+0x60/0xf8 [0.665216] smp_cpus_done+0x34/0xa8 [0.666547] smp_init+0x120/0x138 [0.667555] kernel_init_freeable+0xf4/0x260 [0.668860] kernel_init+0x18/0x110 [0.670025] ret_from_fork+0x10/0x18 [Steps to Reproduce] 1) boot this system 2) uname -a Ubuntu 4.15.0-99.100-generic 4.15.18 [Actual Results] boot error: [0.662089] Call trace: [0.662870] setup_elf_hwcaps+0xb8/0xd4 [0.664023] setup_cpu_features+0x60/0xf8 [0.665216] smp_cpus_done+0x34/0xa8 [0.666547] smp_init+0x120/0x138 [0.667555] kernel_init_freeable+0xf4/0x260 [0.668860] kernel_init+0x18/0x110 [0.670025] ret_from_fork+0x10/0x18 [Expected Results] no error [Reproducibility] NA [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): arm64: cpufeature: Detect SSBS and advertise to userspace https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d71be2b6c0e19180b5f80a6d42039cc074a693a2 backport this following code into "static const struct arm64_cpu_capabilities arm64_elf_hwcaps[]" which will be error. 1274 #ifdef CONFIG_ARM64_SSBD 1275 { 1276 .desc = "Speculative Store Bypassing Safe (SSBS)", 1277 .capability = ARM64_SSBS, 1278 .type = ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE, 1279 .matches = has_cpuid_feature, 1280 .sys_reg = SYS_ID_AA64PFR1_EL1, 1281 .field_pos = ID_AA64PFR1_SSBS_SHIFT, 1282 .sign = FTR_UNSIGNED, 1283 .min_field_value = ID_AA64PFR1_SSBS_PSTATE_ONLY, 1284 .cpu_enable = cpu_enable_ssbs, 1285 }, [Resolution] Can you backport aboving code into "static const struct arm64_cpu_capabilities arm64_features[] = {"? To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1911376/+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 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
All patches hits 20.04.2 HWE kernel. ** Changed in: kunpeng920/ubuntu-20.04-hwe Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: kunpeng920/ubuntu-20.04 Status: Incomplete => Invalid ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Incomplete => Invalid ** Changed in: kunpeng920 Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Invalid Status in kunpeng920 ubuntu-20.04 series: Invalid Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+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 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash
>From description this issue happens with Ubuntu 18.04.4 LTS, 4.15.0-91-generic and can not reproduce with HWE kernel. Is there any qemu options needed to reproduce? I am going to create a KVM guest on Ubuntu 18.04 GA kernel with kunpeng920 machines and see if I can reproduce. -- 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/1869763 Title: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash Status in kunpeng920: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hardware spec: 64 core 64 G ram arm64 OS & kernel version: Ubuntu 18.04.4 LTS, 4.15.0-91-generic `virt-host-validate qemu` output: QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'memory' controller mount-point : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpu' controller mount-point : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'devices' controller mount-point : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for cgroup 'blkio' controller mount-point : PASS WARN (Unknown if this platform has IOMMU support) libvirt version: 4.0.0-1ubuntu8.14 qemu version: 1:2.11+dfsg-1ubuntu7.23arm64 guest vm kernel version: 4.15.0-64-generic aarch64 dmesg log: kvm [49132]: Unexpected L2 read permission error libvirt log: ubuntu libvirtd: 2020-03-20 03:04.474+: 42934: warning : qemuDomainObjTaint:5602 : Domain id=38 name='vm-157' uuid=3d447d79-c2a1-4351-b607-6698a2cd6c5f is tainted: host-cpu When "Unexpected L2 read permission error" this error occured, one of guest machines will become "paused" state, need to `virsh reset PAUSED_VM_NAME` to reset then start it. Those guest vm hang/crash occured very frequently, sometimes several times per hour. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1869763/+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 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)
** Description changed: + [Impact] + The SSBS patch in 4.14 stable kernel, and mainline kernel adds snippet + into arm64_cpufeatures but in bionic kernel, it is landed into arm64_elf_hwcaps. + + [Fix] + Move SSBS snippet from arm64_elf_hwcaps back to arm64_features + + [Test] + No known tool for SSB attack. Regression test only. + + [Regression Potential] + Regression might be on all arm64 platforms. Regression test on all arm64 platform we have is recommended. + + = [Bug Description] ubuntu 18.04.1 fail to enable this SSBS function, this sys log will call trace as follow: - - [0.662089] Call trace: - [0.662870] setup_elf_hwcaps+0xb8/0xd4 - [0.664023] setup_cpu_features+0x60/0xf8 - [0.665216] smp_cpus_done+0x34/0xa8 - [0.666547] smp_init+0x120/0x138 - [0.667555] kernel_init_freeable+0xf4/0x260 - [0.668860] kernel_init+0x18/0x110 - [0.670025] ret_from_fork+0x10/0x18 - + + [0.662089] Call trace: + [0.662870] setup_elf_hwcaps+0xb8/0xd4 + [0.664023] setup_cpu_features+0x60/0xf8 + [0.665216] smp_cpus_done+0x34/0xa8 + [0.666547] smp_init+0x120/0x138 + [0.667555] kernel_init_freeable+0xf4/0x260 + [0.668860] kernel_init+0x18/0x110 + [0.670025] ret_from_fork+0x10/0x18 [Steps to Reproduce] 1) boot this system 2) uname -a Ubuntu 4.15.0-99.100-generic 4.15.18 + [Actual Results] + boot error: + [0.662089] Call trace: + [0.662870] setup_elf_hwcaps+0xb8/0xd4 + [0.664023] setup_cpu_features+0x60/0xf8 + [0.665216] smp_cpus_done+0x34/0xa8 + [0.666547] smp_init+0x120/0x138 + [0.667555] kernel_init_freeable+0xf4/0x260 + [0.668860] kernel_init+0x18/0x110 + [0.670025] ret_from_fork+0x10/0x18 - [Actual Results] - boot error: - [0.662089] Call trace: - [0.662870] setup_elf_hwcaps+0xb8/0xd4 - [0.664023] setup_cpu_features+0x60/0xf8 - [0.665216] smp_cpus_done+0x34/0xa8 - [0.666547] smp_init+0x120/0x138 - [0.667555] kernel_init_freeable+0xf4/0x260 - [0.668860] kernel_init+0x18/0x110 - [0.670025] ret_from_fork+0x10/0x18 - [Expected Results] no error [Reproducibility] NA [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): arm64: cpufeature: Detect SSBS and advertise to userspace https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d71be2b6c0e19180b5f80a6d42039cc074a693a2 backport this following code into "static const struct arm64_cpu_capabilities arm64_elf_hwcaps[]" which will be error. 1274 #ifdef CONFIG_ARM64_SSBD 1275 { 1276 .desc = "Speculative Store Bypassing Safe (SSBS)", 1277 .capability = ARM64_SSBS, 1278 .type = ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE, 1279 .matches = has_cpuid_feature, 1280 .sys_reg = SYS_ID_AA64PFR1_EL1, 1281 .field_pos = ID_AA64PFR1_SSBS_SHIFT, 1282 .sign = FTR_UNSIGNED, 1283 .min_field_value = ID_AA64PFR1_SSBS_PSTATE_ONLY, 1284 .cpu_enable = cpu_enable_ssbs, 1285 }, [Resolution] Can you backport aboving code into "static const struct arm64_cpu_capabilities arm64_features[] = {"? -- 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/1911376 Title: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace) Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] The SSBS patch in 4.14 stable kernel, and mainline kernel adds snippet into arm64_cpufeatures but in bionic kernel, it is landed into arm64_elf_hwcaps. [Fix] Move SSBS snippet from arm64_elf_hwcaps back to arm64_features [Test] No known tool for SSB attack. Regression test only. [Regression Potential] Regression might be on all arm64 platforms. Regression test on all arm64 platform we have is recommended. = [Bug Description] ubuntu 18.04.1 fail to enable this SSBS function, this sys log wi
[Kernel-packages] [Bug 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)
Hi, Could you test the kernel debs here? Thanks https://kernel.ubuntu.com/~ikepanhc/lp1911376.1/ -- 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/1911376 Title: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace) Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Bug Description] ubuntu 18.04.1 fail to enable this SSBS function, this sys log will call trace as follow: [0.662089] Call trace: [0.662870] setup_elf_hwcaps+0xb8/0xd4 [0.664023] setup_cpu_features+0x60/0xf8 [0.665216] smp_cpus_done+0x34/0xa8 [0.666547] smp_init+0x120/0x138 [0.667555] kernel_init_freeable+0xf4/0x260 [0.668860] kernel_init+0x18/0x110 [0.670025] ret_from_fork+0x10/0x18 [Steps to Reproduce] 1) boot this system 2) uname -a Ubuntu 4.15.0-99.100-generic 4.15.18 [Actual Results] boot error: [0.662089] Call trace: [0.662870] setup_elf_hwcaps+0xb8/0xd4 [0.664023] setup_cpu_features+0x60/0xf8 [0.665216] smp_cpus_done+0x34/0xa8 [0.666547] smp_init+0x120/0x138 [0.667555] kernel_init_freeable+0xf4/0x260 [0.668860] kernel_init+0x18/0x110 [0.670025] ret_from_fork+0x10/0x18 [Expected Results] no error [Reproducibility] NA [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): arm64: cpufeature: Detect SSBS and advertise to userspace https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d71be2b6c0e19180b5f80a6d42039cc074a693a2 backport this following code into "static const struct arm64_cpu_capabilities arm64_elf_hwcaps[]" which will be error. 1274 #ifdef CONFIG_ARM64_SSBD 1275 { 1276 .desc = "Speculative Store Bypassing Safe (SSBS)", 1277 .capability = ARM64_SSBS, 1278 .type = ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE, 1279 .matches = has_cpuid_feature, 1280 .sys_reg = SYS_ID_AA64PFR1_EL1, 1281 .field_pos = ID_AA64PFR1_SSBS_SHIFT, 1282 .sign = FTR_UNSIGNED, 1283 .min_field_value = ID_AA64PFR1_SSBS_PSTATE_ONLY, 1284 .cpu_enable = cpu_enable_ssbs, 1285 }, [Resolution] Can you backport aboving code into "static const struct arm64_cpu_capabilities arm64_features[] = {"? To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1911376/+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 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1911376 Title: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace) Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Bug Description] ubuntu 18.04.1 fail to enable this SSBS function, this sys log will call trace as follow: [0.662089] Call trace: [0.662870] setup_elf_hwcaps+0xb8/0xd4 [0.664023] setup_cpu_features+0x60/0xf8 [0.665216] smp_cpus_done+0x34/0xa8 [0.666547] smp_init+0x120/0x138 [0.667555] kernel_init_freeable+0xf4/0x260 [0.668860] kernel_init+0x18/0x110 [0.670025] ret_from_fork+0x10/0x18 [Steps to Reproduce] 1) boot this system 2) uname -a Ubuntu 4.15.0-99.100-generic 4.15.18 [Actual Results] boot error: [0.662089] Call trace: [0.662870] setup_elf_hwcaps+0xb8/0xd4 [0.664023] setup_cpu_features+0x60/0xf8 [0.665216] smp_cpus_done+0x34/0xa8 [0.666547] smp_init+0x120/0x138 [0.667555] kernel_init_freeable+0xf4/0x260 [0.668860] kernel_init+0x18/0x110 [0.670025] ret_from_fork+0x10/0x18 [Expected Results] no error [Reproducibility] NA [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): arm64: cpufeature: Detect SSBS and advertise to userspace https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d71be2b6c0e19180b5f80a6d42039cc074a693a2 backport this following code into "static const struct arm64_cpu_capabilities arm64_elf_hwcaps[]" which will be error. 1274 #ifdef CONFIG_ARM64_SSBD 1275 { 1276 .desc = "Speculative Store Bypassing Safe (SSBS)", 1277 .capability = ARM64_SSBS, 1278 .type = ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE, 1279 .matches = has_cpuid_feature, 1280 .sys_reg = SYS_ID_AA64PFR1_EL1, 1281 .field_pos = ID_AA64PFR1_SSBS_SHIFT, 1282 .sign = FTR_UNSIGNED, 1283 .min_field_value = ID_AA64PFR1_SSBS_PSTATE_ONLY, 1284 .cpu_enable = cpu_enable_ssbs, 1285 }, [Resolution] Can you backport aboving code into "static const struct arm64_cpu_capabilities arm64_features[] = {"? To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1911376/+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 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process
** Changed in: kunpeng920/ubuntu-18.04 Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893711 Title: [hns3-0901]add hns3_gro_complete for HW GRO process Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] kernel oops on hns3 driver when GRO is enabled. [Fix] Cherry-pick patches from upstream d474d88f8826 net: hns3: add hns3_gro_complete for HW GRO process a4d2cdcbb878 net: hns3: minor refactor for hns3_rx_checksum [Test] No known way to reproduce it in our lab. Regression test only. [Regression Potential] Patchset only affects hns3 driver. Minimal risk for other drivers and platform. Stress test on hns3 driver looks good and we also have positive feedback from different lab. Patches also in Ubuntu kernel since Eoan and no regression observed. [Bug Description] When a GRO packet is received by driver, the cwr field in the struct tcphdr needs to be checked to decide whether to set the SKB_GSO_TCP_ECN for skb_shinfo(skb)->gso_type. [Steps to Reproduce] 1.load PF driver 2.turn off GRO of stack, turn on HW GRO [Actual Results] [ 32.597752] bond-dcn: link status definitely up for interface enp189s0f0, 1 Mbps full duplex [1048422.589438] Unable to handle kernel paging request at virtual address 80605d0c [1048422.597506] Mem abort info: [1048422.600463] ESR = 0x9605 [1048422.603679] Exception class = DABT (current EL), IL = 32 bits [1048422.609747] SET = 0, FnV = 0 [1048422.612963] EA = 0, S1PTW = 0 [1048422.616265] Data abort info: [1048422.619309] ISV = 0, ISS = 0x0005 [1048422.623301] CM = 0, WnR = 0 [1048422.626431] swapper pgtable: 4k pages, 48-bit VAs, pgd = 96615bf4 [1048422.633360] [80605d0c] *pgd=205f6003, *pud= [1048422.640465] Internal error: Oops: 9605 [#1] SMP [1048422.645496] Modules linked in: bonding zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) joydev input_leds ipmi_ssif ipmi_si ipmi_devintf shpchp ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure hibmc_drm aes_ce_blk aes_ce_cipher ttm realtek crc32_ce drm_kms_helper crct10dif_ce syscopyarea ghash_ce hisi_sas_v3_hw sysfillrect sha2_ce sysimgblt hns3 nvme hisi_sas_main sha256_arm64 fb_sys_fops sha1_ce drm hclge libsas nvme_core ahci megaraid_sas hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic [1048422.715911] usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [1048422.723192] Process swapper/22 (pid: 0, stack limit = 0xdc9798e5) [1048422.730122] CPU: 22 PID: 0 Comm: swapper/22 Tainted: P O 4.15.0-96-generic #97-Ubuntu [1048422.739297] Hardware name: Huawei TaiShan 200 (Model 2280)/BC82AMDDA, BIOS 1.35 04/30/2020 [1048422.747695] pstate: 8049 (Nzcv daif +PAN -UAO) [1048422.752641] pc : tcp_gro_complete+0x4c/0x80 [1048422.756988] lr : hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.762274] sp : 09893d00 [1048422.765746] x29: 09893d00 x28: a05de384d900 [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280 [1048422.776668] x25: 0040 x24: a05dc7a4e000 [1048422.782130] x23: 0002 x22: [1048422.787590] x21: x20: [1048422.793051] x19: a05de384d900 x18: a3bf2a70 [1048422.798512] x17: a3b68698 x16: 08307aa0 [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08 [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971 [1048422.825820] x7 : 1502726647903506 x6 : 0002 [1048422.831281] x5 : a05dc7ad0480 x4 : 0002 [1048422.836743] x3 : 805f5d00 x2 : 0060 [1048422.842203] x1 : 805f5f00 x0 : 80605cff [1048422.847665] Call trace: [1048422.850276] tcp_gro_complete+0x4c/0x80 [1048422.854274] hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.859217] hns3_nic_common_poll+0x98
[Kernel-packages] [Bug 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process
Thanks. 4.15.0-125.128 works for me. ** Tags removed: ikeradar verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1893711 Title: [hns3-0901]add hns3_gro_complete for HW GRO process Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] kernel oops on hns3 driver when GRO is enabled. [Fix] Cherry-pick patches from upstream d474d88f8826 net: hns3: add hns3_gro_complete for HW GRO process a4d2cdcbb878 net: hns3: minor refactor for hns3_rx_checksum [Test] No known way to reproduce it in our lab. Regression test only. [Regression Potential] Patchset only affects hns3 driver. Minimal risk for other drivers and platform. Stress test on hns3 driver looks good and we also have positive feedback from different lab. Patches also in Ubuntu kernel since Eoan and no regression observed. [Bug Description] When a GRO packet is received by driver, the cwr field in the struct tcphdr needs to be checked to decide whether to set the SKB_GSO_TCP_ECN for skb_shinfo(skb)->gso_type. [Steps to Reproduce] 1.load PF driver 2.turn off GRO of stack, turn on HW GRO [Actual Results] [ 32.597752] bond-dcn: link status definitely up for interface enp189s0f0, 1 Mbps full duplex [1048422.589438] Unable to handle kernel paging request at virtual address 80605d0c [1048422.597506] Mem abort info: [1048422.600463] ESR = 0x9605 [1048422.603679] Exception class = DABT (current EL), IL = 32 bits [1048422.609747] SET = 0, FnV = 0 [1048422.612963] EA = 0, S1PTW = 0 [1048422.616265] Data abort info: [1048422.619309] ISV = 0, ISS = 0x0005 [1048422.623301] CM = 0, WnR = 0 [1048422.626431] swapper pgtable: 4k pages, 48-bit VAs, pgd = 96615bf4 [1048422.633360] [80605d0c] *pgd=205f6003, *pud= [1048422.640465] Internal error: Oops: 9605 [#1] SMP [1048422.645496] Modules linked in: bonding zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) joydev input_leds ipmi_ssif ipmi_si ipmi_devintf shpchp ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure hibmc_drm aes_ce_blk aes_ce_cipher ttm realtek crc32_ce drm_kms_helper crct10dif_ce syscopyarea ghash_ce hisi_sas_v3_hw sysfillrect sha2_ce sysimgblt hns3 nvme hisi_sas_main sha256_arm64 fb_sys_fops sha1_ce drm hclge libsas nvme_core ahci megaraid_sas hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic [1048422.715911] usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [1048422.723192] Process swapper/22 (pid: 0, stack limit = 0xdc9798e5) [1048422.730122] CPU: 22 PID: 0 Comm: swapper/22 Tainted: P O 4.15.0-96-generic #97-Ubuntu [1048422.739297] Hardware name: Huawei TaiShan 200 (Model 2280)/BC82AMDDA, BIOS 1.35 04/30/2020 [1048422.747695] pstate: 8049 (Nzcv daif +PAN -UAO) [1048422.752641] pc : tcp_gro_complete+0x4c/0x80 [1048422.756988] lr : hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.762274] sp : 09893d00 [1048422.765746] x29: 09893d00 x28: a05de384d900 [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280 [1048422.776668] x25: 0040 x24: a05dc7a4e000 [1048422.782130] x23: 0002 x22: [1048422.787590] x21: x20: [1048422.793051] x19: a05de384d900 x18: a3bf2a70 [1048422.798512] x17: a3b68698 x16: 08307aa0 [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08 [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971 [1048422.825820] x7 : 1502726647903506 x6 : 0002 [1048422.831281] x5 : a05dc7ad0480 x4 : 0002 [1048422.836743] x3 : 805f5d00 x2 : 0060 [1048422.842203] x1 : 805f5f00 x0 : 80605cff [1048422.847665] Call trace: [1048422.850276] tcp_gro_complete+0x4c/0x80 [1048422.854274] hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.859217] hns3_nic_common_poll+0x98/0x220 [hns3] [10484
[Kernel-packages] [Bug 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process
Patches sent. https://lists.ubuntu.com/archives/kernel-team/2020-October/113962.html -- 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/1893711 Title: [hns3-0901]add hns3_gro_complete for HW GRO process Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] kernel oops on hns3 driver when GRO is enabled. [Fix] Cherry-pick patches from upstream d474d88f8826 net: hns3: add hns3_gro_complete for HW GRO process a4d2cdcbb878 net: hns3: minor refactor for hns3_rx_checksum [Test] No known way to reproduce it in our lab. Regression test only. [Regression Potential] Patchset only affects hns3 driver. Minimal risk for other drivers and platform. Stress test on hns3 driver looks good and we also have positive feedback from different lab. Patches also in Ubuntu kernel since Eoan and no regression observed. [Bug Description] When a GRO packet is received by driver, the cwr field in the struct tcphdr needs to be checked to decide whether to set the SKB_GSO_TCP_ECN for skb_shinfo(skb)->gso_type. [Steps to Reproduce] 1.load PF driver 2.turn off GRO of stack, turn on HW GRO [Actual Results] [ 32.597752] bond-dcn: link status definitely up for interface enp189s0f0, 1 Mbps full duplex [1048422.589438] Unable to handle kernel paging request at virtual address 80605d0c [1048422.597506] Mem abort info: [1048422.600463] ESR = 0x9605 [1048422.603679] Exception class = DABT (current EL), IL = 32 bits [1048422.609747] SET = 0, FnV = 0 [1048422.612963] EA = 0, S1PTW = 0 [1048422.616265] Data abort info: [1048422.619309] ISV = 0, ISS = 0x0005 [1048422.623301] CM = 0, WnR = 0 [1048422.626431] swapper pgtable: 4k pages, 48-bit VAs, pgd = 96615bf4 [1048422.633360] [80605d0c] *pgd=205f6003, *pud= [1048422.640465] Internal error: Oops: 9605 [#1] SMP [1048422.645496] Modules linked in: bonding zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) joydev input_leds ipmi_ssif ipmi_si ipmi_devintf shpchp ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure hibmc_drm aes_ce_blk aes_ce_cipher ttm realtek crc32_ce drm_kms_helper crct10dif_ce syscopyarea ghash_ce hisi_sas_v3_hw sysfillrect sha2_ce sysimgblt hns3 nvme hisi_sas_main sha256_arm64 fb_sys_fops sha1_ce drm hclge libsas nvme_core ahci megaraid_sas hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic [1048422.715911] usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [1048422.723192] Process swapper/22 (pid: 0, stack limit = 0xdc9798e5) [1048422.730122] CPU: 22 PID: 0 Comm: swapper/22 Tainted: P O 4.15.0-96-generic #97-Ubuntu [1048422.739297] Hardware name: Huawei TaiShan 200 (Model 2280)/BC82AMDDA, BIOS 1.35 04/30/2020 [1048422.747695] pstate: 8049 (Nzcv daif +PAN -UAO) [1048422.752641] pc : tcp_gro_complete+0x4c/0x80 [1048422.756988] lr : hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.762274] sp : 09893d00 [1048422.765746] x29: 09893d00 x28: a05de384d900 [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280 [1048422.776668] x25: 0040 x24: a05dc7a4e000 [1048422.782130] x23: 0002 x22: [1048422.787590] x21: x20: [1048422.793051] x19: a05de384d900 x18: a3bf2a70 [1048422.798512] x17: a3b68698 x16: 08307aa0 [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08 [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971 [1048422.825820] x7 : 1502726647903506 x6 : 0002 [1048422.831281] x5 : a05dc7ad0480 x4 : 0002 [1048422.836743] x3 : 805f5d00 x2 : 0060 [1048422.842203] x1 : 805f5f00 x0 : 80605cff [1048422.847665] Call trace: [1048422.850276] tcp_gro_complete+0x4c/0x80 [1048422.854274] hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.859217] hns3_nic_common_poll+0x98/0x220 [hns3] [1048422.864247] net_rx_action+0x160/0x3d8 [1048422.86
[Kernel-packages] [Bug 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process
** Description changed: + [Impact] + kernel oops on hns3 driver when GRO is enabled. + + [Fix] + Cherry-pick patches from upstream + d474d88f8826 net: hns3: add hns3_gro_complete for HW GRO process + a4d2cdcbb878 net: hns3: minor refactor for hns3_rx_checksum + + [Test] + No known way to reproduce it in our lab. Regression test only. + + [Regression Potential] + Patchset only affects hns3 driver. Minimal risk for other drivers and platform. + Stress test on hns3 driver looks good and we also have positive + feedback from different lab. + Patches also in Ubuntu kernel since Eoan and no regression observed. + + [Bug Description] When a GRO packet is received by driver, the cwr field in the struct tcphdr needs to be checked to decide whether to set the SKB_GSO_TCP_ECN for skb_shinfo(skb)->gso_type. [Steps to Reproduce] 1.load PF driver 2.turn off GRO of stack, turn on HW GRO [Actual Results] [ 32.597752] bond-dcn: link status definitely up for interface enp189s0f0, 1 Mbps full duplex [1048422.589438] Unable to handle kernel paging request at virtual address 80605d0c [1048422.597506] Mem abort info: [1048422.600463] ESR = 0x9605 [1048422.603679] Exception class = DABT (current EL), IL = 32 bits [1048422.609747] SET = 0, FnV = 0 [1048422.612963] EA = 0, S1PTW = 0 [1048422.616265] Data abort info: [1048422.619309] ISV = 0, ISS = 0x0005 [1048422.623301] CM = 0, WnR = 0 [1048422.626431] swapper pgtable: 4k pages, 48-bit VAs, pgd = 96615bf4 [1048422.633360] [80605d0c] *pgd=205f6003, *pud= [1048422.640465] Internal error: Oops: 9605 [#1] SMP [1048422.645496] Modules linked in: bonding zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) joydev input_leds ipmi_ssif ipmi_si ipmi_devintf shpchp ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure hibmc_drm aes_ce_blk aes_ce_cipher ttm realtek crc32_ce drm_kms_helper crct10dif_ce syscopyarea ghash_ce hisi_sas_v3_hw sysfillrect sha2_ce sysimgblt hns3 nvme hisi_sas_main sha256_arm64 fb_sys_fops sha1_ce drm hclge libsas nvme_core ahci megaraid_sas hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic [1048422.715911] usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [1048422.723192] Process swapper/22 (pid: 0, stack limit = 0xdc9798e5) [1048422.730122] CPU: 22 PID: 0 Comm: swapper/22 Tainted: P O 4.15.0-96-generic #97-Ubuntu [1048422.739297] Hardware name: Huawei TaiShan 200 (Model 2280)/BC82AMDDA, BIOS 1.35 04/30/2020 [1048422.747695] pstate: 8049 (Nzcv daif +PAN -UAO) [1048422.752641] pc : tcp_gro_complete+0x4c/0x80 [1048422.756988] lr : hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.762274] sp : 09893d00 - [1048422.765746] x29: 09893d00 x28: a05de384d900 - [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280 - [1048422.776668] x25: 0040 x24: a05dc7a4e000 - [1048422.782130] x23: 0002 x22: - [1048422.787590] x21: x20: - [1048422.793051] x19: a05de384d900 x18: a3bf2a70 - [1048422.798512] x17: a3b68698 x16: 08307aa0 - [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08 - [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd - [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d - [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971 - [1048422.825820] x7 : 1502726647903506 x6 : 0002 - [1048422.831281] x5 : a05dc7ad0480 x4 : 0002 - [1048422.836743] x3 : 805f5d00 x2 : 0060 - [1048422.842203] x1 : 805f5f00 x0 : 80605cff + [1048422.765746] x29: 09893d00 x28: a05de384d900 + [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280 + [1048422.776668] x25: 0040 x24: a05dc7a4e000 + [1048422.782130] x23: 0002 x22: + [1048422.787590] x21: x20: + [1048422.793051] x19: a05de384d900 x18: a3bf2a70 + [1048422.798512] x17: a3b68698 x16: 08307aa0 + [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08 + [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd + [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d + [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971 + [1048422.825820] x7 : 1502726647903506 x6 : 0002 + [1048422.831281] x5 : a05dc7ad0480 x4 : 0002 + [1048422.836743] x3 : 805f5d00 x2 : 0060 + [1048422.842203] x1 :
[Kernel-packages] [Bug 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893711 Title: [hns3-0901]add hns3_gro_complete for HW GRO process Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Bug Description] When a GRO packet is received by driver, the cwr field in the struct tcphdr needs to be checked to decide whether to set the SKB_GSO_TCP_ECN for skb_shinfo(skb)->gso_type. [Steps to Reproduce] 1.load PF driver 2.turn off GRO of stack, turn on HW GRO [Actual Results] [ 32.597752] bond-dcn: link status definitely up for interface enp189s0f0, 1 Mbps full duplex [1048422.589438] Unable to handle kernel paging request at virtual address 80605d0c [1048422.597506] Mem abort info: [1048422.600463] ESR = 0x9605 [1048422.603679] Exception class = DABT (current EL), IL = 32 bits [1048422.609747] SET = 0, FnV = 0 [1048422.612963] EA = 0, S1PTW = 0 [1048422.616265] Data abort info: [1048422.619309] ISV = 0, ISS = 0x0005 [1048422.623301] CM = 0, WnR = 0 [1048422.626431] swapper pgtable: 4k pages, 48-bit VAs, pgd = 96615bf4 [1048422.633360] [80605d0c] *pgd=205f6003, *pud= [1048422.640465] Internal error: Oops: 9605 [#1] SMP [1048422.645496] Modules linked in: bonding zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) joydev input_leds ipmi_ssif ipmi_si ipmi_devintf shpchp ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure hibmc_drm aes_ce_blk aes_ce_cipher ttm realtek crc32_ce drm_kms_helper crct10dif_ce syscopyarea ghash_ce hisi_sas_v3_hw sysfillrect sha2_ce sysimgblt hns3 nvme hisi_sas_main sha256_arm64 fb_sys_fops sha1_ce drm hclge libsas nvme_core ahci megaraid_sas hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic [1048422.715911] usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [1048422.723192] Process swapper/22 (pid: 0, stack limit = 0xdc9798e5) [1048422.730122] CPU: 22 PID: 0 Comm: swapper/22 Tainted: P O 4.15.0-96-generic #97-Ubuntu [1048422.739297] Hardware name: Huawei TaiShan 200 (Model 2280)/BC82AMDDA, BIOS 1.35 04/30/2020 [1048422.747695] pstate: 8049 (Nzcv daif +PAN -UAO) [1048422.752641] pc : tcp_gro_complete+0x4c/0x80 [1048422.756988] lr : hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.762274] sp : 09893d00 [1048422.765746] x29: 09893d00 x28: a05de384d900 [1048422.771207] x27: a05dc660c6c0 x26: a05dc7a6c280 [1048422.776668] x25: 0040 x24: a05dc7a4e000 [1048422.782130] x23: 0002 x22: [1048422.787590] x21: x20: [1048422.793051] x19: a05de384d900 x18: a3bf2a70 [1048422.798512] x17: a3b68698 x16: 08307aa0 [1048422.803973] x15: 0d920112ac4e x14: 0c96b6405c2a0a08 [1048422.809435] x13: 01011cc0f601 x12: 188058b201fc85fd [1048422.814896] x11: cd979f72c04ce5db x10: 2087e1db2087679d [1048422.820358] x9 : 0640004090cff807 x8 : 00450008f034d971 [1048422.825820] x7 : 1502726647903506 x6 : 0002 [1048422.831281] x5 : a05dc7ad0480 x4 : 0002 [1048422.836743] x3 : 805f5d00 x2 : 0060 [1048422.842203] x1 : 805f5f00 x0 : 80605cff [1048422.847665] Call trace: [1048422.850276] tcp_gro_complete+0x4c/0x80 [1048422.854274] hns3_clean_rx_ring+0x63c/0x6f0 [hns3] [1048422.859217] hns3_nic_common_poll+0x98/0x220 [hns3] [1048422.864247] net_rx_action+0x160/0x3d8 [1048422.868153] __do_softirq+0x134/0x330 [1048422.871973] irq_exit+0xcc/0xe0 [1048422.875275] __handle_domain_irq+0x6c/0xc0 [1048422.879526] gic_handle_irq+0x84/0x180 [1048422.883431] el1_irq+0xe8/0x180
[Kernel-packages] [Bug 1890222] Re: Enlarge hisi_sec2 capability
** Changed in: kunpeng920/ubuntu-20.04 Status: Fix Committed => Fix Released ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890222 Title: Enlarge hisi_sec2 capability Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] Current hisi_sec2 driver only allows 2 threads for accelerator but cpu stress test requires more then 50 threads. We have disabled hisi_sec2 temporarily for 20.04.1. Hisilicon proposes a simple patch on upstream mailing list to enlarge the capability. [Fix] commit 57b1aac1b426b7255afa195298ed691ffea204c6 Author: Longfang Liu Date: Mon Jun 8 22:01:11 2020 +0800 Subject: crypto: hisilicon - update SEC driver module parameter [Test] $ lsmod | grep hisi_sec2 # make sure hisi_sec2 loaded $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1890222/+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 1892347] Re: HiSilicon HNS3 ethernet broken
*** This bug is a duplicate of bug 1859756 *** https://bugs.launchpad.net/bugs/1859756 Thanks Torel, 4.15.0-114.115 will be released to -update on August 31th according to kernel SRU schedule[1]. All you need to do is `sudo apt update;sudo apt upgrade` and you can use 4.15 kernel with fix. Set this bug as duplicate of bug 1859756 [1] https://kernel.ubuntu.com/ ** This bug has been marked a duplicate of bug 1859756 [hns3-0115] add 8 BD limit for tx flow -- 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/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04 series: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Hi Torel, No. please get the kernel debs from Ubuntu archive. Here are the steps 1) sudo apt-add-repository "deb http://ports.ubuntu.com/ubuntu-ports bionic-proposed main" 2) sudo apt update 3) sudo apt dist-upgrade Let me know if you need to manual install kernel debs and I can put those debs somewhere you can download. -- 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/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04 series: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
Hi torel, As mentioned in #16, this issue might be solved in -proposed kernel. Would you might test again with bionic-proposed kernel? Please use follow command to enable -proposed pocket for your Ubuntu system $ sudo apt-add-repository "deb http://ports.ubuntu.com/ubuntu-ports bionic-proposed main" $ sudo apt update $ sudo apt dist-upgrade and then reboot for -proposed kernel. -- 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/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04 series: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :
[Kernel-packages] [Bug 1892347] Re: HiSilicon HNS3 ethernet broken
** Also affects: kunpeng920/ubuntu-18.04 Importance: Undecided Status: New ** Changed in: kunpeng920/ubuntu-18.04 Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892347 Title: HiSilicon HNS3 ethernet broken Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04 series: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The TM210 (verified) and TM280 (probably) driver hns3 is broken in Ubuntu 18.04.5 LTS kernel 4.15.0-112-generic. Server Huawei TM200-2280 with Kunpeng920 SOCs. Huawei provides binary distributed driver NIC-hisi_eth-Ubuntu18.04.1-hns3-1.0.2-aarch64.deb but it is only for kernel 4.15.0-29-generic. root@n012:~# uname -ar Linux n012 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:42:54 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux root@n012:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic root@n012:~# dmesg |grep hns3 [3.775711] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [3.789796] hns3: Copyright (c) 2017 Huawei Corporation. [4.295868] hns3 :7d:00.0: The firmware version is 01092806 [4.395325] hns3 :7d:00.0 eth0: No phy led trigger registered for speed(-1) [4.498584] hns3 :7d:00.1: The firmware version is 01092806 [4.634770] hns3 :7d:00.1 eth1: No phy led trigger registered for speed(-1) [4.671546] hns3 :7d:00.2: The firmware version is 01092806 [4.791311] hns3 :7d:00.2 eth2: No phy led trigger registered for speed(-1) [4.813538] hns3 :7d:00.3: The firmware version is 01092806 [4.915305] hns3 :7d:00.3 eth3: No phy led trigger registered for speed(-1) [4.937256] hns3 :bd:00.0: The firmware version is 01092806 [4.994060] hns3 :bd:00.1: The firmware version is 01092806 [5.049951] hns3 :bd:00.2: The firmware version is 01092806 [5.107165] hns3 :bd:00.3: The firmware version is 01092806 [5.159285] hns3 :7d:00.0 enp125s0f0: renamed from eth0 [5.379348] hns3 :bd:00.2 enp189s0f2: renamed from eth6 [5.435880] hns3 :bd:00.1 enp189s0f1: renamed from eth5 [5.903915] hns3 :7d:00.3 enp125s0f3: renamed from eth3 [5.999350] hns3 :7d:00.1 enp125s0f1: renamed from eth1 [6.155353] hns3 :7d:00.2 enp125s0f2: renamed from eth2 [6.295332] hns3 :bd:00.0 enp189s0f0: renamed from eth4 [6.443835] hns3 :bd:00.3 enp189s0f3: renamed from eth7 [ 18.031167] hns3 :7d:00.0 enp125s0f0: link up [77661.965968] beegfs: enabling unsafe global rkey [7.642438] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.642466] hns3 :7d:00.0: PF Reset requested [7.642491] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.650298] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.650315] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.654571] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.654588] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.658807] hns3 :7d:00.0: inform reset to vf(3) failed -5! [7.689650] hns3 :7d:00.0 enp125s0f0: link down [7.797516] hns3 :7d:00.0: prepare wait ok [7.908488] hns3 :7d:00.0: The firmware version is 01092806 [7.915807] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [7.945923] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [7.945976] hns3 :7d:00.0: PF Reset requested [7.946065] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.950200] hns3 :7d:00.0: inform reset to vf(1) failed -5! [7.950218] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.954274] hns3 :7d:00.0: inform reset to vf(2) failed -5! [7.954292] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [7.958067] hns3 :7d:00.0: inform reset to vf(3) failed -5! [8.093493] hns3 :7d:00.0: prepare wait ok [8.203854] hns3 :7d:00.0: The firmware version is 01092806 [8.210947] hns3 :7d:00.0: Reset done, hclge driver initialization finished. [80001.269514] hns3 :7d:00.0 enp125s0f0: link up [80001.269832] hns3 :7d:00.0: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1] [80001.269858] hns3 :7d:00.0: PF Reset requested [80001.269881] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.273380] hns3 :7d:00.0: inform reset to vf(1) failed -5! [80001.273401] hns3 :7d:00.0: PF failed(=-5) to send mailbox message to VF [80001.276876] hns3 00
[Kernel-packages] [Bug 1861972] Re: [hns3-0205]sync mainline kernel 5.5rc7 hns3 patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861972 Title: [hns3-0205]sync mainline kernel 5.5rc7 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] hns3 patchset have merged into mainline 5.4rc7 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] (Fix committed) net: hns3: cleanup some coding style issue (Fix committed) net: hns3: remove redundant print on ENOMEM (Fix committed) net: hns3: delete unnecessary blank line and space for cleanup (Fix committed) net: hns3: rewrite a log in hclge_put_vector() (Fix committed) net: hns3: refine the input parameter 'size' for snprintf() (Fix committed) net: hns3: move duplicated macro definition into header (Fix committed) net: hns3: set VF's default reset_type to HNAE3_NONE_RESET (Fix committed) net: hns3: do not reuse pfmemalloc pages (Fix committed) net: hns3: limit the error logging in the hns3_clean_tx_ring() (Fix committed) net: hns3: replace snprintf with scnprintf in hns3_update_strings (Fix committed) net: hns3: replace snprintf with scnprintf in hns3_dbg_cmd_read (Fix committed) net: hns3: pad the short frame before sending to the hardware To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861972/+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 1864442] Re: dmaengine: hisilicon: Add Kunpeng DMA engine support
** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864442 Title: dmaengine: hisilicon: Add Kunpeng DMA engine support Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] This patch adds a driver for HiSilicon Kunpeng DMA engine. This DMA engine which is an PCIe iEP offers 30 channels, each channel has a send queue, a complete queue and an interrupt to help to do tasks. This DMA engine can do memory copy between memory blocks or between memory and device buffer [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] e9f08b65250d dmaengine: hisilicon: Add Kunpeng DMA engine support https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/dma?h=v5.6-rc1&id=e9f08b65250d73ab70e79e194813f52b8d306784 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1864442/+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 1864950] Re: [roce-0227]sync mainline kernel 5.6rc3 roce patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864950 Title: [roce-0227]sync mainline kernel 5.6rc3 roce patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] RDMA/hns: Optimize eqe buffer allocation flow RDMA/hns: Cleanups of magic numbers RDMA/hns: fix spelling mistake: "attatch" -> "attach" RDMA/hns: Delayed flush cqe process with workqueue RDMA/hns: Add the workqueue framework for flush cqe handler RDMA/hns: Initialize all fields of doorbells to zero RDMA/hns: Optimize qp doorbell allocation flow RDMA/hns: Optimize kernel qp wrid allocation flow RDMA/hns: Optimize qp param setup flow RDMA/hns: Optimize qp buffer allocation flow RDMA/hns: Optimize qp number assign flow RDMA/hns: Optimize qp context create and destroy flow RDMA/hns: Optimize qp destroy flow RDMA/hns: Stop doorbell update while qp state error RDMA/hns: Use flush framework for the case in aeq RDMA/hns: Treat revision HIP08_A as a special case https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=wip /jgg-for-next RDMA/hns: Treat revision HIP08_A as a special case https://www.spinics.net/lists/linux-rdma/msg89428.html RDMA/hns: Support to set mininum depth of qp to 0 https://patchwork.kernel.org/patch/11415067/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1864950/+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 1861976] Re: [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861976 Title: [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] acc patchset have merged into mainline 5.5rc6 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon - fix spelling mistake "disgest" -> "digest" crypto: hisilicon - add branch prediction macro crypto: hisilicon - adjust hpre_crt_para_get crypto: hisilicon - Fixed some tiny bugs of HPRE crypto: hisilicon - Bugfixed tfm leak crypto: hisilicon - Add aead support on SEC2 crypto: hisilicon - redefine skcipher initiation crypto: hisilicon - Add branch prediction macro crypto: hisilicon - Add callback error check crypto: hisilicon - Adjust some inner logic crypto: hisilicon - Update QP resources of SEC V2 crypto: hisilicon - Update some names on SEC V2 crypto: hisilicon - fix print/comment of SEC V2 crypto: hisilicon - Update debugfs usage of SEC V2 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861976/+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 1863575] Re: [hns3-0217]sync mainline kernel 5.6rc1 hns3 patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863575 Title: [hns3-0217]sync mainline kernel 5.6rc1 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] hns3 patchset have merged into mainline 5.6rc1 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: fix a copying IPv6 address error in hclge_fd_get_flow_tuples() net: hns3: fix VF bandwidth does not take effect in some case net: hns3: add management table after IMP reset [Status] (Fix committed) 47327c9315b2 net: hns3: fix a copying IPv6 address error in hclge_fd_get_flow_tuples() (Fix committed) 19eb1123b4e9 net: hns3: fix VF bandwidth does not take effect in some case (Fix committed) d0db7ed39751 net: hns3: add management table after IMP reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1863575/+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 1867586] Re: [hns3-0316]sync mainline kernel 5.6rc4 hns3 patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867586 Title: [hns3-0316]sync mainline kernel 5.6rc4 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] hns3 patchset have merged into mainline 5.6rc1 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: clear port base VLAN when unload PF net: hns3: fix RMW issue for VLAN filter switch net: hns3: fix VF VLAN table entries inconsistent issue net: hns3: fix "tc qdisc del" failed issue net: hns3: reject unsupported coalescing params net: hns3: delete unnecessary logs after kzalloc fails net: hns3: synchronize some print relating to reset issue net: hns3: print out command code when dump fails in debugfs net: hns3: print out status register when VF receives unknown source interrupt net: hns3: add a check before PF inform VF to reset net: hns3: delete some reduandant code net: hns3: remove an unnecessary resetting check in hclge_handle_hw_ras_error() net: hns3: rename macro HCLGE_MAX_NCL_CONFIG_LENGTH net: hns3: fix some mixed type assignment net: hns3: fix a not link up issue when fibre port supports autoneg net: hns3: add missing help info for QS shaper in debugfs net: hns3: add support for dump MAC ID and loopback status in debugfs net: hns3: add enabled TC numbers and DWRR weight info in debugfs net: hns3: modify an unsuitable print when setting unknown duplex to fibre [Status] (Rejected) net: hns3: reject unsupported coalescing params (Fix committed) net: hns3: delete unnecessary logs after kzalloc fails (Fix committed) net: hns3: synchronize some print relating to reset issue (Fix committed) net: hns3: print out command code when dump fails in debugfs (Fix committed) net: hns3: print out status register when VF receives unknown source interrupt (Fix committed) net: hns3: add a check before PF inform VF to reset (Fix committed) net: hns3: delete some reduandant code (Fix committed) net: hns3: remove an unnecessary resetting check in hclge_handle_hw_ras_error() (Fix committed) net: hns3: rename macro HCLGE_MAX_NCL_CONFIG_LENGTH (Fix committed) net: hns3: fix some mixed type assignment (Fix committed) net: hns3: add missing help info for QS shaper in debugfs (Fix committed) net: hns3: add support for dump MAC ID and loopback status in debugfs (Fix committed) net: hns3: add enabled TC numbers and DWRR weight info in debugfs (Fix committed) net: hns3: modify an unsuitable print when setting unknown duplex to fibre (Fix committed) net: hns3: clear port base VLAN when unload PF (Fix committed) net: hns3: fix RMW issue for VLAN filter switch (Fix committed) net: hns3: fix VF VLAN table entries inconsistent issue (Fix committed) net: hns3: fix "tc qdisc del" failed issue (Fix committed) net: hns3: fix a not link up issue when fibre port supports autoneg To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867586/+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 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+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