[Kernel-packages] [Bug 1924256] Re: nvme unpredictibly disappears after some time

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1924256

Title:
  nvme unpredictibly disappears after some time

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have a Lenovo E15 Gen 2 laptop, bought around 1 month ago, runnning
  Ubuntu 20.04 (kernel 5.8.0-48-generic)

  In this Pc, I have a 512 GB nvme running fine, and a 1TB nvme which
  somehow disappears after some time.

  Let's I turn on the PC, use it for development, word processing,
  nothing heavily sollicitating the storage, and after some
  unpredictable time, the PC freezes, and when it comes back to life,
  the nvme is unmounted and does not appear anymore until I reboot.

  I read bug #1910866 which looks very similar, but it is supposed to be
  fixed in kernel 5.8.0-41.46. As i'm facing the problem with kernel
  5.8.0-48-generic, I think it may be another bug.

  In the output of journalctl, I see this from april, 8th (filtered on
  kernel messages):

  avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 576 QID 6 timeout, aborting
  avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 577 QID 6 timeout, aborting
  avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 578 QID 6 timeout, aborting
  avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 579 QID 6 timeout, aborting
  avril 08 20:38:09 Auckland kernel: nvme nvme0: I/O 468 QID 2 timeout, reset 
controller
  avril 08 20:38:40 Auckland kernel: nvme nvme0: I/O 1 QID 0 timeout, reset 
controller
  avril 08 20:40:12 Auckland kernel: INFO: task jbd2/nvme0n1p1-:546 blocked for 
more than 120 seconds.
  avril 08 20:40:12 Auckland kernel:   Not tainted 5.8.0-48-generic 
#54~20.04.1-Ubuntu
  avril 08 20:40:12 Auckland kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  avril 08 20:40:12 Auckland kernel: jbd2/nvme0n1p1- D0   546  2 
0x4000
  avril 08 20:40:12 Auckland kernel: Call Trace:
  avril 08 20:40:12 Auckland kernel:  __schedule+0x394/0xa60
  avril 08 20:40:12 Auckland kernel:  ? percpu_counter_add_batch+0x50/0x70
  avril 08 20:40:12 Auckland kernel:  schedule+0x55/0xc0
  avril 08 20:40:12 Auckland kernel:  io_schedule+0x16/0x40
  avril 08 20:40:12 Auckland kernel:  rq_qos_wait+0x106/0x180
  avril 08 20:40:12 Auckland kernel:  ? __wbt_done+0x40/0x40
  avril 08 20:40:12 Auckland kernel:  ? sysv68_partition+0x290/0x290
  avril 08 20:40:12 Auckland kernel:  ? wbt_cleanup_cb+0x20/0x20
  avril 08 20:40:12 Auckland kernel:  wbt_wait+0x9e/0xe0
  avril 08 20:40:12 Auckland kernel:  __rq_qos_throttle+0x28/0x40
  avril 08 20:40:12 Auckland kernel:  blk_mq_make_request+0xfa/0x5f0
  avril 08 20:40:12 Auckland kernel:  generic_make_request+0x2b1/0x3b0
  avril 08 20:40:12 Auckland kernel:  submit_bio+0x51/0x1b0
  avril 08 20:40:12 Auckland kernel:  ? bio_add_page+0x6a/0x90
  avril 08 20:40:12 Auckland kernel:  submit_bh_wbc+0x182/0x1b0
  avril 08 20:40:12 Auckland kernel:  submit_bh+0x13/0x20
  avril 08 20:40:12 Auckland kernel:  
jbd2_journal_commit_transaction+0x5d0/0x17f0
  avril 08 20:40:12 Auckland kernel:  kjournald2+0xb6/0x280
  avril 08 20:40:12 Auckland kernel:  ? wait_woken+0x80/0x80
  avril 08 20:40:12 Auckland kernel:  kthread+0x114/0x150
  avril 08 20:40:12 Auckland kernel:  ? commit_timeout+0x20/0x20
  avril 08 20:40:12 Auckland kernel:  ? kthread_park+0x90/0x90
  avril 08 20:40:12 Auckland kernel:  ret_from_fork+0x1f/0x30
  avril 08 20:40:12 Auckland kernel: INFO: task kworker/u16:68:27721 blocked 
