[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

2018-03-27 Thread Kamal Mostafa
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1758466 Title: bionic: default io_timeout

[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

2018-03-27 Thread Robert C Jennings
** Also affects: cloud-images Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- 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/1758466 Title: bionic:

[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

2018-03-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Triaged ** Tags added: kernel-da-key -- You received this bug notification

[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

2018-03-23 Thread Phil Sweeney
Can see the difference in the dmesg output 16.04: Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-1049-aws root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 18.04: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws root=LABEL=cloudimg-rootfs ro console=tty1

[Kernel-packages] [Bug 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS

2018-03-23 Thread Phil Sweeney
apport information ** Tags added: apport-collected ec2-images ** Description changed: According to AWS docs, using newer instance types that use NVME drivers (c5/m5), the io timeout should be set to maximum (ideally 4294967295).