Date: Sun, 18 Dec 2016 16:02:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211713] NVME controller failure: resetting Message-ID: <bug-211713-8-bc5mjqzGn9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211713-8@https.bugs.freebsd.org/bugzilla/> References: <bug-211713-8@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=211713 Robin Randhawa <robin.randhawa@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robin.randhawa@arm.com --- Comment #6 from Robin Randhawa <robin.randhawa@arm.com> --- Hi all. I have a similar issue. My hardware is a Lenovo Thinkpad P50 with a 512GB nvme SSD running current (synced yesterday) with a custom kernel configuration that differs from GENERIC only in that VESA is disabled (nvidia issues while resuming from ACPI S3 if not). $ nvcontrol devlist nvme0: SAMSUNG MZVKV512HAJH-000L1 nvme0ns1 (488386MB) The particular manifestation I see is on resume when disk access seems to stall for 5-10 seconds. The relevant messages in the kernel log buffer are a scary stream of: nvme0: READ sqid:6 cid:124 nsid:1 lba:697441256 len:8 nvme0: ABORTED - BY REQUEST (00/07) sqid:6 cid:124 cdw0:0 nvme0: aborting outstanding i/o nvme0: READ sqid:8 cid:109 nsid:1 lba:399615616 len:40 nvme0: ABORTED - BY REQUEST (00/07) sqid:8 cid:109 cdw0:0 Please let me now if you need any more specifics. Thanks. -- 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-211713-8-bc5mjqzGn9>