for more than 120 seconds.
  avril 08 20:40:12 Auckland kernel:   Not tainted 5.8.0-48-generic 
#54~20.04.1-Ubuntu
  avril 08 20:40:12 Auckland kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  avril 08 20:40:12 Auckland kernel: kworker/u16:68  D0 27721  2 
0x4000
  avril 08 20:40:12 Auckland kernel: Workqueue: writeback wb_workfn 
(flush-259:0)
  avril 08 20:40:12 Auckland kernel: Call Trace:
  avril 08 20:40:12 Auckland kernel:  __schedule+0x394/0xa60
  avril 08 20:40:12 Auckland kernel:  ? alloc_pages_current+0x87/0xe0
  avril 08 20:40:12 Auckland kernel:  ? bit_wait_io_timeout+0x70/0x70
  avril 08 20:40:12 Auckland kernel:  schedule+0x55/0xc0
  avril 08 20:40:12 Auckland kernel:  io_schedule+0x16/0x40
  avril 08 20:40:12 Auckland kernel:  bit_wait_io+0x11/0x50
  avril 08 20:40:12 Auckland kernel:  __wait_on_bit+0x33/0xa0
  avril 08 20:40:12 Auckland kernel:  out_of_line_wait_on_bit+0x8d/0xb0
  avril 08 20:40:12 Auckland kernel:  ? var_wake_function+0x30/0x30
  avril 08 20:40:12 Auckland kernel:  do_get_write_access+0x29b/0x3c0
  avril 08 20:40:12 Auckland kernel:  jbd2_journal_get_write_access+0x63/0x90
  avril 08 20:40:12 Auckland kernel:  __ext4_journal_get_write_access+0x7a/0x120
  

[Kernel-packages] [Bug 1924256] Re: nvme unpredictibly disappears after some time

[João Pedro Seara]

I am observing the same in Ubuntu 22.04 @ 5.15.0-46-generic.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1924256

Title:
  nvme unpredictibly disappears after some time

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have a Lenovo E15 Gen 2 laptop, bought around 1 month ago, runnning
  Ubuntu 20.04 (kernel 5.8.0-48-generic)

  In this Pc, I have a 512 GB nvme running fine, and a 1TB nvme which
  somehow disappears after some time.

  Let's I turn on the PC, use it for development, word processing,
  nothing heavily sollicitating the storage, and after some
  unpredictable time, the PC freezes, and when it comes back to life,
  the nvme is unmounted and does not appear anymore until I reboot.

  I read bug #1910866 which looks very similar, but it is supposed to be
  fixed in kernel 5.8.0-41.46. As i'm facing the problem with kernel
  5.8.0-48-generic, I think it may be another bug.

  In the output of journalctl, I see this from april, 8th (filtered on
  kernel messages):

  avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 576 QID 6 timeout, aborting
  avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 577 QID 6 timeout, aborting
  avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 578 QID 6 timeout, aborting
  avril 08 20:37:38 Auckland kernel: nvme nvme0: I/O 579 QID 6 timeout, aborting
  avril 08 20:38:09 Auckland kernel: nvme nvme0: I/O 468 QID 2 timeout, reset 
controller
  avril 08 20:38:40 Auckland kernel: nvme nvme0: I/O 1 QID 0 timeout, reset 
controller
  avril 08 20:40:12 Auckland kernel: INFO: task jbd2/nvme0n1p1-:546 blocked for 
more than 120 seconds.
  avril 08 20:40:12 Auckland kernel:   Not tainted 5.8.0-48-generic 
#54~20.04.1-Ubuntu
  avril 08 20:40:12 Auckland kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  avril 08 20:40:12 Auckland kernel: jbd2/nvme0n1p1- D0   546  2 
