Date: Thu, 29 Nov 2018 22:08:22 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 230722] [nvme][resume] Delay and possible deadlock after resume Message-ID: <bug-230722-227-wKtCz220BZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230722-227@https.bugs.freebsd.org/bugzilla/> References: <bug-230722-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230722 ultrageranium@bleu255.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ultrageranium@bleu255.com --- Comment #3 from ultrageranium@bleu255.com --- I'm seeing the same on a Thinkpad X1 (2018) with 12.0-PRERELEASE (r341261) = and following hardware: nvme0@pci0:4:0:0: class=3D0x010802 card=3D0xa801144d chip=3D0xa808144= d rev=3D0x00 hdr=3D0x00 vendor =3D 'Samsung Electronics Co Ltd' device =3D 'NVMe SSD Controller SM981/PM981' class =3D mass storage subclass =3D NVM Not sure if related but I suffered an unpleasant data loss during one of th= ese hanging resuming state. Is it reliable to use suspend while this issue is not solved? --=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-230722-227-wKtCz220BZ>