From owner-freebsd-current@freebsd.org  Tue May  2 17:49:30 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 24793D5B260
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue,  2 May 2017 17:49:30 +0000 (UTC)
 (envelope-from pete@nomadlogic.org)
Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2])
 (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 0DF0C17DC
 for <freebsd-current@freebsd.org>; Tue,  2 May 2017 17:49:29 +0000 (UTC)
 (envelope-from pete@nomadlogic.org)
Received: from [10.44.135.177] (nat-192-187-90-116.nat.tribpub.com
 [192.187.90.116])
 by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 8277d048
 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO
 for <freebsd-current@freebsd.org>;
 Tue, 2 May 2017 10:49:28 -0700 (PDT)
Subject: Re: regression suspend/resume on Lenovo T420
To: freebsd-current@freebsd.org
References: <20170429115017.GA98553@freebsd-t420.fritz.box>
 <CAJ-VmonopoJtYhL3Ek+3Ywb5JiSOhye-7eMnTva+MMmY-P6gXw@mail.gmail.com>
From: Pete Wright <pete@nomadlogic.org>
Message-ID: <aeb054eb-7947-eaac-08ce-d998a35bf17e@nomadlogic.org>
Date: Tue, 2 May 2017 10:49:27 -0700
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <CAJ-VmonopoJtYhL3Ek+3Ywb5JiSOhye-7eMnTva+MMmY-P6gXw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
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: Tue, 02 May 2017 17:49:30 -0000



On 05/01/2017 14:31, Adrian Chadd wrote:
> There were lots of commits that could break things. :-)
>
>
> Can you compile up some intermediary versions between 315141 and
> r317559 to find which commit range broke things? That'll make chasing
> it down much quicker!
>
> Thanks!

FWIW I'm seeing this on the drm-next repository after the latest merge 
from upstream which happened on April 30th.  I'll try to put some cycles 
into trying to find a range of potential commits that is causing this.

-pete

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA