From owner-freebsd-bugs@freebsd.org  Tue Jan  3 12:49:17 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49591C9DEDC
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  3 Jan 2017 12:49:17 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 392D310D6
 for <freebsd-bugs@FreeBSD.org>; Tue,  3 Jan 2017 12:49:17 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v03CnF4H019059
 for <freebsd-bugs@FreeBSD.org>; Tue, 3 Jan 2017 12:49:17 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 211713] NVME controller failure: resetting
Date: Tue, 03 Jan 2017 12:49:15 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: robin.randhawa@arm.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2017 12:49:17 -0000

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.=