ubuntu_ftrace_smoke_test timeout on F-5.15/H/J/K-riscv

Bug #1909422 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Po-Hsu Lin
linux-riscv (Ubuntu)
Invalid
Undecided
Unassigned
Groovy
Won't Fix
Undecided
Unassigned
Hirsute
Won't Fix
Undecided
Unassigned

Bug Description

Issue found on 5.8.0-13.15 RISCV with a KVM instance.

Test failed with "Timer expired (1350 sec.), nuking pid 520", test log:
$ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_ftrace_smoke_test/control
03:46:12 INFO | Writing results to /home/ubuntu/autotest/client/results/default
03:46:12 DEBUG| Initializing the state engine
03:46:12 DEBUG| Persistent state client.steps now set to []
03:46:13 DEBUG| Persistent option harness now set to None
03:46:13 DEBUG| Persistent option harness_args now set to None
03:46:13 DEBUG| Selected harness: standalone
03:46:15 INFO | START ---- ---- timestamp=1609127175 localtime=Dec 28 03:46:15
03:46:16 DEBUG| Persistent state client._record_indent now set to 1
03:46:16 DEBUG| Test has timeout: 1350 sec.
03:46:16 INFO | START ubuntu_ftrace_smoke_test.ftrace-smoke-test ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127176 timeout=1350 localtime=Dec 28 03:46:16
03:46:16 DEBUG| Persistent state client._record_indent now set to 2
03:46:16 DEBUG| Persistent state client.unexpected_reboot now set to ('ubuntu_ftrace_smoke_test.ftrace-smoke-test', 'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
03:46:16 DEBUG| Waiting for pid 520 for 1350 seconds
03:46:16 WARNI| System python is too old, crash handling disabled
03:46:16 DEBUG| Running '/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
03:46:16 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in /boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-5.8.0-13-generic)
03:46:19 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing files exist
03:46:19 DEBUG| [stdout] PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers)
03:46:19 DEBUG| [stdout] PASSED (function in /sys/kernel/debug/tracing/available_tracers)
03:46:20 DEBUG| [stdout] PASSED (nop in /sys/kernel/debug/tracing/available_tracers)
03:46:26 DEBUG| [stdout] PASSED (tracer function can be enabled)
03:46:35 DEBUG| [stdout] PASSED (tracer function_graph can be enabled)
03:46:35 DEBUG| [stdout] - tracer function_graph got enough data
03:46:35 DEBUG| [stdout] - tracer function_graph completed
03:46:36 DEBUG| [stdout] - tracer function_graph being turned off
03:46:36 DEBUG| [stdout] - tracer got 532 irq events
03:46:43 DEBUG| [stdout] - tracer hwlat got enough data
03:46:43 DEBUG| [stdout] - tracer hwlat completed
03:46:43 DEBUG| [stdout] - tracer hwlat being turned off
03:46:44 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:46 DEBUG| [stdout] PASSED (tracer hwlat can be enabled (got 12 lines of tracing output))
03:46:48 DEBUG| [stdout] - tracer blk got enough data
03:46:48 DEBUG| [stdout] - tracer blk completed
03:46:48 DEBUG| [stdout] - tracer blk being turned off
03:46:48 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:50 DEBUG| [stdout] PASSED (tracer blk can be enabled (got 2 lines of tracing output))
03:46:56 INFO | Timer expired (1350 sec.), nuking pid 520
03:46:57 INFO | ERROR ubuntu_ftrace_smoke_test.ftrace-smoke-test ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127216 localtime=Dec 28 03:46:56 Unhandled AutoservRunError: Could not kill 520
  None
  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/job.py", line 510, in _runtest
      parallel.fork_waitfor_timed(self.resultdir, pid, timeout)
    File "/home/ubuntu/autotest/client/parallel.py", line 112, in fork_waitfor_timed
      utils.nuke_pid(pid)
    File "/home/ubuntu/autotest/client/shared/utils.py", line 1214, in nuke_pid
      raise error.AutoservRunError('Could not kill %d' % pid, None)
  AutoservRunError: Could not kill 520
  None

