$ sudo ./check block/016
block/016 (send a signal to a process waiting on a frozen queue)
block/016 (send a signal to a process waiting on a frozen queue) [failed]
runtime ... 8.112s
--- tests/block/016.out 2018-06-15 10:05:09.080764871 +0100
+++ results/nodev/block/016.out.bad 2018-06-15 10:05:27.236769759 +0100
@@ -1,2 +1,3 @@
Running block/016
+dd: error reading '/dev/nullb0': Input/output error
Test complete
After (i.e. 4.15.0-23.26~lp1776887):
$ sudo ./check block/016
block/016 (send a signal to a process waiting on a frozen queue) [passed]
runtime 8.112s ... 10.086s
$
I don't see any problem with the patched VM, though obviously it would be nice to have someone test both normal suspend and the pm_test reproducer on a physical install.
Awesome. Thanks.
I can't test suspend in a VM, and I don't have a physical Ubuntu install.
The block developers arranged a more convenient test for the underlying issue in https:/ /github. com/osandov/ blktests/
Before (i.e. linux-image- 4.15.0- 23-generic) :
$ sudo ./check block/016 nodev/block/ 016.out. bad 2018-06-15 10:05:27.236769759 +0100
block/016 (send a signal to a process waiting on a frozen queue)
block/016 (send a signal to a process waiting on a frozen queue) [failed]
runtime ... 8.112s
--- tests/block/016.out 2018-06-15 10:05:09.080764871 +0100
+++ results/
@@ -1,2 +1,3 @@
Running block/016
+dd: error reading '/dev/nullb0': Input/output error
Test complete
After (i.e. 4.15.0- 23.26~lp1776887 ):
$ sudo ./check block/016
block/016 (send a signal to a process waiting on a frozen queue) [passed]
runtime 8.112s ... 10.086s
$
I don't see any problem with the patched VM, though obviously it would be nice to have someone test both normal suspend and the pm_test reproducer on a physical install.