* "I/O 8 QID 0 timeout, reset controller" on 5.6-rc2
@ 2020-03-02 2:03 Jason A. Donenfeld
2020-03-03 22:02 ` Keith Busch
0 siblings, 1 reply; 3+ messages in thread
From: Jason A. Donenfeld @ 2020-03-02 2:03 UTC (permalink / raw)
To: linux-nvme, linux-ext4
Hi,
My torrent client was doing some I/O when the below happened. I'm
wondering if this is a known thing that's been fixed during the rc
cycle, a regression, or if my (pretty new) NVMe drive is failing.
Thanks,
Jason
Feb 24 20:36:58 thinkpad kernel: nvme nvme1: I/O 852 QID 15 timeout, aborting
Feb 24 20:37:29 thinkpad kernel: nvme nvme1: I/O 852 QID 15 timeout, reset controller
Feb 24 20:37:59 thinkpad kernel: nvme nvme1: I/O 8 QID 0 timeout, reset controller
Feb 24 20:39:00 thinkpad kernel: nvme nvme1: Device not ready; aborting reset
Feb 24 20:39:00 thinkpad kernel: nvme nvme1: Abort status: 0x371
Feb 24 20:39:18 thinkpad kernel: INFO: task jbd2/dm-1-8:730 blocked for more than 122 seconds.
Feb 24 20:39:18 thinkpad kernel: Tainted: P U O 5.6.0-rc2+ #39
Feb 24 20:39:18 thinkpad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 20:39:18 thinkpad kernel: jbd2/dm-1-8 D 0 730 2 0x80004000
Feb 24 20:39:18 thinkpad kernel: Call Trace:
Feb 24 20:39:18 thinkpad kernel: ? __schedule+0x1ba/0x540
Feb 24 20:39:18 thinkpad kernel: ? bit_wait_timeout+0x60/0x60
Feb 24 20:39:18 thinkpad kernel: schedule+0x45/0xb0
Feb 24 20:39:18 thinkpad kernel: io_schedule+0xd/0x40
Feb 24 20:39:18 thinkpad kernel: bit_wait_io+0x8/0x50
Feb 24 20:39:18 thinkpad kernel: __wait_on_bit+0x23/0x80
Feb 24 20:39:18 thinkpad kernel: out_of_line_wait_on_bit+0x7d/0x90
Feb 24 20:39:18 thinkpad kernel: ? var_wake_function+0x20/0x20
Feb 24 20:39:18 thinkpad kernel: jbd2_journal_commit_transaction+0xeb7/0x16c8
Feb 24 20:39:18 thinkpad kernel: kjournald2+0xa2/0x250
Feb 24 20:39:18 thinkpad kernel: ? wait_woken+0x80/0x80
Feb 24 20:39:18 thinkpad kernel: kthread+0xf3/0x130
Feb 24 20:39:18 thinkpad kernel: ? commit_timeout+0x10/0x10
Feb 24 20:39:18 thinkpad kernel: ? kthread_park+0x80/0x80
Feb 24 20:39:18 thinkpad kernel: ret_from_fork+0x1f/0x30
Feb 24 20:39:18 thinkpad kernel: INFO: task qbittorrent:2456 blocked for more than 122 seconds.
Feb 24 20:39:18 thinkpad kernel: Tainted: P U O 5.6.0-rc2+ #39
Feb 24 20:39:18 thinkpad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 20:39:18 thinkpad kernel: qbittorrent D 0 2456 1 0x00000000
Feb 24 20:39:18 thinkpad kernel: Call Trace:
Feb 24 20:39:18 thinkpad kernel: ? __schedule+0x1ba/0x540
Feb 24 20:39:18 thinkpad kernel: schedule+0x45/0xb0
Feb 24 20:39:18 thinkpad kernel: rwsem_down_write_slowpath+0x1e7/0x440
Feb 24 20:39:18 thinkpad kernel: ext4_buffered_write_iter+0x2e/0x150
Feb 24 20:39:18 thinkpad kernel: ext4_file_write_iter+0x48/0x7a0
Feb 24 20:39:18 thinkpad kernel: do_iter_readv_writev+0x124/0x180
Feb 24 20:39:18 thinkpad kernel: do_iter_write+0x77/0x190
Feb 24 20:39:18 thinkpad kernel: vfs_writev+0x7b/0xd0
Feb 24 20:39:18 thinkpad kernel: ? __fput+0x158/0x240
Feb 24 20:39:18 thinkpad kernel: ? _cond_resched+0x10/0x20
Feb 24 20:39:18 thinkpad kernel: do_pwritev+0x86/0xd0
Feb 24 20:39:18 thinkpad kernel: do_syscall_64+0x3d/0x140
Feb 24 20:39:18 thinkpad kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 24 20:39:18 thinkpad kernel: RIP: 0033:0x7f6f049cafa4
Feb 24 20:39:18 thinkpad kernel: Code: Bad RIP value.
Feb 24 20:39:18 thinkpad kernel: RSP: 002b:00007f6ee3ffc870 EFLAGS: 00000246 ORIG_RAX: 0000000000000128
Feb 24 20:39:18 thinkpad kernel: RAX: ffffffffffffffda RBX: 0000000071e78000 RCX: 00007f6f049cafa4
Feb 24 20:39:18 thinkpad kernel: RDX: 0000000000000001 RSI: 00007f6ee3ffc8c0 RDI: 0000000000000033
Feb 24 20:39:18 thinkpad kernel: RBP: 00007f6ee3ffc940 R08: 0000000000000000 R09: 0000000000000000
Feb 24 20:39:18 thinkpad kernel: R10: 0000000071e78000 R11: 0000000000000246 R12: 0000000000000001
Feb 24 20:39:18 thinkpad kernel: R13: 0000000000000033 R14: 0000000000000001 R15: 00007f6ee3ffc8c0
Feb 24 20:39:18 thinkpad kernel: INFO: task qbittorrent:7733 blocked for more than 122 seconds.
Feb 24 20:39:18 thinkpad kernel: Tainted: P U O 5.6.0-rc2+ #39
Feb 24 20:39:18 thinkpad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 20:39:18 thinkpad kernel: qbittorrent D 0 7733 1 0x00000000
Feb 24 20:39:18 thinkpad kernel: Call Trace:
Feb 24 20:39:18 thinkpad kernel: ? __schedule+0x1ba/0x540
Feb 24 20:39:18 thinkpad kernel: schedule+0x45/0xb0
Feb 24 20:39:18 thinkpad kernel: rwsem_down_write_slowpath+0x1e7/0x440
Feb 24 20:39:18 thinkpad kernel: ext4_buffered_write_iter+0x2e/0x150
Feb 24 20:39:18 thinkpad kernel: ext4_file_write_iter+0x48/0x7a0
Feb 24 20:39:18 thinkpad kernel: ? wake_up_q+0x56/0x90
Feb 24 20:39:18 thinkpad kernel: ? _cond_resched+0x10/0x20
Feb 24 20:39:18 thinkpad kernel: ? __kmalloc+0x15f/0x250
Feb 24 20:39:18 thinkpad kernel: do_iter_readv_writev+0x124/0x180
Feb 24 20:39:18 thinkpad kernel: do_iter_write+0x77/0x190
Feb 24 20:39:18 thinkpad kernel: vfs_writev+0x7b/0xd0
Feb 24 20:39:18 thinkpad kernel: ? do_epoll_ctl+0x250/0x1020
Feb 24 20:39:18 thinkpad kernel: ? __x64_sys_futex+0x127/0x140
Feb 24 20:39:18 thinkpad kernel: do_pwritev+0x86/0xd0
Feb 24 20:39:18 thinkpad kernel: do_syscall_64+0x3d/0x140
Feb 24 20:39:18 thinkpad kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 24 20:39:18 thinkpad kernel: RIP: 0033:0x7f6f049cafa4
Feb 24 20:39:18 thinkpad kernel: Code: Bad RIP value.
Feb 24 20:39:18 thinkpad kernel: RSP: 002b:00007f6e5fffbf30 EFLAGS: 00000246 ORIG_RAX: 0000000000000128
Feb 24 20:39:18 thinkpad kernel: RAX: ffffffffffffffda RBX: 0000000072b38000 RCX: 00007f6f049cafa4
Feb 24 20:39:18 thinkpad kernel: RDX: 0000000000000032 RSI: 00007f6e5fffbf80 RDI: 0000000000000033
Feb 24 20:39:18 thinkpad kernel: RBP: 00007f6e5fffc310 R08: 0000000000000000 R09: 0000000000000000
Feb 24 20:39:18 thinkpad kernel: R10: 0000000072b38000 R11: 0000000000000246 R12: 0000000000000032
Feb 24 20:39:18 thinkpad kernel: R13: 0000000000000033 R14: 0000000000000032 R15: 00007f6e5fffbf80
Feb 24 20:39:18 thinkpad kernel: INFO: task qbittorrent:11389 blocked for more than 122 seconds.
Feb 24 20:39:18 thinkpad kernel: Tainted: P U O 5.6.0-rc2+ #39
Feb 24 20:39:18 thinkpad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 20:39:18 thinkpad kernel: qbittorrent D 0 11389 1 0x00000000
Feb 24 20:39:18 thinkpad kernel: Call Trace:
Feb 24 20:39:18 thinkpad kernel: ? __schedule+0x1ba/0x540
Feb 24 20:39:18 thinkpad kernel: ? bit_wait_timeout+0x60/0x60
Feb 24 20:39:18 thinkpad kernel: schedule+0x45/0xb0
Feb 24 20:39:18 thinkpad kernel: io_schedule+0xd/0x40
Feb 24 20:39:18 thinkpad kernel: bit_wait_io+0x8/0x50
Feb 24 20:39:18 thinkpad kernel: __wait_on_bit+0x23/0x80
Feb 24 20:39:18 thinkpad kernel: out_of_line_wait_on_bit+0x7d/0x90
Feb 24 20:39:18 thinkpad kernel: ? var_wake_function+0x20/0x20
Feb 24 20:39:18 thinkpad kernel: do_get_write_access+0x2c1/0x3d0
Feb 24 20:39:18 thinkpad kernel: jbd2_journal_get_write_access+0x2e/0x50
Feb 24 20:39:18 thinkpad kernel: __ext4_journal_get_write_access+0x32/0x70
Feb 24 20:39:18 thinkpad kernel: ? ext4_dirty_inode+0x4e/0x70
Feb 24 20:39:18 thinkpad kernel: ext4_reserve_inode_write+0x8e/0xc0
Feb 24 20:39:18 thinkpad kernel: ext4_mark_inode_dirty+0x3c/0x1c0
Feb 24 20:39:18 thinkpad kernel: ext4_dirty_inode+0x4e/0x70
Feb 24 20:39:18 thinkpad kernel: __mark_inode_dirty+0x243/0x360
Feb 24 20:39:18 thinkpad kernel: generic_update_time+0x98/0xc0
Feb 24 20:39:18 thinkpad kernel: file_update_time+0xa4/0xf0
Feb 24 20:39:18 thinkpad kernel: ? generic_write_checks+0x59/0xa0
Feb 24 20:39:18 thinkpad kernel: ext4_buffered_write_iter+0x4d/0x150
Feb 24 20:39:18 thinkpad kernel: ext4_file_write_iter+0x48/0x7a0
Feb 24 20:39:18 thinkpad kernel: do_iter_readv_writev+0x124/0x180
Feb 24 20:39:18 thinkpad kernel: do_iter_write+0x77/0x190
Feb 24 20:39:18 thinkpad kernel: vfs_writev+0x7b/0xd0
Feb 24 20:39:18 thinkpad kernel: ? __x64_sys_futex+0x127/0x140
Feb 24 20:39:18 thinkpad kernel: do_pwritev+0x86/0xd0
Feb 24 20:39:18 thinkpad kernel: do_syscall_64+0x3d/0x140
Feb 24 20:39:18 thinkpad kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 24 20:39:18 thinkpad kernel: RIP: 0033:0x7f6f049cafa4
Feb 24 20:39:18 thinkpad kernel: Code: Bad RIP value.
Feb 24 20:39:18 thinkpad kernel: RSP: 002b:00007f6e5f7fb850 EFLAGS: 00000246 ORIG_RAX: 0000000000000128
Feb 24 20:39:18 thinkpad kernel: RAX: ffffffffffffffda RBX: 00000000739b0000 RCX: 00007f6f049cafa4
Feb 24 20:39:18 thinkpad kernel: RDX: 0000000000000001 RSI: 00007f6e5f7fb8a0 RDI: 000000000000002d
Feb 24 20:39:18 thinkpad kernel: RBP: 00007f6e5f7fb920 R08: 0000000000000000 R09: 0000000000000000
Feb 24 20:39:18 thinkpad kernel: R10: 00000000739b0000 R11: 0000000000000246 R12: 0000000000000001
Feb 24 20:39:18 thinkpad kernel: R13: 000000000000002d R14: 0000000000000001 R15: 00007f6e5f7fb8a0
Feb 24 20:39:18 thinkpad kernel: INFO: task kworker/u32:11:9953 blocked for more than 122 seconds.
Feb 24 20:39:18 thinkpad kernel: Tainted: P U O 5.6.0-rc2+ #39
Feb 24 20:39:18 thinkpad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 24 20:39:18 thinkpad kernel: kworker/u32:11 D 0 9953 2 0x80004000
Feb 24 20:39:18 thinkpad kernel: Workqueue: writeback wb_workfn (flush-254:1)
Feb 24 20:39:18 thinkpad kernel: Call Trace:
Feb 24 20:39:18 thinkpad kernel: ? __schedule+0x1ba/0x540
Feb 24 20:39:18 thinkpad kernel: ? bit_wait_timeout+0x60/0x60
Feb 24 20:39:18 thinkpad kernel: schedule+0x45/0xb0
Feb 24 20:39:18 thinkpad kernel: io_schedule+0xd/0x40
Feb 24 20:39:18 thinkpad kernel: bit_wait_io+0x8/0x50
Feb 24 20:39:18 thinkpad kernel: __wait_on_bit+0x23/0x80
Feb 24 20:39:18 thinkpad kernel: out_of_line_wait_on_bit+0x7d/0x90
Feb 24 20:39:18 thinkpad kernel: ? var_wake_function+0x20/0x20
Feb 24 20:39:18 thinkpad kernel: do_get_write_access+0x2c1/0x3d0
Feb 24 20:39:18 thinkpad kernel: jbd2_journal_get_write_access+0x2e/0x50
Feb 24 20:39:18 thinkpad kernel: __ext4_journal_get_write_access+0x32/0x70
Feb 24 20:39:18 thinkpad kernel: ? ext4_dirty_inode+0x4e/0x70
Feb 24 20:39:18 thinkpad kernel: ext4_reserve_inode_write+0x8e/0xc0
Feb 24 20:39:18 thinkpad kernel: ext4_mark_inode_dirty+0x3c/0x1c0
Feb 24 20:39:18 thinkpad kernel: ext4_dirty_inode+0x4e/0x70
Feb 24 20:39:18 thinkpad kernel: __mark_inode_dirty+0x243/0x360
Feb 24 20:39:18 thinkpad kernel: ext4_da_update_reserve_space+0x155/0x170
Feb 24 20:39:18 thinkpad kernel: ext4_ext_map_blocks+0xcde/0x1190
Feb 24 20:39:18 thinkpad kernel: ext4_map_blocks+0xd7/0x540
Feb 24 20:39:18 thinkpad kernel: ? _cond_resched+0x10/0x20
Feb 24 20:39:18 thinkpad kernel: ? kmem_cache_alloc+0x14a/0x200
Feb 24 20:39:18 thinkpad kernel: ext4_writepages+0x750/0xd30
Feb 24 20:39:18 thinkpad kernel: ? dma_pte_clear_level+0x158/0x1b0
Feb 24 20:39:18 thinkpad kernel: ? do_writepages+0x29/0xb0
Feb 24 20:39:18 thinkpad kernel: do_writepages+0x29/0xb0
Feb 24 20:39:18 thinkpad kernel: ? __wb_calc_thresh+0x25/0x100
Feb 24 20:39:18 thinkpad kernel: __writeback_single_inode+0x38/0x320
Feb 24 20:39:18 thinkpad kernel: writeback_sb_inodes+0x1e7/0x460
Feb 24 20:39:18 thinkpad kernel: __writeback_inodes_wb+0x47/0xc0
Feb 24 20:39:18 thinkpad kernel: wb_writeback+0x225/0x2b0
Feb 24 20:39:18 thinkpad kernel: wb_workfn+0x393/0x4c0
Feb 24 20:39:18 thinkpad kernel: process_one_work+0x1d1/0x380
Feb 24 20:39:18 thinkpad kernel: worker_thread+0x45/0x3c0
Feb 24 20:39:18 thinkpad kernel: kthread+0xf3/0x130
Feb 24 20:39:18 thinkpad kernel: ? process_one_work+0x380/0x380
Feb 24 20:39:18 thinkpad kernel: ? kthread_park+0x80/0x80
Feb 24 20:39:18 thinkpad kernel: ret_from_fork+0x1f/0x30
Feb 24 20:39:31 thinkpad kernel: nvme nvme1: Device not ready; aborting reset
Feb 24 20:39:31 thinkpad kernel: nvme nvme1: Removing after probe failure status: -19
Feb 24 20:40:02 thinkpad kernel: nvme nvme1: Device not ready; aborting reset
Feb 24 20:40:02 thinkpad kernel: blk_update_request: I/O error, dev nvme1n1, sector 2161435200 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
Feb 24 20:40:02 thinkpad kernel: Aborting journal on device dm-1-8.
Feb 24 20:40:02 thinkpad kernel: EXT4-fs error (device dm-1) in ext4_reserve_inode_write:5618: Journal has aborted
Feb 24 20:40:02 thinkpad kernel: EXT4-fs error (device dm-1) in ext4_do_update_inode:5055: Journal has aborted
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 217612288, lost sync page write
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): I/O error while writing superblock
Feb 24 20:40:02 thinkpad kernel: EXT4-fs error (device dm-1) in ext4_dirty_inode:5816: Journal has aborted
Feb 24 20:40:02 thinkpad kernel: JBD2: Error -5 detected when updating journal superblock for dm-1-8.
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): I/O error while writing superblock
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): I/O error while writing superblock
Feb 24 20:40:02 thinkpad kernel: EXT4-fs error (device dm-1) in ext4_dirty_inode:5816: IO failure
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): I/O error while writing superblock
Feb 24 20:40:02 thinkpad kernel: EXT4-fs error (device dm-1) in ext4_writepages:2795: IO failure
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): previous I/O error to superblock detected
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): I/O error while writing superblock
Feb 24 20:40:02 thinkpad kernel: EXT4-fs warning (device dm-1): ext4_end_bio:347: I/O error 10 writing to inode 22851099 starting block 43856256)
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): I/O error while writing superblock
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): I/O error while writing superblock
Feb 24 20:40:02 thinkpad kernel: EXT4-fs error (device dm-1): ext4_journal_check_start:84: Detected aborted journal
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): Remounting filesystem read-only
Feb 24 20:40:02 thinkpad kernel: EXT4-fs error (device dm-1): ext4_journal_check_start:84: Detected aborted journal
Feb 24 20:40:02 thinkpad kernel: EXT4-fs (dm-1): Remounting filesystem read-only
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Feb 24 20:40:02 thinkpad kernel: EXT4-fs error (device dm-1): ext4_journal_check_start:84: Detected aborted journal
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on device dm-1, logical block 43856256
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on device dm-1, logical block 43856257
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on device dm-1, logical block 43856258
Feb 24 20:40:02 thinkpad kernel: Buffer I/O error on device dm-1, logical block 43856259
Feb 24 20:40:02 thinkpad kernel: nvme nvme1: failed to set APST feature (-19)
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: "I/O 8 QID 0 timeout, reset controller" on 5.6-rc2
2020-03-02 2:03 "I/O 8 QID 0 timeout, reset controller" on 5.6-rc2 Jason A. Donenfeld
@ 2020-03-03 22:02 ` Keith Busch
2020-03-04 11:19 ` Jason A. Donenfeld
0 siblings, 1 reply; 3+ messages in thread
From: Keith Busch @ 2020-03-03 22:02 UTC (permalink / raw)
To: Jason A. Donenfeld; +Cc: linux-ext4, linux-nvme
On Mon, Mar 02, 2020 at 10:03:39AM +0800, Jason A. Donenfeld wrote:
> Hi,
>
> My torrent client was doing some I/O when the below happened. I'm
> wondering if this is a known thing that's been fixed during the rc
> cycle, a regression, or if my (pretty new) NVMe drive is failing.
>
> Thanks,
> Jason
>
> Feb 24 20:36:58 thinkpad kernel: nvme nvme1: I/O 852 QID 15 timeout, aborting
> Feb 24 20:37:29 thinkpad kernel: nvme nvme1: I/O 852 QID 15 timeout, reset controller
> Feb 24 20:37:59 thinkpad kernel: nvme nvme1: I/O 8 QID 0 timeout, reset controller
> Feb 24 20:39:00 thinkpad kernel: nvme nvme1: Device not ready; aborting reset
> Feb 24 20:39:00 thinkpad kernel: nvme nvme1: Abort status: 0x371
Sorry to say, this indicates the controller has become unresponsive.
You usually see "timeout" messages in batches, though, so I wonder if
only the one IO command timed out or if the controller just doesn't
support an abort command limit.
You can try throttling the queue depth and see if the problem goes away.
The lowest possible depth can be set with kernel param
"nvme.io_queue_depth=2".
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: "I/O 8 QID 0 timeout, reset controller" on 5.6-rc2
2020-03-03 22:02 ` Keith Busch
@ 2020-03-04 11:19 ` Jason A. Donenfeld
0 siblings, 0 replies; 3+ messages in thread
From: Jason A. Donenfeld @ 2020-03-04 11:19 UTC (permalink / raw)
To: Keith Busch; +Cc: linux-ext4, linux-nvme
On Wed, Mar 4, 2020 at 6:02 AM Keith Busch <kbusch@kernel.org> wrote:
>
> On Mon, Mar 02, 2020 at 10:03:39AM +0800, Jason A. Donenfeld wrote:
> > Hi,
> >
> > My torrent client was doing some I/O when the below happened. I'm
> > wondering if this is a known thing that's been fixed during the rc
> > cycle, a regression, or if my (pretty new) NVMe drive is failing.
> >
> > Thanks,
> > Jason
> >
> > Feb 24 20:36:58 thinkpad kernel: nvme nvme1: I/O 852 QID 15 timeout, aborting
> > Feb 24 20:37:29 thinkpad kernel: nvme nvme1: I/O 852 QID 15 timeout, reset controller
> > Feb 24 20:37:59 thinkpad kernel: nvme nvme1: I/O 8 QID 0 timeout, reset controller
> > Feb 24 20:39:00 thinkpad kernel: nvme nvme1: Device not ready; aborting reset
> > Feb 24 20:39:00 thinkpad kernel: nvme nvme1: Abort status: 0x371
>
> Sorry to say, this indicates the controller has become unresponsive.
> You usually see "timeout" messages in batches, though, so I wonder if
> only the one IO command timed out or if the controller just doesn't
> support an abort command limit.
>
> You can try throttling the queue depth and see if the problem goes away.
> The lowest possible depth can be set with kernel param
> "nvme.io_queue_depth=2".
I was unfortunately never able to reproduce. This happened while
downloading a torrent, and torrent clients have a history of creating
"interesting" I/O patterns. Hardware is "Samsung SSD 970 EVO Plus
2TB".
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-03-04 11:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-02 2:03 "I/O 8 QID 0 timeout, reset controller" on 5.6-rc2 Jason A. Donenfeld
2020-03-03 22:02 ` Keith Busch
2020-03-04 11:19 ` Jason A. Donenfeld
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).