See the bug lp:1927076 for recent comments/logs/findings. Shortly summarising: --- this issue can be reproduced in the following order: 1. Run the cpu-hotplug test sudo ./autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh 2. Run the reuseport_bpf_cpu test sudo ./autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu ---
Seen in logs: --- [ 287.477797] Oops: Exception in kernel mode, sig: 4 [#1] --- Or: --- [ 417.696448] BUG: Unable to handle kernel instruction fetch (NULL pointer?) [ 417.696522] Faulting instruction address: 0x00000000 [ 417.696677] Oops: Kernel access of bad area, sig: 11 [#1] --- This issue can be reproduced on P8 node entei with: * F-5.4 (5.4.0-81-generic) * F-5.11 (5.11.0-27-generic #29~20.04.1-Ubuntu) * focal-hwe (Linux thiel 5.11.0-27-generic) * focal-hwe (5.11.0-34-generic) on thiel * H-5.11 (5.11.0-31-generic) * Hirsute (5.11.0-31-generic) * `gulpin` (8335-GTA) with hirsute (5.11.0-34-generic) * `entei` it is also a POWER8 (8335-GTA) with Hirsute latest kernel (5.11.0-34-generic) Looks like not reproducible on different hardware: * Power8 LPAR: P8LPAR05 MAAS * Power9: QEMU with 4 or 128 CPUs (and 4 GB of RAM) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909286 Title: ubuntu_kernel_selftest will be interrupted with the reuseport_bpf_cpu / reuseport_bpf_numa test in net (BUG: Unable to handle kernel instruction fetch (NULL pointer?)) Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Issue found with 5.4.0-59.65~18.04.1 P8 node entei and dryden It looks like the ubuntu_kernel_selftests will be interrupted when running the reuseport_bpf_cpu / reuseport_bpf_numa in net category. From the jenkins test log you will see the test didn't finish. For node entei: 07:37:44 DEBUG| [stdout] # selftests: net: reuseport_bpf_cpu 07:37:44 DEBUG| [stdout] # ---- IPv4 UDP ---- 07:37:44 DEBUG| [stdout] # send cpu 0, receive socket 0 07:37:44 DEBUG| [stdout] # send cpu 1, receive socket 1 07:37:44 DEBUG| [stdout] # send cpu 2, receive socket 2 ... 07:37:44 DEBUG| [stdout] # send cpu 123, receive socket 123 07:37:44 DEBUG| [stdout] # send cpu 125, receive socket 125 07:37:44 DEBUG| [stdout] # send cpu 127, receive socket 127 07:37:44 DEBUG| [stdout] # ---- IPv6 UDP ---- 07:37:44 DEBUG| [stdout] # send cpu 0, receive socket 0 07:37:44 DEBUG| [stdout] # send cpu 1, receive socket 1 07:37:44 DEBUG| [stdout] # send cpu 2, receive socket 2 .... 07:37:44 DEBUG| [stdout] # send cpu 123, receive socket 123 07:37:44 DEBUG| [stdout] # send cpu 125, receive socket 125 07:37:44 DEBUG| [stdout] # send cpu 127, receive socket 127 07:37:44 DEBUG| [stdout] # ---- IPv4 TCP ---- + ARCHIVE=/var/lib/jenkins/jobs/sru-misc__B-hwe-5.4_ppc64el-generic__using_entei__for_kernel/builds/1/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@entei:kernel-test-results /var/lib/jenkins/jobs/sru-misc__B-hwe-5.4_ppc64el-generic__using_entei__for_kernel/builds/1/archive For node dryden: 08:22:09 DEBUG| [stdout] ok 2 selftests: net: reuseport_bpf_cpu 08:22:09 DEBUG| [stdout] # selftests: net: reuseport_bpf_numa 08:22:09 DEBUG| [stdout] # ---- IPv4 UDP ---- + ARCHIVE=/var/lib/jenkins/jobs/sru-misc__B-hwe-5.4_ppc64el-generic__using_dryden__for_kernel/builds/2/archive + scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -r ubuntu@dryden:kernel-test-results /var/lib/jenkins/jobs/sru-misc__B-hwe-5.4_ppc64el-generic__using_dryden__for_kernel/builds/2/archive This issue does not exist in Focal 5.4 Trace back to older Bionic 5.4 kernel: * 5.4.0-58.64~18.04.1 - not tested * 5.4.0-57.63~18.04.1 - this issue does not exist as the bpf test build is blocking the build of net test * 5.4.0-56.62~18.04.1 - missing test result as node modoc is broken * 5.4.0-52.57~18.04.1 - no such issue with node modoc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