03:46:57 INFO | END ERROR ubuntu_ftrace_smoke_test.ftrace-smoke-test ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127217 localtime=Dec 28 03:46:57

Po-Hsu Lin (cypressyew)
tags: added: 5.8 groovy kqa-blocker sru-20201130 ubuntu-ftrace-smoke-test
tags: added: riscv riscv64 sru-20210315
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

There still seems to be a timeout occurring on G/riscv and F/riscv-5.8, though the results cut off:

04/13 22:39:04 DEBUG| utils:0116| Running '/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
04/13 22:39:04 DEBUG| utils:0153| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-5.8.0-21-generic)
04/13 22:39:04 DEBUG| utils:0153| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-5.8.0-21-generic)
04/13 22:39:04 DEBUG| utils:0153| [stdout] PASSED (CONFIG_STACK_TRACER=y in /boot/config-5.8.0-21-generic)
04/13 22:39:05 DEBUG| utils:0153| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-5.8.0-21-generic)
04/13 22:39:07 DEBUG| utils:0153| [stdout] PASSED all expected /sys/kernel/debug/tracing files exist
04/13 22:39:07 DEBUG| utils:0153| [stdout] PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers)
04/13 22:39:07 DEBUG| utils:0153| [stdout] PASSED (function in /sys/kernel/debug/tracing/available_tracers)
04/13 22:39:07 DEBUG| utils:0153| [stdout] PASSED (nop in /sys/kernel/debug/tracing/available_tracers)
04/13 22:39:13 DEBUG| utils:0153| [stdout] PASSED (tracer function can be enabled)
04/13 22:39:22 DEBUG| utils:0153| [stdout] PASSED (tracer function_graph can be enabled)

tags: added: sru-20210412
tags: added: focal
Revision history for this message
Guilherme G. Piccoli (gpiccoli) wrote :

Observed on G/RISC-V , cycle sru-20210510 .

tags: added: sru-20210510
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Seeing on Hirsute/riscv 5.11.0-1010.10

tags: added: hirsute sru-20210531
Revision history for this message
Guilherme G. Piccoli (gpiccoli) wrote :

Observed on G/RISC-V , cycle sru-20210531 .

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Found on 5.11.0-1014.14~20.04.1 RISCV

tags: added: sru-20210621
summary: - ubuntu_ftrace_smoke_test timeout on G-riscv
+ ubuntu_ftrace_smoke_test timeout on F/G-riscv
Revision history for this message
Kleber Sacilotto de Souza (kleber-souza) wrote : Re: ubuntu_ftrace_smoke_test timeout on H/F-riscv

Groovy has reached EOL and hirsute/linux-riscv is also affected. Adjusting bug accordingly.

summary: - ubuntu_ftrace_smoke_test timeout on F/G-riscv
+ ubuntu_ftrace_smoke_test timeout on H/F-riscv
Changed in linux-riscv (Ubuntu Groovy):
status: New → Won't Fix
tags: added: sru-20210816
removed: kqa-blocker
Revision history for this message
Brian Murray (brian-murray) wrote :

The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release.

Changed in linux-riscv (Ubuntu Hirsute):
status: New → Won't Fix
no longer affects: linux-riscv (Ubuntu Jammy)
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This happens with the current 15 min timeout on J-riscv, K-riscv, F-5.15-riscv

They're failing even with 30 min.

45 works.

tags: added: 5.15 jammy kinetic sru-20220808
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
summary: - ubuntu_ftrace_smoke_test timeout on H/F-riscv
+ ubuntu_ftrace_smoke_test timeout on F-5.15/H/J/K-riscv
Changed in linux-riscv (Ubuntu):
status: New → Invalid
Changed in ubuntu-kernel-tests:
assignee: nobody → Po-Hsu Lin (cypressyew)
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.