[VERIFICATION ZESTY]
# rmadison linux-image-4.10.0-41-generic | 4.10.0-41.45 | zesty-proposed | amd64, arm64, armhf, i386, ppc64el, s390x
# lsb_release -r Release: 17.04
# apt-get changelog linux-image-4.10.0-41-generic | grep -A2 1729119 * NVMe timeout is too short (LP: #1729119) - nvme: update timeout module parameter type
# uname -r 4.10.0-41-generic
I had no nvme drive at my disposal but the following test should suffice :
# lsmod | grep -i nvme
# modprobe nvme_core io_timeout=123456
# lsmod | grep -i nvme nvme_core 57344 0
# cat /sys/module/nvme_core/parameters/io_timeout 123456
** Note that it doesn't seems to work at runtime (if the module is already loaded). It only works when the module haven't been previously loaded for some reasons **
But I don't see this as a blocker for the current SRU.
root@zesty:~# lsmod | grep -i nvme nvme_core 57344 0
root@zesty:~# modprobe nvme_core io_timeout=123457
root@zesty:~# cat /sys/module/nvme_core/parameters/io_timeout 123456
- Eric
[VERIFICATION ZESTY]
# rmadison 4.10.0- 41-generic | 4.10.0-41.45 | zesty-proposed | amd64, arm64, armhf, i386, ppc64el, s390x
linux-image-
# lsb_release -r
Release: 17.04
# apt-get changelog linux-image- 4.10.0- 41-generic | grep -A2 1729119
* NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
# uname -r
4.10.0-41-generic
I had no nvme drive at my disposal but the following test should suffice :
# lsmod | grep -i nvme
# modprobe nvme_core io_timeout=123456
# lsmod | grep -i nvme
nvme_core 57344 0
# cat /sys/module/ nvme_core/ parameters/ io_timeout
123456
** Note that it doesn't seems to work at runtime (if the module is already loaded). It only works when the module haven't been previously loaded for some reasons **
But I don't see this as a blocker for the current SRU.
root@zesty:~# lsmod | grep -i nvme
nvme_core 57344 0
root@zesty:~# modprobe nvme_core io_timeout=123457
root@zesty:~# cat /sys/module/ nvme_core/ parameters/ io_timeout
123456
- Eric