Comment 0 for bug 1933969

Revision history for this message
Po-Hsu Lin (cypressyew) wrote : ubuntu_kernel_selftests will unable to finish properly on Groovy s390x

Issue found on kernel03 zVM with Groovy 5.8.0-60.67

On Jenkins, the test will hang and killed by the timeout:
10:08:18 INFO | ========== Summary ===========
10:08:18 INFO | No failed cases reported
10:08:18 INFO | GOOD ubuntu_kernel_selftests.ftrace ubuntu_kernel_selftests.ftrace timestamp=1624439298 localtime=Jun 23 10:08:18 completed successfully
10:08:18 INFO | END GOOD ubuntu_kernel_selftests.ftrace ubuntu_kernel_selftests.ftrace timestamp=1624439298 localtime=Jun 23 10:08:18
10:08:18 DEBUG| Persistent state client._record_indent now set to 1
10:08:18 DEBUG| Persistent state client.unexpected_reboot deleted
10:08:18 INFO | END GOOD ---- ---- timestamp=1624439298 localtime=Jun 23 10:08:18
10:08:18 DEBUG| Persistent state client._record_indent now set to 0
10:08:18 INFO | Report successfully generated at /home/ubuntu/autotest/client/results/default/job_report.html
Build timed out (after 240 minutes). Marking the build as aborted.
Build was aborted
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?

If you take a closer look on this node, you will see it's complaining modprobe command hung and killed:
  unregister_netdevice: waiting for ip6_vti0 to become free. Usage count = 1
  unregister_netdevice: waiting for ip6_vti0 to become free. Usage count = 1
  INFO: task modprobe:40237 blocked for more than 122 seconds.
        Tainted: P O 5.8.0-60-generic #67-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  modprobe D 0 40237 1265 0x00000000
  Call Trace:
   [<0000000036dc7860>] __schedule+0x300/0x840
   [<0000000036dc7e02>] schedule+0x62/0x100
   [<00000000362c3bce>] rwsem_down_write_slowpath+0x23e/0x6c0
   [<0000000036b3716c>] register_pernet_device+0x2c/0xa0
   [<000003ff80a16034>] vti_init+0x34/0x1000 [ip_vti]
   [<00000000361a88b0>] do_one_initcall+0x40/0x200
   [<000000003632b34e>] do_init_module+0x6e/0x530
   [<000000003632e06a>] __do_sys_finit_module+0xaa/0xf0
   [<0000000036dcefbc>] system_call+0xe0/0x2b8
  unregister_netdevice: waiting for ip6_vti0 to become free. Usage count = 1

Running process shows:
  root 40236 0.0 0.0 3748 1040 ? D 10:39 0:00 ip link add vti4_a type vti local 192.168.1.1 remote 192.168.1.2 key 10
  root 40237 0.0 0.0 6092 1560 ? D 10:39 0:00 /sbin/modprobe -q -- rtnl-link-vti

From the code it looks like this is caused by the net/pmtu.sh