[Bug 2044334] Re: Unable to put CPU back online on AWS x1e.xlarge instance with kernel 6.2+
Still visible on x1e.xlarge with Noble AWS 6.8.0-1009.9 ** Tags added: 6.8 noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044334 Title: Unable to put CPU back online on AWS x1e.xlarge instance with kernel 6.2+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2044334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071756] Re: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10
Thanks for the bug report and the reproducer! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071756 Title: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953287] Re: test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and variants
Fix released and no other hints is using this bug. Closing this. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953287 Title: test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and variants To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062138] Re: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2
Hi Christian, sorry for the late reply, I saw the following failure with Noble-lowlatency 6.8.0-36.36.1 AMR64 instances on openstack: ERROR: test_0 (__main__.TestLogprof.test_0) test 'ping' -- Traceback (most recent call last): File "/tmp/testlib3kk_zswu/source/noble/apparmor-4.0.0-beta3/utils/test/common_test.py", line 90, in stub_test self._run_test(test_data, expected) File "/tmp/testlib3kk_zswu/source/noble/apparmor-4.0.0-beta3/utils/test/test-logprof.py", line 99, in _run_test self.process.wait(timeout=0.3) File "/usr/lib/python3.12/subprocess.py", line 1264, in wait return self._wait(timeout=timeout) ^^^ File "/usr/lib/python3.12/subprocess.py", line 2045, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/usr/bin/python3', '../aa-logprof', '--json', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-wcpdfssw/profiles', '--no-check-mountpoint']' timed out after 0.3 seconds -- Ran 1 test in 3.599s ERROR: test_0 (__main__.TestLogprof.test_0) test 'ping' -- Traceback (most recent call last): File "/tmp/testlib3kk_zswu/source/noble/apparmor-4.0.0-beta3/utils/test/common_test.py", line 90, in stub_test self._run_test(test_data, expected) File "/tmp/testlib3kk_zswu/source/noble/apparmor-4.0.0-beta3/utils/test/test-logprof.py", line 99, in _run_test self.process.wait(timeout=0.3) File "/usr/lib/python3.12/subprocess.py", line 1264, in wait return self._wait(timeout=timeout) ^^^ File "/usr/lib/python3.12/subprocess.py", line 2045, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/usr/bin/python3', '../aa-logprof', '--json', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-wcpdfssw/profiles', '--no-check-mountpoint']' timed out after 0.3 seconds -- Ran 1 test in 3.599s -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062138 Title: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2062138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071756] Re: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10
This issue can be found with Oracular 6.10.0-4.4 AMD64 openstack instance as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071756 Title: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071776] Re: pty07 from ubuntu_ltp cause VM crash with N-oem-6.10
This issue can be found with Oracular 6.10.0-4.4 AMD64 openstack instance as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071776 Title: pty07 from ubuntu_ltp cause VM crash with N-oem-6.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071756] Re: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux-oem-6.10 (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: linux-oem-6.10 (Ubuntu Oracular) Status: New => Invalid ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.10 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071756 Title: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071776] [NEW] pty07 from ubuntu_ltp cause VM crash with N-oem-6.10
Public bug reported: The pty07 test from ubuntu_ltp will cause test interrupt with Noble OEM 6.10 VM on openstack since 6.10.0-1003.3 This issue can be reproduced with a VM on a bare-metal. When this happens the VM will be terminated. (Test passed on a Bare-metal with 6.10.0-1005-oem). Test log: <<>> tag=pty07 stime=1719989938 cmdline="pty07" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1733: TINFO: LTP version: 20230929-609-g3fc2d1b15 tst_test.c:1617: TINFO: Timeout per run is 0h 03m 00s pty07.c:92: TINFO: Saving active console 1 (VM terminated here) Steps: # On a bare-metal running with Noble sudo apt install uvtool build-essential -y sudo uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=noble arch=amd64 SSH_KEY="$HOME/.ssh/id_rsa" ssh-keygen -f $SSH_KEY -t rsa -N '' sudo -u ubuntu uvt-kvm create oem610 release=noble arch=amd64 --memory 2048 sleep 60 ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i .ssh/id_rsa ubuntu@`sudo uvt-kvm ip oem610` # Inside the VM sudo apt-add-repository ppa:canonical-kernel-team/ubuntu/proposed -y sudo apt install kernel-testing--linux-oem-6.10--full--oem -y sudo reboot sleep 60 ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i .ssh/id_rsa ubuntu@`sudo uvt-kvm ip oem610` git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests -b build-only git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest -b autotest3 rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_ltp/control echo "pty07 pty07" > /home/ubuntu/pty sudo /opt/ltp/runltp -f /home/ubuntu/pty This issue can be reproduced with mainline kernel v6.10-rc4 (AMD64 debs are not available for v6.10-rc6) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.10 (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Affects: linux-oem-6.10 (Ubuntu Oracular) Importance: Undecided Status: Invalid ** Tags: 6.10 amd64 noble oem ubuntu-ltp ** Also affects: linux-oem-6.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux-oem-6.10 (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: linux-oem-6.10 (Ubuntu Oracular) Status: New => Invalid ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.10 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Invalid ** Description changed: The pty07 test from ubuntu_ltp will cause test interrupt with Noble OEM 6.10 VM on openstack since 6.10.0-1003.3 This issue can be reproduced with a VM on a bare-metal. When this happens the VM will be terminated. (Test passed on a Bare-metal with 6.10.0-1005-oem). Test log: <<>> tag=pty07 stime=1719989938 cmdline="pty07" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1733: TINFO: LTP version: 20230929-609-g3fc2d1b15 tst_test.c:1617: TINFO: Timeout per run is 0h 03m 00s pty07.c:92: TINFO: Saving active console 1 (VM terminated here) + Steps: + # On a bare-metal running with Noble + sudo apt install uvtool build-essential -y + sudo uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=noble arch=amd64 + SSH_KEY="$HOME/.ssh/id_rsa" + ssh-keygen -f $SSH_KEY -t rsa -N '' + sudo -u ubuntu uvt-kvm create oem610 release=noble arch=amd64 --memory 2048 + sleep 60 + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i .ssh/id_rsa ubuntu@`sudo uvt-kvm ip oem610` + # Inside the VM + sudo apt-add-repository ppa:canonical-kernel-team/ubuntu/proposed -y + sudo apt install kernel-testing--linux-oem-6.10--full--oem -y + sudo reboot + sleep 60 + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i .ssh/id_rsa ubuntu@`sudo uvt-kvm ip oem610` + git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests -b build-only + git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest -b autotest3 + rm -fr autotest/client/tests + ln -sf ~/autotest-client-tests autotest/client/tests +
[Bug 2069243] Re: [Potential Regression] ubuntu_kvm_smoke_test failed with X-4.4.0-255.289 on Oracle instances
The respined Xenial kernel 4.4.0-256.290 works fine with this test. ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Released ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069243 Title: [Potential Regression] ubuntu_kvm_smoke_test failed with X-4.4.0-255.289 on Oracle instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2069243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071756] Re: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10
** Also affects: linux-oem-6.10 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071756 Title: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64 (TFAIL: Could not offline cpuXX)
** Summary changed: - cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64 + cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64 (TFAIL: Could not offline cpuXX) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836169 Title: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64 (TFAIL: Could not offline cpuXX) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071308] [NEW] CONFIG_PAGE_TABLE_ISOLATION and CONFIG_RETPOLINE should be set in N-OEM-6.10
Public bug reported:
Issue reported by ubuntu_qrt_kernel_security test with N-oem-6.10
These two kernel configs are expected to be set to satisfy the test:
FAIL: test_260_config_PTI
(__main__.KernelSecurityConfigTest.test_260_config_PTI)
Ensure kernel page table isolation is set appropriately
--
Traceback (most recent call last):
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
line 2686, in test_260_config_PTI
self.assertKernelConfig('PAGE_TABLE_ISOLATION', expected)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
line 231, in assertKernelConfig
self.assertKernelConfigSet(name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
line 217, in assertKernelConfigSet
self.assertTrue(self._test_config(name),
AssertionError: False is not true : PAGE_TABLE_ISOLATION option was expected
to be set in the kernel config
FAIL: test_265_config_retpoline
(__main__.KernelSecurityConfigTest.test_265_config_retpoline)
Ensure retpoline configuration option is set
--
Traceback (most recent call last):
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
line 2702, in test_265_config_retpoline
self.assertKernelConfig('RETPOLINE', expected)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
line 231, in assertKernelConfig
self.assertKernelConfigSet(name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
line 217, in assertKernelConfigSet
self.assertTrue(self._test_config(name),
AssertionError: False is not true : RETPOLINE option was expected to be set in
the kernel config
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Affects: linux-oem-6.10 (Ubuntu)
Importance: Undecided
Status: New
** Tags: 6.10 noble oem ubuntu-qrt-kernel-security
** Also affects: linux-oem-6.10 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- CONFIG_PTI and CONFIG_RETPOLINE should be set in N-OEM-6.10
+ CONFIG_PAGE_TABLE_ISOLATION and CONFIG_RETPOLINE should be set in N-OEM-6.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071308
Title:
CONFIG_PAGE_TABLE_ISOLATION and CONFIG_RETPOLINE should be set in
N-OEM-6.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071308/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071300] [NEW] lttng-modules failed to build with N-OEM-6.10
Public bug reported: This DKMS failed to build with Noble OEM 6.10.0-1005 Error! Bad return status for module build on kernel: 6.10.0-1005-oem (x86_64) Consult /var/lib/dkms/lttng-modules/2.13.11/build/make.log for more information. dpkg: error processing package lttng-modules-dkms (--configure): installed lttng-modules-dkms package post-installation script subprocess returned error exit status 10 Setting up g++-x86-64-linux-gnu (4:13.2.0-7ubuntu1) ... Setting up gcc-multilib (4:13.2.0-7ubuntu1) ... Setting up g++-13 (13.2.0-23ubuntu4) ... Setting up g++ (4:13.2.0-7ubuntu1) ... update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode Setting up build-essential (12.10ubuntu1) ... Processing triggers for sgml-base (1.31) ... Processing triggers for libc-bin (2.39-0ubuntu8.2) ... Processing triggers for man-db (2.12.0-4build2) ... Setting up lttng-tools (2.13.11-2.1build4) ... Created symlink /etc/systemd/system/multi-user.target.wants/lttng-sessiond.service → /usr/lib/systemd/system/lttng-sessiond.service. Errors were encountered while processing: lttng-modules-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 lttng-modules | grep installed' Running 'cat /var/lib/dkms/lttng-modules/*/build/make.log' DKMS make.log for lttng-modules-2.13.11 for kernel 6.10.0-1005-oem (x86_64) Fri Jun 21 22:08:42 UTC 2024 make: Entering directory '/usr/src/linux-headers-6.10.0-1005-oem' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0 You are using: gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0 /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/Kbuild:27: File ./mm/slab.h not found. Probe "kmem" is disabled. Use full kernel source tree to enable it. /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/Kbuild:81: File ./arch/x86/kvm/lapic.h not found. Probe "kvm" x86-specific is disabled. Use full kernel source tree to enable it. /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/Kbuild:188: Files ./fs/btrfs/*.h not found. Probe "btrfs" is disabled. Use full kernel source tree to enable it. /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/Kbuild:207: Files ./mm/internal.h not found. Probe "compaction" is disabled. Use full kernel source tree to enable it. /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/Kbuild:216: Files ./fs/ext4/*.h not found. Probe "ext4" is disabled. Use full kernel source tree to enable it. CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/ringbuffer/ring_buffer_backend.o /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/Kbuild:245: File ./drivers/base/regmap/trace.h not found. Probe "regmap" is disabled. Need Linux 4.1+ kernel source tree to enable it. CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/lttng-probe-sched.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/ringbuffer/ring_buffer_frontend.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/lttng-probe-irq.o /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/ringbuffer/ring_buffer_frontend.c:2409:12: warning: no previous prototype for ‘init_lib_ring_buffer_frontend’ [-Wmissing-prototypes] 2409 | int __init init_lib_ring_buffer_frontend(void) |^ /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/ringbuffer/ring_buffer_frontend.c:2420:13: warning: no previous prototype for ‘exit_lib_ring_buffer_frontend’ [-Wmissing-prototypes] 2420 | void __exit exit_lib_ring_buffer_frontend(void) | ^ CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/lttng-probe-timer.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/ringbuffer/ring_buffer_iterator.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/lttng-probe-module.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/ringbuffer/ring_buffer_vfs.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/lttng-probe-power.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/ringbuffer/ring_buffer_splice.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/lttng-probe-statedump.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/ringbuffer/ring_buffer_mmap.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/prio_heap/lttng_prio_heap.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/../wrapper/splice.o CC [M] /var/lib/dkms/lttng-modules/2.13.11/build/src/probes/lttng-probe-9p.o /var/lib/dkms/lttng-modules/2.13.11/build/src/lib/../wrapper/splice.c:59:9: warning: no previous prototype for ‘wrapper_splice_to_pipe’ [-Wmissing-prototypes] 59 | ssize_t
[Bug 2071301] [NEW] falcosecurity-scap-dkms failed to build on N-oem-6.10
Public bug reported:
This DKMS is required for ubuntu_sysdig_smoke_test.
Build log:
DKMS make.log for scap-0.15.1 for kernel 6.10.0-1005-oem (x86_64)
Thu Jun 27 04:29:18 UTC 2024
make: Entering directory '/usr/src/linux-headers-6.10.0-1005-oem'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4)
13.2.0
You are using: gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0
[configure-kmod] Including
/var/lib/dkms/scap/0.15.1/build//configure/DEVNODE_ARG1_CONST/Makefile.inc
/var/lib/dkms/scap/0.15.1/build//configure/ACCESS_OK_2/Makefile.inc
/var/lib/dkms/scap/0.15.1/build//configure/CLASS_CREATE_1/Makefile.inc
[configure-kmod] Setting HAS_DEVNODE_ARG1_CONST flag
[configure-kmod] Setting HAS_ACCESS_OK_2 flag
[configure-kmod] Setting HAS_CLASS_CREATE_1 flag
CC [M] /var/lib/dkms/scap/0.15.1/build/main.o
CC [M] /var/lib/dkms/scap/0.15.1/build/dynamic_params_table.o
CC [M] /var/lib/dkms/scap/0.15.1/build/fillers_table.o
CC [M] /var/lib/dkms/scap/0.15.1/build/flags_table.o
CC [M] /var/lib/dkms/scap/0.15.1/build/ppm_events.o
CC [M] /var/lib/dkms/scap/0.15.1/build/ppm_fillers.o
CC [M] /var/lib/dkms/scap/0.15.1/build/event_table.o
CC [M] /var/lib/dkms/scap/0.15.1/build/syscall_table64.o
CC [M] /var/lib/dkms/scap/0.15.1/build/ppm_cputime.o
CC [M] /var/lib/dkms/scap/0.15.1/build/ppm_tp.o
CC [M] /var/lib/dkms/scap/0.15.1/build/syscall_ia32_64_map.o
/var/lib/dkms/scap/0.15.1/build/ppm_cputime.c:353:10: warning: no previous
prototype for ‘nsec_to_clock_t’ [-Wmissing-prototypes]
353 | uint64_t nsec_to_clock_t(uint64_t x)
| ^~~
/var/lib/dkms/scap/0.15.1/build/main.c: In function ‘drop_nostate_event’:
/var/lib/dkms/scap/0.15.1/build/main.c:1653:22: error: implicit declaration of
function ‘fd_is_open’; did you mean ‘finish_open’?
[-Werror=implicit-function-declaration]
1653 | !fd_is_open(close_fd, fdt)
| ^~
| finish_open
/var/lib/dkms/scap/0.15.1/build/main.c: At top level:
/var/lib/dkms/scap/0.15.1/build/main.c:2829:5: warning: no previous prototype
for ‘scap_init’ [-Wmissing-prototypes]
2829 | int scap_init(void)
| ^
/var/lib/dkms/scap/0.15.1/build/main.c:2992:6: warning: no previous prototype
for ‘scap_exit’ [-Wmissing-prototypes]
2992 | void scap_exit(void)
| ^
/var/lib/dkms/scap/0.15.1/build/ppm_fillers.c:509:14: warning: no previous
prototype for ‘ppm_get_mm_exe_file’ [-Wmissing-prototypes]
509 | struct file *ppm_get_mm_exe_file(struct mm_struct *mm)
| ^~~
/var/lib/dkms/scap/0.15.1/build/ppm_fillers.c:550:15: warning: no previous
prototype for ‘ppm_get_mm_counter’ [-Wmissing-prototypes]
550 | unsigned long ppm_get_mm_counter(struct mm_struct *mm, int member)
| ^~
/var/lib/dkms/scap/0.15.1/build/ppm_fillers.c:728:5: warning: no previous
prototype for ‘accumulate_argv_or_env’ [-Wmissing-prototypes]
728 | int accumulate_argv_or_env(const char __user * __user *argv,
| ^~
/var/lib/dkms/scap/0.15.1/build/ppm_fillers.c:874:6: warning: no previous
prototype for ‘ppm_is_upper_layer’ [-Wmissing-prototypes]
874 | bool ppm_is_upper_layer(struct file *exe_file){
| ^~
/var/lib/dkms/scap/0.15.1/build/ppm_fillers.c:2269:5: warning: no previous
prototype for ‘f_sys_send_e_common’ [-Wmissing-prototypes]
2269 | int f_sys_send_e_common(struct event_filler_arguments *args, int *fd)
| ^~~
/var/lib/dkms/scap/0.15.1/build/ppm_fillers.c:2405:5: warning: no previous
prototype for ‘f_sys_recv_x_common’ [-Wmissing-prototypes]
2405 | int f_sys_recv_x_common(struct event_filler_arguments *args, int64_t
*retval)
| ^~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:244:
/var/lib/dkms/scap/0.15.1/build/main.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[1]: *** [/usr/src/linux-headers-6.10.0-1005-oem/Makefile:1939:
/var/lib/dkms/scap/0.15.1/build] Error 2
make: *** [Makefile:240: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.10.0-1005-oem'
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Affects: falcosecurity-libs (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-6.10 (Ubuntu)
Importance: Undecided
Status: New
** Tags: 6.10 noble oem ubuntu-sysdig-smoke-test
** Also affects: falcosecurity-libs (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.10 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071301
Title:
falcosecurity-scap-dkms failed to
[Bug 2068024] Re: race_sched in ubuntu_stress_smoke_test will cause kernel panic on 6.8 with Azure Standard_A2_v2 instance
Didn't see this issue anymore with 6.8.0-38.38. ** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068024 Title: race_sched in ubuntu_stress_smoke_test will cause kernel panic on 6.8 with Azure Standard_A2_v2 instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2068024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067291] Re: ftrace:test.d--dynevent--add_remove_btfarg.tc in ubuntu_kselftests_ftrace failed on some architectures
** Tags added: 6.8 arm64 noble sru-20240429 ubuntu-kselftests-ftrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067291 Title: ftrace:test.d--dynevent--add_remove_btfarg.tc in ubuntu_kselftests_ftrace failed on some architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2067291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067464] Re: udpgro_fwd.sh / pmtu.sh from ubuntu_kselftests_net needs net_helper.sh on Mantic
It will need this set as well: https://lore.kernel.org/stable/20240614065820.865974-1-po-hsu@canonical.com/T/#t -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067464 Title: udpgro_fwd.sh / pmtu.sh from ubuntu_kselftests_net needs net_helper.sh on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2067464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069127] Re: net:unicast_extensions.sh complains about missing lib.sh
Fix sent to stable 6.6 https://lore.kernel.org/stable/20240614065820.865974-1-po-hsu@canonical.com/T/#t -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069127 Title: net:unicast_extensions.sh complains about missing lib.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2069127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069243] Re: [Potential Regression] ubuntu_kvm_smoke_test failed with X-4.4.0-255.289 on Oracle instances
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069243 Title: [Potential Regression] ubuntu_kvm_smoke_test failed with X-4.4.0-255.289 on Oracle instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2069243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067464] Re: udpgro_fwd.sh from ubuntu_kselftests_net needs net_helper.sh on Mantic
Patch submitted to upstream but no response so far, since this is the
last cycle for Mantic I will have myself unassigned.
In 6.5.0-44 this is affecting pmtu.sh as well, it's complaining missing
helper.sh:
Running 'make run_tests -C net TEST_PROGS=pmtu.sh TEST_GEN_PROGS=''
TEST_CUSTOM_PROGS='''
make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net'
TAP version 13
1..1
# timeout set to 0
# selftests: net: pmtu.sh
# ./pmtu.sh: line 201: lib.sh: No such file or directory
# ./pmtu.sh: line 202: net_helper.sh: No such file or directory
# ./pmtu.sh: line 941: cleanup_all_ns: command not found
# ./pmtu.sh: line 536: setup_ns: command not found
# Error: argument "type" is wrong: Invalid "netns" value
** Changed in: ubuntu-kernel-tests
Assignee: Po-Hsu Lin (cypressyew) => (unassigned)
** Summary changed:
- udpgro_fwd.sh from ubuntu_kselftests_net needs net_helper.sh on Mantic
+ udpgro_fwd.sh / pmtu.sh from ubuntu_kselftests_net needs net_helper.sh on
Mantic
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Mantic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067464
Title:
udpgro_fwd.sh / pmtu.sh from ubuntu_kselftests_net needs net_helper.sh
on Mantic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2067464/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069127] [NEW] net:unicast_extensions.sh complains about missing lib.sh
Public bug reported: Issue found on Mantic 6.5.0-44.44 in cycle 2024.06.10 Running 'make run_tests -C net TEST_PROGS=unicast_extensions.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net' TAP version 13 1..1 # timeout set to 0 # selftests: net: unicast_extensions.sh # ./unicast_extensions.sh: line 31: lib.sh: No such file or directory # ### # Unicast address extensions tests (behavior of reserved IPv4 addresses) # ### # TEST: assign and ping within 240/4 (1 of 2) (is allowed)[FAIL] # TEST: assign and ping within 240/4 (2 of 2) (is allowed)[FAIL] # TEST: assign and ping within 0/8 (1 of 2) (is allowed) [FAIL] # TEST: assign and ping within 0/8 (2 of 2) (is allowed) [FAIL] # TEST: assign and ping inside 255.255/16 (is allowed)[FAIL] # TEST: assign and ping inside 255.255.255/24 (is allowed)[FAIL] # TEST: route between 240.5.6/24 and 255.1.2/24 (is allowed) [FAIL] # TEST: route between 0.200/16 and 245.99/16 (is allowed) [FAIL] # TEST: assign and ping lowest address (/24) [FAIL] # TEST: assign and ping lowest address (/26) [FAIL] # TEST: routing using lowest address [FAIL] # TEST: assigning 0.0.0.0 (is forbidden) [ OK ] # TEST: assigning 255.255.255.255 (is forbidden) [ OK ] # TEST: assign and ping inside 127/8 (is forbidden) [ OK ] # TEST: assign and ping class D address (is forbidden)[ OK ] # TEST: routing using class D (is forbidden) [ OK ] # TEST: routing using 127/8 (is forbidden)[ OK ] not ok 1 selftests: net: unicast_extensions.sh # exit=1 make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net' This is because of the stable update bug 2059991 pulls in commit 0f4765d0b4 "selftests/net: convert unicast_extensions.sh to run it in unique name space", which adds a dependency of a share library "lib.sh". And we don't have that commit for adding lib.sh to our kernel. Since this will be the last cycle of Mantic kernel, we will leave it as- is. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Tags: 6.5 mantic sru-20240610 ubuntu-kselftests-net ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069127 Title: net:unicast_extensions.sh complains about missing lib.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2069127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B/F/J
Found with jammy-lowlatency-hwe-64k 6.5.0-41.41.1~22.04.1 on node wright-kernel. Failing with "Exceeded execution time, requesting exit" as well. Maybe we need to extend the execution time. ** Tags added: 6.5 jammy sru-20240429 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892860 Title: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B/F/J To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062138] Re: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2
Hello Garcia, thanks for add that patch, I can see that we're now using this 0.3 seconds timeout now. However we have found there are still some exceptions that will still fail with this 0.3 seconds timeout: * M-lowlatency-64k 6.5.0-41.41.1 openstack ARM64 instance * M-lowlatency 6.5.0-41.41.1 bare-metal ARM64 node "wright-kerenl" * M-64k 6.5.0-41.41 openstack ARM64 instance Perhaps we will need a longer timeout. ** Tags added: sru-20240429 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062138 Title: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2062138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067527] Re: kernel BUG at crypto/algapi.c:431!
*** This bug is a duplicate of bug 2067865 *** https://bugs.launchpad.net/bugs/2067865 With Ike's help, I am now testing on doerfel with 5.4.0-186-generic. And yes this issue can be reproduced with the command mentioned in #2, I have also verified that the stress-ng update from upstream is still capable of triggering this issue. Next is to investigate the behaviour difference I will mark this bug as a duplicate of the stable update report, to get this tracked automatically. Thanks! ** This bug has been marked a duplicate of bug 2067865 Focal update: v5.4.275 upstream stable release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067527 Title: kernel BUG at crypto/algapi.c:431! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068024] Re: race_sched in ubuntu_stress_smoke_test will cause kernel panic on 6.8 with Azure Standard_A2_v2 instance
6.10.0-061000rc2-generic on Azure Standard_A2_v2 is OK. ** Description changed: This issue can be found on: * N-Azure-6.8.0-1008.8 * N-geneirc-6.8.0-35.35 * J-Azure-6.8.0-1008.8~22.04.1 With 100% reproduced rate on Azure Standard_A2_v2 instance, (reproduce rate 100%), it can be found on Standard_D2pds_v5 as well, but with a lower reproduce rate. syslog output: 2024-06-04T12:21:29.655736+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test kernel: zswap: loaded using pool lzo/zbud 2024-06-04T12:21:29.727437+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: invoked with './stress-ng -v -t 5 --race-sched 4 --race-sched-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root' 2024-06-04T12:21:29.727600+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: system: 'n-laz-az-6-8-stda2v2-u-stress-smk-test' Linux 6.8.0-1001-azure #1-Ubuntu SMP Tue Feb 13 17:53:47 UTC 2024 x86_64 2024-06-04T12:21:29.727683+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: memory (MB): total 3918.72, free 3424.57, shared 4.08, buffer 36.20, swap 0.00, free swap 0.00 2024-06-04T12:21:29.727723+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: stress-ng: info: [1250] setting to a 5 secs run per stressor 2024-06-04T12:21:29.805799+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: stress-ng: info: [1250] dispatching hogs: 4 race-sched - Console output: [ 1167.163045] I/O error, dev loop0, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 1435.517597] BUG: kernel NULL pointer dereference, address: 00a0 [ 1435.522651] #PF: supervisor read access in kernel mode [ 1435.525407] #PF: error_code(0x) - not-present page [ 1435.528122] PGD 0 P4D 0 [ 1435.529813] Oops: [#1] SMP PTI [ 1435.531744] CPU: 0 PID: 121253 Comm: stress-ng-race- Tainted: P O 6.8.0-1008-azure #8-Ubuntu [ 1435.536481] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 1435.543274] RIP: 0010:pick_next_task_fair+0x91/0x620 [ 1435.545480] Code: 91 00 00 00 49 81 bd b0 02 00 00 80 a8 89 92 75 60 4d 89 fe eb 27 4c 89 f7 e8 0b b7 ff ff 84 c0 75 3f 4c 89 f7 e8 5f 04 ff ff <4c> 8b b0 a0 00 00 00 48 89 c3 4d 85 f6 0f 84 f4 00 00 00 49 8b 46 [ 1435.554629] RSP: 0018:b2b202e73cf8 EFLAGS: 00010096 [ 1435.558030] RAX: RBX: b2b202e73dc8 RCX: fd78d84d198c4000 [ 1435.562226] RDX: 0c00 RSI: e411d03fda1d7382 RDI: 0c02 [ 1435.566496] RBP: b2b202e73d38 R08: 0002 R09: 0002 [ 1435.570327] R10: R11: R12: 920dbbc33580 [ 1435.574620] R13: 920d0557 R14: 920dbbc33680 R15: 920dbbc33680 [ 1435.579115] FS: 7fb92ad12d00() GS:920dbbc0() knlGS: [ 1435.583308] CS: 0010 DS: ES: CR0: 80050033 [ 1435.586094] CR2: 00a0 CR3: 000102364001 CR4: 003706f0 [ 1435.590178] DR0: DR1: DR2: [ 1435.594054] DR3: DR6: fffe0ff0 DR7: 0400 [ 1435.597740] Call Trace: [ 1435.599469] [ 1435.600605] ? show_regs+0x65/0x70 [ 1435.602396] ? __die+0x24/0x70 [ 1435.603999] ? page_fault_oops+0x99/0x1a0 [ 1435.605856] ? do_user_addr_fault+0x2ae/0x670 [ 1435.607915] ? exc_page_fault+0x7b/0x170 [ 1435.609976] ? asm_exc_page_fault+0x27/0x30 [ 1435.611989] ? pick_next_task_fair+0x91/0x620 [ 1435.614311] ? pick_next_task_fair+0x91/0x620 [ 1435.616811] ? wp_page_copy+0x2f7/0x690 [ 1435.618799] pick_next_task+0x5f/0xcd0 [ 1435.621060] ? do_wp_page+0x1d0/0x430 [ 1435.623596] __schedule+0x169/0x760 [ 1435.625947] ? __cgroup_account_cputime+0x28/0x30 [ 1435.628329] ? update_curr+0x15e/0x1e0 [ 1435.630179] schedule+0x2c/0xf0 [ 1435.633476] do_sched_yield+0x85/0xb0 [ 1435.635452] __do_sys_sched_yield+0xe/0x20 [ 1435.637356] x64_sys_call+0x3d9/0x2030 [ 1435.639400] do_syscall_64+0x7b/0x160 [ 1435.641857] ? handle_mm_fault+0xac/0x3a0 [ 1435.644956] ? irqentry_exit_to_user_mode+0x7b/0x220 [ 1435.647799] ? irqentry_exit+0x1d/0x30 [ 1435.650587] ? exc_page_fault+0x87/0x170 [ 1435.653213] entry_SYSCALL_64_after_hwframe+0x78/0x80 [ 1435.656728] RIP: 0033:0x7fb92ab0e7db [ 1435.659593] Code: 73 01 c3 48 8b 0d 3d 46 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 18 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 0d 46 0f 00 f7 d8 64 89 01 48 [ 1435.675388] RSP: 002b:7fff7ca243d8 EFLAGS: 0282 ORIG_RAX: 0018 [ 1435.680830] RAX: ffda RBX: RCX: 7fb92ab0e7db [ 1435.686046] RDX: 55c47ee77db0 RSI: RDI: 0002 [ 1435.690268] RBP: 0791 R08: 0002 R09: 011d99605fac8414 [ 1435.694941] R10:
[Bug 2068024] Re: race_sched in ubuntu_stress_smoke_test will cause kernel panic on Azure 6.8
** Description changed: This issue can be found on: - * N-Azure-6.8.0-1008.8 - * N-geneirc-6.8.0-35.35 - * J-Azure-6.8.0-1008.8~22.04.1 + * N-Azure-6.8.0-1008.8 + * N-geneirc-6.8.0-35.35 + * J-Azure-6.8.0-1008.8~22.04.1 - With 100% reproduced rate on Standard_A2_v2 instance, (reproduce rate - 100%), it can be found on Standard_D2pds_v5 as well, but with a lower - reproduce rate. + With 100% reproduced rate on Azure Standard_A2_v2 instance, (reproduce + rate 100%), it can be found on Standard_D2pds_v5 as well, but with a + lower reproduce rate. + syslog output: + 2024-06-04T12:21:29.655736+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test kernel: zswap: loaded using pool lzo/zbud + 2024-06-04T12:21:29.727437+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: invoked with './stress-ng -v -t 5 --race-sched 4 --race-sched-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root' + 2024-06-04T12:21:29.727600+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: system: 'n-laz-az-6-8-stda2v2-u-stress-smk-test' Linux 6.8.0-1001-azure #1-Ubuntu SMP Tue Feb 13 17:53:47 UTC 2024 x86_64 + 2024-06-04T12:21:29.727683+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: memory (MB): total 3918.72, free 3424.57, shared 4.08, buffer 36.20, swap 0.00, free swap 0.00 + 2024-06-04T12:21:29.727723+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: stress-ng: info: [1250] setting to a 5 secs run per stressor + 2024-06-04T12:21:29.805799+00:00 n-laz-az-6-8-stda2v2-u-stress-smk-test stress-ng: stress-ng: info: [1250] dispatching hogs: 4 race-sched + + + Console output: [ 1167.163045] I/O error, dev loop0, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 1435.517597] BUG: kernel NULL pointer dereference, address: 00a0 [ 1435.522651] #PF: supervisor read access in kernel mode [ 1435.525407] #PF: error_code(0x) - not-present page - [ 1435.528122] PGD 0 P4D 0 + [ 1435.528122] PGD 0 P4D 0 [ 1435.529813] Oops: [#1] SMP PTI [ 1435.531744] CPU: 0 PID: 121253 Comm: stress-ng-race- Tainted: P O 6.8.0-1008-azure #8-Ubuntu [ 1435.536481] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 1435.543274] RIP: 0010:pick_next_task_fair+0x91/0x620 [ 1435.545480] Code: 91 00 00 00 49 81 bd b0 02 00 00 80 a8 89 92 75 60 4d 89 fe eb 27 4c 89 f7 e8 0b b7 ff ff 84 c0 75 3f 4c 89 f7 e8 5f 04 ff ff <4c> 8b b0 a0 00 00 00 48 89 c3 4d 85 f6 0f 84 f4 00 00 00 49 8b 46 [ 1435.554629] RSP: 0018:b2b202e73cf8 EFLAGS: 00010096 [ 1435.558030] RAX: RBX: b2b202e73dc8 RCX: fd78d84d198c4000 [ 1435.562226] RDX: 0c00 RSI: e411d03fda1d7382 RDI: 0c02 [ 1435.566496] RBP: b2b202e73d38 R08: 0002 R09: 0002 [ 1435.570327] R10: R11: R12: 920dbbc33580 [ 1435.574620] R13: 920d0557 R14: 920dbbc33680 R15: 920dbbc33680 [ 1435.579115] FS: 7fb92ad12d00() GS:920dbbc0() knlGS: [ 1435.583308] CS: 0010 DS: ES: CR0: 80050033 [ 1435.586094] CR2: 00a0 CR3: 000102364001 CR4: 003706f0 [ 1435.590178] DR0: DR1: DR2: [ 1435.594054] DR3: DR6: fffe0ff0 DR7: 0400 [ 1435.597740] Call Trace: [ 1435.599469] [ 1435.600605] ? show_regs+0x65/0x70 [ 1435.602396] ? __die+0x24/0x70 [ 1435.603999] ? page_fault_oops+0x99/0x1a0 [ 1435.605856] ? do_user_addr_fault+0x2ae/0x670 [ 1435.607915] ? exc_page_fault+0x7b/0x170 [ 1435.609976] ? asm_exc_page_fault+0x27/0x30 [ 1435.611989] ? pick_next_task_fair+0x91/0x620 [ 1435.614311] ? pick_next_task_fair+0x91/0x620 [ 1435.616811] ? wp_page_copy+0x2f7/0x690 [ 1435.618799] pick_next_task+0x5f/0xcd0 [ 1435.621060] ? do_wp_page+0x1d0/0x430 [ 1435.623596] __schedule+0x169/0x760 [ 1435.625947] ? __cgroup_account_cputime+0x28/0x30 [ 1435.628329] ? update_curr+0x15e/0x1e0 [ 1435.630179] schedule+0x2c/0xf0 [ 1435.633476] do_sched_yield+0x85/0xb0 [ 1435.635452] __do_sys_sched_yield+0xe/0x20 [ 1435.637356] x64_sys_call+0x3d9/0x2030 [ 1435.639400] do_syscall_64+0x7b/0x160 [ 1435.641857] ? handle_mm_fault+0xac/0x3a0 [ 1435.644956] ? irqentry_exit_to_user_mode+0x7b/0x220 [ 1435.647799] ? irqentry_exit+0x1d/0x30 [ 1435.650587] ? exc_page_fault+0x87/0x170 [ 1435.653213] entry_SYSCALL_64_after_hwframe+0x78/0x80 [ 1435.656728] RIP: 0033:0x7fb92ab0e7db [ 1435.659593] Code: 73 01 c3 48 8b 0d 3d 46 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 18 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 0d 46 0f 00 f7 d8 64 89 01 48 [ 1435.675388] RSP: 002b:7fff7ca243d8 EFLAGS: 0282 ORIG_RAX: 0018 [ 1435.680830] RAX: ffda RBX:
[Bug 2067527] Re: kernel BUG at crypto/algapi.c:431!
Hi Dann, I would like to know how lone does it take to reproduce this issue? I am trying to reproduce this with a ThunderX Cavium ARM64 box (wright-kernel). But I can't trigger this panic with a 35 minutes test. BTW We have found another af-alg test hang issue on that wright-kernel https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2067570 For the patch mentioned by Hon Ming, the fix will be included in the 5.4 and 5.15 generic kernel in the following stable updates: * https://lists.ubuntu.com/archives/kernel-team/2024-June/151271.html * https://lists.ubuntu.com/archives/kernel-team/2024-June/151309.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067527 Title: kernel BUG at crypto/algapi.c:431! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066332] Re: net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble
** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: linux (Ubuntu Oracular) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Masahiro Yamada (myamada) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Masahiro Yamada (myamada) ** Changed in: linux (Ubuntu Oracular) Assignee: (unassigned) => Masahiro Yamada (myamada) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066332 Title: net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2066332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2008085] Re: net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault)
Hints removed, closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2008085 Title: net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066332] Re: net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066332 Title: net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2066332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066332] Re: net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066332 Title: net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2066332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065350] Re: rtnetlink.sh test in ubuntu_kselftests_net cause kernel panic on ARM64 node scobee-kernel with J-5.15
Failed with -97 + test code from -106. Failed with -94 + test code from -106. Passed with -92 + test code from -106. So it looks like this issue happens between -92 and -94. We didn't catch this becuase scobee-kernel was added to the pool since 2024.04.01 cycle but at that time the ubuntu_kselftests_net failed with deployment error with 5.15.0-106.116. And then we finally get it tested with -111 in 2024.04.29 ** Description changed: - Issue found with 5.15.0-106-generic + Issue found with 5.15.0-111.121, verified manually with + 5.15.0-106-generic When running the rtnetlink.sh test from ubuntu_kselftests_net, it will cause kernel panic on ARM64 node scobee-kernel. Reproduce rate is 100%, just run the rtnetlink.sh from the Jammy tree. Test log: - ubuntu@scobee-kernel:~/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net$ sudo ./rtnetlink.sh + ubuntu@scobee-kernel:~/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net$ sudo ./rtnetlink.sh PASS: policy routing PASS: route get PASS: preferred_lft addresses have expired PASS: promote_secondaries complete PASS: tc htb hierarchy PASS: gre tunnel endpoint PASS: gretap PASS: ip6gretap PASS: erspan PASS: ip6erspan PASS: bridge setup PASS: ipv6 addrlabel PASS: set ifalias 0b5c1e3b-f766-4ec3-bdf0-08779e7d3601 for test-dummy0 PASS: vrf PASS: vxlan PASS: fou (system hangs here) You will need to use console to see error message from dmesg: [ 274.758075] MACsec IEEE 802.1AE [ 275.075237] kernel BUG at mm/vmalloc.c:2716! [ 275.079520] Internal error: Oops - BUG: f2000800 [#1] SMP [ 275.085590] Modules linked in: macsec fou vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy binfmt_misc nls_iso8859_1 hisi_zip hisi_hpre hisi_sec2 hns_roce_hw_v2 hisi_qm arm_spe_pmu ecdh_generic libcurve25519_generic uacce ecc ipmi_ssif authenc hisi_trng_v2 hisi_uncore_l3c_pmu hisi_uncore_hha_pmu hisi_uncore_ddrc_pmu acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_uncore_pmu cppc_cpufreq sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx5_ib ib_uverbs ib_core realtek hibmc_drm crct10dif_ce drm_vram_helper ghash_ce sha2_ce drm_ttm_helper mlx5_core ttm sha256_arm64 sha1_ce i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt hns3 fb_sys_fops cec [ 275.085753] hisi_sas_v3_hw mlxfw rc_core hisi_sas_main psample hclge tls drm libsas xhci_pci hnae3 xhci_pci_renesas ahci scsi_transport_sas spi_dw_mmio spi_dw gpio_dwapb aes_neon_blk crypto_simd cryptd aes_ce_cipher [ 275.190870] CPU: 75 PID: 0 Comm: swapper/75 Not tainted 5.15.0-106-generic #116-Ubuntu [ 275.198753] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B160.01 01/15/2020 [ 275.207584] pstate: 0049 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 275.214514] pc : vunmap+0x50/0x54 [ 275.217824] lr : dma_common_free_remap+0x5c/0x70 [ 275.222427] sp : 8825bc50 [ 275.225728] x29: 8825bc50 x28: b7e0ce3efb40 x27: b7e0cbc0ea50 [ 275.232831] x26: 203f7fb9e9b0 x25: x24: b7e0ccd9be90 [ 275.239934] x23: f7eff000 x22: 20205cfa7480 x21: 0001 [ 275.247036] x20: 80001c1db000 x19: 80001c1db000 x18: [ 275.254139] x17: 685eb207 x16: b7e0cbc15324 x15: 63657363616d3d45 [ 275.261242] x14: b7e0ce30bf30 x13: b7e0ce30ba18 x12: 004b [ 275.268345] x11: x10: 202006e44000 x9 : b7e0cbc1af5c [ 275.275447] x8 : 001f x7 : 0061 x6 : 0021 [ 275.282550] x5 : 80001c1dbfff x4 : x3 : 80001b12dfff [ 275.289652] x2 : b7e0ce7ab5d8 x1 : 0100 x0 : 80001c1db000 [ 275.296756] Call trace: [ 275.299194] vunmap+0x50/0x54 [ 275.302149] __iommu_dma_free+0xc4/0x10c [ 275.306061] iommu_dma_free+0x44/0x60 [ 275.309706] dma_free_attrs+0xe0/0xec [ 275.313356] sec_cipher_uninit+0x54/0x70 [hisi_sec2] [ 275.318303] sec_aead_exit+0x34/0x80 [hisi_sec2] [ 275.322902] sec_aead_xcm_ctx_exit+0x30/0x40 [hisi_sec2] [ 275.328190] crypto_aead_exit_tfm+0x28/0x3c [ 275.332361] crypto_destroy_tfm+0x48/0xa0 [ 275.336359] free_rxsa+0x28/0x50 [macsec] [ 275.340354] rcu_do_batch+0x16c/0x450 [ 275.344001] rcu_core+0x160/0x310 [ 275.347302] rcu_core_si+0x18/0x2c [ 275.350688] __do_softirq+0x15c/0x410 [ 275.354336] irq_exit+0xa0/0xe0 [ 275.357468] handle_domain_irq+0x6c/0xa0 [ 275.361378] gic_handle_irq+0xec/0x1b0 [ 275.365110]
[Bug 2023051] Re: net:tls sefltest caused an oops in scobee for lunar:generic-arm64k kernel
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023051 Title: net:tls sefltest caused an oops in scobee for lunar:generic-arm64k kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2023051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064724] Re: tls in ubuntu_kselftests_net cause oops on J-xilinx
** Description changed: - Issue found on xilinx-ZCU102, xilinx-ZCU104 and xilinx-ZCU106 with - 5.15.0-1029-xilinx-zynqmp + Issue found on xilinx-ZCU104 and xilinx-ZCU106 with 5.15.0-1029-xilinx- + zynqmp $ sudo ./tls TAP version 13 1..179 # Starting 179 tests from 6 test cases. # RUN global.non_established ... #OK global.non_established ok 1 global.non_established # RUN global.keysizes ... #OK global.keysizes ok 2 global.keysizes # RUN tls_basic.base_base ... #OK tls_basic.base_base ok 3 tls_basic.base_base # RUN tls.12_gcm.sendfile ... # sendfile: Test terminated unexpectedly by signal 11 # FAIL tls.12_gcm.sendfile not ok 4 tls.12_gcm.sendfile # RUN tls.12_gcm.send_then_sendfile ... (I hit Ctrl-c here) - [ 355.715691] [ cut here ] [ 355.715691] Unable to handle kernel read from unreadable memory at virtual address [ 355.715703] Mem abort info: [ 355.715705] ESR = 0x9604 [ 355.715708] EC = 0x25: DABT (current EL), IL = 32 bits [ 355.724739] WARNING: CPU: 3 PID: 2391 at include/linux/skmsg.h:138 __sk_msg_free+0xa8/0x100 [ 355.724758] Modules linked in: tls binfmt_misc ina2xx_adc [ 355.727553] SET = 0, FnV = 0 [ 355.731276] xilinx_can can_dev mali(C) uio_pdrv_genirq sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua dmaproxy(C) pstore_blk ramoops reed_solomon [ 355.736613] EA = 0, S1PTW = 0 [ 355.739644] pstore_zone efi_pstore ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy [ 355.742791] FSC = 0x04: level 0 translation fault [ 355.742796] async_pq async_xor async_tx raid1 raid0 multipath [ 355.747666] Data abort info: [ 355.747668] ISV = 0, ISS = 0x0004 [ 355.750530] linear i2c_mux_pca954x crct10dif_ce rtc_zynqmp spi_zynqmp_gqspi i2c_cadence [ 355.754358] CM = 0, WnR = 0 [ 355.754361] zynqmp_dpsub ahci_ceva aes_neon_blk crypto_simd cryptd [ 355.757320] user pgtable: 4k pages, 48-bit VAs, pgdp=000802b55000 [ 355.757325] CPU: 3 PID: 2391 Comm: tls Tainted: G C 5.15.0-1029-xilinx-zynqmp #33-Ubuntu [ 355.763751] Hardware name: ZynqMP ZCU106 RevA (DT) [ 355.763756] pstate: 6045 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 355.763760] [] pgd=, p4d= [ 355.763764] pc : __sk_msg_free+0xa8/0x100 [ 355.770540] lr : __sk_msg_free+0x78/0x100 [ 355.770546] sp : 8cec3c30 [ 355.770549] x29: 8cec3c30 x28: 000809de8000 x27: [ 355.770556] Internal error: Oops: 9604 [#1] SMP [ 355.777676] x26: [ 355.783232] Modules linked in: [ 355.784706] x25: dead0100 [ 355.788005] tls [ 355.791043] x24: dead0122 [ 355.794429] binfmt_misc [ 355.799637] ina2xx_adc [ 355.802154] x23: 4010 [ 355.803630] xilinx_can [ 355.806061] x22: 0008038622e0 [ 355.809360] can_dev [ 355.811790] x21: 0001 [ 355.815176] mali(C) [ 355.820731] uio_pdrv_genirq [ 355.822902] x20: 00080bb1bd40 [ 355.824377] sch_fq_codel [ 355.827242] x19: 0001 [ 355.830541] dm_multipath [ 355.833145] x18: [ 355.836531] scsi_dh_rdac [ 355.842520] scsi_dh_emc [ 355.845124] x17: [ 355.846601] scsi_dh_alua [ 355.849118] x16: [ 355.852417] dmaproxy(C) [ 355.855021] x15: [ 355.858406] pstore_blk [ 355.864310] ramoops [ 355.866740] x14: [ 355.868216] reed_solomon [ 355.870386] x13: [ 355.873685] pstore_zone [ 355.876289] x12: 899d4e78 [ 355.879675] efi_pstore [ 355.885577] ip_tables [ 355.888008] x11: 8aa8dad0 [ 355.889485] x_tables [ 355.891828] x10: 8cec3b80 [ 355.895127] autofs4 [ 355.897383] x9 : 00087f79cfa0 [ 355.900769] raid10 [ 355.906325] raid456 [ 355.908408] x8 : fc00200e1a08 [ 355.909884] async_raid6_recov [ 355.912054] x7 : fc00200e1c08 [ 355.915353] async_memcpy [ 355.918391] x6 : fc00200e1c00 [ 355.921777] async_pq [ 355.927767] async_xor [ 355.930023] x5 : 800875238000 [ 355.931499] async_tx [ 355.933843] x4 : 000d [ 355.937142] raid1 [ 355.939399] x3 : 0040 [ 355.942785] raid0 [ 355.948167] multipath [ 355.950163] x2 : 00087f79cf00 [ 355.951639] linear [ 355.953983] x1 : 0704 [ 355.957282] i2c_mux_pca954x [ 355.959365] x0 : 0001 [ 355.962750] crct10dif_ce [ 355.969001] rtc_zynqmp [ 355.971606] Call trace: [ 355.973081] spi_zynqmp_gqspi [ 355.975513]
[Bug 2061107] Re: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing"
Patch applied, failed test restarted. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061107 Title: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2061107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061107] Re: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing"
LXD team got this issue resolved by pushing a version that supports ZFS 0.8 to 5.21/stable channel. Please find the detailed comment in the discourse post above. I have the MP updated. ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Merge proposal linked: https://code.launchpad.net/~canonical-kernel-team/+git/overlay-shiftfs-tests/+merge/464522 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061107 Title: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2061107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062138] Re: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2
This issue can be found on openstack ARM64 instance with M/M-lowlatency as well. ** Changed in: apparmor (Ubuntu) Status: New => Fix Released ** Tags added: sru-20240401 sru-s20240304 ** Tags added: ubuntu-qrt-apparmor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062138 Title: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2062138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062138] Re: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062138 Title: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2062138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061107] Re: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing"
LXD release note: https://discourse.ubuntu.com/t/lxd-5-21-1-lts-has-been-released/43823/5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061107 Title: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2061107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061107] Re: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing"
Comment from Simon Déziel: 5.21 and later require ZFS 2.1 or later. This means if you are using Ubuntu 20.04, you need the HWE kernel. So this failure is expected. We should either hint it or skip it from the test. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061107 Title: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2061107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061107] Re: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing"
I tried the same command with Focal 5.4.0-1089-gkeop in 2024.03.04 cycle, and it's failing with the same issue. $ sudo lxc storage create zfs zfs size=2GiB Error: Required tool 'zpool' is missing $ uname -a Linux f-lgkeop-gkeop-5-4-e2hcpu8-u-overlayfs-smk-test 5.4.0-1089-gkeop #93-Ubuntu SMP Wed Mar 13 18:13:26 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This looks like a regression in LXD to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061107 Title: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2061107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061107] [NEW] shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing"
Public bug reported: Issue found in cycle 2024.04.01 with F-gkeop (5.4.0-1091.95), F-oracle (5.4.0-1123.132) Test log Running 'sudo -iu ubuntu /home/ubuntu/autotest/client/tmp/ubuntu_overlayfs_smoke_test/src/overlay-shiftfs-tests/tests/shiftfs-lxd.sh' Error: Required tool 'zpool' is missing Creating c1 Error: Failed loading storage pool "zfs": Storage pool not found Error: Failed to fetch instance "c1" in project "default": Instance not found FAIL Error: Failed to fetch instance "c1" in project "default": Instance not found Error: Failed checking instance exists "local:c1": Failed to fetch instance "c1" in project "default": Instance not found Error: Storage pool not found This is the failing command in shiftfs-lxd.sh: $ sudo lxc storage create zfs zfs size=2GiB Error: Required tool 'zpool' is missing $ snap list lxd Name Version RevTracking Publisher Notes lxd 5.21.1-43998c6 28155 latest/stable canonical✓ - This issue does not exist in 2024.03.04 cycle for these two kernels. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: 5.4 focal sru-20240401 ubuntu-overlayfs-smoke-test ** Tags added: 5.4 focal sru-20240401 ubuntu-overlayfs-smoke-test ** Description changed: Issue found in cycle 2024.04.01 with F-gkeop (5.4.0-1091.95), F-oracle (5.4.0-1123.132) Test log - Running 'sudo -iu ubuntu /home/ubuntu/autotest/client/tmp/ubuntu_overlayfs_smoke_test/src/overlay-shiftfs-tests/tests/shiftfs-lxd.sh' - Error: Required tool 'zpool' is missing - Creating c1 - Error: Failed loading storage pool "zfs": Storage pool not found - Error: Failed to fetch instance "c1" in project "default": Instance not found - FAIL - Error: Failed to fetch instance "c1" in project "default": Instance not found - Error: Failed checking instance exists "local:c1": Failed to fetch instance "c1" in project "default": Instance not found - Error: Storage pool not found + Running 'sudo -iu ubuntu /home/ubuntu/autotest/client/tmp/ubuntu_overlayfs_smoke_test/src/overlay-shiftfs-tests/tests/shiftfs-lxd.sh' + Error: Required tool 'zpool' is missing + Creating c1 + Error: Failed loading storage pool "zfs": Storage pool not found + Error: Failed to fetch instance "c1" in project "default": Instance not found + FAIL + Error: Failed to fetch instance "c1" in project "default": Instance not found + Error: Failed checking instance exists "local:c1": Failed to fetch instance "c1" in project "default": Instance not found + Error: Storage pool not found This is the failing command in shiftfs-lxd.sh: - $ sudo lxc storage create zfs zfs size=2GiB - Error: Required tool 'zpool' is missing + $ sudo lxc storage create zfs zfs size=2GiB + Error: Required tool 'zpool' is missing + + This issue does not exist in 2024.03.04 cycle for these two kernels. ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** Description changed: Issue found in cycle 2024.04.01 with F-gkeop (5.4.0-1091.95), F-oracle (5.4.0-1123.132) Test log Running 'sudo -iu ubuntu /home/ubuntu/autotest/client/tmp/ubuntu_overlayfs_smoke_test/src/overlay-shiftfs-tests/tests/shiftfs-lxd.sh' Error: Required tool 'zpool' is missing Creating c1 Error: Failed loading storage pool "zfs": Storage pool not found Error: Failed to fetch instance "c1" in project "default": Instance not found FAIL Error: Failed to fetch instance "c1" in project "default": Instance not found Error: Failed checking instance exists "local:c1": Failed to fetch instance "c1" in project "default": Instance not found Error: Storage pool not found This is the failing command in shiftfs-lxd.sh: $ sudo lxc storage create zfs zfs size=2GiB Error: Required tool 'zpool' is missing + $ snap list lxd + Name Version RevTracking Publisher Notes + lxd 5.21.1-43998c6 28155 latest/stable canonical✓ - + This issue does not exist in 2024.03.04 cycle for these two kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061107 Title: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2061107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057734 Title: proc_sched_rt01 from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2057734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057734 Title: proc_sched_rt01 from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2057734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057734 Title: proc_sched_rt01 from ubuntu_ltp failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2057734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
Hints removed, closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056725] [NEW] virtualbox-hwe DKMS ADT test failed on F-aws ARM64 (DKMS failed to build)
Public bug reported: Our ADT test for virtualbox-hwe DKMS failed on F-aws ARM64 Based on our hint database we can see this failure at least since 5.4.0-1072.77 from commit 9333a4a0 [1] Test failed when trying to build the DKMS: Loading new virtualbox-guest-6.1.50 DKMS files... Building for 5.4.0-1120-aws Building initial module for 5.4.0-1120-aws Error! Bad return status for module build on kernel: 5.4.0-1120-aws (aarch64) Consult /var/lib/dkms/virtualbox-guest/6.1.50/build/make.log for more information. A quick grep for error from that make.log shows it's failing with: /var/lib/dkms/virtualbox-guest/6.1.50/build/vboxguest/include/iprt/assertcompile.h:97:88: error: conflicting types for ‘RTASSERTVAR’ /var/lib/dkms/virtualbox-guest/6.1.50/build/vboxguest/r0drv/linux/the-linux-kernel.h:189:11: fatal error: asm/fpu/api.h: No such file or directory Please find attachment for the complete make.log The architecture for virtualbox-hwe listed on the project page are: amd64 i386, I am not sure why this was triggered for ARM64 ADT. [1] https://git.launchpad.net/~canonical-kernel/+git/adt-matrix-hints/commit/?id=9333a4a0b81bc436e9b2fb89f99b73477715a66e ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: virtualbox-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: arm64 aws focal sru-20240205 ** Attachment added: "virtual-box-dkms-make.log" https://bugs.launchpad.net/bugs/2056725/+attachment/5754735/+files/virtual-box-dkms-make.log ** Also affects: virtualbox-hwe (Ubuntu) Importance: Undecided Status: New ** Description changed: Our ADT test for virtualbox-hwe DKMS failed on F-aws ARM64 Based on our hint database we can see this failure at least since 5.4.0-1072.77 from commit 9333a4a0 [1] Test failed when trying to build the DKMS: - Loading new virtualbox-guest-6.1.50 DKMS files... - Building for 5.4.0-1120-aws - Building initial module for 5.4.0-1120-aws - Error! Bad return status for module build on kernel: 5.4.0-1120-aws (aarch64) - Consult /var/lib/dkms/virtualbox-guest/6.1.50/build/make.log for more information. + Loading new virtualbox-guest-6.1.50 DKMS files... + Building for 5.4.0-1120-aws + Building initial module for 5.4.0-1120-aws + Error! Bad return status for module build on kernel: 5.4.0-1120-aws (aarch64) + Consult /var/lib/dkms/virtualbox-guest/6.1.50/build/make.log for more information. A quick grep for error from that make.log shows it's failing with: /var/lib/dkms/virtualbox-guest/6.1.50/build/vboxguest/include/iprt/assertcompile.h:97:88: error: conflicting types for ‘RTASSERTVAR’ /var/lib/dkms/virtualbox-guest/6.1.50/build/vboxguest/r0drv/linux/the-linux-kernel.h:189:11: fatal error: asm/fpu/api.h: No such file or directory Please find attachment for the complete make.log - [1] https://git.launchpad.net/~canonical-kernel/+git/adt-matrix- - hints/commit/?id=9333a4a0b81bc436e9b2fb89f99b73477715a66e + The architecture for virtualbox-hwe listed on the project page are: + amd64 i386, I am not sure why this was triggered for ARM64 ADT. + + + [1] https://git.launchpad.net/~canonical-kernel/+git/adt-matrix-hints/commit/?id=9333a4a0b81bc436e9b2fb89f99b73477715a66e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056725 Title: virtualbox-hwe DKMS ADT test failed on F-aws ARM64 (DKMS failed to build) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2056725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055483 Title: net:pmtu.sh ubuntu_kselftests_net fails vxlan test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055483 Title: net:pmtu.sh ubuntu_kselftests_net fails vxlan test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055483 Title: net:pmtu.sh ubuntu_kselftests_net fails vxlan test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055483 Title: net:pmtu.sh ubuntu_kselftests_net fails vxlan test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055473 Title: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055473 Title: pmtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967493] Re: pl2303 serial adapter not recognized
Hello, thanks for the bug report, I have built some test kernels with this patch: https://people.canonical.com/~phlin/kernel/lp-1967493-pl2303/ Can you give them a try? Thank you. The kernel version for F-5.13 should be: 5.13.0-47-generic #52~20.04.1+lp1967493 Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967493 Title: pl2303 serial adapter not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967493] Re: pl2303 serial adapter not recognized
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967493 Title: pl2303 serial adapter not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967493] Re: pl2303 serial adapter not recognized
** Package changed: linux-signed-hwe-5.13 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967493 Title: pl2303 serial adapter not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959215] Re: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought
Found on node vought with F-OEM 5.14.0-1040.44 ** Tags added: 5.14 focal oem sru-20220509 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959215 Title: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 1cc8" on Impish with node vought To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1959215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969624] Re: kernel NULL pointer dereference while removing floppy module
This issue does not exist in mainline 5.16-rc1 [1] but exist in 5.15 [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.16-rc1/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969624 Title: kernel NULL pointer dereference while removing floppy module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 Note that this test is not failing on F-oem-5.14 but it's better to have corresponding patches applied to reduce the maintenance cost in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case - Only I-5.13 and F-oem-5.14 need these patches. + Only F-5.4, I-5.13 and F-oem-5.14 need these patches. First patch (e7e4785f): - - Can be cherry-picked to Impish 5.13 + - Can be cherry-picked to F-5.4 / Impish 5.13 - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - - Can be cherry-picked to Impish 5.13 (-C2 is required while + - Can be cherry-picked to F-5.4 / Impish 5.13 (-C2 is required while applying it due to our SAUCE patches) - F-oem-5.14 has already got this one applied. The reason why we need the second patch is that after the first one got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish 5.13 and F-oem-5.14 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. v2: Update cover-letter content and target in patch title to make it easier to read. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
https://lists.ubuntu.com/archives/kernel-team/2022-May/130739.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
** Description changed: [Impact] - test_vxlan_under_vrf.sh should not be failing anymore (unless it's a - kernel config related issue) with patches submitted for fixing this - test in bug 1871015. + test_vxlan_under_vrf.sh should not be failing anymore with patches + submitted to fix it in bug 1871015 (unless it's a kernel config + related issue). - We should remove the SAUCE patches that mark "vxlan_under_vrf" test - failure as expected failure to catch regressions in the future. + With the regression-testing result hinting system available, we should + remove the SAUCE patches that mark "vxlan_under_vrf" test failure as + an expected failure to catch regressions in the future. This could + reduce maintenance cost as well. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] - Tested with F/I/J/F-oem-5.14/J-oem-5.17. + Patched test script tested with F/I/J/F-oem-5.14/J-oem-5.17. I have + also modify the test case to fail it deliberately to verify this + change, it works as expected. [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. ** Description changed: [Impact] test_vxlan_under_vrf.sh should not be failing anymore with patches submitted to fix it in bug 1871015 (unless it's a kernel config related issue). With the regression-testing result hinting system available, we should - remove the SAUCE patches that mark "vxlan_under_vrf" test failure as + remove the SAUCE patches that mark "underlay in a VRF" test failure as an expected failure to catch regressions in the future. This could reduce maintenance cost as well. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] Patched test script tested with F/I/J/F-oem-5.14/J-oem-5.17. I have also modify the test case to fail it deliberately to verify this change, it works as expected. [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
** Description changed: [Impact] - test_vxlan_under_vrf.sh should not be failing anymore (except if it's a config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 1871015 + test_vxlan_under_vrf.sh should not be failing anymore (unless it's a + kernel config related issue) with patches submitted for fixing this + test in bug 1871015. - We should remove the SAUCE patches that mark "vxlan_under_vrf" failure - as expected failure to catch regressions in the future. + We should remove the SAUCE patches that mark "vxlan_under_vrf" test + failure as expected failure to catch regressions in the future. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] - + Tested with F/I/J/F-oem-5.14/J-oem-5.17. [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975691
Title:
Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Tags added: focal impish jammy kinetic oem ubuntu-kernel-selftests -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
Just realized that Focal need this patch as well. ** Changed in: linux (Ubuntu Focal) Status: Fix Released => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
** Summary changed: - Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests + Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975691] Re: Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
V2 https://lists.ubuntu.com/archives/kernel-team/2022-May/130594.html ** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but it's better to have corresponding patches applied to reduce the maintenance cost in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case First patch (e7e4785f): - Can be cherry-picked to Impish 5.13 - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - Can be cherry-picked to Impish 5.13 (-C2 is required while applying it due to our SAUCE patches) - F-oem-5.14 has already got this one applied. - - Can be cherry-picked to J-oem-5.17 The reason why we need the second patch is that after the first one got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish - 5.13, F-oem-5.14 and J-oem-5.17 without any issue: + 5.13 and F-oem-5.14 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 ** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity [ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity [ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 - Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but - it's better to have corresponding patches applied to reduce the - maintenance cost in the future. + Note that this test is not failing on F-oem-5.14 but it's better to + have corresponding patches applied to reduce the maintenance cost + in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case First patch (e7e4785f): - - Can be cherry-picked to Impish 5.13 - - Can be cherry-picked to F-oem-5.14. + - Can be cherry-picked to Impish 5.13 + - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - - Can be cherry-picked to Impish 5.13 (-C2 is required while - applying it due to our SAUCE patches) - - F-oem-5.14 has already got this one applied. + - Can be cherry-picked to Impish 5.13 (-C2 is required while + applying it due to our SAUCE patches) + - F-oem-5.14 has already got this one applied. The reason why we need the second patch is that after the first one got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: - Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] + Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish 5.13 and F-oem-5.14 without any issue: - Checking HV connectivity [ OK ] - Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] - Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] + Checking HV connectivity [ OK ] + Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] + Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but + it's better to have corresponding patches applied to reduce the + maintenance cost in the future. + [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case - The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and - F-oem-5.14. + First patch (e7e4785f): + - Can be cherry-picked to Impish 5.13 + - Can be cherry-picked to F-oem-5.14. + Second patch (b50d3b46): + - Can be cherry-picked to Impish 5.13 (-C2 is required while + applying it due to our SAUCE patches) + - F-oem-5.14 has already got this one applied. + - Can be cherry-picked to J-oem-5.17 - Note that this test is not failing on F-oem-5.14, but it's better to - have it applied to reduce the maintenance cost. - - After the first patch was applied, we will need the second patch on - Impish 5.13 to solve the another failure, which we made it an expected + The reason why we need the second patch is that after the first one + got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] - The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but - must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has - already got this one applied. - [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish - 5.13 and F-oem-5.14 without any issue: + 5.13, F-oem-5.14 and J-oem-5.17 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. - [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975691] [NEW] Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
Public bug reported: [Impact] test_vxlan_under_vrf.sh should not be failing anymore (except if it's a config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 1871015 We should remove the SAUCE patches that mark "vxlan_under_vrf" failure as expected failure to catch regressions in the future. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. ** Affects: ubuntu-kernel-tests Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remvoe SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
https://lists.ubuntu.com/archives/kernel-team/2022-May/130587.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] - The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: + test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests + will fail on 5.13 kernel with: - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity[ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity [ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. - After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches: - Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] + After the first patch was applied, we will need the second patch on + Impish 5.13 to solve the another failure, which we made it an expected + failure (XFAIL) with SAUCE patches: + Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] - The second patch (b50d3b46) can be cherry-picked with must be applied - with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one - applied. + The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but + must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has + already got this one applied. [Test] - Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: - Checking HV connectivity [ OK ] - Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] - Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] + With the patched test_vxlan_under_vrf.sh test, it can pass on Impish + 5.13 and F-oem-5.14 without any issue: + Checking HV connectivity [ OK ] + Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] + Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] - Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. + Change limit to test cases, should not have any real impact to any + kernel functions. But if these fixes are incorrect we will see + failures in our regression-testing report. The worst scenario is + getting false-negative results. + [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity[ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case - The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. + The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and + F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] - F-oem-5.14 has already got this one applied. + The second patch (b50d3b46) can be cherry-picked with must be applied + with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one + applied. [Test] Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: - Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' - make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' - make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install - make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' -INSTALL ./usr/include - make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - TAP version 13 - 1..1 - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity[ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 + Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' + make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' + make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install + make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + INSTALL ./usr/include + make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + TAP version 13 + 1..1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity[ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test - * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case + * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: - + Checking HV connectivity [ OK ] + Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] + Check VM connectivity through VXLAN (underlay in a VRF)[ OK ] [Where problems could occur] + Change limit to test cases, should not have any real impact to kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 ** Description changed: [Impact] The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: - Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' - make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' - make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install - make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - INSTALL ./usr/include - make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' - TAP version 13 - 1..1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity[ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost. After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] Patch tested on Impish 5.13 and
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: [Impact] + The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: + Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' + make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' + make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install + make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' +INSTALL ./usr/include + make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' + TAP version 13 + 1..1 + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity[ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 [Fix] + * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test + * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case + The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14. + + Note that this test is not failing on F-oem-5.14, but it's better to + have it applied to reduce the maintenance cost. + + After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches: + Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] + Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue: [Where problems could occur] [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Summary changed: - test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) + test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Description changed: + [Impact] + + + [Fix] + + + [Test] + + + [Where problems could occur] + + [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 - # selftests: net: test_vxlan_under_vrf.sh - # Checking HV connectivity [ OK ] - # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] - not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 - + # selftests: net: test_vxlan_under_vrf.sh + # Checking HV connectivity [ OK ] + # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] + not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Invalid => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid ** Tags added: 13 5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972791] Re: If i want my P.C. OK, i must to start with the 5.11.0-40-generic Kernel Release . Not another.
Good to hear that :D enjoy it! ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972791 Title: If i want my P.C. OK, i must to start with the 5.11.0-40-generic Kernel Release . Not another. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming
This has been applied in Jammy via stable update process: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959376 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957753 Title: net/mlx5e: EPERM on vlan 0 programming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947836] Re: nvidia-340 cannot be installed on F-Intel-5.13
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947836 Title: nvidia-340 cannot be installed on F-Intel-5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1947836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940080] Re: ubuntu-kernel-selftests.ftrace hangs on riscv64
** Summary changed: - ubuntu-kernel-selftests.ftrace fails on riscv64 + ubuntu-kernel-selftests.ftrace hangs on riscv64 ** Tags added: sru-20220509 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940080 Title: ubuntu-kernel-selftests.ftrace hangs on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966417] Re: memcontrol04 in ubuntu_ltp_controllers failed on J-azure (Low events in F)
Found with J-OEM 5.17.0-1004.4 with node wildcat ** Tags added: 5.17 oem sru-20220418 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966417 Title: memcontrol04 in ubuntu_ltp_controllers failed on J-azure (Low events in F) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1966417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] Re: kernel BUG in pci_assign_unassigned_bus_resources
Hi, the kernel you're using, 5.4.0-64.72, is relatively old. Can you give the latest Focal kernel 5.4.0-111.125 a try to see if this issue still exist? Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy)
** Tags removed: azures ** Tags added: azure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973261] Re: f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17
This issue can be reproduced with 5.18.0-051800rc6-generic as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973261 Title: f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1973261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973261] Re: f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17
** Package changed: linux-signed-oem-5.17 (Ubuntu) => linux-oem-5.17 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973261 Title: f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1973261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973261] [NEW] f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17
Public bug reported: Issue found on Jammy OEM 5.17.0-1004.4 Test output: 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) dmesg output: [ 390.757211] Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 [ 390.773367] loop6: detected capacity change from 0 to 2097152 [ 390.801666] loop7: detected capacity change from 0 to 2097152 [ 392.126867] BTRFS: device fsid 3c464492-2cf2-4feb-a6fd-26f90d644196 devid 1 transid 6 /dev/loop6 scanned by systemd-udevd (1407) [ 392.196398] BTRFS: device fsid 3c464492-2cf2-4feb-a6fd-26f90d644196 devid 2 transid 6 /dev/loop7 scanned by mkfs.btrfs (1409) [ 392.548599] BTRFS info (device loop6): flagging fs with big metadata feature [ 392.548610] BTRFS info (device loop6): allowing degraded mounts [ 392.548614] BTRFS info (device loop6): using free space tree [ 392.548617] BTRFS info (device loop6): has skinny extents [ 392.549304] BTRFS warning (device loop6): devid 2 uuid 918c3e31-5c12-491e-aac0-a007eda45078 is missing [ 392.549434] BTRFS warning (device loop6): devid 2 uuid 918c3e31-5c12-491e-aac0-a007eda45078 is missing [ 392.550341] BTRFS info (device loop6): checking UUID tree [ 392.562271] BTRFS info (device loop6): balance: force reducing metadata redundancy [ 392.622941] BTRFS info (device loop6): balance: start -f -dconvert=single -mconvert=single -sconvert=single [ 392.623003] BTRFS info (device loop6): relocating block group 362545152 flags system [ 392.742941] BTRFS info (device loop6): relocating block group 245104640 flags metadata [ 393.004397] BTRFS info (device loop6): relocating block group 137756672 flags data|raid1 [ 393.298466] BTRFS info (device loop6): relocating block group 30408704 flags metadata|raid1 [ 393.591373] BTRFS info (device loop6): found 7 extents, stage: move data extents [ 393.959629] BTRFS info (device loop6): relocating block group 22020096 flags system|raid1 [ 394.210882] BTRFS info (device loop6): 1 enospc errors during balance [ 394.210893] BTRFS info (device loop6): balance: ended with status: -28 [ 394.437519] Test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 returned 0 This is not a regression as this failure can be found with 5.17.0-1002.2 / 5.17.0-1003.3 as well. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1004-oem 5.17.0-1004.4 ProcVersionSignature: User Name 5.17.0-1004.4-oem 5.17.3 Uname: Linux 5.17.0-1004-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri May 13 05:52:35 2022 SourcePackage: linux-signed-oem-5.17 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-signed-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Tags: 5.17 amd64 apport-bug jammy oem package-from-proposed ubuntu-btrfs-kernel-fixes uec-images ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: 5.17 oem ubuntu-btrfs-kernel-fixes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973261 Title: f88ba6a2a in ubuntu_btrfs_kernel_fixes failed on J-OEM-5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1973261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel"
This would fail on another ARM64 node howzit-kernel as well with Jammy 5.15.0-27-generic But without the messages from mpt3sas_cm0 dmesg output: [ 2945.964263] LTP: starting read_all_sys (read_all -d /sys -q -r 3) [ 2947.922462] WARNING! power/level is deprecated; use power/control instead [ 2949.808190] bdi 7:6: the stable_pages_required attribute has been removed. Use the stable_writes queue attribute instead. [ 2949.931340] No UUID available providing old NGUID [ 2949.937332] No UUID available providing old NGUID [ 2949.937814] No UUID available providing old NGUID [ 2950.630986] Unable to handle kernel paging request at virtual address 80007cf003bf [ 2950.631121] Unable to handle kernel paging request at virtual address 80007cf003bf [ 2950.631160] Unable to handle kernel paging request at virtual address 80007cf003bf [ 2950.631168] Mem abort info: [ 2950.631172] ESR = 0x9621 [ 2950.631175] EC = 0x25: DABT (current EL), IL = 32 bits [ 2950.631180] SET = 0, FnV = 0 [ 2950.631183] EA = 0, S1PTW = 0 [ 2950.631186] FSC = 0x21: alignment fault [ 2950.631190] Data abort info: [ 2950.631193] ISV = 0, ISS = 0x0021 [ 2950.631196] CM = 0, WnR = 0 [ 2950.631199] swapper pgtable: 4k pages, 48-bit VAs, pgdp=400a02db7000 [ 2950.631204] [80007cf003bf] pgd=181b3003, p4d=181b3003, pud=18000c3dc003, pmd=18007a118003, pte=006888230f0f [ 2950.631228] Internal error: Oops: 9621 [#1] SMP [ 2950.631236] Modules linked in: arm_spe_pmu efi_pstore nls_iso8859_1 input_leds joydev acpi_ipmi ipmi_ssif arm_cmn xgene_hwmon arm_dmc620_pmu arm_dsu_pmu cppc_cpufreq acpi_tad sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid cdc_ether hid usbnet mlx5_ib ib_uverbs ib_core uas usb_storage ast drm_vram_helper drm_ttm_helper ttm i2c_algo_bit drm_kms_helper crct10dif_ce ghash_ce syscopyarea sha2_ce sysfillrect sysimgblt sha256_arm64 fb_sys_fops mlx5_core sha1_ce cec rc_core nvme mlxfw drm xhci_pci psample nvme_core xhci_pci_renesas tls aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 2950.631420] CPU: 5 PID: 46308 Comm: read_all Not tainted 5.15.0-27-generic #28-Ubuntu [ 2950.631426] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26 [ 2950.631430] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2950.631437] pc : __memcpy+0x168/0x260 [ 2950.631456] lr : memory_read_from_buffer+0x58/0x80 [ 2950.631470] sp : 8000776ebb60 [ 2950.631473] x29: 8000776ebb60 x28: 07fff4eb x27: [ 2950.631485] x26: x25: x24: 07ff8ac2ae20 [ 2950.631495] x23: 8000776ebc60 x22: 03ff x21: 8000776ebbc8 [ 2950.631506] x20: 03ff x19: 03ff x18: [ 2950.631516] x17: x16: x15: [ 2950.631526] x14: x13: x12: [ 2950.631536] x11: x10: x9 : [ 2950.631546] x8 : x7 : x6 : [ 2950.631556] x5 : 07fff26a6bff x4 : 80007cf003ff x3 : 07fff26a6b80 [ 2950.631566] x2 : ffef x1 : 80007cf003c0 x0 : 07fff26a6800 [ 2950.631576] Call trace: [ 2950.631579] __memcpy+0x168/0x260 [ 2950.631585] acpi_data_show+0x5c/0x90 [ 2950.631596] sysfs_kf_bin_read+0x78/0xa0 [ 2950.631607] kernfs_file_read_iter+0x9c/0x1a4 [ 2950.631613] kernfs_fop_read_iter+0x34/0x50 [ 2950.631619] new_sync_read+0xf0/0x184 [ 2950.631629] vfs_read+0x158/0x1f0 [ 2950.631635] ksys_read+0x74/0x100 [ 2950.631640] __arm64_sys_read+0x28/0x34 [ 2950.631645] invoke_syscall+0x78/0x100 [ 2950.631657] el0_svc_common.constprop.0+0x54/0x184 [ 2950.631664] do_el0_svc+0x34/0x9c [ 2950.631670] el0_svc+0x48/0x1b0 [ 2950.631681] el0t_64_sync_handler+0xa4/0x130 [ 2950.631686] el0t_64_sync+0x1a4/0x1a8 [ 2950.631697] Code: a984346c a9c4342c f1010042 54fffee8 (a97c3c8e) [ 2950.631703] ---[ end trace 36f3d711c3548ceb ]--- [ 2950.638926] Mem abort info: [ 2950.646846] Mem abort info: [ 2950.646852] ESR = 0x9621 [ 2950.646855] EC = 0x25: DABT (current EL), IL = 32 bits [ 2950.646860] SET = 0, FnV = 0 [ 2950.646861] EA = 0, S1PTW = 0 [ 2950.646866] FSC = 0x21: alignment fault [ 2950.654786] ESR = 0x9621 [ 2950.654792] EC = 0x25: DABT (current EL), IL = 32 bits [ 2950.654797] SET = 0, FnV = 0 [ 2950.654800] EA = 0, S1PTW = 0 [ 2950.657589] Data abort info: [ 2950.657593] ISV = 0, ISS = 0x0021 [ 2950.657596] CM = 0, WnR = 0 [ 2950.657599] swapper pgtable: 4k pages, 48-bit VAs,
[Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel"
** Summary changed: - kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel" + kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel" ** Description changed: Issue found on Jammy 5.17.0-8-generic #8~22.04.2-Ubuntu and Jammy 5.15.0-27-generic with ARM64 node helo-kernel only. It looks like this is hardware-specific. The read_all_sys test in fs from ubuntu_ltp will cause kernel oops and test will timeout. + + Steps to reproduce this: + git clone -b sru git://git.launchpad.net/~canonical-kernel-team/+git/ltp + cd ltp + make autotools + ./configure + make + make install + echo "read_all_sys read_all -d /sys -q -r 3" > /tmp/fs + sudo /opt/ltp/runltp -f /tmp/fs Test log: <<>> tag=read_all_sys stime=1652343855 cmdline="read_all -d /sys -q -r 3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1456: TINFO: Timeout per run is 0h 30m 00s Test timeouted, sending SIGKILL! tst_test.c:1500: TINFO: Killed the leftover descendant processes tst_test.c:1506: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1508: TBROK: Test killed! (timeout?) Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1800 termination_type=exited termination_id=2 corefile=no cutime=39 cstime=140 <<>> dmesg output: [ 1614.203083] LTP: starting read_all_sys (read_all -d /sys -q -r 3) [ 1617.509566] mpt3sas :8d:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM [ 1617.543837] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550373] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550381] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550474] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550504] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550593] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.550622] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.598371] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.606183] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.641990] mpt3sas :8d:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 1617.973894] WARNING! power/level is deprecated; use power/control instead [ 1619.368112] bdi 7:6: the stable_pages_required attribute has been removed. Use the stable_writes queue attribute instead. [ 1627.430319] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.438256] Mem abort info: [ 1627.441086] ESR = 0x9621 [ 1627.444133] EC = 0x25: DABT (current EL), IL = 32 bits [ 1627.449469] SET = 0, FnV = 0 [ 1627.452515] EA = 0, S1PTW = 0 [ 1627.455676] FSC = 0x21: alignment fault [ 1627.459701] Data abort info: [ 1627.462597] ISV = 0, ISS = 0x0021 [ 1627.466449] CM = 0, WnR = 0 [ 1627.469434] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f4aba000 [ 1627.476160] [800033b503bf] pgd=10bffcfff003, p4d=10bffcfff003, pud=10bffcffe003, pmd=1008948f5003, pte=006880213f0f [ 1627.488712] Internal error: Oops: 9621 [#1] SMP [ 1627.493585] Modules linked in: efi_pstore nls_iso8859_1 joydev input_leds acpi_ipmi ipmi_ssif thunderx2_pmu cppc_cpufreq sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid uas hid usb_storage ast drm_vram_helper drm_ttm_helper i2c_smbus ttm i2c_algo_bit drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 rc_core sha1_ce qede mpt3sas qed raid_class drm scsi_transport_sas xhci_pci ahci xhci_pci_renesas gpio_xlp i2c_xlp9xx aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 1627.500861] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.562614] CPU: 71 PID: 4190 Comm: read_all Not tainted 5.17.0-8-generic #8~22.04.2-Ubuntu [ 1627.562623] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030 06/04/2020 [ 1627.562626] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1627.570544] Mem abort info: [ 1627.571497] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.571505] Mem abort info: [ 1627.571508] ESR = 0x9621 [ 1627.571511] EC = 0x25: DABT (current EL), IL = 32 bits [ 1627.571516] SET =
[Bug 1973153] Re: kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel"
** Summary changed: - kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.17 ARM64 + kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel" ** Description changed: - Issue found on 5.17.0-8-generic #8~22.04.2-Ubuntu with ARM64 node helo- - kernel + Issue found on Jammy 5.17.0-8-generic #8~22.04.2-Ubuntu and Jammy + 5.15.0-27-generic with ARM64 node helo-kernel only. + + It looks like this is hardware-specific. The read_all_sys test in fs from ubuntu_ltp will cause kernel oops and test will timeout. Test log: <<>> tag=read_all_sys stime=1652343855 cmdline="read_all -d /sys -q -r 3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1456: TINFO: Timeout per run is 0h 30m 00s Test timeouted, sending SIGKILL! tst_test.c:1500: TINFO: Killed the leftover descendant processes tst_test.c:1506: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1508: TBROK: Test killed! (timeout?) Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1800 termination_type=exited termination_id=2 corefile=no cutime=39 cstime=140 <<>> - dmesg output: [ 1614.203083] LTP: starting read_all_sys (read_all -d /sys -q -r 3) [ 1617.509566] mpt3sas :8d:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM [ 1617.543837] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550373] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550381] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550474] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550504] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550593] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.550622] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.598371] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.606183] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.641990] mpt3sas :8d:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 1617.973894] WARNING! power/level is deprecated; use power/control instead [ 1619.368112] bdi 7:6: the stable_pages_required attribute has been removed. Use the stable_writes queue attribute instead. [ 1627.430319] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.438256] Mem abort info: [ 1627.441086] ESR = 0x9621 [ 1627.444133] EC = 0x25: DABT (current EL), IL = 32 bits [ 1627.449469] SET = 0, FnV = 0 [ 1627.452515] EA = 0, S1PTW = 0 [ 1627.455676] FSC = 0x21: alignment fault [ 1627.459701] Data abort info: [ 1627.462597] ISV = 0, ISS = 0x0021 [ 1627.466449] CM = 0, WnR = 0 [ 1627.469434] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f4aba000 [ 1627.476160] [800033b503bf] pgd=10bffcfff003, p4d=10bffcfff003, pud=10bffcffe003, pmd=1008948f5003, pte=006880213f0f [ 1627.488712] Internal error: Oops: 9621 [#1] SMP [ 1627.493585] Modules linked in: efi_pstore nls_iso8859_1 joydev input_leds acpi_ipmi ipmi_ssif thunderx2_pmu cppc_cpufreq sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid uas hid usb_storage ast drm_vram_helper drm_ttm_helper i2c_smbus ttm i2c_algo_bit drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 rc_core sha1_ce qede mpt3sas qed raid_class drm scsi_transport_sas xhci_pci ahci xhci_pci_renesas gpio_xlp i2c_xlp9xx aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 1627.500861] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.562614] CPU: 71 PID: 4190 Comm: read_all Not tainted 5.17.0-8-generic #8~22.04.2-Ubuntu [ 1627.562623] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030 06/04/2020 [ 1627.562626] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1627.570544] Mem abort info: [ 1627.571497] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.571505] Mem abort info: [ 1627.571508] ESR = 0x9621 [ 1627.571511] EC = 0x25: DABT (current EL), IL = 32 bits [ 1627.571516] SET = 0, FnV = 0 [ 1627.571519] EA = 0, S1PTW = 0 [ 1627.571521] FSC = 0x21: alignment fault [ 1627.571524] Data abort info: [ 1627.571526] ISV = 0, ISS = 0x0021 [ 1627.571529] CM =
