[Canonical-ubuntu-qa] [Bug 2068024] Re: race_sched in ubuntu_stress_smoke_test will cause kernel panic on 6.8 with Azure Standard_A2_v2 instance
This bug is awaiting verification that the linux-nvidia- tegra/6.8.0-1001.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-done-noble-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-failed-noble-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-nvidia-tegra-v2 verification-needed-noble-linux-nvidia-tegra -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. 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 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: 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]
[Canonical-ubuntu-qa] [Bug 2066332] Re: net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble
This bug is awaiting verification that the linux-nvidia-
tegra/6.8.0-1001.1 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-noble-linux-nvidia-tegra' to
'verification-done-noble-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-noble-linux-nvidia-tegra' to
'verification-failed-noble-linux-nvidia-tegra'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-tegra-v2
verification-needed-noble-linux-nvidia-tegra
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2066332
Title:
net:fib_rule_tests.sh in ubuntu_kselftests_net fails on Noble
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released
Bug description:
In our SRU cycles, all Noble kernels fail in the aforementioned
kselftests:
11238 20:50:51 DEBUG| [stdout] # Cannot open network
namespace "testns": No such file or directory
This error is caused by the local fix added in 2019:
"UBUNTU: SAUCE: selftests: net: fix "from" match test in fib_rule_tests.sh"
It was no longer necessary because a similar fix was applied in upstream:
d1abf388604f ("selftests: fib_rule_tests: enable forwarding before ipv4
from/iif test")
However, such a Ubuntu-local commit is often blindly carried over to
future releases because nobody re-evaluates whether it is still needed
or not.
Now, it is causing a real issue on Noble kselftests.
$ linux/tools/testing/selftests/net$ sudo ./fib_rule_tests.sh
Cannot open network namespace "testns": No such file or directory
The reason for the failure is obvious; there is no such a namespace since the
upstream commit 6c0ee7b4d69d ("selftests/net: convert fib_rule_tests.sh to run
it in unique namespace").
Reverting the outdated commit fixes this failure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2066332/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2085649] [NEW] io_control01 test in ubuntu_ltp_controllers failed on amd64
Public bug reported:
In cycle 2024.09.30, the io_control01 test in ubuntu_ltp_controllers
failed on noble:linux-ibm-gt running on Testflinger with:
"io_control01.c:115: TFAIL: Expect: (wbytes=606720) >
(st_wbytes=630784)"
Log:
19:23:55 DEBUG| Persistent state client._record_indent now set to 2
19:23:55 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_controllers.io_control01', 'ubuntu_ltp_controllers.io_control01')
19:23:55 DEBUG| Waiting for pid 702784 for 4500 seconds
19:23:55 WARNI| System python is too old, crash handling disabled
19:23:56 ERROR| Exception escaping from test:
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 290, in execute
self._call_run_once(constraints, profile_only,
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File
"/home/ubuntu/autotest/client/tests/ubuntu_ltp_controllers/ubuntu_ltp_controllers.py",
line 136, in run_once
print(utils.system_output(cmd, verbose=False))
^^^
File "/home/ubuntu/autotest/client/shared/utils.py", line 1269, in
system_output
out = run(command, timeout=timeout, ignore_status=ignore_status,
^^
File "/home/ubuntu/autotest/client/shared/utils.py", line 916, in run
raise error.CmdError(command, bg_job.result,
autotest.client.shared.error.CmdError: Command failed, rc=1, Command returned
non-zero exit status
* Command:
/opt/ltp/runltp -f /tmp/target -q -C /dev/null -l /dev/null -T /dev/null
Exit status: 1
Duration: 0.7181665897369385
stdout:
Checking for required user/group ids
'root' user id and group found.
'nobody' user id and group found.
'bin' user id and group found.
'daemon' user id and group found.
Users group found.
Sys group found.
Required users/groups exist.
no big block device was specified on commandline.
Tests which require a big block device are disabled.
You can specify it with option -z
INFO: Test start time: Fri Oct 25 19:23:55 UTC 2024
COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 702789 -n 702789 -f
/tmp/ltp-gMZkGJeGWE/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_tmpdir.c:316: TINFO: Using /tmp/ltp-gMZkGJeGWE/LTP_io_aA6doz as tmpdir
(ext2/ext3/ext4 filesystem)
tst_device.c:96: TINFO: Found free device 0 '/dev/loop0'
tst_test.c:1860: TINFO: LTP version: 20240930
tst_test.c:1864: TINFO: Tested kernel: 6.8.0-1014-ibm-gt #15-Ubuntu SMP
PREEMPT_DYNAMIC Fri Oct 18 16:47:06 UTC 2024 x86_64
tst_test.c:1703: TINFO: Timeout per run is 0h 00m 30s
tst_supported_fs_types.c:96: TINFO: Kernel supports ext2
tst_supported_fs_types.c:61: TINFO: mkfs.ext2 does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports ext3
tst_supported_fs_types.c:61: TINFO: mkfs.ext3 does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports ext4
tst_supported_fs_types.c:61: TINFO: mkfs.ext4 does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports xfs
tst_supported_fs_types.c:61: TINFO: mkfs.xfs does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports btrfs
tst_supported_fs_types.c:61: TINFO: mkfs.btrfs does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports bcachefs
tst_supported_fs_types.c:57: TINFO: mkfs.bcachefs does not exist
tst_supported_fs_types.c:96: TINFO: Kernel supports vfat
tst_supported_fs_types.c:61: TINFO: mkfs.vfat does exist
tst_supported_fs_types.c:96: TINFO: Kernel supports exfat
tst_supported_fs_types.c:57: TINFO: mkfs.exfat does not exist
tst_supported_fs_types.c:168: TINFO: Skipping tmpfs as requested by the test
tst_test.c:1799: TINFO: === Testing on ext2 ===
tst_test.c:1158: TINFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.47.0 (5-Feb-2023)
tst_test.c:1170: TINFO: Mounting /dev/loop0 to
/tmp/ltp-gMZkGJeGWE/LTP_io_aA6doz/mnt fstyp=ext2 flags=0
io_control01.c:95: TPASS: Did some IO in the IO controller
io_control01.c:111: TPASS: Found 7:0 in io.stat
io_control01.c:112: TPASS: Expect: (rbytes=36864) > (st_rbytes=0)
io_control01.c:115: TPASS: Expect: (wbytes=36864) > (st_wbytes=0)
io_control01.c:118: TPASS: Expect: (rios=7) > (st_rios=0)
io_control01.c:121: TPASS: Expect: (wios=13) > (st_wios=0)
tst_test.c:1799: TINFO: === Testing on ext3 ===
tst_test.c:1158: TINFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
mke2fs 1.47.0 (5-Feb-2023)
tst_test.c:1170: TINFO: Mounting /dev/loop0 to
/tmp/ltp-gMZkGJeGWE/LTP_io_aA6doz/mnt fstyp=ext3 flags=0
io_control01.c:67: TINFO: Found 7:0 in io.stat
io_control01.c:95: TPASS: Did some IO