0x4000
  avril 08 20:40:12 Auckland kernel: Call Trace:
  avril 08 20:40:12 Auckland kernel:  __schedule+0x394/0xa60
  avril 08 20:40:12 Auckland kernel:  ? percpu_counter_add_batch+0x50/0x70
  avril 08 20:40:12 Auckland kernel:  schedule+0x55/0xc0
  avril 08 20:40:12 Auckland kernel:  io_schedule+0x16/0x40
  avril 08 20:40:12 Auckland kernel:  rq_qos_wait+0x106/0x180
  avril 08 20:40:12 Auckland kernel:  ? __wbt_done+0x40/0x40
  avril 08 20:40:12 Auckland kernel:  ? sysv68_partition+0x290/0x290
  avril 08 20:40:12 Auckland kernel:  ? wbt_cleanup_cb+0x20/0x20
  avril 08 20:40:12 Auckland kernel:  wbt_wait+0x9e/0xe0
  avril 08 20:40:12 Auckland kernel:  __rq_qos_throttle+0x28/0x40
  avril 08 20:40:12 Auckland kernel:  blk_mq_make_request+0xfa/0x5f0
  avril 08 20:40:12 Auckland kernel:  generic_make_request+0x2b1/0x3b0
  avril 08 20:40:12 Auckland kernel:  submit_bio+0x51/0x1b0
  avril 08 20:40:12 Auckland kernel:  ? bio_add_page+0x6a/0x90
  avril 08 20:40:12 Auckland kernel:  submit_bh_wbc+0x182/0x1b0
  avril 08 20:40:12 Auckland kernel:  submit_bh+0x13/0x20
  avril 08 20:40:12 Auckland kernel:  
jbd2_journal_commit_transaction+0x5d0/0x17f0
  avril 08 20:40:12 Auckland kernel:  kjournald2+0xb6/0x280
  avril 08 20:40:12 Auckland kernel:  ? wait_woken+0x80/0x80
  avril 08 20:40:12 Auckland kernel:  kthread+0x114/0x150
  avril 08 20:40:12 Auckland kernel:  ? commit_timeout+0x20/0x20
  avril 08 20:40:12 Auckland kernel:  ? kthread_park+0x90/0x90
  avril 08 20:40:12 Auckland kernel:  ret_from_fork+0x1f/0x30
  avril 08 20:40:12 Auckland kernel: INFO: task kworker/u16:68:27721 blocked 
for more than 120 seconds.
  avril 08 20:40:12 Auckland kernel:   Not tainted 5.8.0-48-generic 
#54~20.04.1-Ubuntu
  avril 08 20:40:12 Auckland kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  avril 08 20:40:12 Auckland kernel: kworker/u16:68  D0 27721  2 
0x4000
  avril 08 20:40:12 Auckland kernel: Workqueue: writeback wb_workfn 
(flush-259:0)
  avril 08 20:40:12 Auckland kernel: Call Trace:
  avril 08 20:40:12 Auckland kernel:  __schedule+0x394/0xa60
  avril 08 20:40:12 Auckland kernel:  ? alloc_pages_current+0x87/0xe0
  avril 08 20:40:12 Auckland kernel:  ? bit_wait_io_timeout+0x70/0x70
  avril 08 20:40:12 Auckland kernel:  schedule+0x55/0xc0
  avril 08 20:40:12 Auckland kernel:  io_schedule+0x16/0x40
  avril 08 20:40:12 Auckland kernel:  bit_wait_io+0x11/0x50
  avril 08 20:40:12 Auckland kernel:  __wait_on_bit+0x33/0xa0
  avril 08 20:40:12 Auckland kernel:  out_of_line_wait_on_bit+0x8d/0xb0
  avril 08 20:40:12 Auckland kernel:  ? var_wake_function+0x30/0x30
  avril 08 20:40:12 Auckland kernel:  do_get_write_access+0x29b/0x3c0
  avril 08 20:40:12 Auckland kernel:  jbd2_journal_get_write_access+0x63/0x90
  avril 08 20:40:12 Auckland kernel:  __ext4_journal_get_write_access+0x7a/0x120
  avril 08 20:40:12 Auckland kernel:  ext4_mb_mark_diskspace_used+0x80/0x430
  avril 08 2