Date: Tue, 03 Jan 2017 12:49:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211713] NVME controller failure: resetting Message-ID: <bug-211713-8-VcQCYaNysk@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=3D211713 --- Comment #9 from Robin Randhawa <robin.randhawa@arm.com> --- (In reply to Terry Kennedy from Comment #8) Hi Terry. Thanks for the responses. I concur with your view that this is likely somet= hing to do with the suspend-resume pathway and missing context that isn't restor= ed correctly (or at all). BTW I was incorrectly stating a ~5 second 'stall'. This is in fact closer to ~30 seconds. So after a resume from ACPI S3, there is a ~30 second freeze before the abort messages and the system becoming usable again. Most irritating. I'm trying to grok the nvme driver source to see if there is some basic sus= pend resume callbacks that need fleshing out. I will update if I make any headwa= y. I also worry that there is some ACPI <-> NVMe overlaps that may be to blame. This is a fairly new laptop and there are a whole lot of ACPI related messa= ges appearing in the kernel log buffer at suspend-resume time. Cheers. --=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-211713-8-VcQCYaNysk>