Date: Sat, 20 Oct 2018 08:49:17 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 232466] nvme is not shut properly for suspend/resume Message-ID: <bug-232466-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232466 Bug ID: 232466 Summary: nvme is not shut properly for suspend/resume Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: phk@FreeBSD.org On a Thinkpad T480, trying to suspend/resume results in these messages on resume: nvme0: Resetting controller due to a timeout. nvme0: resetting controller nvme0: aborting outstanding i/o nvme0: READ sqid:1 cid:32 nsid:1 lba:75554599 len:8 nvme0: ABORTED - BY REQUEST (00/07) sqid:1 cid:32 cdw0:0 nvme0: aborting outstanding i/o nvme0: WRITE sqid:1 cid:39 nsid:1 lba:43225663 len:64 nvme0: ABORTED - BY REQUEST (00/07) sqid:1 cid:39 cdw0:0 nvme0: aborting outstanding i/o Sometimes there is also filesystem corruption. I als see increments to "Unsafe Shutdowns" in smartctl -a Various google searches indicates that this may be a general problem for mo= dern laptops. Most recently see on -current r339250M --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-232466-227>