This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1897764
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1897764
Title:
mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests
failed on X-gcp-4.15 / F-5.4 zVM
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
Issue found on Focal 5.4.0-49.53 zVM kernel04
Test failed with:
# selftests: memory-hotplug: mem-on-off-test.sh
# Test scope: 2% hotplug memory
# online all hot-pluggable memory in offline state:
# SKIPPED - no hot-pluggable memory in offline state
# offline 2% hot-pluggable memory in online state
# trying to offline 1 out of 16 memory block(s):
# online->offline memory0
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 0: unexpected fail
# online->offline memory1
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 1: unexpected fail
# online->offline memory10
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 10: unexpected fail
# online->offline memory11
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 11: unexpected fail
# online->offline memory12
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 12: unexpected fail
# online->offline memory13
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 13: unexpected fail
# online->offline memory14
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 14: unexpected fail
# online->offline memory15
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 15: unexpected fail
# online->offline memory2
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 2: unexpected fail
# online->offline memory3
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 3: unexpected fail
# online->offline memory4
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 4: unexpected fail
# online->offline memory5
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 5: unexpected fail
# online->offline memory6
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 6: unexpected fail
# online->offline memory7
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 7: unexpected fail
# online->offline memory8
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 8: unexpected fail
# online->offline memory9
# ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy
# offline_memory_expect_success 9: unexpected fail
# FAILED - unable to offline some memory blocks, device busy?
# online all hot-pluggable memory in offline state:
# SKIPPED - no hot-pluggable memory in offline state
# Test with memory notifier error injection
not ok 1 selftests: memory-hotplug: mem-on-off-test.sh # exit=1
This issue can be found on 5.4.0-46.50, 5.4.0-45.49 zVM as well.
Passed with 5.4.0-44.48
Passed with 5.4.0-43.47
Failed with 5.4.0-42.46
Looks like it's not very stable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1897764/+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
