Date: Tue, 2 May 2017 10:49:27 -0700 From: Pete Wright <pete@nomadlogic.org> To: freebsd-current@freebsd.org Subject: Re: regression suspend/resume on Lenovo T420 Message-ID: <aeb054eb-7947-eaac-08ce-d998a35bf17e@nomadlogic.org> In-Reply-To: <CAJ-VmonopoJtYhL3Ek%2B3Ywb5JiSOhye-7eMnTva%2BMMmY-P6gXw@mail.gmail.com> References: <20170429115017.GA98553@freebsd-t420.fritz.box> <CAJ-VmonopoJtYhL3Ek%2B3Ywb5JiSOhye-7eMnTva%2BMMmY-P6gXw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aeb054eb-7947-eaac-08ce-d998a35bf17e>