Also verified that in an AWS instance running the aws kernel in -proposed:
$ uname -rv 4.4.0-1075-aws #85-Ubuntu SMP Thu Jan 17 17:15:12 UTC 2019
$ dmesg #cleared that before testing
[ 5429.330967] nvme 0000:00:04.0: I/O 10 QID 1 timeout, completion polled [39630.417191] nvme 0000:00:04.0: I/O 0 QID 2 timeout, completion polled [52869.430017] nvme 0000:00:04.0: I/O 17 QID 1 timeout, completion polled [69245.492236] nvme 0000:00:04.0: I/O 3 QID 2 timeout, completion polled [111366.577241] nvme 0000:00:04.0: I/O 20 QID 2 timeout, completion polled [120978.583000] nvme 0000:00:04.0: I/O 11 QID 2 timeout, completion polled [136204.614939] nvme 0000:00:04.0: I/O 7 QID 1 timeout, completion polled [142200.642476] nvme 0000:00:04.0: I/O 3 QID 1 timeout, completion polled [145549.661249] nvme 0000:00:04.0: I/O 29 QID 2 timeout, completion polled
$ uptime 10:57:48 up 1 day, 20:22, 2 users, load average: 0.00, 0.03, 0.02
Also verified that in an AWS instance running the aws kernel in -proposed:
$ uname -rv
4.4.0-1075-aws #85-Ubuntu SMP Thu Jan 17 17:15:12 UTC 2019
$ dmesg #cleared that before testing
[ 5429.330967] nvme 0000:00:04.0: I/O 10 QID 1 timeout, completion polled
[39630.417191] nvme 0000:00:04.0: I/O 0 QID 2 timeout, completion polled
[52869.430017] nvme 0000:00:04.0: I/O 17 QID 1 timeout, completion polled
[69245.492236] nvme 0000:00:04.0: I/O 3 QID 2 timeout, completion polled
[111366.577241] nvme 0000:00:04.0: I/O 20 QID 2 timeout, completion polled
[120978.583000] nvme 0000:00:04.0: I/O 11 QID 2 timeout, completion polled
[136204.614939] nvme 0000:00:04.0: I/O 7 QID 1 timeout, completion polled
[142200.642476] nvme 0000:00:04.0: I/O 3 QID 1 timeout, completion polled
[145549.661249] nvme 0000:00:04.0: I/O 29 QID 2 timeout, completion polled
$ uptime
10:57:48 up 1 day, 20:22, 2 users, load average: 0.00, 0.03, 0.02