[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64)
** Changed in: ubuntu-kernel-tests Status: Confirmed => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1836694 Title: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64)
Note that with LTP test suite update this test is not causing failure to cgroup_fj_* anymore. Now it's only failing on GCP g1-small instance. This test will take over an hour (1h2m) which is slightly above our current threshold (120x, actual timeout is 60m). I think we can bump it to 150x (75m). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64) Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057734] Re: proc_sched_rt01 from ubuntu_ltp failed
** Description changed: - This is a new test case, issue found on M/J/F/B when testing LTP update - 20240312 + [Impact] + The updated LTP has added proc_sched_rt01 testcase which can't pass + since several commits are missed from kernel side. + + Test log: + INFO: Test start time: Tue Mar 12 11:52:21 UTC 2024 + COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 163430 -n 163430 -f /tmp/ltp-X3Nz2HWCQe/alltests -l /dev/null -C /dev/null -T /dev/null + LOG File: /dev/null + FAILED COMMAND File: /dev/null + TCONF COMMAND File: /dev/null + Running tests... + tst_kconfig.c:87: TINFO: Parsing kernel config '/lib/modules/6.5.0-27-generic/build/.config' + tst_test.c:1741: TINFO: LTP version: 20230929-406-gcbc2d0568 + tst_test.c:1625: TINFO: Timeout per run is 0h 00m 30s + proc_sched_rt01.c:45: TFAIL: Expect: timeslice_ms > 0 after reset to default + proc_sched_rt01.c:51: TPASS: echo 0 > /proc/sys/kernel/sched_rt_period_us : EINVAL (22) + proc_sched_rt01.c:53: TFAIL: echo -1 > /proc/sys/kernel/sched_rt_period_us invalid retval 2: SUCCESS (0) + proc_sched_rt01.c:59: TPASS: echo -2 > /proc/sys/kernel/sched_rt_runtime_us : EINVAL (22) + proc_sched_rt01.c:72: TFAIL: echo rt_period_us+1 > /proc/sys/kernel/sched_rt_runtime_us invalid retval 1: SUCCESS (0) + + HINT: You _MAY_ be missing kernel fixes: + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1fc6484e1fb + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=079be8fc6309 + + [Fix] + There are 3 relevant commits from upstream. + + 1. 079be8fc6309 sched/rt: Disallow writing invalid values to sched_rt_period_us + 2. c1fc6484e1fb sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset + 3. c7fcb99877f9 sched/rt: Fix sysctl_sched_rr_timeslice intial value + + Mantic: the 3rd is already in master-next. + Jammy: stable v5.15.150 includes the three commits. + Focal: master-next has include them after update to v5.4.270 + Bionic: all the three commits are needed. + + [Test case] + Run LTP update 20240312 to check the log of proc_sched_rt01. + + [Regression potential] + Low risk since these content are existed in upstream for a while. + + Cyril Hrubis (2): + sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset + sched/rt: Disallow writing invalid values to sched_rt_period_us + + kernel/sched/rt.c | 12 + 1 file changed, 8 insertions(+), 4 deletions(-) + + + [Original Bug Description] + This is a new test case, issue found on M/J/F/B when testing LTP update 20240312 Test log: INFO: Test start time: Tue Mar 12 11:52:21 UTC 2024 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 163430 -n 163430 -f /tmp/ltp-X3Nz2HWCQe/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_kconfig.c:87: TINFO: Parsing kernel config '/lib/modules/6.5.0-27-generic/build/.config' tst_test.c:1741: TINFO: LTP version: 20230929-406-gcbc2d0568 tst_test.c:1625: TINFO: Timeout per run is 0h 00m 30s proc_sched_rt01.c:45: TFAIL: Expect: timeslice_ms > 0 after reset to default proc_sched_rt01.c:51: TPASS: echo 0 > /proc/sys/kernel/sched_rt_period_us : EINVAL (22) proc_sched_rt01.c:53: TFAIL: echo -1 > /proc/sys/kernel/sched_rt_period_us invalid retval 2: SUCCESS (0) proc_sched_rt01.c:59: TPASS: echo -2 > /proc/sys/kernel/sched_rt_runtime_us : EINVAL (22) proc_sched_rt01.c:72: TFAIL: echo rt_period_us+1 > /proc/sys/kernel/sched_rt_runtime_us invalid retval 1: SUCCESS (0) HINT: You _MAY_ be missing kernel fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1fc6484e1fb https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=079be8fc6309 Summary: passed 2 failed 3 broken 0 skipped 0 warnings 0 INFO: ltp-pan reported some tests FAIL LTP Version: 20230929-406-gcbc2d0568 INFO: Test end time: Tue Mar 12 11:52:21 UTC 2024 ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057734 Title: proc_sched_rt01 from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Mantic: In Progress Bug description: [Impact] The updated LTP has added proc_sched_rt01
[Kernel-packages] [Bug 2057734] Re: proc_sched_rt01 from ubuntu_ltp failed
** Changed in: linux (Ubuntu Focal) Status: Won't Fix => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057734 Title: proc_sched_rt01 from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Mantic: In Progress Bug description: This is a new test case, issue found on M/J/F/B when testing LTP update 20240312 Test log: INFO: Test start time: Tue Mar 12 11:52:21 UTC 2024 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 163430 -n 163430 -f /tmp/ltp-X3Nz2HWCQe/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_kconfig.c:87: TINFO: Parsing kernel config '/lib/modules/6.5.0-27-generic/build/.config' tst_test.c:1741: TINFO: LTP version: 20230929-406-gcbc2d0568 tst_test.c:1625: TINFO: Timeout per run is 0h 00m 30s proc_sched_rt01.c:45: TFAIL: Expect: timeslice_ms > 0 after reset to default proc_sched_rt01.c:51: TPASS: echo 0 > /proc/sys/kernel/sched_rt_period_us : EINVAL (22) proc_sched_rt01.c:53: TFAIL: echo -1 > /proc/sys/kernel/sched_rt_period_us invalid retval 2: SUCCESS (0) proc_sched_rt01.c:59: TPASS: echo -2 > /proc/sys/kernel/sched_rt_runtime_us : EINVAL (22) proc_sched_rt01.c:72: TFAIL: echo rt_period_us+1 > /proc/sys/kernel/sched_rt_runtime_us invalid retval 1: SUCCESS (0) HINT: You _MAY_ be missing kernel fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1fc6484e1fb https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=079be8fc6309 Summary: passed 2 failed 3 broken 0 skipped 0 warnings 0 INFO: ltp-pan reported some tests FAIL LTP Version: 20230929-406-gcbc2d0568 INFO: Test end time: Tue Mar 12 11:52:21 UTC 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2057734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057734] Re: proc_sched_rt01 from ubuntu_ltp failed
** Changed in: linux (Ubuntu) Milestone: noble-updates => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057734 Title: proc_sched_rt01 from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Mantic: In Progress Bug description: This is a new test case, issue found on M/J/F/B when testing LTP update 20240312 Test log: INFO: Test start time: Tue Mar 12 11:52:21 UTC 2024 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 163430 -n 163430 -f /tmp/ltp-X3Nz2HWCQe/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_kconfig.c:87: TINFO: Parsing kernel config '/lib/modules/6.5.0-27-generic/build/.config' tst_test.c:1741: TINFO: LTP version: 20230929-406-gcbc2d0568 tst_test.c:1625: TINFO: Timeout per run is 0h 00m 30s proc_sched_rt01.c:45: TFAIL: Expect: timeslice_ms > 0 after reset to default proc_sched_rt01.c:51: TPASS: echo 0 > /proc/sys/kernel/sched_rt_period_us : EINVAL (22) proc_sched_rt01.c:53: TFAIL: echo -1 > /proc/sys/kernel/sched_rt_period_us invalid retval 2: SUCCESS (0) proc_sched_rt01.c:59: TPASS: echo -2 > /proc/sys/kernel/sched_rt_runtime_us : EINVAL (22) proc_sched_rt01.c:72: TFAIL: echo rt_period_us+1 > /proc/sys/kernel/sched_rt_runtime_us invalid retval 1: SUCCESS (0) HINT: You _MAY_ be missing kernel fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1fc6484e1fb https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=079be8fc6309 Summary: passed 2 failed 3 broken 0 skipped 0 warnings 0 INFO: ltp-pan reported some tests FAIL LTP Version: 20230929-406-gcbc2d0568 INFO: Test end time: Tue Mar 12 11:52:21 UTC 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2057734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
Hints removed. Closing this bug. This issue cannot be found on J-azure, J-azure-fips, J-gcp-fips, J-mtk, J-nvidia-tegra, J-xilinx. We don't run this test on J-raspi, J-bluefield. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Tags removed: verification-needed-jammy-linux-azure verification-needed-jammy-linux-azure-fips verification-needed-jammy-linux-bluefield verification-needed-jammy-linux-gcp-fips verification-needed-jammy-linux-mtk verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-raspi verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-azure verification-done-jammy-linux-azure-fips verification-done-jammy-linux-bluefield verification-done-jammy-linux-gcp-fips verification-done-jammy-linux-mtk verification-done-jammy-linux-nvidia-tegra verification-done-jammy-linux-raspi verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, event-pid.tc in linux/tools/testing/selftests/ftrace will take too much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: sudo ./ftracetest -vvv test.d/event/event-pid.tc The test should finish within a few minutes. [Regression Potential] Change limited to testing tools, it should not have any actual impact to kernel functions. == Original Bug Report == First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999589] Re: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / J-hwe-6.5
** Tags added: mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999589 Title: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / J-hwe-6.5 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Confirmed Bug description: All of the sm4* ciper testcases are failing in net:tls for kinetic linux 5.19.0-27.28 These seem like new testcases that have not been run before. and this has only been seen as far as I am aware of on s390x - 21:31:48 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendfile ... 21:31:48 DEBUG| [stdout] # # tls.c:314:sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # not ok 197 tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.send_then_sendfile ... 21:31:49 DEBUG| [stdout] # # tls.c:314:send_then_sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # send_then_sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # not ok 198 tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_max ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_max:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_max: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # not ok 199 tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_small ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_small:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_small: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # not ok 200 tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # not ok 201 tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more_unsent ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more_unsent:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more_unsent: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # not ok 202 tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_single ... 21:31:49 DEBUG| [stdout] # # tls.c:314:sendmsg_single:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_single: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # not ok 203 tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_fragmented ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_fragmented:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_fragmented: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # not ok 204 tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_large ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_large:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_large: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # not ok 205 tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_multiple ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_multiple: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_multiple 21:31:50 DEBUG| [stdout] # not ok 206 tls.13_sm4_gcm.sendmsg_multiple 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_multiple_stress ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple_stress:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_multiple_stress: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_multiple_stress 21:31:50 DEBUG| [stdout] # not ok 207 tls.13_sm4_gcm.sendmsg_multiple_stress 21:31:50 DEBUG| [stdout] # # RUN
[Kernel-packages] [Bug 1999589] Re: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x Kinetic
This is affecting J-hwe-6.5 openstack s390x instances since 6.5.0-14.14~22.04.1 ** Tags added: 6.5 jammy ** Tags added: sru-20240205 sru-20240304 ** Summary changed: - net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x Kinetic + net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / 6.5 ** Summary changed: - net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / 6.5 + net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / J-hwe-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999589 Title: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / J-hwe-6.5 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Confirmed Bug description: All of the sm4* ciper testcases are failing in net:tls for kinetic linux 5.19.0-27.28 These seem like new testcases that have not been run before. and this has only been seen as far as I am aware of on s390x - 21:31:48 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendfile ... 21:31:48 DEBUG| [stdout] # # tls.c:314:sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # not ok 197 tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.send_then_sendfile ... 21:31:49 DEBUG| [stdout] # # tls.c:314:send_then_sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # send_then_sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # not ok 198 tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_max ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_max:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_max: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # not ok 199 tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_small ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_small:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_small: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # not ok 200 tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # not ok 201 tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more_unsent ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more_unsent:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more_unsent: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # not ok 202 tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_single ... 21:31:49 DEBUG| [stdout] # # tls.c:314:sendmsg_single:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_single: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # not ok 203 tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_fragmented ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_fragmented:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_fragmented: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # not ok 204 tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_large ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_large:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_large: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # not ok 205 tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_multiple ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_multiple: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_multiple 21:31:50 DEBUG| [stdout] # not ok 206
[Kernel-packages] [Bug 1881643] Re: pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete veth device in a timely manner, PMTU dst likely leaked)
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/461647 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881643 Title: pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete veth device in a timely manner, PMTU dst likely leaked) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz [...] 03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop objects [FAIL] 03:48:34 DEBUG| [stdout] # can't delete veth device in a timely manner, PMTU dst likely leaked [...] 03:49:17 DEBUG| [stdout] not ok 16 selftests: net: pmtu.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055483] Re: net:pmtu.sh ubuntu_kselftests_net fails vxlan test
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/461647 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055483 Title: net:pmtu.sh ubuntu_kselftests_net fails vxlan test Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: net:pmtu.sh fails on openstack cpu2 M-lowlatency-64k ubuntu_kselftests_net. It fails with: DEBUG| [stdout] # TEST: IPv4, bridged geneve6: PMTU exceptions [FAIL] DEBUG| [stdout] # File size 1001302 mismatches exepcted value in locally bridged vxlan test I've included a file containing the console output as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055483] Re: net:pmtu.sh ubuntu_kselftests_net fails vxlan test
** Description changed: - net:pmtu.sh fails on openstack cpu2 lowlatency-64k + net:pmtu.sh fails on openstack cpu2 M-lowlatency-64k ubuntu_kselftests_net. It fails with: DEBUG| [stdout] # TEST: IPv4, bridged geneve6: PMTU exceptions [FAIL] DEBUG| [stdout] # File size 1001302 mismatches exepcted value in locally bridged vxlan test I've included a file containing the console output as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055483 Title: net:pmtu.sh ubuntu_kselftests_net fails vxlan test Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: net:pmtu.sh fails on openstack cpu2 M-lowlatency-64k ubuntu_kselftests_net. It fails with: DEBUG| [stdout] # TEST: IPv4, bridged geneve6: PMTU exceptions [FAIL] DEBUG| [stdout] # File size 1001302 mismatches exepcted value in locally bridged vxlan test I've included a file containing the console output as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055483] Re: net:pmtu.sh ubuntu_kselftests_net fails vxlan test
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: 6.5 arm64 mantic sru-20240205 ubuntu-kselftests-net -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055483 Title: net:pmtu.sh ubuntu_kselftests_net fails vxlan test Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: net:pmtu.sh fails on openstack cpu2 lowlatency-64k ubuntu_kselftests_net. It fails with: DEBUG| [stdout] # TEST: IPv4, bridged geneve6: PMTU exceptions [FAIL] DEBUG| [stdout] # File size 1001302 mismatches exepcted value in locally bridged vxlan test I've included a file containing the console output as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881643] Re: pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete veth device in a timely manner, PMTU dst likely leaked)
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/461647 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881643 Title: pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete veth device in a timely manner, PMTU dst likely leaked) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz [...] 03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop objects [FAIL] 03:48:34 DEBUG| [stdout] # can't delete veth device in a timely manner, PMTU dst likely leaked [...] 03:49:17 DEBUG| [stdout] not ok 16 selftests: net: pmtu.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055483] Re: net:pmtu.sh ubuntu_kselftests_net fails vxlan test
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/461647 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055483 Title: net:pmtu.sh ubuntu_kselftests_net fails vxlan test Status in linux package in Ubuntu: New Bug description: net:pmtu.sh fails on openstack cpu2 lowlatency-64k ubuntu_kselftests_net. It fails with: DEBUG| [stdout] # TEST: IPv4, bridged geneve6: PMTU exceptions [FAIL] DEBUG| [stdout] # File size 1001302 mismatches exepcted value in locally bridged vxlan test I've included a file containing the console output as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055473] Re: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU
** Description changed: + Issue found on J-gcp-6.5.0-1015.15~22.04.1 and M-gcp-6.5.0-1015.15 in + cycle sru-20240205 + + And can be reproduced with generic kernel on GCP cloud. + + This is not a regression but something emerges after the pmtu.sh result + parsing logic update, which landed via stable update in sru-20240205 + cycle (bug 2043198) + + Dive into test history, we can see this failure all the way back to + sru-20231030 with M-6.5.0-1010.10 on GCP cloud. + 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) ** Tags added: jammy sru-s20231030 ** Tags added: gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055473 Title: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: Issue found on J-gcp-6.5.0-1015.15~22.04.1 and M-gcp-6.5.0-1015.15 in cycle sru-20240205 And can be reproduced with generic kernel on GCP cloud. This is not a regression but something emerges after the pmtu.sh result parsing logic update, which landed via stable update in sru-20240205 cycle (bug 2043198) Dive into test history, we can see this failure all the way back to sru-20231030 with M-6.5.0-1010.10 on GCP cloud. 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055473] Re: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU
** Summary changed: - mtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU + pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU ** Tags added: 6.5 mantic sru-20240108 ubuntu-kselftests-net ** Tags removed: sru-20240108 ** Tags added: sru-20240205 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055473 Title: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
Hints removed, closing this bug. ** Changed in: ubuntu-kernel-tests 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/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:unknown # [FAIL] Test FAILED on line 94 # GPR[14]: 1 Expected: 2 # GPR[15]: 1 Expected: 2 # GPR[16]: 1 Expected: 2 # GPR[17]: 1 Expected: 2 # GPR[18]: 1 Expected: 2 # GPR[19]: 1 Expected: 2 # GPR[20]: 1 Expected: 2 # GPR[21]: 1 Expected: 2 # GPR[22]: 1 Expected: 2 # GPR[23]: 1 Expected: 2 # GPR[24]: 1 Expected: 2 # GPR[25]: 1 Expected: 2 # GPR[26]: 1 Expected: 2 # GPR[27]: 1 Expected: 2 # GPR[28]: 1 Expected: 2 # GPR[29]: 1 Expected: 2 # GPR[30]: 1 Expected: 2 # GPR[31]: 1 Expected: 2 # failure: ptrace_tm_gpr not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 [Fix] * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations This patch has already landed on Jammy+. Only Focal will need this patch. And it needs to be backported to skip changes on the tm-signal-pagefault.c test, which does not exist on Focal tree. [Test Plan] Run the patched powerpc tests from kernel selftests: $ sudo make TARGETS=powerpc run_tests Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. For example the ptrace-tm-gpr test: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:b315960-dirty # [SKIP] Test skipped on line 116 # skip: ptrace_tm_gpr ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr [Where problems could occur] Change limited to testing tools, and it's just skipping unsuitable tests for specific architecture, no impact to real kernel functions. == Original Bug Report == First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: * powerpc/ptrace:ptrace-tm-gpr FAIL * powerpc/ptrace:ptrace-tm-spd-gpr FAIL * powerpc/ptrace:ptrace-tm-tar timeout * powerpc/ptrace:ptrace-tm-spd-tar timeout * powerpc/ptrace:ptrace-tm-vsx timeout * powerpc/ptrace:ptrace-tm-spd-vsx timeout * powerpc/ptrace:ptrace-tm-spr timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2032641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054362] Re: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4 / 5.15
** Summary changed: - ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4 + ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4 / 5.15 ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054362 Title: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4 / 5.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux source package in Jammy: New Bug description: Issue found on B-hwe-5.4.0-173.191~18.04.1 F-5.4.0-173.191 and J-5.15.0-96.106, 5.15.0-100.110 in sru-20240205 This kprobe_non_uniq_symbol.tc test case came from stable update (bug 2049024) and landed in our Focal kernel since Ubuntu-5.4.0-173.191 For Jammy it came from stable update (bug 2049350) and landed in our Jammy kernel since Ubuntu-5.15.0-96.106 So this is not a regression, but a new test case. Test log: Running './ftracetest -vvv test.d/kprobe/kprobe_non_uniq_symbol.tc' === Ftrace unit tests === + initialize_ftrace + disable_tracing + echo 0 + reset_tracer + echo nop + reset_trigger + [ -d events/synthetic ] ... + read line ... + read line ... + reset_events_filter + read line ... + reset_ftrace_filter + [ ! -f set_ftrace_filter ] + echo + grep -v ^# set_ftrace_filter + read t + disable_events + echo 0 + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] [1] Test failure of registering kprobe on non unique symbol + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc + SYMBOL=name_show + grep -c -E [[:alnum:]]+ t name_show /proc/kallsyms + [ 14 -le 1 ] + echo p:test_non_unique name_show [FAIL] # of passed: 0 # of failed: 1 # of unresolved: 0 # of untested: 0 # of unsupported: 0 # of xfailed: 0 # of undefined(test bug): 0 I think we're probably missing https://github.com/torvalds/linux/commit/b022f0c7e404887a7c5229788fc99eff9f9a80d5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2054362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054362] Re: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4
** Description changed: - Issue found on B-hwe-5.4.0-173.191~18.04.1 + Issue found on B-hwe-5.4.0-173.191~18.04.1 F-5.4.0-173.191 and + J-5.15.0-96.106, 5.15.0-100.110 in sru-20240205 This kprobe_non_uniq_symbol.tc test case came from stable update (bug 2049024) and landed in our Focal kernel since Ubuntu-5.4.0-173.191 + For Jammy it came from stable update (bug 2049350) and landed in our + Jammy kernel since Ubuntu-5.15.0-96.106 + So this is not a regression, but a new test case. Test log: - Running './ftracetest -vvv test.d/kprobe/kprobe_non_uniq_symbol.tc' - === Ftrace unit tests === - + initialize_ftrace - + disable_tracing - + echo 0 - + reset_tracer - + echo nop - + reset_trigger - + [ -d events/synthetic ] - ... - + read line - ... - + read line - ... - + reset_events_filter - + read line - ... - + reset_ftrace_filter - + [ ! -f set_ftrace_filter ] - + echo - + grep -v ^# set_ftrace_filter - + read t - + disable_events - + echo 0 - + [ -f set_event_pid ] - + echo - + [ -f set_ftrace_pid ] - + echo - + [ -f set_ftrace_notrace ] - + echo - + [ -f set_graph_function ] - [1] Test failure of registering kprobe on non unique symbol - + echo - + tee set_graph_function set_graph_notrace - + [ -f stack_trace_filter ] - + echo - + [ -f kprobe_events ] - + echo - + [ -f uprobe_events ] - + echo - + [ -f synthetic_events ] - + echo - + [ -f snapshot ] - + echo 0 - + clear_trace - + echo - + enable_tracing - + echo 1 - + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc - + SYMBOL=name_show - + grep -c -E [[:alnum:]]+ t name_show /proc/kallsyms - + [ 14 -le 1 ] - + echo p:test_non_unique name_show - [FAIL] - - - # of passed: 0 - # of failed: 1 - # of unresolved: 0 - # of untested: 0 - # of unsupported: 0 - # of xfailed: 0 - # of undefined(test bug): 0 + Running './ftracetest -vvv test.d/kprobe/kprobe_non_uniq_symbol.tc' + === Ftrace unit tests === + + initialize_ftrace + + disable_tracing + + echo 0 + + reset_tracer + + echo nop + + reset_trigger + + [ -d events/synthetic ] + ... + + read line + ... + + read line + ... + + reset_events_filter + + read line + ... + + reset_ftrace_filter + + [ ! -f set_ftrace_filter ] + + echo + + grep -v ^# set_ftrace_filter + + read t + + disable_events + + echo 0 + + [ -f set_event_pid ] + + echo + + [ -f set_ftrace_pid ] + + echo + + [ -f set_ftrace_notrace ] + + echo + + [ -f set_graph_function ] + [1] Test failure of registering kprobe on non unique symbol + + echo + + tee set_graph_function set_graph_notrace + + [ -f stack_trace_filter ] + + echo + + [ -f kprobe_events ] + + echo + + [ -f uprobe_events ] + + echo + + [ -f synthetic_events ] + + echo + + [ -f snapshot ] + + echo 0 + + clear_trace + + echo + + enable_tracing + + echo 1 + + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc + + SYMBOL=name_show + + grep -c -E [[:alnum:]]+ t name_show /proc/kallsyms + + [ 14 -le 1 ] + + echo p:test_non_unique name_show + [FAIL] + + # of passed: 0 + # of failed: 1 + # of unresolved: 0 + # of untested: 0 + # of unsupported: 0 + # of xfailed: 0 + # of undefined(test bug): 0 I think we're probably missing https://github.com/torvalds/linux/commit/b022f0c7e404887a7c5229788fc99eff9f9a80d5 ** Tags added: 5.15 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/2054362 Title: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Bug description: Issue found on B-hwe-5.4.0-173.191~18.04.1 F-5.4.0-173.191 and J-5.15.0-96.106, 5.15.0-100.110 in sru-20240205 This kprobe_non_uniq_symbol.tc test case came from stable update (bug 2049024) and landed in our Focal kernel since Ubuntu-5.4.0-173.191 For Jammy it came from stable update (bug 2049350) and landed in our Jammy kernel since Ubuntu-5.15.0-96.106 So this is not a regression, but a new test case. Test log: Running './ftracetest -vvv test.d/kprobe/kprobe_non_uniq_symbol.tc' === Ftrace unit tests === + initialize_ftrace + disable_tracing + echo 0 + reset_tracer + echo nop + reset_trigger + [ -d events/synthetic ] ... + read line ... + read line ... + reset_events_filter + read line ... + reset_ftrace_filter + [ ! -f set_ftrace_filter ] + echo + grep -v ^# set_ftrace_filter + read t + disable_events + echo 0 + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] +
[Kernel-packages] [Bug 2054362] Re: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054362 Title: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Bug description: Issue found on B-hwe-5.4.0-173.191~18.04.1 This kprobe_non_uniq_symbol.tc test case came from stable update (bug 2049024) and landed in our Focal kernel since Ubuntu-5.4.0-173.191 So this is not a regression, but a new test case. Test log: Running './ftracetest -vvv test.d/kprobe/kprobe_non_uniq_symbol.tc' === Ftrace unit tests === + initialize_ftrace + disable_tracing + echo 0 + reset_tracer + echo nop + reset_trigger + [ -d events/synthetic ] ... + read line ... + read line ... + reset_events_filter + read line ... + reset_ftrace_filter + [ ! -f set_ftrace_filter ] + echo + grep -v ^# set_ftrace_filter + read t + disable_events + echo 0 + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] [1] Test failure of registering kprobe on non unique symbol + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc + SYMBOL=name_show + grep -c -E [[:alnum:]]+ t name_show /proc/kallsyms + [ 14 -le 1 ] + echo p:test_non_unique name_show [FAIL] # of passed: 0 # of failed: 1 # of unresolved: 0 # of untested: 0 # of unsupported: 0 # of xfailed: 0 # of undefined(test bug): 0 I think we're probably missing https://github.com/torvalds/linux/commit/b022f0c7e404887a7c5229788fc99eff9f9a80d5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2054362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054362] Re: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054362 Title: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: Issue found on B-hwe-5.4.0-173.191~18.04.1 This kprobe_non_uniq_symbol.tc test case came from stable update (bug 2049024) and landed in our Focal kernel since Ubuntu-5.4.0-173.191 So this is not a regression, but a new test case. Test log: Running './ftracetest -vvv test.d/kprobe/kprobe_non_uniq_symbol.tc' === Ftrace unit tests === + initialize_ftrace + disable_tracing + echo 0 + reset_tracer + echo nop + reset_trigger + [ -d events/synthetic ] ... + read line ... + read line ... + reset_events_filter + read line ... + reset_ftrace_filter + [ ! -f set_ftrace_filter ] + echo + grep -v ^# set_ftrace_filter + read t + disable_events + echo 0 + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] [1] Test failure of registering kprobe on non unique symbol + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc + SYMBOL=name_show + grep -c -E [[:alnum:]]+ t name_show /proc/kallsyms + [ 14 -le 1 ] + echo p:test_non_unique name_show [FAIL] # of passed: 0 # of failed: 1 # of unresolved: 0 # of untested: 0 # of unsupported: 0 # of xfailed: 0 # of undefined(test bug): 0 I think we're probably missing https://github.com/torvalds/linux/commit/b022f0c7e404887a7c5229788fc99eff9f9a80d5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2054362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
No PPC for raspi and oracle. ** Tags removed: verification-needed-focal-linux-oracle verification-needed-focal-linux-raspi ** Tags added: verification-done-focal-linux-oracle verification-done-focal-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:unknown # [FAIL] Test FAILED on line 94 # GPR[14]: 1 Expected: 2 # GPR[15]: 1 Expected: 2 # GPR[16]: 1 Expected: 2 # GPR[17]: 1 Expected: 2 # GPR[18]: 1 Expected: 2 # GPR[19]: 1 Expected: 2 # GPR[20]: 1 Expected: 2 # GPR[21]: 1 Expected: 2 # GPR[22]: 1 Expected: 2 # GPR[23]: 1 Expected: 2 # GPR[24]: 1 Expected: 2 # GPR[25]: 1 Expected: 2 # GPR[26]: 1 Expected: 2 # GPR[27]: 1 Expected: 2 # GPR[28]: 1 Expected: 2 # GPR[29]: 1 Expected: 2 # GPR[30]: 1 Expected: 2 # GPR[31]: 1 Expected: 2 # failure: ptrace_tm_gpr not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 [Fix] * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations This patch has already landed on Jammy+. Only Focal will need this patch. And it needs to be backported to skip changes on the tm-signal-pagefault.c test, which does not exist on Focal tree. [Test Plan] Run the patched powerpc tests from kernel selftests: $ sudo make TARGETS=powerpc run_tests Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. For example the ptrace-tm-gpr test: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:b315960-dirty # [SKIP] Test skipped on line 116 # skip: ptrace_tm_gpr ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr [Where problems could occur] Change limited to testing tools, and it's just skipping unsuitable tests for specific architecture, no impact to real kernel functions. == Original Bug Report == First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: * powerpc/ptrace:ptrace-tm-gpr FAIL * powerpc/ptrace:ptrace-tm-spd-gpr FAIL * powerpc/ptrace:ptrace-tm-tar timeout * powerpc/ptrace:ptrace-tm-spd-tar timeout * powerpc/ptrace:ptrace-tm-vsx timeout * powerpc/ptrace:ptrace-tm-spd-vsx timeout * powerpc/ptrace:ptrace-tm-spr timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2032641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020607] Re: ftracetest from selftests in linux ADT test failure with jammy/linux-intel-iotg (kernel NULL pointer dereference)
After splitting ubuntu_kselftests_ftrace out and run test cases one-by- one, we can see it's failing with the second test case, ftrace:test.d-- 00basic--basic2.tc, on J-intel-iotg-5.15.0-1048.54 with node rizzo. However I was unable to reproduce this manually on rizzo: * Passed with running just the ftrace:test.d--00basic--basic2.tc, with "./ftracetest -vvv test.d/00basic/basic2.tc" * Passed with running basic2.tc multiple times. * Passed with running the 1st test case and the offending basic2.tc test case. * Passed with running the whole test suite. But if you try to run this remotely from out build server: SRU_CYCLE="2024.01.08-1" INSTANCE_TYPE="rizzo" timeout 180m $KT/sut-test --nc --region kernel $DEBUG metal $SUT jammy ubuntu_kselftests_ftrace $HOME It will panic right away when hitting the second test case. It looks like it has something to do with CPU hotplug: [ 5990.967618] mmiotrace: Disabling non-boot CPUs... [ 5991.032796] smpboot: CPU 1 is now offline [ 5991.052877] mmiotrace: CPU1 is down. [ 5991.124833] smpboot: CPU 2 is now offline [ 5991.140709] mmiotrace: CPU2 is down. [ 5991.196717] smpboot: CPU 3 is now offline [ 5991.216486] mmiotrace: CPU3 is down. [ 5991.233400] smpboot: CPU 4 is now offline [ 5991.272507] mmiotrace: CPU4 is down. [ 5991.313356] smpboot: CPU 5 is now offline [ 5991.328204] mmiotrace: CPU5 is down. [ 5991.353591] smpboot: CPU 6 is now offline [ 5991.376155] mmiotrace: CPU6 is down. [ 5991.393484] smpboot: CPU 7 is now offline [ 5991.394580] mmiotrace: CPU7 is down. [ 5991.394586] mmiotrace: enabled. [ 5991.394693] mmiotrace: Re-enabling CPUs... [ 5991.394761] x86: Booting SMP configuration: [ 5991.394763] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 5991.432595] mmiotrace: enabled CPU1. [ 5991.479537] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 5991.508524] mmiotrace: enabled CPU2. [ 5991.547586] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 5991.576690] mmiotrace: enabled CPU3. [ 5991.619582] smpboot: Booting Node 0 Processor 4 APIC 0x1 [ 5991.639516] BUG: kernel NULL pointer dereference, address: [ 5991.646618] #PF: supervisor instruction fetch in kernel mode [ 5991.652336] #PF: error_code(0x0010) - not-present page [ 5991.657530] PGD 0 P4D 0 [ 5991.660096] Oops: 0010 [#1] SMP PTI [ 5991.663626] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-1048-intel-iotg #54-Ubuntu [ 5991.671709] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013 [ 5991.679350] RIP: 0010:0x0 [ 5991.682010] Code: Unable to access opcode bytes at RIP 0xffd6. [ 5991.688955] RSP: 0018:b92a40003e90 EFLAGS: 00010097 [ 5991.694233] RAX: RBX: 000231f0 RCX: 0004 [ 5991.701435] RDX: RSI: 0020 RDI: 9c20c007b990 [ 5991.708639] RBP: b92a40003eb8 R08: 9c20c007b990 R09: 0001 [ 5991.715842] R10: 0020 R11: R12: 9c20c007b990 [ 5991.723050] R13: 0572e77e8500 R14: 0004 R15: [ 5991.730252] FS: () GS:9c21f760() knlGS: [ 5991.738417] CS: 0010 DS: ES: CR0: 80050033 [ 5991.744218] CR2: ffd6 CR3: 10c1 CR4: 06f0 [ 5991.751425] Call Trace: [ 5991.753903] [ 5991.755945] ? show_trace_log_lvl+0x1d6/0x2ea [ 5991.760362] ? show_trace_log_lvl+0x1d6/0x2ea [ 5991.764773] ? tick_do_broadcast+0xa1/0xd0 [ 5991.768922] ? show_regs.part.0+0x23/0x29 [ 5991.773026] ? __die_body.cold+0x8/0xd [ 5991.776821] ? __die+0x2b/0x37 [ 5991.779918] ? page_fault_oops+0x13b/0x170 [ 5991.784063] ? do_user_addr_fault+0x321/0x670 [ 5991.788476] ? obj_cgroup_uncharge_pages+0x68/0xf0 [ 5991.793324] ? exc_page_fault+0x77/0x170 [ 5991.797293] ? asm_exc_page_fault+0x27/0x30 [ 5991.801529] tick_do_broadcast+0xa1/0xd0 [ 5991.805501] tick_handle_oneshot_broadcast+0x14d/0x200 [ 5991.810694] timer_interrupt+0x18/0x30 [ 5991.814495] __handle_irq_event_percpu+0x42/0x170 [ 5991.819255] handle_irq_event+0x59/0xb0 [ 5991.823136] handle_edge_irq+0x8c/0x230 [ 5991.827019] __common_interrupt+0x52/0xe0 [ 5991.831078] common_interrupt+0x89/0xa0 [ 5991.834966] [ 5991.837098] [ 5991.839247] asm_common_interrupt+0x27/0x40 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2020607 Title: ftracetest from selftests in linux ADT test failure with jammy/linux- intel-iotg (kernel NULL pointer dereference) Status in ubuntu-kernel-tests: New Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: New Bug description: the failure only is seen on the machine rizzo. how to reproduce: 1. run net selftest in the kernel. 2. run ftracetest in the kernel, and then there is a highly chance that causes the kernel oops. issue could be seen on
[Kernel-packages] [Bug 2034057] Re: function_graph tracer in ftrace related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge
The bug for GCP n2d-standard-4.sev_snp can be tracked in bug 2051378 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2034057 Title: function_graph tracer in ftrace related tests triggers kernel bug (arch/x86/xen/spinlock.c:62) and kernel panic on AWS cloud c3.xlarge Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-aws source package in Focal: New Status in linux-aws source package in Jammy: New Status in linux-aws source package in Lunar: Won't Fix Bug description: Test: * ftrace:test.d--00basic--basic2.tc from ubuntu_kselftests_ftrace * test_enable_all_tracers() and test_enable_all_tracers() from ubuntu_ftrace_smoke_test Will crash AWS instance c3.xlarge when testing the "function_graph" tracer. We have a similar issue filed against Azure (bug 1882669). Filing a new bug report because on AWS this is affecting 5.4 ~ 6.2 AWS kernel. However on Azure this is not affecting newer kernels. Take B-aws-5.4-1108 for example, with the ubuntu_kselftests_ftrace test the system will crash with the following error message and reboot (similar to bug 2029917): [ 211.675624] kernel BUG at /build/linux-aws-5.4-VHOhmt/linux-aws-5.4-5.4.0/arch/x86/xen/spinlock.c:62! [ 211.678258] invalid opcode: [#1] SMP PTI [ 211.679596] CPU: 1 PID: 14 Comm: cpuhp/1 Not tainted 5.4.0-1108-aws #116~18.04.1-Ubuntu [ 211.681825] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006 [ 211.683728] RIP: 0010:dummy_handler+0x4/0x10 [ 211.685042] Code: 8b 75 e4 74 d6 44 89 e7 e8 f9 88 61 00 eb d6 44 89 e7 e8 6f ab 61 00 eb cc 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 80 3d 59 d0 9f 01 00 75 02 f3 [ 211.690314] RSP: :aecd4000ee38 EFLAGS: 00010046 [ 211.691934] RAX: b462e3e0 RBX: 003b RCX: [ 211.694036] RDX: 00400e00 RSI: RDI: 003b [ 211.696159] RBP: aecd4000ee38 R08: 8aefa6c036c0 R09: 8aefa6c038c0 [ 211.698232] R10: R11: b6064da8 R12: [ 211.700365] R13: R14: R15: 8aefa34b8700 [ 211.702482] FS: () GS:8aefa804() knlGS: [ 211.704894] CS: 0010 DS: ES: CR0: 80050033 [ 211.706598] CR2: CR3: 0001b400a001 CR4: 001606e0 [ 211.708731] DR0: DR1: DR2: [ 211.710835] DR3: DR6: fffe0ff0 DR7: 0400 [ 211.713448] Call Trace: [ 211.714796] [ 211.715996] __handle_irq_event_percpu+0x44/0x1a0 [ 211.717907] handle_irq_event_percpu+0x32/0x80 [ 211.719759] handle_percpu_irq+0x3d/0x60 [ 211.721474] generic_handle_irq+0x28/0x40 [ 211.723184] handle_irq_for_port+0x8f/0xe0 [ 211.724988] evtchn_2l_handle_events+0x157/0x270 [ 211.726913] __xen_evtchn_do_upcall+0x76/0xe0 [ 211.728749] xen_evtchn_do_upcall+0x2b/0x40 [ 211.730520] xen_hvm_callback_vector+0xf/0x20 [ 211.732271] [ 211.733425] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20 [ 211.735470] Code: e8 70 3d 64 ff 4c 29 e0 4c 39 f0 76 cf 80 0b 08 eb 8a 90 90 90 0f 1f 44 00 00 55 48 89 e5 e8 a6 ad 66 ff 66 90 48 89 f7 57 9d <0f> 1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 07 [ 211.741920] RSP: :aecd400fbcf8 EFLAGS: 0246 ORIG_RAX: ff0c [ 211.744980] RAX: 0001 RBX: 8aefa34b8700 RCX: 0002cc00 [ 211.747420] RDX: 0001 RSI: 0246 RDI: 0246 [ 211.749882] RBP: aecd400fbcf8 R08: 8aefa6c036c0 R09: 8aefa6c038c0 [ 211.752340] R10: R11: 0246 R12: 003b [ 211.754785] R13: R14: 8aef95bdfa00 R15: 8aef95bdfaa4 [ 211.757249] __setup_irq+0x456/0x760 [ 211.758779] ? kmem_cache_alloc_trace+0x170/0x230 [ 211.760639] request_threaded_irq+0xfb/0x160 [ 211.762358] bind_ipi_to_irqhandler+0xba/0x1c0 [ 211.764124] ? xen_qlock_wait+0x90/0x90 [ 211.765734] ? snr_uncore_mmio_init+0x20/0x20 [ 211.767496] xen_init_lock_cpu+0x78/0xd0 [ 211.769135] ? snr_uncore_mmio_init+0x20/0x20 [ 211.770864] xen_cpu_up_online+0xe/0x20 [ 211.772500] cpuhp_invoke_callback+0x8a/0x580 [ 211.774233] cpuhp_thread_fun+0xb8/0x120 [ 211.775866] smpboot_thread_fn+0xfc/0x170 [ 211.777524] kthread+0x121/0x140 [ 211.778968] ? sort_range+0x30/0x30 [ 211.780508] ? kthread_park+0x90/0x90 [ 211.782073] ret_from_fork+0x35/0x40 [ 211.783622] Modules linked in: nls_iso8859_1 binfmt_misc serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp
[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
There is no ARM64 for jammy-linux-ibm-gt-fips. ** Tags removed: verification-needed-jammy-linux-ibm-gt-fips ** Tags added: verification-done-jammy-linux-ibm-gt-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: [Impact] On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, event-pid.tc in linux/tools/testing/selftests/ftrace will take too much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: sudo ./ftracetest -vvv test.d/event/event-pid.tc The test should finish within a few minutes. [Regression Potential] Change limited to testing tools, it should not have any actual impact to kernel functions. == Original Bug Report == First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051184] Re: ubuntu_boot test failures on b/linux-gcp-5.4 on c3a-standard instance
Here is my investigation when discussing this issue with Jesse:
This warning is triggered in spectre_bhb_enable_mitigation() from
arch/arm64/kernel/cpu_errata.c, inside this if statement:
} else if (spectre_bhb_loop_affected(SCOPE_LOCAL_CPU)) {
switch (spectre_bhb_loop_affected(SCOPE_SYSTEM)) {
case 8:
/*
* A57/A72-r0 will already have selected the
* spectre-indirect vector, which is sufficient
* for BHB too.
*/
if (!__this_cpu_read(bp_hardening_data.fn))
kvm_setup_bhb_slot(__spectre_bhb_loop_k8_start);
break;
case 24:
kvm_setup_bhb_slot(__spectre_bhb_loop_k24_start);
break;
case 32:
kvm_setup_bhb_slot(__spectre_bhb_loop_k32_start);
break;
default:
WARN_ON_ONCE(1);
}
this_cpu_set_vectors(EL1_VECTOR_BHB_LOOP);
This is because the case value (spectre_bhb_loop_affected(SCOPE_SYSTEM))
does not match, and falls into the "default" case.
This piece of code came from a SAUCE patch 14d45ef5 (UBUNTU: SAUCE: arm64:
Mitigate spectre style branch history side channels), in which it moves the
code that exist in arch/arm64/kernel/proton-pack.c to cpu_errata.c as mentioned
in the commit message:
[ modified for stable, moved code to cpu_errata.c removed bitmap of
mitigations, use kvm template infrastructure ]
This issue does not exist in 5.15 kernel, and there is a new commit that
added a new "case 11" to the switch-case, 0e5d5ae8 (arm64: Add AMPERE1
to the Spectre-BHB affected list).
According to Google [1]:
> C3A powered by AmpereOne processors
So I think this 0e5d5ae8 is very likely the fix we need for 5.4.
[1] https://cloud.google.com/blog/products/compute/whats-new-in-googles-
workload-optimized-computing
** Tags added: arm64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051184
Title:
ubuntu_boot test failures on b/linux-gcp-5.4 on c3a-standard instance
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
New
Bug description:
Boot testing fails for b/gcp-5.4 on new c3a-standard instance as
below:
Causes WARNING at: arch/arm64/kernel/cpu_errata.c:1387
spectre_bhb_enable_mitigation+0x148
[0.060607] WARNING: CPU: 3 PID: 29 at
/build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387
spectre_bhb_enable_mitigation+0x148/0x228
[0.060612] WARNING: CPU: 2 PID: 23 at
/build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387
spectre_bhb_enable_mitigation+0x148/0x228
[0.060613] Modules linked in:
[0.060615] Modules linked in:
[0.060621] CPU: 3 PID: 29 Comm: migration/3 Not tainted 5.4.0-1122-gcp
#131~18.04.1-Ubuntu
[0.060622] CPU: 2 PID: 23 Comm: migration/2 Not tainted 5.4.0-1122-gcp
#131~18.04.1-Ubuntu
[0.060628] WARNING: CPU: 1 PID: 17 at
/build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387
spectre_bhb_enable_mitigation+0x148/0x228
[0.060629] pstate: 20400085 (nzCv daIf +PAN -UAO)
[0.060630] Modules linked in:
[0.060632] pc : spectre_bhb_enable_mitigation+0x148/0x228
[0.060635] lr : spectre_bhb_enable_mitigation+0x120/0x228
[0.060636] CPU: 1 PID: 17 Comm: migration/1 Not tainted 5.4.0-1122-gcp
#131~18.04.1-Ubuntu
[0.060637] sp : 80001012bce0
[0.060639] pstate: 20400085 (nzCv daIf +PAN -UAO)
[0.060639] x29: 80001012bce0 x28: 0002
[0.060642] pc : spectre_bhb_enable_mitigation+0x148/0x228
[0.060645] lr : spectre_bhb_enable_mitigation+0x120/0x228
[0.060646] x27: 80001003bd10
[0.060647] sp : 8000100fbce0
[0.060647] x26:
[0.060648] x29: 8000100fbce0
[0.060650] x28: 0002
[0.060652] x25: 0060
[0.060653] x24:
[0.060655] x27: 80001003bd10 x26:
[0.060657] x23: 0001
[0.060661] x22: dca01ea9a3c0
[0.060663] x25: 0060 x24:
[0.060665] x21: dca01dda4970
[0.060668] x20: 0001
[0.060669] x23: 0001 x22: dca01ea9a3c0
[0.060671] x19: dca01ecca000
[0.060675] x18: dca01dc56a10
[0.060680] x21: dca01dda4970 x20: 0001
[0.060684] x17: bc8dcec3
[0.060687] x16: b1e1b9b5
[0.060688] x19: dca01ecca000 x18: dca01dc56a10
[0.060694] x17: 7e50fa5f
[0.060694] x15: 0001
[0.060695] x16:
[Kernel-packages] [Bug 2051184] Re: ubuntu_boot test failures on b/linux-gcp-5.4 on c3a-standard instance
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => 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/2051184 Title: ubuntu_boot test failures on b/linux-gcp-5.4 on c3a-standard instance Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Bug description: Boot testing fails for b/gcp-5.4 on new c3a-standard instance as below: Causes WARNING at: arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148 [0.060607] WARNING: CPU: 3 PID: 29 at /build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148/0x228 [0.060612] WARNING: CPU: 2 PID: 23 at /build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148/0x228 [0.060613] Modules linked in: [0.060615] Modules linked in: [0.060621] CPU: 3 PID: 29 Comm: migration/3 Not tainted 5.4.0-1122-gcp #131~18.04.1-Ubuntu [0.060622] CPU: 2 PID: 23 Comm: migration/2 Not tainted 5.4.0-1122-gcp #131~18.04.1-Ubuntu [0.060628] WARNING: CPU: 1 PID: 17 at /build/linux-gcp-5.4-FHHMzo/linux-gcp-5.4-5.4.0/arch/arm64/kernel/cpu_errata.c:1387 spectre_bhb_enable_mitigation+0x148/0x228 [0.060629] pstate: 20400085 (nzCv daIf +PAN -UAO) [0.060630] Modules linked in: [0.060632] pc : spectre_bhb_enable_mitigation+0x148/0x228 [0.060635] lr : spectre_bhb_enable_mitigation+0x120/0x228 [0.060636] CPU: 1 PID: 17 Comm: migration/1 Not tainted 5.4.0-1122-gcp #131~18.04.1-Ubuntu [0.060637] sp : 80001012bce0 [0.060639] pstate: 20400085 (nzCv daIf +PAN -UAO) [0.060639] x29: 80001012bce0 x28: 0002 [0.060642] pc : spectre_bhb_enable_mitigation+0x148/0x228 [0.060645] lr : spectre_bhb_enable_mitigation+0x120/0x228 [0.060646] x27: 80001003bd10 [0.060647] sp : 8000100fbce0 [0.060647] x26: [0.060648] x29: 8000100fbce0 [0.060650] x28: 0002 [0.060652] x25: 0060 [0.060653] x24: [0.060655] x27: 80001003bd10 x26: [0.060657] x23: 0001 [0.060661] x22: dca01ea9a3c0 [0.060663] x25: 0060 x24: [0.060665] x21: dca01dda4970 [0.060668] x20: 0001 [0.060669] x23: 0001 x22: dca01ea9a3c0 [0.060671] x19: dca01ecca000 [0.060675] x18: dca01dc56a10 [0.060680] x21: dca01dda4970 x20: 0001 [0.060684] x17: bc8dcec3 [0.060687] x16: b1e1b9b5 [0.060688] x19: dca01ecca000 x18: dca01dc56a10 [0.060694] x17: 7e50fa5f [0.060694] x15: 0001 [0.060695] x16: 9cd7320e [0.060696] x14: 74e6bd9c01c8 [0.060699] x13: 0004 [0.060701] x15: 0001 [0.060702] x12: 0228 [0.060703] x14: 74e6bd99f1c8 [0.060705] x11: [0.060711] x13: 0004 [0.060712] x10: 0b00 [0.060713] x12: 0228 [0.060716] x11: [0.060722] x9 : 80001012bd20 [0.060723] x10: 0b00 [0.060724] x8 : 74e6ba3c66e0 [0.060726] x7 : x6 : dca01d822000 [0.060727] x9 : 8000100fbd20 [0.060729] x8 : 74e6ba33a9e0 [0.060729] x5 : c00fac30 [0.060730] x4 : [0.060731] x7 : [0.060734] x6 : dca01d822000 [0.060735] x3 : 000b [0.060736] x2 : dca01ecca508 [0.060738] x5 : c00fac30 x4 : [0.060740] x1 : 000b [0.060742] x0 : 000b [0.060746] x3 : 000b x2 : dca01ecca508 [0.060749] Call trace: [0.060751] x1 : 000b [0.060753] spectre_bhb_enable_mitigation+0x148/0x228 [0.060755] x0 : 000b [0.060757] cpu_enable_non_boot_scope_capabilities+0x6c/0xa8 [0.060761] multi_cpu_stop+0xac/0x188 [0.060762] Call trace: [0.060763] cpu_stopper_thread+0xe4/0x1a0 [0.060766] spectre_bhb_enable_mitigation+0x148/0x228 [0.060769] smpboot_thread_fn+0x1a8/0x1d8 [0.060771] cpu_enable_non_boot_scope_capabilities+0x6c/0xa8 [0.060773] kthread+0x114/0x118 [0.060775] multi_cpu_stop+0xac/0x188 [0.060778] ret_from_fork+0x10/0x18 [0.060779]
[Kernel-packages] [Bug 1939035] Re: memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11
*** This bug is a duplicate of bug 1942426 *** https://bugs.launchpad.net/bugs/1942426 ** This bug has been marked a duplicate of bug 1942426 memcg_subgroup_charge from controllers in ubuntu_ltp fails with "timed out on memory.usage_in_byte" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939035 Title: memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Won't Fix Bug description: memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out when running with hirsute/linux 5.11. startup='Mon Jul 19 15:17:41 2021' memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no relationship memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 270336 memcg_subgroup_charge 1 TINFO: Warming up pid: 443417 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 443417 memcg_subgroup_charge 1 TBROK: timed out on memory.usage_in_bytes memcg_subgroup_charge 1 TINFO: AppArmor enabled, this may affect test results memcg_subgroup_charge 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) memcg_subgroup_charge 1 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 tag=memcg_subgroup_charge stime=1626707861 dur=11 exit=exited stat=2 core=no cu=19 cs=12 This is not a regression as it already failed on previous releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
There is no ARM64 for intel iotg kernel. ** Tags removed: verification-needed-jammy-linux-intel-iotg ** Tags added: verification-dibe-jammy-linux-intel-iotg ** Tags removed: verification-dibe-jammy-linux-intel-iotg ** Tags added: verification-done-jammy-linux-intel-iotg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: [Impact] On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, event-pid.tc in linux/tools/testing/selftests/ftrace will take too much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: sudo ./ftracetest -vvv test.d/event/event-pid.tc The test should finish within a few minutes. [Regression Potential] Change limited to testing tools, it should not have any actual impact to kernel functions. == Original Bug Report == First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
Verified with Jammy 5.15.0-93.103 ARM64, this test is not failing anymore. ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: [Impact] On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, event-pid.tc in linux/tools/testing/selftests/ftrace will take too much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: sudo ./ftracetest -vvv test.d/event/event-pid.tc The test should finish within a few minutes. [Regression Potential] Change limited to testing tools, it should not have any actual impact to kernel functions. == Original Bug Report == First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
These are not failing on Focal anymore. Verified with 5.4.0-171.189 ** Tags removed: verification-needed-focal-linux ** Tags added: verification-done-focal-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:unknown # [FAIL] Test FAILED on line 94 # GPR[14]: 1 Expected: 2 # GPR[15]: 1 Expected: 2 # GPR[16]: 1 Expected: 2 # GPR[17]: 1 Expected: 2 # GPR[18]: 1 Expected: 2 # GPR[19]: 1 Expected: 2 # GPR[20]: 1 Expected: 2 # GPR[21]: 1 Expected: 2 # GPR[22]: 1 Expected: 2 # GPR[23]: 1 Expected: 2 # GPR[24]: 1 Expected: 2 # GPR[25]: 1 Expected: 2 # GPR[26]: 1 Expected: 2 # GPR[27]: 1 Expected: 2 # GPR[28]: 1 Expected: 2 # GPR[29]: 1 Expected: 2 # GPR[30]: 1 Expected: 2 # GPR[31]: 1 Expected: 2 # failure: ptrace_tm_gpr not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 [Fix] * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations This patch has already landed on Jammy+. Only Focal will need this patch. And it needs to be backported to skip changes on the tm-signal-pagefault.c test, which does not exist on Focal tree. [Test Plan] Run the patched powerpc tests from kernel selftests: $ sudo make TARGETS=powerpc run_tests Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. For example the ptrace-tm-gpr test: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:b315960-dirty # [SKIP] Test skipped on line 116 # skip: ptrace_tm_gpr ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr [Where problems could occur] Change limited to testing tools, and it's just skipping unsuitable tests for specific architecture, no impact to real kernel functions. == Original Bug Report == First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: * powerpc/ptrace:ptrace-tm-gpr FAIL * powerpc/ptrace:ptrace-tm-spd-gpr FAIL * powerpc/ptrace:ptrace-tm-tar timeout * powerpc/ptrace:ptrace-tm-spd-tar timeout * powerpc/ptrace:ptrace-tm-vsx timeout * powerpc/ptrace:ptrace-tm-spd-vsx timeout * powerpc/ptrace:ptrace-tm-spr timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2032641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956561] Re: 5.15 / 5.19 kernel selftest srv6_end_dt46_l3vpn_test.sh failure (SRv6 VPN connectivity test)
This might need iproute2 update mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961566/comments/2 as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956561 Title: 5.15 / 5.19 kernel selftest srv6_end_dt46_l3vpn_test.sh failure (SRv6 VPN connectivity test) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Won't Fix Bug description: Kernel selftest srv6_end_dt46_l3vpn_test.sh reports the following error (it seems to be an upstream issue): # ### # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # ### # # TEST: IPv6 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100)[ OK ] # # TEST: IPv4 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100)[FAIL] # # TEST: IPv6 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100)[ OK ] # # TEST: IPv4 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100)[FAIL] # # TEST: IPv6 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200)[ OK ] # # TEST: IPv4 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200)[FAIL] # # TEST: IPv6 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200)[ OK ] # # TEST: IPv4 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200)[FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1956561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956562] Re: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure
This might need iproute2 update mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961566/comments/2 as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956562 Title: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Won't Fix Bug description: Script srv6_end_dt4_l3vpn_test.sh reports the following failure (upstream issue). With Jammy 5.15: # ### # TEST SECTION: IPv6 routers connectivity test # ### # # TEST: Routers connectivity: rt-1 -> rt-2 [FAIL] # # TEST: Routers connectivity: rt-2 -> rt-1 [FAIL] # ### # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # ### # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] # With Kinetic 5.19: # ### # TEST SECTION: IPv6 routers connectivity test # ### # # TEST: Routers connectivity: rt-1 -> rt-2 [FAIL] # # TEST: Routers connectivity: rt-2 -> rt-1 [ OK ] # # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # ### # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1956562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961566] Re: 5.15 kernel selftest srv6_end_dt6_l3vpn_test.sh failure
** Also affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: iproute2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: iproute2 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1961566 Title: 5.15 kernel selftest srv6_end_dt6_l3vpn_test.sh failure Status in ubuntu-kernel-tests: New Status in iproute2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in iproute2 source package in Focal: New Status in linux source package in Focal: New Status in iproute2 source package in Jammy: Fix Released Status in linux source package in Jammy: Confirmed Bug description: Kernel selftest srv6_end_dt6_l3vpn_test.sh fails on s2lp4.s390x: # selftests: net: srv6_end_dt6_l3vpn_test.sh # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. ... # # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1961566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961566] Re: 5.15 kernel selftest srv6_end_dt6_l3vpn_test.sh failure
This issue has gone on Jammy+, but still visible on Focal 5.15 variants. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1961566 Title: 5.15 kernel selftest srv6_end_dt6_l3vpn_test.sh failure Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: Kernel selftest srv6_end_dt6_l3vpn_test.sh fails on s2lp4.s390x: # selftests: net: srv6_end_dt6_l3vpn_test.sh # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. ... # # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1961566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956561] Re: 5.15 / 5.19 kernel selftest srv6_end_dt46_l3vpn_test.sh failure (SRv6 VPN connectivity test)
This issue has gone on Jammy+, but still visible on Focal 5.15 variants. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956561 Title: 5.15 / 5.19 kernel selftest srv6_end_dt46_l3vpn_test.sh failure (SRv6 VPN connectivity test) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Won't Fix Bug description: Kernel selftest srv6_end_dt46_l3vpn_test.sh reports the following error (it seems to be an upstream issue): # ### # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # ### # # TEST: IPv6 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100)[ OK ] # # TEST: IPv4 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100)[FAIL] # # TEST: IPv6 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100)[ OK ] # # TEST: IPv4 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100)[FAIL] # # TEST: IPv6 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200)[ OK ] # # TEST: IPv4 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200)[FAIL] # # TEST: IPv6 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200)[ OK ] # # TEST: IPv4 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200)[FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1956561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956562] Re: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure
This issue has gone on Jammy+, but still visible on Focal 5.15 variants. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956562 Title: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Won't Fix Bug description: Script srv6_end_dt4_l3vpn_test.sh reports the following failure (upstream issue). With Jammy 5.15: # ### # TEST SECTION: IPv6 routers connectivity test # ### # # TEST: Routers connectivity: rt-1 -> rt-2 [FAIL] # # TEST: Routers connectivity: rt-2 -> rt-1 [FAIL] # ### # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # ### # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] # With Kinetic 5.19: # ### # TEST SECTION: IPv6 routers connectivity test # ### # # TEST: Routers connectivity: rt-1 -> rt-2 [FAIL] # # TEST: Routers connectivity: rt-2 -> rt-1 [ OK ] # # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # ### # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1956562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Hints removed, closing this bug.
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
** Tags removed: verification-needed-lunar-linux-oracle
verification-needed-lunar-linux-riscv
** Tags added: verification-done-lunar-linux-oracle
verification-done-lunar-linux-riscv
** Tags removed: verification-needed-jammy-linux-oracle-6.2
verification-needed-jammy-linux-starfive-6.2
verification-needed-jammy-linux-xilinx-zynqmp
** Tags added: verification-done-jammy-linux-oracle-6.2
verification-done-jammy-linux-starfive-6.2
verification-done-jammy-linux-xilinx-zynqmp
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035181
Title:
Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
2 errors
[Kernel-packages] [Bug 1848680] Re: hugetlb tests in ubuntu_ltp failed on B-KVM
Closing this bug as this does not exist in our hint database and we didn't see this issue in recent cycles. There is a new hugetlb failure after recent LTP update, which will be recorded separately. https://lists.ubuntu.com/archives/kernel-team/2023-December/147590.html ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1848680 Title: hugetlb tests in ubuntu_ltp failed on B-KVM Status in ubuntu-kernel-tests: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Invalid Bug description: Failed test cases : hugemmap01 hugemmap02 hugemmap04 hugemmap05 hugemmap05_1 hugemmap05_2 hugemmap05_3 hugemmap06 hugeshmat01 hugeshmat02 hugeshmat03 hugeshmat04 hugeshmat05 hugeshmctl01 hugeshmctl02 hugeshmctl03 hugeshmdt01 hugeshmget01 hugeshmget02 hugeshmget03 hugeshmget05 However, if you run this test suite directly, all these test will pass. So I think this is caused by some other failures before the hugetlbfs test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1047-kvm 4.15.0-1047.47 ProcVersionSignature: User Name 4.15.0-1047.47-kvm 4.15.18 Uname: Linux 4.15.0-1047-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 18 08:30:08 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013064] Re: ubuntu_ltp_kernel_misc.zram01 fails to create xfs on a device too small in lunar
*** This bug is a duplicate of bug 2044510 *** https://bugs.launchpad.net/bugs/2044510 ** This bug has been marked a duplicate of bug 2044510 memcontrol02, memcontrol03, memcontrol04 in ubuntu_ltp_controllers failed with "filesystem must be larger than 300MB." when testing XFS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013064 Title: ubuntu_ltp_kernel_misc.zram01 fails to create xfs on a device too small in lunar Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Lunar: Incomplete Bug description: 16637 zram01 5 TINFO: make xfs filesystem on /dev/zram3 16638 Filesystem must be larger than 300MB. 16639 Usage: mkfs.xfs 16640 /* blocksize */[-b size=num] 16641 /* config file */[-c options=xxx] 16642 /* metadata */[-m crc=0|1,finobt=0|1,uuid=xxx,rmapbt=0|1,reflink=0|1, 16643 inobtcount=0|1,bigtime=0|1] 16644 /* data subvol */[-d agcount=n,agsize=n,file,name=xxx,size=num, 16645 (sunit=value,swidth=value|su=num,sw=num|noalign), 16646 sectsize=num 16647 /* force overwrite */[-f] 16648 /* inode size */[-i perblock=n|size=num,maxpct=n,attr=0|1|2, 16649 projid32bit=0|1,sparse=0|1,nrext64=0|1] 16650 /* no discard */[-K] 16651 /* log subvol */[-l agnum=n,internal,size=num,logdev=xxx,version=n 16652 sunit=value|su=num,sectsize=num,lazy-count=0|1] 16653 /* label */[-L label (maximum 12 characters)] 16654 /* naming */[-n size=num,version=2|ci,ftype=0|1] 16655 /* no-op info only */[-N] 16656 /* prototype file */[-p fname] 16657 /* quiet */[-q] 16658 /* realtime subvol */[-r extsize=num,size=num,rtdev=xxx] 16659 /* sectorsize */[-s size=num] 16660 /* version */[-V] 16661 devicename 16662is required unless -d name=xxx is given. 16663is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB), 16664 xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB). 16665is xxx (512 byte blocks). 1 zram01 5 TFAIL: failed to make xfs on /dev/zram3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2013064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
https://lists.ubuntu.com/archives/kernel-team/2023-December/147649.html ** Description changed: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: - # selftests: powerpc/ptrace: ptrace-tm-gpr - # test: ptrace_tm_gpr - # tags: git_version:unknown - # [FAIL] Test FAILED on line 94 - # GPR[14]: 1 Expected: 2 - # GPR[15]: 1 Expected: 2 - # GPR[16]: 1 Expected: 2 - # GPR[17]: 1 Expected: 2 - # GPR[18]: 1 Expected: 2 - # GPR[19]: 1 Expected: 2 - # GPR[20]: 1 Expected: 2 - # GPR[21]: 1 Expected: 2 - # GPR[22]: 1 Expected: 2 - # GPR[23]: 1 Expected: 2 - # GPR[24]: 1 Expected: 2 - # GPR[25]: 1 Expected: 2 - # GPR[26]: 1 Expected: 2 - # GPR[27]: 1 Expected: 2 - # GPR[28]: 1 Expected: 2 - # GPR[29]: 1 Expected: 2 - # GPR[30]: 1 Expected: 2 - # GPR[31]: 1 Expected: 2 - # failure: ptrace_tm_gpr - not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 + # selftests: powerpc/ptrace: ptrace-tm-gpr + # test: ptrace_tm_gpr + # tags: git_version:unknown + # [FAIL] Test FAILED on line 94 + # GPR[14]: 1 Expected: 2 + # GPR[15]: 1 Expected: 2 + # GPR[16]: 1 Expected: 2 + # GPR[17]: 1 Expected: 2 + # GPR[18]: 1 Expected: 2 + # GPR[19]: 1 Expected: 2 + # GPR[20]: 1 Expected: 2 + # GPR[21]: 1 Expected: 2 + # GPR[22]: 1 Expected: 2 + # GPR[23]: 1 Expected: 2 + # GPR[24]: 1 Expected: 2 + # GPR[25]: 1 Expected: 2 + # GPR[26]: 1 Expected: 2 + # GPR[27]: 1 Expected: 2 + # GPR[28]: 1 Expected: 2 + # GPR[29]: 1 Expected: 2 + # GPR[30]: 1 Expected: 2 + # GPR[31]: 1 Expected: 2 + # failure: ptrace_tm_gpr + not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 [Fix] * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations This patch has already landed on Jammy+. Only Focal will need this - patch. And it needs to be backported to skip tm-signal-pagefault.c - which does not exist on Focal tree. + patch. And it needs to be backported to skip changes on the + tm-signal-pagefault.c test, which does not exist on Focal tree. [Test Plan] Run the patched powerpc tests from kernel selftests: - $ sudo make TARGETS=powerpc run_tests + $ sudo make TARGETS=powerpc run_tests Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. For example the ptrace-tm-gpr test: - # selftests: powerpc/ptrace: ptrace-tm-gpr - # test: ptrace_tm_gpr - # tags: git_version:b315960-dirty - # [SKIP] Test skipped on line 116 - # skip: ptrace_tm_gpr - ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr + # selftests: powerpc/ptrace: ptrace-tm-gpr + # test: ptrace_tm_gpr + # tags: git_version:b315960-dirty + # [SKIP] Test skipped on line 116 + # skip: ptrace_tm_gpr + ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr [Where problems could occur] Change limited to testing tools, and it's just skipping unsuitable tests for specific architecture, no impact to real kernel functions. - == Original Bug Report == First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: * powerpc/ptrace:ptrace-tm-gpr FAIL * powerpc/ptrace:ptrace-tm-spd-gpr FAIL * powerpc/ptrace:ptrace-tm-tar timeout * powerpc/ptrace:ptrace-tm-spd-tar timeout * powerpc/ptrace:ptrace-tm-vsx timeout * powerpc/ptrace:ptrace-tm-spd-vsx timeout * powerpc/ptrace:ptrace-tm-spr timeout -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:unknown # [FAIL] Test FAILED on line 94 # GPR[14]: 1 Expected: 2 # GPR[15]: 1 Expected: 2 # GPR[16]: 1 Expected: 2 # GPR[17]: 1 Expected: 2 # GPR[18]: 1 Expected: 2 # GPR[19]: 1 Expected: 2 # GPR[20]: 1 Expected: 2 # GPR[21]: 1 Expected: 2 # GPR[22]: 1 Expected: 2 # GPR[23]: 1 Expected: 2 # GPR[24]: 1 Expected: 2 # GPR[25]: 1 Expected: 2 # GPR[26]: 1 Expected: 2 # GPR[27]: 1 Expected: 2 # GPR[28]: 1 Expected: 2 # GPR[29]: 1 Expected: 2 # GPR[30]: 1 Expected: 2 # GPR[31]: 1 Expected: 2 #
[Kernel-packages] [Bug 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
** Description changed: + [Impact] + The powerpc tests from kernel selftests were unable to finish properly + on Power10 VM with Focal 5.4 kernel. There will be lots of failures for + powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: + # selftests: powerpc/ptrace: ptrace-tm-gpr + # test: ptrace_tm_gpr + # tags: git_version:unknown + # [FAIL] Test FAILED on line 94 + # GPR[14]: 1 Expected: 2 + # GPR[15]: 1 Expected: 2 + # GPR[16]: 1 Expected: 2 + # GPR[17]: 1 Expected: 2 + # GPR[18]: 1 Expected: 2 + # GPR[19]: 1 Expected: 2 + # GPR[20]: 1 Expected: 2 + # GPR[21]: 1 Expected: 2 + # GPR[22]: 1 Expected: 2 + # GPR[23]: 1 Expected: 2 + # GPR[24]: 1 Expected: 2 + # GPR[25]: 1 Expected: 2 + # GPR[26]: 1 Expected: 2 + # GPR[27]: 1 Expected: 2 + # GPR[28]: 1 Expected: 2 + # GPR[29]: 1 Expected: 2 + # GPR[30]: 1 Expected: 2 + # GPR[31]: 1 Expected: 2 + # failure: ptrace_tm_gpr + not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 + + [Fix] + * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations + + This patch has already landed on Jammy+. Only Focal will need this + patch. And it needs to be backported to skip tm-signal-pagefault.c + which does not exist on Focal tree. + + [Test Plan] + Run the patched powerpc tests from kernel selftests: + $ sudo make TARGETS=powerpc run_tests + + Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. + For example the ptrace-tm-gpr test: + # selftests: powerpc/ptrace: ptrace-tm-gpr + # test: ptrace_tm_gpr + # tags: git_version:b315960-dirty + # [SKIP] Test skipped on line 116 + # skip: ptrace_tm_gpr + ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr + + [Where problems could occur] + Change limited to testing tools, and it's just skipping unsuitable + tests for specific architecture, no impact to real kernel functions. + + + == Original Bug Report == First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: - * powerpc/ptrace:ptrace-tm-gpr FAIL - * powerpc/ptrace:ptrace-tm-spd-gpr FAIL - * powerpc/ptrace:ptrace-tm-tar timeout - * powerpc/ptrace:ptrace-tm-spd-tar timeout - * powerpc/ptrace:ptrace-tm-vsx timeout - * powerpc/ptrace:ptrace-tm-spd-vsx timeout - * powerpc/ptrace:ptrace-tm-spr timeout + * powerpc/ptrace:ptrace-tm-gpr FAIL + * powerpc/ptrace:ptrace-tm-spd-gpr FAIL + * powerpc/ptrace:ptrace-tm-tar timeout + * powerpc/ptrace:ptrace-tm-spd-tar timeout + * powerpc/ptrace:ptrace-tm-vsx timeout + * powerpc/ptrace:ptrace-tm-spd-vsx timeout + * powerpc/ptrace:ptrace-tm-spr timeout -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:unknown # [FAIL] Test FAILED on line 94 # GPR[14]: 1 Expected: 2 # GPR[15]: 1 Expected: 2 # GPR[16]: 1 Expected: 2 # GPR[17]: 1 Expected: 2 # GPR[18]: 1 Expected: 2 # GPR[19]: 1 Expected: 2 # GPR[20]: 1 Expected: 2 # GPR[21]: 1 Expected: 2 # GPR[22]: 1 Expected: 2 # GPR[23]: 1 Expected: 2 # GPR[24]: 1 Expected: 2 # GPR[25]: 1 Expected: 2 # GPR[26]: 1 Expected: 2 # GPR[27]: 1 Expected: 2 # GPR[28]: 1 Expected: 2 # GPR[29]: 1 Expected: 2 # GPR[30]: 1 Expected: 2 # GPR[31]: 1 Expected: 2 # failure: ptrace_tm_gpr not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 [Fix] * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations This patch has already landed on Jammy+. Only Focal will need this patch. And it needs to be backported to skip changes on the tm-signal-pagefault.c test, which does not exist on Focal tree. [Test Plan] Run the patched powerpc tests from kernel selftests: $ sudo make TARGETS=powerpc run_tests Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. For example the ptrace-tm-gpr test: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:b315960-dirty # [SKIP] Test skipped on line 116 # skip: ptrace_tm_gpr ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr [Where problems could occur] Change limited to testing tools, and it's just
[Kernel-packages] [Bug 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Focal) 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/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: * powerpc/ptrace:ptrace-tm-gpr FAIL * powerpc/ptrace:ptrace-tm-spd-gpr FAIL * powerpc/ptrace:ptrace-tm-tar timeout * powerpc/ptrace:ptrace-tm-spd-tar timeout * powerpc/ptrace:ptrace-tm-vsx timeout * powerpc/ptrace:ptrace-tm-spd-vsx timeout * powerpc/ptrace:ptrace-tm-spr timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2032641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837037] Re: memcg_move_charge_at_immigrate_test from ubuntu_ltp_controllers failed (shmget() failed: Invalid argument)
** Summary changed: - memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp + memcg_move_charge_at_immigrate_test from ubuntu_ltp_controllers failed (shmget() failed: Invalid argument) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837037 Title: memcg_move_charge_at_immigrate_test from ubuntu_ltp_controllers failed (shmget() failed: Invalid argument) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Won't Fix Bug description: Similar to bug 1837035 This memcg_move_charge_at_immigrate_test test failed on an i386 node "pepe" with Disco kernel. It failed with: memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up <<>> tag=memcg_move_charge_at_immigrate stime=1563448078 cmdline="memcg_move_charge_at_immigrate_test.sh" contacts="" analysis=exit <<>> memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 2162 memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm up: 2162 memcg_move_charge_at_immigrate_test 1 TPASS: rss is 0 as expected memcg_move_charge_at_immigrate_test 2 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 3 TPASS: rss is 135168 as expected memcg_move_charge_at_immigrate_test 4 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up memcg_move_charge_at_immigrate_test 6 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 6 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 6 TINFO: Warming up pid: 2207 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 6 TFAIL: Process 2207 exited with 1 after warm up memcg_move_charge_at_immigrate_test 7 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 7 TINFO: Running memcg_process --mmap-anon --shm -s 135168 memcg_move_charge_at_immigrate_test 7 TINFO: Warming up pid: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 7 TFAIL: Process exited with 1 after warm up <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=2 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_move_charge_at_immigrate memcg_move_charge_at_immigrate_test.sh" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 18 10:01 seq crw-rw 1 root audio 116, 33 Jul 18 10:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error:
[Kernel-packages] [Bug 1839143] Re: cve test from ubuntu_ltp will failed to fork on B-KVM
We have test split out to ubuntu-ltp-cve, and this issue does not exist anymore. ** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-cve ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839143 Title: cve test from ubuntu_ltp will failed to fork on B-KVM Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Bug description: Not sure if this has something to do with another timeout issue in controller test, the test will not get started at all: 08/06 06:14:10 INFO |ubuntu_ltp:0088| Checking virt-what to see if we need to set LTP_TIMEOUT_MUL for memcg_test_3... 08/06 06:14:10 INFO |ubuntu_ltp:0091| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL>1 (lp:1836694) for memcg_test_3 08/06 06:29:32 ERROR| test:0414| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 830, in _call_test_function raise error.UnhandledTestFail(e) UnhandledTestFail: Unhandled OSError: [Errno 11] Resource temporarily unavailable Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ltp/ubuntu_ltp.py", line 103, in run_once utils.run(cmd, ignore_status=True, verbose=False) File "/home/ubuntu/autotest/client/shared/utils.py", line 914, in run stderr_level=get_stderr_level(stderr_is_expected)),), File "/home/ubuntu/autotest/client/shared/utils.py", line 128, in __init__ stdin=stdin) File "/usr/lib/python2.7/subprocess.py", line 394, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 938, in _execute_child self.pid = os.fork() OSError: [Errno 11] Resource temporarily unavailable ~ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1039-kvm 4.15.0-1039.39 ProcVersionSignature: User Name 4.15.0-1039.39-kvm 4.15.18 Uname: Linux 4.15.0-1039-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Tue Aug 6 11:51:21 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942612] Re: cve-2017-7616 in cve from ubuntu_ltp failed on bionic with linux/linux-hwe-5.4 on i386
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-cve -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942612 Title: cve-2017-7616 in cve from ubuntu_ltp failed on bionic with linux/linux-hwe-5.4 on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Bug description: ubuntu_ltp.cve cve-2017-7616 testcase output: 16:10:41 DEBUG| [stdout] startup='Sun Aug 29 15:53:35 2021' 16:10:41 DEBUG| [stdout] tst_test.c:1346: TINFO: Timeout per run is 0h 05m 00s 16:10:41 DEBUG| [stdout] set_mempolicy05.c:66: TINFO: stack pattern is in 0xbf996ccc-0xbf9970cc 16:10:41 DEBUG| [stdout] set_mempolicy05.c:111: TFAIL: set_mempolicy should fail with EFAULT or EINVAL, instead returned 38 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cf01fb9985e8 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] HINT: You _MAY_ be vulnerable to CVE(s), see: 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-CVE-2017-7616 16:10:41 DEBUG| [stdout] 16:10:41 DEBUG| [stdout] Summary: 16:10:41 DEBUG| [stdout] passed 0 16:10:41 DEBUG| [stdout] failed 1 16:10:41 DEBUG| [stdout] broken 0 16:10:41 DEBUG| [stdout] skipped 0 16:10:41 DEBUG| [stdout] warnings 0 16:10:41 DEBUG| [stdout] tag=cve-2017-7616 stime=1630252415 dur=0 exit=exited stat=1 core=no cu=0 cs=0 This is not a regression as this is a new testcase which runs only on 32-bit systems (i386 and powerpc). This test was added by ltp commit 6feed808040a86c54b7ab2dd3839fefd819a42cc (Add set_mempolicy05, CVE-2017-7616). The commit sha1 (cf01fb9985e8deb25ccf0ea54d916b8871ae0e62 - mm/mempolicy.c: fix error handling in set_mempolicy and mbind.) which fixes this CVE according to https://ubuntu.com/security/CVE-2017-7616, was applied upstream for v4.11-rc6, so both focal/linux and bionic/linux supposedly contain the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1942612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943627] Re: Controllers test in ubuntu_ltp fails to mount on /dev/cpuctl
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1943627 Title: Controllers test in ubuntu_ltp fails to mount on /dev/cpuctl Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Found on Focal linux-gcp 5.11.0-1019.21 on g1-small instance. The tests are not able to mount on /dev/cpuctl which is causing cpu controller testing, latency tests, and cpuctl_test_fj to fail, seems to be only on g1-small instances. This error has been observed in previous cycles and is not a new regression. 20:09:23 DEBUG| [stdout] startup='Mon Sep 13 20:07:02 2021' 20:09:23 DEBUG| [stdout] TEST 1: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 3: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 4: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 5: CPU CONTROLLER TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 97: /opt/ltp/output/cpuctl_results_stress-678.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 6: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 7: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TEST 8: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 120: /opt/ltp/output/cpuctl_results_stress-9.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 9: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] /opt/ltp/testcases/bin/run_cpuctl_stress_test.sh: line 127: /opt/ltp/output/cpuctl_results_stress-10.txt: No such file or directory 20:09:23 DEBUG| [stdout] TEST 10: CPU CONTROLLER STRESS TESTING 20:09:23 DEBUG| [stdout] RUNNING SETUP. 20:09:23 DEBUG| [stdout] ERROR: Could not mount cgroup filesystem on /dev/cpuctl..Exiting test 20:09:23 DEBUG| [stdout] Cleanup called 20:09:23 DEBUG| [stdout] cat: /dev/cpuctl/group_def/tasks: No such file or directory 20:09:23 DEBUG| [stdout] TINFO Running cpuctl Latency Test 1 20:09:23 DEBUG| [stdout] TINFOThe latency check task started 20:09:23 DEBUG| [stdout] FAIL The Latency test 1 failed 20:09:23 DEBUG| [stdout] Max latency observed = 123838 in Iteration 0 20:09:23 DEBUG| [stdout] The results FAIL is just intuitive and not exact failure. Please look at cpuctl_testplan.txt in the test directory. 20:09:23 DEBUG| [stdout] Task 763103 exited abnormally with return value: 1 20:09:23 DEBUG| [stdout] TBROK Test could'nt execute for expected duration 20:09:23 DEBUG| [stdout] Doing cleanup 20:09:23 DEBUG| [stdout] Cleanup done for latency test 1 20:09:23 DEBUG|
[Kernel-packages] [Bug 1853798] Re: umip_basic_test in kernel_misc from ubuntu_ltp failed on D-Oracle / B-oracle-4.15
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-kernel-misc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1853798 Title: umip_basic_test in kernel_misc from ubuntu_ltp failed on D-Oracle / B-oracle-4.15 Status in ubuntu-kernel-tests: New Status in linux-signed-oracle package in Ubuntu: New Bug description: <<>> tag=umip_basic_test stime=1574662675 cmdline="umip_basic_test" contacts="" analysis=exit <<>> tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1005-oracle' incrementing stop tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s umip_basic_test.c:158: INFO: cpuinfo contains umip, CPU supports umip umip_basic_test.c:40: INFO: TEST sgdt, sgdt result save at [0x7ffdd514086e] umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4 umip_basic_test.c:135: PASS: Got SIGSEGV umip_basic_test.c:50: INFO: TEST sidt, sidt result save at [0x7ffdd514086e] umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4 umip_basic_test.c:135: PASS: Got SIGSEGV umip_basic_test.c:59: INFO: TEST sldt, sldt result save at [0x7ffdd5140860] umip_basic_test.c:135: PASS: Got SIGSEGV umip_basic_test.c:68: INFO: TEST smsw, smsw result save at [0x7ffdd5140860] umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4 umip_basic_test.c:139: FAIL: Didn't receive SIGSEGV, child exited with exited with 0 umip_basic_test.c:77: INFO: TEST str, str result save at [0x7ffdd5140860] umip_basic_test.c:135: PASS: Got SIGSEGV Summary: passed 4 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9 ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21 Uname: Linux 5.0.0-1005-oracle x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Nov 25 06:18:04 2019 SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943732] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-kernel-misc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943732 Title: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: Testcase cpufreq_boost from ubuntu_ltp.kernel_misc failed with focal/linux 5.4.0-85.95 on the P9 node baltar. 13:50:50 DEBUG| [stdout] startup='Wed Sep 8 13:42:39 2021' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : found 'acpi_cpufreq' driver, sysfs knob '/sys /devices/system/cpu/cpufreq/boost' 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : maximum speed is 380 KHz 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost enabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2006 ms 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost disabled 13:50:50 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 2027 ms 13:50:50 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189: compare time spent with and without boost (-2%) 13:50:50 DEBUG| [stdout] tag=cpufreq_boost stime=1631108559 dur=4 exit=exited stat=1 core=no cu=404 cs=2 This is not a regression as it has been failing since older versions (at least since 5.4.0-75.84). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947016] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux-realtime
** Tags removed: ubuntu-kernel-selftests ubuntu-ltp ** Tags added: ubuntu-ltp-kernel-misc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947016 Title: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux- realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Jammy: Confirmed Bug description: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux- realtime 5.11.0-27.28 on amd64 nodes. This test seems to be flaky as it doesn't fail consistently. 07:34:27 DEBUG| [stdout] startup='Tue Oct 12 07:21:09 2021' 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : found 'intel_pstate' driver, sysfs knob '/sys/devices/system/cpu/intel_pstate/no_turbo' 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : maximum speed is 300 KHz 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost enabled 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 1588 ms 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : load CPU0 with boost disabled 07:34:27 DEBUG| [stdout] cpufreq_boost0 TINFO : elapsed time is 1543 ms 07:34:27 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189: compare time spent with and without boost (-2%) 07:34:27 DEBUG| [stdout] tag=cpufreq_boost stime=1634023269 dur=4 exit=exited stat=1 core=no cu=303 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1947016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898633] Re: timer_settime01 from ubuntu_ltp_syscalls failed on bionic /aws-4.15 on c5.metal
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-syscalls -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1898633 Title: timer_settime01 from ubuntu_ltp_syscalls failed on bionic /aws-4.15 on c5.metal Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Invalid Bug description: 21367.09/25 08:38:06 DEBUG| utils:0153| [stdout] startup='Fri Sep 25 08:37:00 2020' 21368.09/25 08:38:06 DEBUG| utils:0153| [stdout] tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s 21369.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:85: TINFO: Testing variant: syscall with old kernel spec 21370.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:96: TINFO: Testing for general initialization: 21371.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME) passed 21372.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_MONOTONIC) passed 21373.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_PROCESS_CPUTIME_ID) passed 21374.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_THREAD_CPUTIME_ID) passed 21375.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME) passed 21376.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME_ALARM) passed 21377.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME_ALARM) passed 21378.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_TAI) passed 21379.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:96: TINFO: Testing for setting old_value: 21380.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME) passed 21381.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_MONOTONIC) passed 21382.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_PROCESS_CPUTIME_ID) passed 21383.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_THREAD_CPUTIME_ID) passed 21384.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME) passed 21385.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME_ALARM) passed 21386.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME_ALARM) passed 21387.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_TAI) passed 21388.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:96: TINFO: Testing for using periodic timer: 21389.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME) passed 21390.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_MONOTONIC) passed 21391.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_PROCESS_CPUTIME_ID) passed 21392.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_THREAD_CPUTIME_ID) passed 21393.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME) passed 21394.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_BOOTTIME_ALARM) passed 21395.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME_ALARM) passed 21396.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_TAI) passed 21397.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:96: TINFO: Testing for using absolute time: 21398.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_REALTIME) passed 21399.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:160: TFAIL: timer_gettime(CLOCK_MONOTONIC) reported bad values (0: 5034): SUCCESS (0) 21400.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS: timer_settime(CLOCK_MONOTONIC) passed 21401.09/25 08:38:06 DEBUG| utils:0153| [stdout] timer_settime01.c:170: TPASS:
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-cve -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux-ibm source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-ibm source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-ibm source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-ibm source package in Impish: Won't Fix Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs
[Kernel-packages] [Bug 1848473] Re: cgroup_fj_stress_* in controllers from ubuntu_ltp failed with dir creation / fork on B-KVM
I didn't see this issue in recent B-kvm and I didn't see this failure on the only hinted f-aws. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1848473 Title: cgroup_fj_stress_* in controllers from ubuntu_ltp failed with dir creation / fork on B-KVM Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Invalid Bug description: It looks like the test failed with cannot fork, and the following test will failed with mkdir. Take this one for example: tag=cgroup_fj_stress_perf_event_2_9_each stime=1571098406 dur=7 exit=exited stat=2 core=no cu=451 cs=280 ... ... cgroup_fj_stress_perf_event_2_9_each 1 TINFO: Attaching task 1326 to /sys/fs/cgroup/perf_event/ltp/2/1/1/2/1/2/1 cgroup_fj_stress_perf_event_2_9_each 1 TINFO: Attaching task 1329 to /sys/fs/cgroup/perf_event/ltp/2/1/1/2/1/2/1/1 /opt/ltp/testcases/bin/cgroup_fj_stress.sh: 53: /opt/ltp/testcases/bin/cgroup_fj_stress.sh: Cannot fork tag=cgroup_fj_stress_perf_event_10_3_each stime=1571098419 dur=2 exit=exited stat=2 core=no cu=134 cs=84 startup='Tue Oct 15 00:13:39 2019' cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Subsystem perf_event is mounted at /sys/fs/cgroup/perf_event cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Creating subgroups ... mkdir: cannot create directory ‘/sys/fs/cgroup/perf_event/ltp’: File exists cgroup_fj_stress_perf_event_10_3_each 1 TBROK: mkdir /sys/fs/cgroup/perf_event/ltp failed cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Removing all ltp subgroups... Failed test cases sorted alphabetically: cgroup_fj_stress_blkio_10_3_each-mkdir cgroup_fj_stress_blkio_2_9_each -cannot fork cgroup_fj_stress_cpu_10_3_each -mkdir cgroup_fj_stress_cpu_2_9_each -cannot fork cgroup_fj_stress_cpuacct_10_3_each -mkdir cgroup_fj_stress_cpuacct_2_9_each -cannot fork cgroup_fj_stress_cpuset_10_3_each -mkdir cgroup_fj_stress_cpuset_2_9_each-cannot fork cgroup_fj_stress_devices_10_3_each -mkdir cgroup_fj_stress_devices_2_9_each -cannot fork cgroup_fj_stress_freezer_10_3_each -mkdir cgroup_fj_stress_freezer_2_9_each -cannot fork cgroup_fj_stress_hugetlb_10_3_each -mkdir cgroup_fj_stress_hugetlb_2_9_each -cannot fork cgroup_fj_stress_memory_10_3_each -mkdir cgroup_fj_stress_memory_2_9_each-cannot fork cgroup_fj_stress_net_cls_10_3_each -mkdir cgroup_fj_stress_net_cls_2_9_each -cannot fork cgroup_fj_stress_net_prio_10_3_each -mkdir cgroup_fj_stress_net_prio_2_9_each -cannot fork cgroup_fj_stress_perf_event_10_3_each -mkdir cgroup_fj_stress_perf_event_2_9_each-cannot fork To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839144] Re: controller test from ubuntu_ltp will timeout B-KVM / B-gke
We can have ubuntu_ltp_controllers finish on B-kvm and I didn't see B-gke-4.15 in recent cycles. Considered that we don't have this issue in our hint database I will just close this. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid ** Changed in: linux-gke (Ubuntu) Status: New => Invalid ** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/1839144 Title: controller test from ubuntu_ltp will timeout B-KVM / B-gke Status in ubuntu-kernel-tests: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Bug description: Test timeout with 2hrs threshold. Steps to reproduce: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install sudo /opt/ltp/runltp -f /opt/ltp/runtest/controller This needs to be executed manually to see where is the culprit, and how long will it take. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1039-kvm 4.15.0-1039.39 ProcVersionSignature: User Name 4.15.0-1039.39-kvm 4.15.18 Uname: Linux 4.15.0-1039-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Tue Aug 6 11:55:48 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848473] Re: cgroup_fj_stress_* in controllers from ubuntu_ltp failed with dir creation / fork on B-KVM
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1848473 Title: cgroup_fj_stress_* in controllers from ubuntu_ltp failed with dir creation / fork on B-KVM Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Invalid Bug description: It looks like the test failed with cannot fork, and the following test will failed with mkdir. Take this one for example: tag=cgroup_fj_stress_perf_event_2_9_each stime=1571098406 dur=7 exit=exited stat=2 core=no cu=451 cs=280 ... ... cgroup_fj_stress_perf_event_2_9_each 1 TINFO: Attaching task 1326 to /sys/fs/cgroup/perf_event/ltp/2/1/1/2/1/2/1 cgroup_fj_stress_perf_event_2_9_each 1 TINFO: Attaching task 1329 to /sys/fs/cgroup/perf_event/ltp/2/1/1/2/1/2/1/1 /opt/ltp/testcases/bin/cgroup_fj_stress.sh: 53: /opt/ltp/testcases/bin/cgroup_fj_stress.sh: Cannot fork tag=cgroup_fj_stress_perf_event_10_3_each stime=1571098419 dur=2 exit=exited stat=2 core=no cu=134 cs=84 startup='Tue Oct 15 00:13:39 2019' cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Subsystem perf_event is mounted at /sys/fs/cgroup/perf_event cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Creating subgroups ... mkdir: cannot create directory ‘/sys/fs/cgroup/perf_event/ltp’: File exists cgroup_fj_stress_perf_event_10_3_each 1 TBROK: mkdir /sys/fs/cgroup/perf_event/ltp failed cgroup_fj_stress_perf_event_10_3_each 1 TINFO: Removing all ltp subgroups... Failed test cases sorted alphabetically: cgroup_fj_stress_blkio_10_3_each-mkdir cgroup_fj_stress_blkio_2_9_each -cannot fork cgroup_fj_stress_cpu_10_3_each -mkdir cgroup_fj_stress_cpu_2_9_each -cannot fork cgroup_fj_stress_cpuacct_10_3_each -mkdir cgroup_fj_stress_cpuacct_2_9_each -cannot fork cgroup_fj_stress_cpuset_10_3_each -mkdir cgroup_fj_stress_cpuset_2_9_each-cannot fork cgroup_fj_stress_devices_10_3_each -mkdir cgroup_fj_stress_devices_2_9_each -cannot fork cgroup_fj_stress_freezer_10_3_each -mkdir cgroup_fj_stress_freezer_2_9_each -cannot fork cgroup_fj_stress_hugetlb_10_3_each -mkdir cgroup_fj_stress_hugetlb_2_9_each -cannot fork cgroup_fj_stress_memory_10_3_each -mkdir cgroup_fj_stress_memory_2_9_each-cannot fork cgroup_fj_stress_net_cls_10_3_each -mkdir cgroup_fj_stress_net_cls_2_9_each -cannot fork cgroup_fj_stress_net_prio_10_3_each -mkdir cgroup_fj_stress_net_prio_2_9_each -cannot fork cgroup_fj_stress_perf_event_10_3_each -mkdir cgroup_fj_stress_perf_event_2_9_each-cannot fork To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837037] Re: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837037 Title: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Won't Fix Bug description: Similar to bug 1837035 This memcg_move_charge_at_immigrate_test test failed on an i386 node "pepe" with Disco kernel. It failed with: memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up <<>> tag=memcg_move_charge_at_immigrate stime=1563448078 cmdline="memcg_move_charge_at_immigrate_test.sh" contacts="" analysis=exit <<>> memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 2162 memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm up: 2162 memcg_move_charge_at_immigrate_test 1 TPASS: rss is 0 as expected memcg_move_charge_at_immigrate_test 2 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 3 TPASS: rss is 135168 as expected memcg_move_charge_at_immigrate_test 4 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up memcg_move_charge_at_immigrate_test 6 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 6 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 6 TINFO: Warming up pid: 2207 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 6 TFAIL: Process 2207 exited with 1 after warm up memcg_move_charge_at_immigrate_test 7 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 7 TINFO: Running memcg_process --mmap-anon --shm -s 135168 memcg_move_charge_at_immigrate_test 7 TINFO: Warming up pid: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 7 TFAIL: Process exited with 1 after warm up <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=2 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_move_charge_at_immigrate memcg_move_charge_at_immigrate_test.sh" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 18 10:01 seq crw-rw 1 root audio 116, 33 Jul 18 10:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 18 11:16:36 2019 IwConfig: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1916046] Re: cve-2020-29373 in cve from ubuntu_ltp failed
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp0cve ** Tags removed: ubuntu-ltp0cve ** Tags added: ubuntu-ltp-cve -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916046 Title: cve-2020-29373 in cve from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Not a regression, this is a new test added Feb 8, 2021: https://github.com/linux-test- project/ltp/commit/c4f669f13106862b6d8be38adf7825ae00ca7ac5 The log shows: 13260.02/08 21:37:31 DEBUG| utils:0153| [stdout] startup='Mon Feb 8 21:37:30 2021' 13261.02/08 21:37:31 DEBUG| utils:0153| [stdout] tst_test.c:1261: TINFO: Timeout per run is 0h 05m 00s 13262.02/08 21:37:31 DEBUG| utils:0153| [stdout] io_uring02.c:148: TFAIL: Write outside chroot succeeded. 13263.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13264.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 13265.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13266.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9392a27d88b9 13267.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff002b30181d 13268.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13269.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be vulnerable to CVE(s), see: 13270.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13271.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29373 13272.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13273.02/08 21:37:31 DEBUG| utils:0153| [stdout] Summary: 13274.02/08 21:37:31 DEBUG| utils:0153| [stdout] passed 0 13275.02/08 21:37:31 DEBUG| utils:0153| [stdout] failed 1 13276.02/08 21:37:31 DEBUG| utils:0153| [stdout] broken 0 13277.02/08 21:37:31 DEBUG| utils:0153| [stdout] skipped 0 13278.02/08 21:37:31 DEBUG| utils:0153| [stdout] warnings 0 13279.02/08 21:37:31 DEBUG| utils:0153| [stdout] tag=cve-2020-29373 stime=1612820250 dur=0 exit=exited stat=1 core=no cu=0 As of Feb 18, 2021, this CVE is not mitigated yet: https://ubuntu.com/security/CVE-2020-29373 Seen with linux-kvm 5.4.0-1033.34. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1916046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837005] Re: cve-2015-3290 in cve from ubuntu_ltp failed with B/D-i386
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-cve -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837005 Title: cve-2015-3290 in cve from ubuntu_ltp failed with B/D-i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Bug description: This issue was only spotted on an i386 node "pepe" with Disco kernel, passed with other arch with Disco. On B/C i386, the CVE test was not successfully executed, failed with Resource temporarily unavailable. Will need to verify this manually. Test report: <<>> tag=cve-2015-3290 stime=1563431630 cmdline="cve-2015-3290" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 03m 00s cve-2015-3290.c:407: INFO: attempting to corrupt nested NMI stack state cve-2015-3290.c:460: FAIL: corrupted NMI stack Summary: passed 0 failed 1 skipped 0 warnings 0 syslog output: 06:33:50 pepe kernel: [ 6042.144077] LTP: starting cve-2015-3290 06:33:50 pepe kernel: [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79250 06:33:50 pepe kernel: [ 6042.159531] show_signal: 16 callbacks suppressed 06:33:50 pepe kernel: [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef sp:b7d43280 error:800 06:33:50 pepe AutotestCrashHandler: Application cve-2015-3290, PID 7760 crashed 06:33:50 pepe AutotestCrashHandler: Writing core files to ['/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760'] 06:33:50 pepe AutotestCrashHandler: Could not determine from which application core file /home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760/core is from ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-20-generic 5.0.0-20.21 ProcVersionSignature: User Name 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 18 04:53 seq crw-rw 1 root audio 116, 33 Jul 18 04:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [ 6042.144077] LTP: starting cve-2015-3290 [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79250 [ 6042.159531] show_signal: 16 callbacks suppressed [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef sp:b7d43280 error:800 Date: Thu Jul 18 06:36:51 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed (shmget() failed: Invalid argument, Process ### exited with 1 after warm up)
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1837035 Title: memcg_stat_rss from controllers in ubuntu_ltp failed (shmget() failed: Invalid argument, Process ### exited with 1 after warm up) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Bug description: This issue was spotted on an i386 node "pepe" with Disco kernel, it failed with: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up <<>> tag=memcg_stat_rss stime=1563448062 cmdline="memcg_stat_rss.sh" contacts="" analysis=exit <<>> memcg_stat_rss 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 1 TINFO: Warming up pid: 1784 memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784 memcg_stat_rss 1 TPASS: rss is 135168 as expected memcg_stat_rss 2 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 2 TINFO: Warming up pid: 1804 memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804 memcg_stat_rss 2 TPASS: rss is 0 as expected memcg_stat_rss 3 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096 memcg_stat_rss 3 TINFO: Warming up pid: 1825 memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825 memcg_stat_rss 3 TPASS: rss is 0 as expected memcg_stat_rss 4 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 4 TINFO: Warming up pid: 1845 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up memcg_stat_rss 5 TINFO: Starting test 5 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168 memcg_stat_rss 5 TINFO: Warming up pid: 1858 memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858 memcg_stat_rss 5 TPASS: rss is 135168 as expected memcg_stat_rss 6 TINFO: Starting test 6 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 6 TINFO: Warming up pid: 1878 memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878 memcg_stat_rss 6 TPASS: rss is 135168 as expected memcg_stat_rss 7 TPASS: rss is 0 as expected memcg_stat_rss 8 TINFO: Starting test 7 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 8 TINFO: Warming up pid: 1901 memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901 memcg_stat_rss 8 TPASS: rss is 0 as expected memcg_stat_rss 9 TPASS: rss is 0 as expected memcg_stat_rss 10 TINFO: Starting test 8 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096 memcg_stat_rss 10 TINFO: Warming up pid: 1925 memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925 memcg_stat_rss 10 TPASS: rss is 0 as expected memcg_stat_rss 11 TPASS: rss is 0 as expected memcg_stat_rss 12 TINFO: Starting test 9 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 12 TINFO: Warming up pid: 1948 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 12
[Kernel-packages] [Bug 1830360] Re: cpuset_load_balance from controller test suite in LTP failed
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830360 Title: cpuset_load_balance from controller test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:24:55 2019' cpuset_load_balance 1 TINFO: general group load balance test cpuset_load_balance 1 TINFO: root group info: cpuset_load_balance 1 TINFO: sched load balance: 0 cpuset_load_balance 1 TINFO: general group info: cpuset_load_balance 1 TINFO: cpus: - cpuset_load_balance 1 TINFO: sched load balance: 1 cpuset_load_balance 1 TFAIL: load balance test failed. cpuset_load_balance 3 TINFO: general group load balance test cpuset_load_balance 3 TINFO: root group info: cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TINFO: general group info: cpuset_load_balance 3 TINFO: cpus: 1 cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TFAIL: load balance test failed. cpuset_load_balance 5 TINFO: general group load balance test cpuset_load_balance 5 TINFO: root group info: cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TINFO: general group info: cpuset_load_balance 5 TINFO: cpus: - cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TFAIL: load balance test failed. cpuset_load_balance 7 TINFO: general group load balance test cpuset_load_balance 7 TINFO: root group info: cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TINFO: general group info: cpuset_load_balance 7 TINFO: cpus: 1 cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TFAIL: load balance test failed. cpuset_load_balance 9 TINFO: general group load balance test cpuset_load_balance 9 TINFO: root group info: cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TINFO: general group info: cpuset_load_balance 9 TINFO: cpus: 1,2 cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TFAIL: load balance test failed. cpuset_load_balance 11 TINFO: general group load balance test cpuset_load_balance 11 TINFO: root group info: cpuset_load_balance 11 TINFO: sched load balance: 0 cpuset_load_balance 11 TINFO: general group info: cpuset_load_balance 11 TINFO: cpus: 1,2 cpuset_load_balance 11 TINFO: sched load balance: 1 cpuset_load_balance 11 TFAIL: load balance test failed. cpuset_load_balance 13 TINFO: general group load balance test cpuset_load_balance 13 TINFO: root group info: cpuset_load_balance 13 TINFO: sched load balance: 0 cpuset_load_balance 13 TINFO: general group info: cpuset_load_balance 13 TINFO: cpus: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39 cpuset_load_balance 13 TINFO: sched load balance: 1 cpuset_load_balance 13 TFAIL: load balance test failed. cpuset_load_balance 15 TINFO: general group load balance test cpuset_load_balance 15 TINFO: root group info: cpuset_load_balance 15 TINFO: sched load balance: 0 cpuset_load_balance 15 TINFO: general group1 info: cpuset_load_balance 15 TINFO: cpus: 1 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: general group2 info: cpuset_load_balance 15 TINFO: cpus: 0 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: CPU hotplug: none cpuset_load_balance 15 TFAIL: load balance test failed. cpuset_load_balance 17 TINFO: general group load balance test cpuset_load_balance 17 TINFO: root group info: cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: general group1 info: cpuset_load_balance 17 TINFO: cpus: 1,2 cpuset_load_balance 17 TINFO: sched load balance: 1 cpuset_load_balance 17 TINFO: general group2 info: cpuset_load_balance 17 TINFO: cpus: 0-3 cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: CPU hotplug: none cpuset_load_balance 17 TFAIL: load balance test failed. cpuset_load_balance 19 TINFO: general group load balance test cpuset_load_balance 19 TINFO: root group info: cpuset_load_balance 19 TINFO: sched load balance: 0 cpuset_load_balance 19 TINFO: general group1 info: cpuset_load_balance 19 TINFO: cpus: 1,2 cpuset_load_balance 19 TINFO: sched load balance: 1 cpuset_load_balance 19
[Kernel-packages] [Bug 1830361] Re: cpuset_sched_domains from controller test suite in LTP failed
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830361 Title: cpuset_sched_domains from controller test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:24:26 2019' cpuset_sched_domains 1 TINFO: root group load balance test cpuset_sched_domains 1 TINFO: sched load balance: 0 cpuset_sched_domains 1 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 1 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 1 TFAIL: partition sched domains failed. cpuset_sched_domains 3 TINFO: root group load balance test cpuset_sched_domains 3 TINFO: sched load balance: 1 cpuset_sched_domains 3 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 3 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 3 TFAIL: partition sched domains failed. cpuset_sched_domains 5 TINFO: root group load balance test cpuset_sched_domains 5 TINFO: sched load balance: 0 cpuset_sched_domains 5 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 5 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 5 TFAIL: partition sched domains failed. cpuset_sched_domains 7 TINFO: root group load balance test cpuset_sched_domains 7 TINFO: sched load balance: 0 cpuset_sched_domains 7 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 7 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 7 TFAIL: partition sched domains failed. cpuset_sched_domains 9 TINFO: root group load balance test cpuset_sched_domains 9 TINFO: sched load balance: 1 cpuset_sched_domains 9 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 9 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 9 TFAIL: partition sched domains failed. cpuset_sched_domains 11 TINFO: root group load balance test cpuset_sched_domains 11 TINFO: sched load balance: 1 cpuset_sched_domains 11 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 11 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 11 TFAIL: partition sched domains failed. cpuset_sched_domains 13 TINFO: general group load balance test cpuset_sched_domains 13 TINFO: root group info: cpuset_sched_domains 13 TINFO: sched load balance: 0 cpuset_sched_domains 13 TINFO: general group info: cpuset_sched_domains 13 TINFO: cpus: - cpuset_sched_domains 13 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 13 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 13 TFAIL: partition sched domains failed. cpuset_sched_domains 15 TINFO: general group load balance test cpuset_sched_domains 15 TINFO: root group info: cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_sched_domains 15 TINFO: general group info: cpuset_sched_domains 15 TINFO: cpus: 1 cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 15 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 15 TFAIL: partition sched domains failed. cpuset_sched_domains 17 TINFO: general group load balance test cpuset_sched_domains 17 TINFO: root group info: cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_sched_domains 17 TINFO: general group info: cpuset_sched_domains 17 TINFO: cpus: - cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 17 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 17 TFAIL: partition sched domains failed. cpuset_sched_domains 19 TINFO: general group load balance test
[Kernel-packages] [Bug 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node)
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830585 Title: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Focal: New Status in linux-azure source package in Focal: New Status in linux source package in Hirsute: Won't Fix Status in linux-azure source package in Hirsute: Won't Fix Bug description: Test failed with: cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). <<>> tag=cpuset_memory_spread stime=1558937747 cmdline=" cpuset_memory_spread_testset.sh" contacts="" analysis=exit <<>> 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 0.0993112 s, 1.1 GB/s cpuset_memory_spread 1 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 3 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 5 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). cpuset_memory_spread 9 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 11 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 13 TPASS: Cpuset memory spread page test succeeded. <<>> initiation_status="ok" duration=10 termination_type=exited termination_id=1 corefile=no cutime=364 cstime=383 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 05:39 seq crw-rw 1 root audio 116, 33 May 27 05:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon May 27 06:16:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64)
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64) Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830678] Re: netns_sysfs from containers test suite in LTP failed with KVM kernel
We have config_dummy enabled for newer KVM kernels. And the test is capable of detecting missing config now. https://github.com/linux-test- project/ltp/commit/5059889abdb61a53d2598cd0e52147af22e3d2c3 ** Changed in: ubuntu-kernel-tests Status: Confirmed => Fix Released ** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-stable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1830678 Title: netns_sysfs from containers test suite in LTP failed with KVM kernel Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Invalid Bug description: <<>> tag=netns_sysfs stime=1559024934 cmdline="netns_sysfs.sh" contacts="" analysis=exit <<>> incrementing stop RTNETLINK answers: Operation not supported netns_sysfs 1 TBROK: failed to add a new (host) dummy device <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=1 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35 ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18 Uname: Linux 4.15.0-1035-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 28 06:22:51 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046085] Re: Problem with driver for Realtek 8852be Wi-Fi pci card
Close this as per reporter's comment in #5. ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2046085 Title: Problem with driver for Realtek 8852be Wi-Fi pci card Status in linux-firmware package in Ubuntu: Invalid Bug description: I am not sure that this shall come into Ubuntu bug tracker, but correct me if I am wrong. I have a fan-less media pc that has PCI WI-FI adapter rtl8852be. I know this chipset has support in HWE Ubuntu kernel but for some reason, firmware for it still not being recognized. First I tried to make it work with 6.2 generic HWE kernel and the only strings I have in dmesg: [ 15.034783] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 15.061504] rtw89_8852be :03:00.0: no suitable firmware found [ 15.061543] rtw89_8852be :03:00.0: failed to recognize firmware [ 15.061557] rtw89_8852be :03:00.0: failed to setup chip information [ 15.075283] rtw89_8852be: probe of :03:00.0 failed with error -2 Then I tried to use linux-image-6.5.0-1009-oem kernel and get a little bit more info: [ 16.501540] rtw89_8852be :03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 16.503083] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 16.567443] rtw89_8852be :03:00.0: xtal si not ready(R): offset=41 [ 16.567470] rtw89_8852be :03:00.0: no suitable firmware found [ 16.567494] rtw89_8852be :03:00.0: failed to recognize firmware [ 16.567509] rtw89_8852be :03:00.0: failed to setup chip information [ 16.572860] rtw89_8852be: probe of :03:00.0 failed with error -2 I suspect my PCI WIFI card has different subvendor ID and subdevice ID compare to the popular ones: Lenovo laptops have 8852be has PCI 10ec:b852:17aa:4853 HP laptops have 8852be has PCI 10ec:b852:103c:88e3 Mine is: PCI 10ec:b852:10ec:b852 Any suggestions are welcomed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.23 ProcVersionSignature: Ubuntu 6.5.0-1009.10-oem 6.5.3 Uname: Linux 6.5.0-1009-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Dec 10 21:46:40 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.4 InstallationDate: Installed on 2023-09-15 (86 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SDZ X133 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1009-oem root=UUID=cd870d97-e484-43d5-aafa-2ba1ec68a7a8 ro cpufreq.default_governor=powersave RelatedPackageVersions: linux-restricted-modules-6.5.0-1009-oem N/A linux-backports-modules-6.5.0-1009-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2023 dmi.bios.release: 1.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: PC_STICK_8G_D8R2 dmi.board.asset.tag: Default string dmi.board.name: X133 dmi.board.vendor: SDZ dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: SDZ dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrPC_STICK_8G_D8R2:bd05/12/2023:br1.20:svnSDZ:pnX133:pvrDefaultstring:rvnSDZ:rnX133:rvrDefaultstring:cvnSDZ:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Notebook dmi.product.name: X133 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SDZ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2046085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1830316] Re: ksm06* from mm test suite in LTP failed on D
Kernel EOL and this does not exist in our hint database. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830316 Title: ksm06* from mm test suite in LTP failed on D Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: Issue found on node "grumman". Test failed with: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY startup='Thu May 23 14:41:43 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s safe_file_ops.c:301: BROK: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ksm06 stime=1558622503 dur=0 exit=exited stat=2 core=no cu=0 cs=0 startup='Thu May 23 14:41:44 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s safe_file_ops.c:301: BROK: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ksm06_1 stime=1558622504 dur=0 exit=exited stat=2 core=no cu=0 cs=1 startup='Thu May 23 14:41:44 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s safe_file_ops.c:301: BROK: Failed to close FILE '/sys/kernel/mm/ksm/max_page_sharing' at mem.c:576: EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ksm06_2 stime=1558622504 dur=1 exit=exited stat=2 core=no cu=0 cs=25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830359] Re: cpuset_base_ops from controller test suite in LTP failed
** Tags removed: ubuntu-ltp ** Tags added: ubuntu-ltp-controllers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830359 Title: cpuset_base_ops from controller test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:23:44 2019' cpuset_base_ops 1 TPASS: cpuset.cpus(READONLY): Get the expected string cpuset_base_ops 3 TPASS: cpuset.mems(READONLY): Get the expected string cpuset_base_ops 5 TPASS: cpuset.memory_pressure(READONLY): Get the expected string cpuset_base_ops 7 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 9 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 11 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 13 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 15 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 17 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 19 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 21 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 23 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 25 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 27 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 29 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 31 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 33 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 35 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result - Expected string - "0" cpuset_base_ops 39 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 41 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 43 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 45 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 47 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 49 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 51 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 53 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 55 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 57 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 59 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 61 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 63 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 65 TFAIL: cpuset.mems: Test result - Expected string - "0" cpuset_base_ops 67 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 69 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 71 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 73 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 75 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 77 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 79 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 81 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 83 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 85 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 87 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 89 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 91 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 93 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 95 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 97 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 99 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 101 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 103 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 105 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 107 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 109 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 111 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 113 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 115 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 117 TPASS: cpuset.memory_spread_slab: Get the expected string
[Kernel-packages] [Bug 1933112] Re: fallocate05 from ltp-syscalls fails on H-azure
This issue does not exist in our database. And the kernels are EOL. ** Changed in: ubuntu-kernel-tests Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Impish) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933112 Title: fallocate05 from ltp-syscalls fails on H-azure Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: Found on hirsute/azure 5.11.0-1007.7 and 5.11.0-1006.6. might be re- appearance of lp:1783880, btrfs file system, only on Azure instance Standard_F32s_v2: tst_test.c:1379: TINFO: Testing on btrfs tst_test.c:888: TINFO: Formatting /dev/loop3 with btrfs opts='' extra opts='' tst_test.c:1311: TINFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:32: TINFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: TINFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) fallocate05.c:81: TPASS: write() wrote 65536 bytes fallocate05.c:102: TINFO: fallocate()d 0 extra blocks on full FS fallocate05.c:114: TPASS: fallocate() on full FS fallocate05.c:130: TPASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) fallocate05.c:134: TFAIL: write(): ENOSPC (28) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1933112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851653] Re: copy_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3
Kernel EOL, and this issue does not exist in our hinting database. ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851653 Title: copy_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: copy_file_range02 from ubuntu_ltp_syscalls failed on i386 node pepe with B-hwe-edge 5.3 kernel Test failed with: copy_file_range02.c:141: FAIL: copy_file_range failed unexpectedly; expected EOVERFLOW, but got: EFBIG (27) Test output: startup='Thu Nov 7 09:22:16 2019' tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s copy_file_range.h:36: INFO: Testing libc copy_file_range() tst_device.c:87: INFO: Found free device 1 '/dev/loop1' Setting up swapspace version 1, size = 36 KiB (36864 bytes) no label, UUID=d68e7005-a932-41eb-a444-3aff47d5cf84 copy_file_range02.c:108: INFO: Test #0: readonly file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #1: directory copy_file_range02.c:137: PASS: copy_file_range failed as expected: EISDIR (21) copy_file_range02.c:108: INFO: Test #2: append to file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #3: closed file descriptor copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #4: invalid flags copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #5: immutable file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EPERM (1) copy_file_range02.c:108: INFO: Test #6: swap file copy_file_range02.c:137: PASS: copy_file_range failed as expected: ETXTBSY (26) copy_file_range02.c:108: INFO: Test #7: overlaping range copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #8: block device copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #9: char device copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #10: fifo copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #11: pipe copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #12: max length lenght copy_file_range02.c:141: FAIL: copy_file_range failed unexpectedly; expected EOVERFLOW, but got: EFBIG (27) copy_file_range02.c:108: INFO: Test #13: max file size copy_file_range02.c:137: PASS: copy_file_range failed as expected: EFBIG (27) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s copy_file_range.h:39: INFO: Testing __NR_copy_file_range syscall tst_device.c:87: INFO: Found free device 1 '/dev/loop1' Setting up swapspace version 1, size = 36 KiB (36864 bytes) no label, UUID=7ef630e1-d0f3-4072-91ec-ae49ab13c6dc copy_file_range02.c:108: INFO: Test #0: readonly file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #1: directory copy_file_range02.c:137: PASS: copy_file_range failed as expected: EISDIR (21) copy_file_range02.c:108: INFO: Test #2: append to file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #3: closed file descriptor copy_file_range02.c:137: PASS: copy_file_range failed as expected: EBADF (9) copy_file_range02.c:108: INFO: Test #4: invalid flags copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #5: immutable file copy_file_range02.c:137: PASS: copy_file_range failed as expected: EPERM (1) copy_file_range02.c:108: INFO: Test #6: swap file copy_file_range02.c:137: PASS: copy_file_range failed as expected: ETXTBSY (26) copy_file_range02.c:108: INFO: Test #7: overlaping range copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #8: block device copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22) copy_file_range02.c:108: INFO: Test #9: char device copy_file_range02.c:137: PASS: copy_file_range failed as expected: EINVAL (22)
[Kernel-packages] [Bug 1855841] Re: syslog10 from ubuntu_ltp_syscalls failed on Standard_B1ms with E-Azure 5.3
Kernel EOL, and this issue does not exist in our hinting database. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux-azure (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1855841 Title: syslog10 from ubuntu_ltp_syscalls failed on Standard_B1ms with E-Azure 5.3 Status in ubuntu-kernel-tests: Won't Fix Status in linux-azure package in Ubuntu: Won't Fix Bug description: syslog10 failed on Standard_B1ms instance with Eoan Azure 5.3.0-1009.10 Fail rate 2 out of 2, this is the only failing instance among all the other instances. startup='Sat Dec 7 03:00:58 2019' syslog100 TINFO : Test setlogmask() with LOG_MASK macro. syslog100 TINFO : o Use setlogmask() with LOG_MASK macro to set an syslog100 TINFO : individual priority level. syslog100 TINFO : o Send the message of above prority and expect it to be syslog100 TINFO : logged. syslog100 TINFO : o Send message which is at other priority level to syslog100 TINFO : the one set above, which should not be logged. syslog100 TINFO : syslog: Testing setlogmask() with LOG_MASK macro... syslog100 TINFO : restarting syslog daemon syslog101 TFAIL : ltpapicmd.c:188: Expected message was not logged syslog100 TINFO : restarting syslog daemon tag=syslog10 stime=1575687658 dur=17 exit=exited stat=1 core=no cu=2 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896616] Re: set correct device size of loopback devices
https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/groovy/commit/?id=05fa16bade61432bc7858d7316e4480938aa0cb8 ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: ubuntu-kernel-tests Status: New => 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/1896616 Title: set correct device size of loopback devices Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] SRU test ubuntu_ltp_syscalls is reporting the following message: 11:52:03 DEBUG| [stdout] ioctl_loop07.c:62: FAIL: /sys/block/loop4/size != 1024 got 2048 11:52:03 DEBUG| [stdout] ioctl_loop07.c:63: PASS: /sys/block/loop4/loop/sizelimit = 524288 11:52:03 DEBUG| [stdout] ioctl_loop07.c:66: PASS: LOOP_GET_STATUS64 gets correct lo_sizelimit(524288) 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 11:52:03 DEBUG| [stdout] 11:52:03 DEBUG| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79e5dc59e297 [Test case] $ sudo autotest/client/autotest-local -v autotest/client/tests/ubuntu_ltp_syscalls/control [Fix] Apply upstream commit 79e5dc59e297. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902473] Re: select03 from ubuntu_ltp_syscalls failed on G / F-oem-5.10
Kernel EOL, I didn't see this among other kernels. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902473 Title: select03 from ubuntu_ltp_syscalls failed on G / F-oem-5.10 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Won't Fix Bug description: This is a new test case, test failed with: <<>> tag=select03 stime=1604290335 cmdline="select03" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:107: TINFO: Testing libc select() select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22) select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0 select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14) tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:110: TINFO: Testing SYS_select syscall select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22) select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0 select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14) tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:113: TINFO: Testing SYS_pselect6 syscall select03.c:62: TPASS: Negative nfds: select() failed as expected: EINVAL (22) select03.c:51: TFAIL: Invalid readfds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid writefds: select() passed unexpectedly with 0 select03.c:51: TFAIL: Invalid exceptfds: select() passed unexpectedly with 0 select03.c:62: TPASS: Faulty readfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty writefds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty exceptfds: select() failed as expected: EFAULT (14) select03.c:62: TPASS: Faulty timeout: select() failed as expected: EFAULT (14) tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:116: TINFO: Testing SYS_pselect6 time64 syscall select_var.h:81: TCONF: __NR_pselect6 time64 variant not supported tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s select_var.h:119: TINFO: Testing SYS__newselect syscall select_var.h:87: TCONF: syscall(-1) __NR__newselect not supported Summary: passed 15 failed 9 skipped 2 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=1 <<>> ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 28 09:30 seq crw-rw 1 root audio 116, 33 Oct 28 09:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Mon Nov 2 04:10:52 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=f06509c5-4a0a-4cae-be3c-e5d21c1687c9 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1855243] Re: pkey01 from ubuntu_ltp_syscalls failed on X-KVM with nr_hugepages = 0
With LTP-20230516 this test will be skipped with <<>> tag=pkey01 stime=1702290779 cmdline="pkey01" contacts="" analysis=exit <<>> incrementing stop tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved tst_test.c:1560: TINFO: Timeout per run is 0h 00m 30s pkey.h:27: TCONF: syscall(330) __NR_pkey_alloc not supported on your arch Summary: passed 0 failed 0 broken 0 skipped 1 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=32 corefile=no cutime=0 cstime=0 <<>> ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1855243 Title: pkey01 from ubuntu_ltp_syscalls failed on X-KVM with nr_hugepages = 0 Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Bug description: Reproduce rate: 4/4 Test failed with: pkey01.c:69: BROK: nr_hugepages = 0, but expect 1 <<>> tag=pkey01 stime=1575532698 cmdline="pkey01" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s pkey01.c:69: BROK: nr_hugepages = 0, but expect 1 Summary: passed 0 failed 0 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1063-kvm 4.4.0-1063.70 ProcVersionSignature: User Name 4.4.0-1063.70-kvm 4.4.200 Uname: Linux 4.4.0-1063-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Dec 5 07:58:24 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988582] Re: RT test failures: ubuntu_lxc lxc-test-api-reboot and lxc-test-shutdowntest
This can be found on J-oracle-6.5.0-1013.13~22.04.4 as well. ** Tags added: 6.5 sru-20231030 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1988582 Title: RT test failures: ubuntu_lxc lxc-test-api-reboot and lxc-test- shutdowntest Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Bug description: ubuntu_lxc test failures for cases lxc-test-api-reboot and lxc-test- shutdowntest. These tests fail since 5.15. Kernel source: linux-oracle Test name: ubuntu_lxc Test case: lxc-test-shutdowntest +++-+---+---+---++ | Kernel | BM.Standard.A1.160 | BM.Standard2.52 | VM.DenseIO2.8 | VM.Standard.A1.Flex-4c.8m | VM.Standard.E3.Flex-4c.8m | VM.Standard2.1 | +++-+---+---+---++ | 5.15.0-1017.22 |FAIL| FAIL | FAIL | FAIL |FAIL | FAIL | | 5.15.0-1013.17 |FAIL| FAIL | FAIL | FAIL |FAIL | FAIL | | 5.15.0-1007.9 |FAIL| PASS | PASS | PASS |PASS | PASS | | 5.15.0-1005.7 |FAIL| PASS | PASS | PASS |PASS | PASS | | 5.15.0-1004.6 |FAIL| PASS | PASS | PASS |PASS | PASS | | 5.13.0-1031.36 |PASS| PASS | PASS | PASS |PASS | PASS | | 5.13.0-1029.34 |PASS| PASS | PASS | PASS |PASS | PASS | | 5.13.0-1028.33 |PASS| PASS | PASS | PASS |PASS | PASS | | 5.13.0-1027.32 || PASS | PASS | PASS |PASS | PASS | | 5.13.0-1026.31 || PASS | PASS | PASS |PASS | PASS | | 5.13.0-1025.30 || PASS | PASS | PASS |PASS | PASS | | 5.13.0-1024.29 || PASS | PASS | PASS |PASS | PASS | | 5.13.0-1023.28 || PASS | PASS | PASS |PASS | PASS | | 5.13.0-1022.27 || PASS | PASS | PASS |PASS | PASS | | 5.13.0-1019.23 || PASS | PASS | PASS |PASS | PASS | | 5.13.0-1018.22 || PASS | PASS | PASS |PASS | PASS | | 5.13.0-1017.21 || PASS | PASS | PASS |PASS | PASS | | 5.13.0-1016.20 || PASS | PASS | |PASS | PASS | | 5.13.0-1011.13 || PASS | PASS | |PASS | PASS | | 5.13.0-1010.12 || | PASS | |PASS | PASS | +++-+---+---+---++ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1988582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045636] Re: Update debian.master/reconstruct for is_rust_module.sh removal on L
*** This bug is a duplicate of bug 2045562 *** https://bugs.launchpad.net/bugs/2045562 ** This bug has been marked a duplicate of bug 2045562 [Debian] autoreconstruct - Do not generate chmod -x for deleted files -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045636 Title: Update debian.master/reconstruct for is_rust_module.sh removal on L Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE: scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the debian.master/reconstruct is not updated for this. Consequently we will see this error message when running "fakeroot debian/rules clean" command: chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory We didn't notice this as this is not a show-stopper. [Fix] Remove corresponding lines from debian.master/reconstruct. We already have this issue fixed in Mantic+. [Test Plan] Run "fakeroot debian/rules clean" with the patched kernel tree and this error message should not exist anymore. [Where problems could occur] Removing command line operation on a non-existing file, this should not cause any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038611] Re: drop all references to is_rust_module.sh in kernels >= 6.5
Marking linux as "fix-released" since this is_rust_module.sh does not
exist in debian.master/reconstruct
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038611
Title:
drop all references to is_rust_module.sh in kernels >= 6.5
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
[Impact]
The script tools/is_rust_module.sh has been dropped by this commit:
079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
is_rust_module.sh")
And upstream as well (in 6.6):
41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")
But we still have a reference of it in debian.master/reconstruct and
that generates the following warning during the build:
chmod: cannot access 'scripts/is_rust_module.sh': No such file or
directory
[Fix]
Drop the reference to is_rust_module.sh from reconstruct to prevent
unnecessary warnings during the build.
[Test case]
The following command ran from the kernel source directory is enough
to trigger the warning:
$ fakeroot debian/rules clean
[Regression potential]
This change is affecting only our packaging. The change is trivial but
it might affect our kernel build process in case of regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038611/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038611] Re: drop all references to is_rust_module.sh in kernels >= 6.5
** Changed in: linux (Ubuntu)
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/2038611
Title:
drop all references to is_rust_module.sh in kernels >= 6.5
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
[Impact]
The script tools/is_rust_module.sh has been dropped by this commit:
079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
is_rust_module.sh")
And upstream as well (in 6.6):
41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")
But we still have a reference of it in debian.master/reconstruct and
that generates the following warning during the build:
chmod: cannot access 'scripts/is_rust_module.sh': No such file or
directory
[Fix]
Drop the reference to is_rust_module.sh from reconstruct to prevent
unnecessary warnings during the build.
[Test case]
The following command ran from the kernel source directory is enough
to trigger the warning:
$ fakeroot debian/rules clean
[Regression potential]
This change is affecting only our packaging. The change is trivial but
it might affect our kernel build process in case of regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038611/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045636] Re: Update debian.master/reconstruct for is_rust_module.sh removal on L
https://lists.ubuntu.com/archives/kernel-team/2023-December/147458.html ** Description changed: [Impact] - The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE: scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the debian.master/reconstruct is not updated for this. + The script/is_rust_module.sh has been removed with commit "UBUNTU: + SAUCE: scripts: rust: drop is_rust_module.sh" (LP: #2007654). + But the debian.master/reconstruct is not updated for this. - Consequently we will see this error message when running "fakeroot debian/rules clean" command: - chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory + Consequently we will see this error message when running "fakeroot + debian/rules clean" command: + + chmod: cannot access 'scripts/is_rust_module.sh': No such file or + directory We didn't notice this as this is not a show-stopper. [Fix] - Remove corresponding lines from debian.master/reconstruct + Remove corresponding lines from debian.master/reconstruct. + + We already have this issue fixed in Mantic+. [Test Plan] - Run "fakeroot debian/rules clean" and this error message should not exist anymore. + Run "fakeroot debian/rules clean" with the patched kernel tree and + this error message should not exist anymore. [Where problems could occur] - Removing command line operation on a non-existing file, this should not cause any regression. + Removing command line operation on a non-existing file, this should + not cause any regression. ** Tags added: lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045636 Title: Update debian.master/reconstruct for is_rust_module.sh removal on L Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE: scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the debian.master/reconstruct is not updated for this. Consequently we will see this error message when running "fakeroot debian/rules clean" command: chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory We didn't notice this as this is not a show-stopper. [Fix] Remove corresponding lines from debian.master/reconstruct. We already have this issue fixed in Mantic+. [Test Plan] Run "fakeroot debian/rules clean" with the patched kernel tree and this error message should not exist anymore. [Where problems could occur] Removing command line operation on a non-existing file, this should not cause any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045636] Re: Update debian.master/reconstruct for is_rust_module.sh removal on L
For Mantic it's already been tracked here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038611 ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Noble) Assignee: Po-Hsu Lin (cypressyew) => (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/2045636 Title: Update debian.master/reconstruct for is_rust_module.sh removal on L Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE: scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the debian.master/reconstruct is not updated for this. Consequently we will see this error message when running "fakeroot debian/rules clean" command: chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory We didn't notice this as this is not a show-stopper. [Fix] Remove corresponding lines from debian.master/reconstruct [Test Plan] Run "fakeroot debian/rules clean" and this error message should not exist anymore. [Where problems could occur] Removing command line operation on a non-existing file, this should not cause any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045636] [NEW] Update debian.master/reconstruct for is_rust_module.sh removal on L
Public bug reported:
[Impact]
The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE:
scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the
debian.master/reconstruct is not updated for this.
Consequently we will see this error message when running "fakeroot debian/rules
clean" command:
chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory
We didn't notice this as this is not a show-stopper.
[Fix]
Remove corresponding lines from debian.master/reconstruct
[Test Plan]
Run "fakeroot debian/rules clean" and this error message should not exist
anymore.
[Where problems could occur]
Removing command line operation on a non-existing file, this should not cause
any regression.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Lunar)
Importance: Undecided
Assignee: Po-Hsu Lin (cypressyew)
Status: In Progress
** Affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Fix Committed
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Po-Hsu Lin (cypressyew)
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Description changed:
[Impact]
- The script/is_rust_module.sh has been removed. But the
debian.master/reconstruct is not updated for this.
+ The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE:
scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the
debian.master/reconstruct is not updated for this.
- Therefore we will see this error message when running "fakeroot debian/rules
clean":
+ Consequently we will see this error message when running "fakeroot
debian/rules clean" command:
chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory
- As this is not a show-stopper, it can be easily ignored.
+ We didn't notice this as this is not a show-stopper.
[Fix]
Remove corresponding lines from debian.master/reconstruct
[Test Plan]
Run "fakeroot debian/rules clean" and this error message should not exist
anymore.
[Where problems could occur]
- Removing command line operation on non-existing file, this should not cause
any regression.
+ Removing command line operation on a non-existing file, this should not cause
any regression.
** Summary changed:
- Update debian.master/reconstruct for is_rust_module.sh removal on L/M
+ Update debian.master/reconstruct for is_rust_module.sh removal on L
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045636
Title:
Update debian.master/reconstruct for is_rust_module.sh removal on L
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
Fix Committed
Status in linux source package in Noble:
Fix Released
Bug description:
[Impact]
The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE:
scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the
debian.master/reconstruct is not updated for this.
Consequently we will see this error message when running "fakeroot
debian/rules clean" command:
chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory
We didn't notice this as this is not a show-stopper.
[Fix]
Remove corresponding lines from debian.master/reconstruct
[Test Plan]
Run "fakeroot debian/rules clean" and this error message should not exist
anymore.
[Where problems could occur]
Removing command line operation on a non-existing file, this should not cause
any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045636/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029280] Re: shiftfs is not available without installing linux-modules-extras package
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2029280 Title: shiftfs is not available without installing linux-modules-extras package Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Bug description: The shiftfs module, used by lxd, is not available out-of-the-box on cloud images (I've tested on aws, azure and gcp so far). The shiftfs module is installed with the `linux-modules-extra-$(uname -r)` package. This package is not seeded into the cloud images by default. Two potential solutions to this are: * Move the shiftfs module to the `linux-modules-$(uname -r)` package. * Seed the `linux-modules-extra-$(uname -r)` package into the cloud image. This all works for the generic kernel. When investigating why, I see that shiftfs.ko is included in linux-modules-5.15.0-78-generic (not the `linux-modules-extra` package). So it appears the location of shiftfs.ko is inconsistent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828380] Re: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on D i386
Kernel EOL and we don't have this issue recorded in our hint database. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) 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/1828380 Title: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on D i386 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Won't Fix Bug description: Test failed with: btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43 Test log: * Command: BINDIR=/home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes /home /ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/ubuntu_btrfs_kerne l_fixes.sh /home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/fi xes/f88ba6a2a44ee98e8d59654463dc157bb6d13c43.sh 2>&1 Exit status: 1 Duration: 11.0287649632 stdout: Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43 Btrfs: skip submitting barrier for missing device I got an error on v3.13: BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure (errors while submitting device barriers.) how to reproduce: > mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2 > wipefs -a /dev/sdf2 > mount -o degraded /dev/sdf1 /mnt > btrfs balance start -f -sconvert=single -mconvert=single -dconvert=single /mnt The reason of the error is that barrier_all_devices() failed to submit barrier to the missing device. However it is clear that we cannot do anything on missing device, and also it is not necessary to care chunks on the missing device. This patch stops sending/waiting barrier if device is missing. btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43 FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1) Syslog: kernel: [ 1531.598180] Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 kernel: [ 1531.822544] BTRFS: device fsid 28683721-4c7a-4922-a753-e61ca95c0726 devid 1 transid 5 /dev/loop2 kernel: [ 1531.917840] BTRFS: device fsid 28683721-4c7a-4922-a753-e61ca95c0726 devid 2 transid 5 /dev/loop3 kernel: [ 1532.314274] BTRFS info (device loop2): allowing degraded mounts kernel: [ 1532.314276] BTRFS info (device loop2): disk space caching is enabled kernel: [ 1532.314277] BTRFS info (device loop2): has skinny extents kernel: [ 1532.314278] BTRFS info (device loop2): flagging fs with big metadata feature kernel: [ 1532.315442] BTRFS warning (device loop2): devid 2 uuid b6fe3a66-6a6d-42fe-9b57-5373a2f8d014 is missing kernel: [ 1532.315882] BTRFS info (device loop2): checking UUID tree kernel: [ 1532.319154] BTRFS error (device loop2): balance: invalid convert data profile single systemd[965]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: Succeeded. systemd[1]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: Succeeded. kernel: [ 1532.524774] Test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 returned 0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 9 09:31 seq crw-rw 1 root audio 116, 33 May 9 09:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu May 9 09:33:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Error: [Errno 2] No such
[Kernel-packages] [Bug 1845858] Re: pmtu.sh in net from ubuntu_kernel_selftests failed on B-hwe-edge 5.3
Kernel EOL and we don't have this issue recorded in our hint database. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: linux-hwe (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe (Ubuntu Eoan) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1845858 Title: pmtu.sh in net from ubuntu_kernel_selftests failed on B-hwe-edge 5.3 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Disco: Won't Fix Status in linux-hwe source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-hwe source package in Eoan: Won't Fix Bug description: Issue found on B-hwe 5.3 amd64, test failed with: # TEST: ipv6: list and flush cached exceptions [FAIL] Complete test log: # selftests: net: pmtu.sh # TEST: ipv4: PMTU exceptions [ OK ] # TEST: ipv6: PMTU exceptions [ OK ] # vxlan4 not supported # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] # vxlan4 not supported # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] # geneve4 not supported # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] # geneve4 not supported # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] # TEST: vti6: PMTU exceptions [ OK ] # TEST: vti4: PMTU exceptions [ OK ] # TEST: vti4: default MTU assignment [ OK ] # TEST: vti6: default MTU assignment [ OK ] # TEST: vti4: MTU setting on link creation [ OK ] # TEST: vti6: MTU setting on link creation [ OK ] # TEST: vti6: MTU changes on link changes [ OK ] # vxlan4 not supported # TEST: ipv4: cleanup of cached exceptions [SKIP] # TEST: ipv6: cleanup of cached exceptions [ OK ] # TEST: ipv4: list and flush cached exceptions [ OK ] # TEST: ipv6: list and flush cached exceptions [FAIL] # can't list cached exceptions not ok 16 selftests: net: pmtu.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827845] Re: ubuntu_bpf_jit report result in D on s390x is a bit confusing
Kernel EOL and we don't have this issue recorded in our hint database. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827845 Title: ubuntu_bpf_jit report result in D on s390x is a bit confusing Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: The only failure is the test_bpf module load failure, and there are 378 tests (0-377) But the result shows "Summary: 377 PASSED, 1 FAILED" Module test_bpf load failure [ 873.481738] test_bpf: #0 TAX jited:1 36 34 35 PASS [ 873.481888] test_bpf: #1 TXA jited:1 17 17 17 PASS [ 873.481960] test_bpf: #2 ADD_SUB_MUL_K jited:1 18 PASS [ 873.481997] test_bpf: #3 DIV_MOD_KX jited:1 35 PASS [ 873.482054] test_bpf: #4 AND_OR_LSH_K jited:1 16 16 PASS [ 873.482106] test_bpf: #5 LD_IMM_0 jited:1 16 PASS [ 873.482141] test_bpf: #6 LD_IND jited:1 48 47 47 PASS [ 873.482305] test_bpf: #7 LD_ABS jited:1 49 49 49 PASS [ 873.482472] test_bpf: #8 LD_ABS_LL jited:1 72 72 PASS [ 873.482637] test_bpf: #9 LD_IND_LL jited:1 49 49 49 PASS [ 873.482804] test_bpf: #10 LD_ABS_NET jited:1 71 71 PASS [ 873.482966] test_bpf: #11 LD_IND_NET jited:1 48 48 48 PASS [ 873.483132] test_bpf: #12 LD_PKTTYPE jited:1 18 18 PASS [ 873.483189] test_bpf: #13 LD_MARK jited:1 18 18 PASS [ 873.483242] test_bpf: #14 LD_RXHASH jited:1 18 18 PASS [ 873.483295] test_bpf: #15 LD_QUEUE jited:1 18 18 PASS [ 873.483347] test_bpf: #16 LD_PROTOCOL jited:1 20 20 PASS [ 873.483410] test_bpf: #17 LD_VLAN_TAG jited:1 18 18 PASS [ 873.483463] test_bpf: #18 LD_VLAN_TAG_PRESENT jited:1 17 17 PASS [ 873.483515] test_bpf: #19 LD_IFINDEX jited:1 17 17 PASS [ 873.483567] test_bpf: #20 LD_HATYPE jited:1 17 17 PASS [ 873.483618] test_bpf: #21 LD_CPU jited:1 52 52 PASS [ 873.483742] test_bpf: #22 LD_NLATTR jited:1 34 44 PASS [ 873.483839] test_bpf: #23 LD_NLATTR_NEST jited:1 155 236 PASS [ 873.484254] test_bpf: #24 LD_PAYLOAD_OFF jited:1 295 325 PASS [ 873.484894] test_bpf: #25 LD_ANC_XOR jited:1 16 16 PASS [ 873.484945] test_bpf: #26 SPILL_FILL jited:1 20 20 20 PASS [ 873.485026] test_bpf: #27 JEQ jited:1 47 18 18 PASS [ 873.485131] test_bpf: #28 JGT jited:1 47 18 18 PASS [ 873.485236] test_bpf: #29 JGE (jt 0), test 1 jited:1 46 18 18 PASS [ 873.485339] test_bpf: #30 JGE (jt 0), test 2 jited:1 18 18 18 PASS [ 873.485414] test_bpf: #31 JGE jited:1 34 35 35 PASS [ 873.485540] test_bpf: #32 JSET jited:1 37 36 39 PASS [ 873.485678] test_bpf: #33 tcpdump port 22 jited:1 47 52 57 PASS [ 873.485871] test_bpf: #34 tcpdump complex jited:1 47 50 74 PASS [ 873.486082] test_bpf: #35 RET_A jited:1 16 16 PASS [ 873.486132] test_bpf: #36 INT: ADD trivial jited:1 16 PASS [ 873.486165] test_bpf: #37 INT: MUL_X jited:1 16 PASS [ 873.486197] test_bpf: #38 INT: MUL_X2 jited:1 17 PASS [ 873.486230] test_bpf: #39 INT: MUL32_X jited:1 17 PASS [ 873.486263] test_bpf: #40 INT: ADD 64-bit jited:1 36 PASS [ 873.486331] test_bpf: #41 INT: ADD 32-bit jited:1 50 PASS [ 873.486411] test_bpf: #42 INT: SUB jited:1 33 PASS [ 873.486472] test_bpf: #43 INT: XOR jited:1 22 PASS [ 873.486516] test_bpf: #44 INT: MUL jited:1 71 PASS [ 873.486609] test_bpf: #45 MOV REG64 jited:1 19 PASS [ 873.486647] test_bpf: #46 MOV REG32 jited:1 19 PASS [ 873.486685] test_bpf: #47 LD IMM64 jited:1 20 PASS [ 873.486725] test_bpf: #48 INT: ALU MIX jited:1 24 PASS [ 873.486788] test_bpf: #49 INT: shifts by register jited:1 19 PASS [ 873.486827] test_bpf: #50 check: missing ret PASS [ 873.486834] test_bpf: #51 check: div_k_0 PASS [ 873.486840] test_bpf: #52 check: unknown insn PASS [ 873.486846] test_bpf: #53 check: out of range spill/fill PASS [ 873.486851] test_bpf: #54 JUMPS + HOLES jited:1 21 PASS [ 873.486964] test_bpf: #55 check: RET X PASS [ 873.486970] test_bpf: #56 check: LDX + RET X PASS [ 873.486976] test_bpf: #57 M[]: alt STX + LDX jited:1 57 PASS [ 873.487065] test_bpf: #58 M[]: full STX + full LDX jited:1 27 PASS [ 873.487122] test_bpf: #59 check: SKF_AD_MAX PASS [ 873.487128] test_bpf: #60 LD [SKF_AD_OFF-1] jited:1 48 PASS [ 873.487196] test_bpf: #61 load 64-bit immediate jited:1 17 PASS [ 873.487231] test_bpf: #62 ALU_MOV_X: dst = 2 jited:1 16 PASS [ 873.487265] test_bpf: #63 ALU_MOV_X: dst = 4294967295 jited:1 16 PASS [ 873.487298] test_bpf: #64 ALU64_MOV_X: dst = 2 jited:1 16 PASS [ 873.487331] test_bpf: #65 ALU64_MOV_X: dst = 4294967295 jited:1 16 PASS [ 873.487364] test_bpf: #66 ALU_MOV_K: dst = 2 jited:1 16 PASS [ 873.487397] test_bpf: #67 ALU_MOV_K: dst = 4294967295 jited:1 16 PASS [ 873.487430] test_bpf: #68 ALU_MOV_K:
[Kernel-packages] [Bug 1837365] Re: ubuntu_kvm_smoke_test failed on Intel KVM node with D-KVM kernel
Kernel EOL and we don't have this issue recorded in our hint database.
Closing this bug.
** Changed in: ubuntu-kernel-tests
Status: New => Won't Fix
** Changed in: linux-kvm (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1837365
Title:
ubuntu_kvm_smoke_test failed on Intel KVM node with D-KVM kernel
Status in ubuntu-kernel-tests:
Won't Fix
Status in linux-kvm package in Ubuntu:
Won't Fix
Bug description:
The KVM can be started in our KVM node (zeppo) with the D-KVM kernel.
But it looks like that we can't run it on the Intel Cloud KVM nodes
(automation-vm8)
Test failed with:
+ uvt-kvm wait bjf-test --insecure --ssh-private-key-file
/home/ubuntu/.ssh/id_rsa
uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:67:78:dc.
++ uvt-kvm ip bjf-test
uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
sudo -u ubuntu /home/ubuntu/autotest/client/tests/ubuntu_kvm_smoke_test
/the-test amd64
Exit status: 1
Duration: 354.469812155
stdout:
INFO: /dev/kvm exists
KVM acceleration can be used
Generating public/private rsa key pair.
Your identification has been saved in /home/ubuntu/.ssh/id_rsa.
Your public key has been saved in /home/ubuntu/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:hXBMvlRcr+MMJACF2ymdbkl+gxISLagx0ZUSlOYR/+E ubuntu@automation-vm8
The key's randomart image is:
+---[RSA 2048]+
|.=+*o=+oo |
|+ O.+ =.o. . |
|.= =.+.o= o . |
|. o +o*o = . |
| . *EoS . o |
| . * o + . |
| o . . o |
| |
| |
+[SHA256]-+
** ERROR: The codename returned from lsb_release -c was ( ) and we were
expecting 'disco'
stderr:
+ SUT=bjf-test
+ SSH_KEY=/home/ubuntu/.ssh/id_rsa
+ SSH_OPTIONS='-o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null -o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
++ lsb_release -c
++ awk '{print$2}'
+ DISTRO=disco
+ ARCHITECTURE=amd64
+ '[' -z amd64 ']'
+ kvm-ok
+ '[' 0 '!=' 0 ']'
+ '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
+ ssh-keygen -f /home/ubuntu/.ssh/id_rsa -t rsa -N ''
+ '[' amd64 = ppc64el ']'
++ grep -P 'disco.*amd64'
++ uvt-simplestreams-libvirt query
+ image=
+ '[' -z '' ']'
+ uvt-simplestreams-libvirt sync --source
http://cloud-images.ubuntu.com/daily release=disco arch=amd64
+ uvt-kvm create bjf-test release=disco arch=amd64
+ uvt-kvm wait bjf-test --insecure --ssh-private-key-file
/home/ubuntu/.ssh/id_rsa
uvt-kvm: error: timed out waiting for dnsmasq lease for
52:54:00:67:78:dc.
++ uvt-kvm ip bjf-test
uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
+ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@ uname -a
+++ uvt-kvm ip bjf-test
++ cut '-d ' -f 2
uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
++ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@ lsb_release -c
+ RESULT=
+ '[' '' '!=' disco ']'
+ echo '** ERROR: The codename returned from lsb_release -c was (' ')
and we were expecting '\''disco'\'''
+ exit 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837365/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930100] Re: selftests/net/bpf - Failure in building bpf program on G/RISC-V (kernel 5.8)
Kernel EOL and we don't have this issue recorded in our hint database. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930100 Title: selftests/net/bpf - Failure in building bpf program on G/RISC-V (kernel 5.8) Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in linux source package in Groovy: Won't Fix Bug description: I found the following failure in G/RISC-V, cycle sru-20210510 : 21:07:11 ERROR| [stderr] progs/test_vmlinux.c:24:18: error: use of undeclared identifier '__NR_nanosleep' 21:07:11 ERROR| [stderr] if (args->id != __NR_nanosleep) 21:07:11 ERROR| [stderr] ^ [...] 21:07:11 ERROR| [stderr] progs/test_vmlinux.c:60:12: error: use of undeclared identifier '__NR_nanosleep' 21:07:11 ERROR| [stderr] if (id != __NR_nanosleep) 21:07:11 ERROR| [stderr] ^ 21:07:11 ERROR| [stderr] progs/test_vmlinux.c:63:15: warning: implicit declaration of function 'PT_REGS_PARM1_CORE' is invalid in C99 [-Wimplicit-function-declaration] 21:07:11 ERROR| [stderr] ts = (void *)PT_REGS_PARM1_CORE(regs); 21:07:11 ERROR| [stderr] ^ [...] /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_tracing.h:298:29: note: expanded from macro '___bpf_concat' 21:07:12 ERROR| [stderr] #define ___bpf_concat(a, b) a ## b 21:07:12 ERROR| [stderr] ^ 21:07:12 ERROR| [stderr] :28:1: note: expanded from here 21:07:12 ERROR| [stderr] ___bpf_kprobe_args3 21:07:12 ERROR| [stderr] ^ 21:07:12 ERROR| [stderr] /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_tracing.h:359:29: note: expanded from macro '___bpf_kprobe_args3' 21:07:12 ERROR| [stderr] ___bpf_kprobe_args2(args), (void *)PT_REGS_PARM3(ctx) 21:07:12 ERROR| [stderr] ^~ 21:07:12 ERROR| [stderr] 10 warnings and 3 errors generated. 21:07:12 ERROR| [stderr] llc: error: llc: :1:1: error: expected top-level entity 21:07:12 ERROR| [stderr] BPF obj compilation failed 21:07:12 ERROR| [stderr] ^ 21:07:12 ERROR| [stderr] make[1]: *** [Makefile:376: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_vmlinux.o] Error 1 21:07:12 ERROR| [stderr] make: *** [Makefile:159: all] Error 2 21:07:12 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 239, in run_once utils.system(cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=2, Command returned non-zero exit status * Command: make -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= KDIR=/usr/src/linux-headers-5.8.0-26-generic Exit status: 2 See more on the attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1930100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042388] Re: context test in ubuntu_stress_smoke_test failed with M-6.5 riscv / starfive instances
** Also affects: linux-starfive (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-starfive (Ubuntu) Status: New => Invalid ** Changed in: linux-starfive (Ubuntu Mantic) Status: New => Fix Committed ** Also affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-riscv (Ubuntu) Status: New => Invalid ** Changed in: linux-riscv (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive in Ubuntu. https://bugs.launchpad.net/bugs/2042388 Title: context test in ubuntu_stress_smoke_test failed with M-6.5 riscv / starfive instances Status in ubuntu-kernel-tests: New Status in glibc package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: Invalid Status in linux-starfive package in Ubuntu: Invalid Status in glibc source package in Mantic: Invalid Status in linux-riscv source package in Mantic: Fix Committed Status in linux-starfive source package in Mantic: Fix Committed Bug description: This issue can be found from the very beginning of these two kernels * mantic/linux-starfive/6.5.0-1001.2 * mantic/linux-riscv/6.5.0-7.7.2 Test failed with: context STARTING context RETURNED 2 context FAILED stress-ng: debug: [12644] invoked with './stress-ng -v -t 5 --context 4 --context-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root' stress-ng: debug: [12644] stress-ng 0.16.05 gaea6f3306f46 stress-ng: debug: [12644] system: Linux mantic-starfive-riscv64 6.5.0-1001-starfive #2-Ubuntu SMP Fri Oct 6 12:08:59 UTC 2023 riscv64, gcc 13.2.0, glibc 2.38 stress-ng: debug: [12644] RAM total: 7.7G, RAM free: 6.6G, swap free: 1024.0M stress-ng: debug: [12644] temporary file path: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng', filesystem type: ext2 (4617314 blocks available) stress-ng: debug: [12644] 8 processors online, 8 processors configured stress-ng: info: [12644] setting to a 5 secs run per stressor stress-ng: debug: [12644] cache allocate: using defaults, cannot determine cache level details stress-ng: debug: [12644] cache allocate: shared cache buffer size: 2048K stress-ng: info: [12644] dispatching hogs: 4 context stress-ng: debug: [12644] starting stressors stress-ng: debug: [12644] 4 stressors started stress-ng: debug: [12645] context: [12645] started (instance 0 on CPU 2) stress-ng: debug: [12647] context: [12647] started (instance 2 on CPU 5) stress-ng: debug: [12648] context: [12648] started (instance 3 on CPU 7) stress-ng: debug: [12646] context: [12646] started (instance 1 on CPU 4) stress-ng: debug: [12644] context: [12645] terminated on signal: 11 (Segmentation fault) stress-ng: debug: [12644] context: [12645] terminated (success) stress-ng: debug: [12644] context: [12646] terminated on signal: 11 (Segmentation fault) stress-ng: debug: [12644] context: [12646] terminated (success) stress-ng: debug: [12644] context: [12647] terminated on signal: 11 (Segmentation fault) stress-ng: debug: [12644] context: [12647] terminated (success) stress-ng: debug: [12644] context: [12648] terminated on signal: 11 (Segmentation fault) stress-ng: debug: [12644] context: [12648] terminated (success) stress-ng: warn: [12644] metrics-check: all bogo-op counters are zero, data may be incorrect stress-ng: debug: [12644] metrics-check: all stressor metrics validated and sane stress-ng: info: [12644] skipped: 0 stress-ng: info: [12644] passed: 4: context (4) stress-ng: info: [12644] failed: 0 stress-ng: info: [12644] metrics untrustworthy: 0 stress-ng: info: [12644] unsuccessful run completed in 9.98 secs Looks like the tests have passed. But marked as failed with a non-zero return code. Tested with stress-ng V0.16.05 and V0.17.00, they all failed with the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2042388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038522] Re: disable shiftfs
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/overlay-shiftfs-tests/+merge/454842 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038522 Title: disable shiftfs Status in linux package in Ubuntu: Triaged Status in linux source package in Mantic: Fix Committed Bug description: [Impact] Now that all the filesystems that we officially support have the idmapped mounts capability we can get rid of shiftfs. The benefit of this change is that we don't have to maintain an out- of-tree filesystem anymore and we can completely rely on upstream features. [Test case] lxd was the main user of shiftfs to compensate the lack of idmapped mounts capability of certain filesystems, such as zfs / ceph, but now in mantic also these two filesystem received the support for idmapped mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see LP: #2032959). The lxd team provided a positive feedback, testing the latest 6.5 Mantic kernel across all the supported filesystems with shiftfs disabled. [Fix] Disable shiftfs in the kernel config and enable unsafe idmapped mounts by default (default=on). [Regression potential] The support for idmapped mounts for the ceph filesystem is not applied upstream yet, so we may experience regressions in systems that are using this filesystem. Moreover disabling shiftfs may trigger failures in our testing (testing shiftfs capabilities will obviously fail) or break any other user-space application that is relying on shiftfs (however to our knowledge lxd was the only "official" user or shiftfs; for this reason we may also see potential regressions in lxd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839450] Re: ubuntu_ftrace_smoke_test failed on D-aws a1.medium arm64 instance
Disco EOL. ** Changed in: linux-aws (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839450 Title: ubuntu_ftrace_smoke_test failed on D-aws a1.medium arm64 instance Status in ubuntu-kernel-tests: Won't Fix Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Won't Fix Bug description: Issue found on AWS ARM64 instance a1.medium, passed on the other 2 (a1.2xlarge / a1.large) Test failed with: FAILED (irq traces found must be > 32, got 18) PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-5.0.0-1011-aws) PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-5.0.0-1011-aws) PASSED (CONFIG_STACK_TRACER=y in /boot/config-5.0.0-1011-aws) PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-5.0.0-1011-aws) PASSED all expected /sys/kernel/debug/tracing files exist PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers) PASSED (function in /sys/kernel/debug/tracing/available_tracers) PASSED (nop in /sys/kernel/debug/tracing/available_tracers) PASSED (function can be enabled) FAILED (irq traces found must be > 32, got 18) PASSED (function_graph can be enabled) PASSED (irq traces found must be > 32, got 9279) PASSED (tracer hwlat can be enabled (got 12 lines of tracing output)) PASSED (tracer blk can be enabled (got 2 lines of tracing output)) PASSED (tracer function_graph can be enabled (got 1374 lines of tracing output)) PASSED (tracer wakeup_dl can be enabled (got 2 lines of tracing output)) PASSED (tracer wakeup_rt can be enabled (got 66 lines of tracing output)) PASSED (tracer wakeup can be enabled (got 64 lines of tracing output)) PASSED (tracer function can be enabled (got 757 lines of tracing output)) Summary: 18 passed, 1 failed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12 ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15 Uname: Linux 5.0.0-1011-aws aarch64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: arm64 Date: Thu Aug 8 10:56:19 2019 Ec2AMI: ami-0ac1a3bc4f5c85238 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959424] Re: ubuntu_kernel_selftests / ftrace:ftracetest hangs on arm64 on Jammy realtime
*** This bug is a duplicate of bug 2029405 *** https://bugs.launchpad.net/bugs/2029405 ** This bug has been marked a duplicate of bug 2029405 Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959424 Title: ubuntu_kernel_selftests / ftrace:ftracetest hangs on arm64 on Jammy realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: d2021.10.26/jammy/linux-realtime/5.15.0-1004.4, only on node appleton-kernel.arm64, hangs (timeouts) on ubuntu_kernel_selftests / ftrace:ftracetest test: 01:28:34 DEBUG| [stdout] # === Ftrace unit tests === 01:28:34 DEBUG| [stdout] # [1] Basic trace file check[PASS] 01:28:38 DEBUG| [stdout] # [2] Basic test for tracers[PASS] 01:28:38 DEBUG| [stdout] # [3] Basic trace clock test[PASS] 01:28:38 DEBUG| [stdout] # [4] Basic event tracing check[PASS] 01:28:39 DEBUG| [stdout] # [5] Change the ringbuffer size[PASS] 01:28:39 DEBUG| [stdout] # [6] Snapshot and tracing setting[PASS] 01:28:40 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS] 01:28:40 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 01:28:40 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 01:28:40 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe events[PASS] 01:28:41 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe events[PASS] 01:28:41 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic events[PASS] 01:28:41 DEBUG| [stdout] # [13] Generic dynamic event - selective clear (compatibility)[PASS] 01:28:41 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event [PASS] 01:28:42 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate events are caught[PASS] 01:58:36 INFO | Timer expired (1800 sec.), nuking pid 161336 The issue was not reproduced on mcdivitt36 (HP ProLiant m400 server cartridge with AppliedMicro X-Gene 64-bit ARM). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1959424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels
** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1812189 Title: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: New Status in linux-gke package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: New Bug description: This test will attempt to insert the test_bpf module, but this module does not exist in KVM kernels: $ sudo modprobe test_bpf modprobe: FATAL: Module test_bpf not found in directory /lib/modules/4.15.0-1028-kvm The script: $ sudo ./test_bpf.sh test_bpf: [FAIL] $ cat test_bpf.sh #!/bin/sh # SPDX-License-Identifier: GPL-2.0 # Runs bpf test using test_bpf kernel module if /sbin/modprobe -q test_bpf ; then /sbin/modprobe -q -r test_bpf; echo "test_bpf: ok"; else echo "test_bpf: [FAIL]"; exit 1; fi This test_bpf module will need the CONFIG_TEST_BPF to be enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 08:29:29 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
https://lists.ubuntu.com/archives/kernel-team/2023-November/147192.html ** Description changed: - First time seen this since ftrace refactor out from - ubuntu_kernel_selftests to ubuntu-kselftests-ftrace + + [Impact] + On ARM64 systems, tests like event-enable.tc, event-pid.tc in + linux/tools/testing/selftests/ftrace will take too much time to run + and consequently leading to test timeout. + + The culprit is the `cat` command on the changing trace file. + + [Fix] + * 25b9513872 selftests/ftrace: Stop tracing while reading the trace + file by default + + This patch can be cherry-picked into Jammy. I didn't see this issue in + our 5.4 kernels. And it's already landed in newer kernels. + + [Test] + On an ARM64 testing node, apply this patch to the kernel tree and run + event-pid.tc test in linux/tools/testing/selftests/ftrace with: + + sudo ./ftracetest -vvv test.d/event/event-pid.tc + + The test should finish within a few minutes. + + [Regression Potential] + Change limited to testing tools, it should not have any actual impact + to kernel functions. + + == Original Bug Report == + First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: - Running './ftracetest -vvv test.d/event/subsystem-enable.tc' - === Ftrace unit tests === - - [1] event tracing - enable/disable with event level files - + [ 2 -eq 1 ] - + [ -f set_event_pid ] - + echo - + [ -f set_ftrace_pid ] - + echo - + [ -f set_ftrace_notrace ] - + echo - + [ -f set_graph_function ] - + echo - + tee set_graph_function set_graph_notrace - + [ -f stack_trace_filter ] - + echo - + [ -f kprobe_events ] - + echo - + [ -f uprobe_events ] - + echo - + [ -f synthetic_events ] - + echo - + [ -f snapshot ] - + echo 0 - + clear_trace - + echo - + enable_tracing - + echo 1 - + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc - + echo sched:sched_switch - + yield - + ping 127.0.0.1 -c 1 - PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. - 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms - - --- 127.0.0.1 ping statistics --- - 1 packets transmitted, 1 received, 0% packet loss, time 0ms - rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms - + cat trace - + grep sched_switch - + wc -l - Timer expired (600 sec.), nuking pid 20982 + Running './ftracetest -vvv test.d/event/subsystem-enable.tc' + === Ftrace unit tests === + + [1] event tracing - enable/disable with event level files + + [ 2 -eq 1 ] + + [ -f set_event_pid ] + + echo + + [ -f set_ftrace_pid ] + + echo + + [ -f set_ftrace_notrace ] + + echo + + [ -f set_graph_function ] + + echo + + tee set_graph_function set_graph_notrace + + [ -f stack_trace_filter ] + + echo + + [ -f kprobe_events ] + + echo + + [ -f uprobe_events ] + + echo + + [ -f synthetic_events ] + + echo + + [ -f snapshot ] + + echo 0 + + clear_trace + + echo + + enable_tracing + + echo 1 + + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + + echo sched:sched_switch + + yield + + ping 127.0.0.1 -c 1 + PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. + 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms + + --- 127.0.0.1 ping statistics --- + 1 packets transmitted, 1 received, 0% packet loss, time 0ms + rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + + cat trace + + grep sched_switch + + wc -l + Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: - count=`cat trace | grep sched_switch | wc -l` + count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. ** Description changed: - [Impact] - On ARM64 systems, tests like event-enable.tc, event-pid.tc in - linux/tools/testing/selftests/ftrace will take too much time to run - and consequently leading to test timeout. + On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, + event-pid.tc in linux/tools/testing/selftests/ftrace will take too + much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace - file by default + file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: - sudo ./ftracetest -vvv test.d/event/event-pid.tc + sudo ./ftracetest -vvv test.d/event/event-pid.tc The
[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
** Summary changed: - ftrace:test.d--event--subsystem-enable.tc fails with timeout on focal:linux-hwe-5.15 ARM64 + Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029405] Re: ftrace:test.d--event--subsystem-enable.tc fails with timeout on focal:linux-hwe-5.15 ARM64
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029405 Title: ftrace:test.d--event--subsystem-enable.tc fails with timeout on focal:linux-hwe-5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940080] Re: ubuntu-kernel-selftests.ftrace hangs on riscv64
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/447331 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1940080 Title: ubuntu-kernel-selftests.ftrace hangs on riscv64 Status in ubuntu-kernel-tests: New Status in linux-riscv package in Ubuntu: Confirmed Bug description: 08/12 22:10:03 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 08/12 22:10:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 08/12 22:10:45 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 08/12 22:10:51 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 08/12 22:10:56 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check[PASS] 08/12 22:11:01 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 08/12 22:11:06 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 08/12 22:11:11 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 08/12 22:11:15 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 08/12 22:11:16 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNSUPPORTED] 08/12 22:11:20 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events[FAIL] 08/12 22:11:21 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [UNSUPPORTED] 08/12 22:11:22 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [UNSUPPORTED] 08/12 22:11:22 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [UNSUPPORTED] 08/12 22:11:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 08/12 22:11:34 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [PASS] 08/12 22:11:40 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 08/12 22:11:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 08/12 22:11:51 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] 08/12 22:11:58 DEBUG| utils:0153| [stdout] # [19] Test trace_printk from module [PASS] 08/12 22:12:15 DEBUG| utils:0153| [stdout] # [20] ftrace - function graph filters with stack tracer [PASS] 08/12 22:12:24 DEBUG| utils:0153| [stdout] # [21] ftrace - function graph filters [PASS] 08/12 22:12:35 DEBUG| utils:0153| [stdout] # [22] ftrace - function pid notrace filters [PASS] 08/12 22:12:46 DEBUG| utils:0153| [stdout] # [23] ftrace - function pid filters [PASS] 08/12 22:12:54 DEBUG| utils:0153| [stdout] # [24] ftrace - stacktrace filter command [PASS] 08/12 22:13:03 DEBUG| utils:0153| [stdout] # [25] ftrace - function trace with cpumask[PASS] 08/12 22:13:28 DEBUG| utils:0153| [stdout] # [26] ftrace - test for function event triggers [FAIL] 08/12 22:13:42 DEBUG| utils:0153| [stdout] # [27] ftrace - function trace on module [PASS] ** hang, whilst a lot more test cases are expected ** I.e. the next test case result should have been # [28] ftrace - function profiling Failure: # [10] Generic dynamic event - add/remove kprobe events [FAIL] # [26] ftrace - test for function event triggers [FAIL] nothing exciting in the dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: sru-20231030
--
You 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 2044334] Re: Unable to put CPU back online on AWS x1e.xlarge instance with kernel 6.2+
This can be reproduced with generic kernel on x1e.xlarge as well: * L 6.2.0-39-generic * M 6.5.0-14-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2044334 Title: Unable to put CPU back online on AWS x1e.xlarge instance with kernel 6.2+ Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: Issue found on AWS x1e.xlarge instance with: * M-aws 6.5.0-1011.11 * L-aws 6.2.0-1007.7 * J-aws-6.5.0-1008.8~22.04.1 * J-aws-6.2.0-1005.5~22.04.1 J-aws-5.15 looks OK. And I can't see this failure on other instances in our pool. CPU can be offlined but you won't be able to put it back online. There are 4 CPUs on this instance. $ uname -a Linux ip-172-31-2-102 6.5.0-1011-aws #11~22.04.1-Ubuntu SMP Mon Nov 20 18:38:58 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ grep CONFIG_HOTPLUG_CPU /boot/config-6.5.0-1011-aws CONFIG_HOTPLUG_CPU=y $ cat /sys/devices/system/cpu/cpu3/online 1 $ echo 0| sudo tee /sys/devices/system/cpu/cpu3/online 0 $ echo 1| sudo tee /sys/devices/system/cpu/cpu3/online 1 tee: /sys/devices/system/cpu/cpu3/online: Input/output error Output from # Offline cpu3 - OK Nov 23 06:21:06 ip-172-31-2-102 kernel: [ 1124.449748] smpboot: CPU 3 is now offline # Online cpu3 - Failed Nov 23 06:21:14 ip-172-31-2-102 kernel: [ 1132.310197] installing Xen timer for CPU 3 Nov 23 06:21:14 ip-172-31-2-102 kernel: [ 1132.310424] smpboot: Booting Node 0 Processor 3 APIC 0x3 Nov 23 06:21:24 ip-172-31-2-102 kernel: [ 1142.312481] CPU3 failed to report alive state This is affecting the ubuntu_kernel_selftests/cpu-hotplug:cpu-on-off- test.sh and ubuntu_ltp/cpuhotplug:cpuhotplug02, cpuhotplug03, cpuhotplug04, cpuhotplug06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2044334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044334] Re: Unable to put CPU back online on AWS x1e.xlarge instance with kernel 6.2+
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2044334 Title: Unable to put CPU back online on AWS x1e.xlarge instance with kernel 6.2+ Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: Issue found on AWS x1e.xlarge instance with: * M-aws 6.5.0-1011.11 * L-aws 6.2.0-1007.7 * J-aws-6.5.0-1008.8~22.04.1 * J-aws-6.2.0-1005.5~22.04.1 J-aws-5.15 looks OK. And I can't see this failure on other instances in our pool. CPU can be offlined but you won't be able to put it back online. There are 4 CPUs on this instance. $ uname -a Linux ip-172-31-2-102 6.5.0-1011-aws #11~22.04.1-Ubuntu SMP Mon Nov 20 18:38:58 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ grep CONFIG_HOTPLUG_CPU /boot/config-6.5.0-1011-aws CONFIG_HOTPLUG_CPU=y $ cat /sys/devices/system/cpu/cpu3/online 1 $ echo 0| sudo tee /sys/devices/system/cpu/cpu3/online 0 $ echo 1| sudo tee /sys/devices/system/cpu/cpu3/online 1 tee: /sys/devices/system/cpu/cpu3/online: Input/output error Output from # Offline cpu3 - OK Nov 23 06:21:06 ip-172-31-2-102 kernel: [ 1124.449748] smpboot: CPU 3 is now offline # Online cpu3 - Failed Nov 23 06:21:14 ip-172-31-2-102 kernel: [ 1132.310197] installing Xen timer for CPU 3 Nov 23 06:21:14 ip-172-31-2-102 kernel: [ 1132.310424] smpboot: Booting Node 0 Processor 3 APIC 0x3 Nov 23 06:21:24 ip-172-31-2-102 kernel: [ 1142.312481] CPU3 failed to report alive state This is affecting the ubuntu_kernel_selftests/cpu-hotplug:cpu-on-off- test.sh and ubuntu_ltp/cpuhotplug:cpuhotplug02, cpuhotplug03, cpuhotplug04, cpuhotplug06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2044334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031287] Re: sysdig-dkms failed to build with J-6.5
This is affecting other J-6.5 variants as well (jammy-linux-ibm-gt-opt, jammy-linux-aws) ** Summary changed: - sysdig-dkms failed to build with J-oem-6.5 + sysdig-dkms failed to build with J-6.5 ** Tags added: aws -- 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/2031287 Title: sysdig-dkms failed to build with J-6.5 Status in ubuntu-kernel-tests: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Confirmed Bug description: ubuntu_sysdig_smoke_test failed because of sysdig DKMS build failed with J-oem-6.5 Error! Bad return status for module build on kernel: 6.5.0-1002-oem (x86_64) Consult /var/lib/dkms/sysdig/0.27.1/build/make.log for more information. dpkg: error processing package sysdig-dkms (--configure): installed sysdig-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.10.2-1) ... Processing triggers for libc-bin (2.35-0ubuntu3.1) ... Errors were encountered while processing: sysdig-dkms needrestart is being skipped since dpkg has failed W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Sub-process /usr/bin/dpkg returned an error code (1) Running 'dkms status -m sysdig | grep installed' Running 'cat /var/lib/dkms/sysdig/*/build/make.log' DKMS make.log for sysdig-0.27.1 for kernel 6.5.0-1002-oem (x86_64) Thu Aug 10 12:17:20 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.5.0-1002-oem' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 CC [M] /var/lib/dkms/sysdig/0.27.1/build/main.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/dynamic_params_table.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/fillers_table.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/flags_table.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/ppm_events.o In file included from ./include/linux/linkage.h:7, from ./arch/x86/include/asm/cache.h:5, from ./include/linux/cache.h:6, from ./arch/x86/include/asm/current.h:9, from ./include/linux/sched.h:12, from ./arch/x86/include/asm/syscall.h:14, from /var/lib/dkms/sysdig/0.27.1/build/main.c:19: /var/lib/dkms/sysdig/0.27.1/build/main.c: In function ‘sysdig_init’: ./include/linux/export.h:29:22: error: passing argument 1 of ‘class_create’ from incompatible pointer type [-Werror=incompatible-pointer-types] 29 | #define THIS_MODULE (&__this_module) | ~^~~ | | | struct module * /var/lib/dkms/sysdig/0.27.1/build/main.c:2484:36: note: in expansion of macro ‘THIS_MODULE’ 2484 | g_ppm_class = class_create(THIS_MODULE, PROBE_DEVICE_NAME); |^~~ In file included from ./include/linux/device.h:31, from ./include/linux/cdev.h:8, from /var/lib/dkms/sysdig/0.27.1/build/main.c:26: ./include/linux/device/class.h:230:54: note: expected ‘const char *’ but argument is of type ‘struct module *’ 230 | struct class * __must_check class_create(const char *name); | ^~~~ /var/lib/dkms/sysdig/0.27.1/build/main.c:2484:23: error: too many arguments to function ‘class_create’ 2484 | g_ppm_class = class_create(THIS_MODULE, PROBE_DEVICE_NAME); | ^~~~ ./include/linux/device/class.h:230:29: note: declared here 230 | struct class * __must_check class_create(const char *name); | ^~~~ cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:251: /var/lib/dkms/sysdig/0.27.1/build/main.o] Error 1 make[2]: *** Waiting for unfinished jobs make[1]: *** [/usr/src/linux-headers-6.5.0-1002-oem/Makefile:2037: /var/lib/dkms/sysdig/0.27.1/build] Error 2 make: *** [Makefile:234: __sub-make] Error 2 make: Leaving directory '/usr/src/linux-headers-6.5.0-1002-oem' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040249] Re: test_600_config_net_cls_rsvp, test_601_config_net_cls_rsvp6 in ubuntu_qrt_kernel_security failed with J-xilinx
This is affecting j-azure-fips 5.15.0-1049.56+fips1 as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2040249 Title: test_600_config_net_cls_rsvp, test_601_config_net_cls_rsvp6 in ubuntu_qrt_kernel_security failed with J-xilinx Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: Invalid Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: Issue found with J-xilinx 5.15.0-1024.28 These are new test cases added on Oct.13 https://git.launchpad.net/qa-regression-testing/commit/?id=02d310eed77d4a21c5ecb78a2b4a1d8efb0ddf91 These two test cases are expecting NET_CLS_RSVP and NET_CLS_RSVP6 to be disabled / removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2040249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
