From owner-freebsd-current@freebsd.org  Mon May 15 17:42:44 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 C6C17D6DC2A
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 15 May 2017 17:42:44 +0000 (UTC)
 (envelope-from jonathan@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2610:1c1:1:6074::16:84])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id A5A65CB3;
 Mon, 15 May 2017 17:42:44 +0000 (UTC)
 (envelope-from jonathan@FreeBSD.org)
Received: from [134.153.0.231] (unknown [127.0.1.132])
 by freefall.freebsd.org (Postfix) with ESMTP id 653A359F7;
 Mon, 15 May 2017 17:42:43 +0000 (UTC)
 (envelope-from jonathan@FreeBSD.org)
From: "Jonathan Anderson" <jonathan@FreeBSD.org>
To: "Konstantin Belousov" <kostikbel@gmail.com>
Cc: "Poul-Henning Kamp" <phk@phk.freebsd.dk>,
 "Edward Tomasz Napiera??a" <trasz@FreeBSD.org>,
 "Manuel St?hn" <freebsdnewbie@freenet.de>, freebsd-current@freebsd.org
Subject: Re: regression suspend/resume on Lenovo T420
Date: Mon, 15 May 2017 15:12:43 -0230
Message-ID: <70A6E833-37A3-45F1-BA61-95A2A4378DB4@FreeBSD.org>
In-Reply-To: <20170515172725.GE1622@kib.kiev.ua>
References: <5746a37cd73e062c963512df1a6d24c6@email.freenet.de>
 <e1405329-412a-2c12-c599-dfe6a8870aaf@freenet.de>
 <20170506090341.GA12163@freebsd-t420.fritz.box> <20170514193006.GA1298@brick>
 <1190.1494792172@critter.freebsd.dk> <20170515095647.GA1622@kib.kiev.ua>
 <A03DC1D2-3E87-4936-8C28-70B9553DFE64@FreeBSD.org>
 <20170515172725.GE1622@kib.kiev.ua>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 May 2017 17:42:44 -0000

On 15 May 2017, at 14:57, Konstantin Belousov wrote:

> On Mon, May 15, 2017 at 02:37:16PM -0230, Jonathan Anderson wrote:
>>
>> Running drm-next (which has -CURRENT last merged somewhere around
>> r317651), this patch fixes one of the two problems I've been
>> experiencing with suspend/resume. Definite progress. :)
>
> Could you, please, clarify.  Does the resume work after this  ?  If 
> not,
> how did you diagnosed that 'one of two problems' is solved with the 
> change ?

Sorry, I'll try to clarify. My problems were:

1. since at least late March, I've had visual artifacts on resume that 
make the screen unusable;
2. more recently, the machine didn't resume at all.

Applying your patch, I can successfully suspend to S3 and resume again, 
so problem #2 is resolved. This leaves me in a better position to try 
and test solutions for problem #1 (which might be an issue related to 
the Mar 13 firmware update on drm-next rather than a -CURRENT problem).

Thanks,


Jon
--
Jonathan Anderson
jonathan@FreeBSD.org