Date: Wed, 3 May 2017 10:30:28 -0700 From: Pete Wright <pete@nomadlogic.org> To: freebsd-current@freebsd.org Subject: Re: regression suspend/resume on Lenovo T420 Message-ID: <d6ba096b-c871-937f-bb41-58c84219a4f5@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! > Hey Adrian - I was looking through the drm-next commit logs and was wondering if this commit could be the root cause of the issues i'm seeing? https://github.com/FreeBSDDesktop/freebsd-base-graphics/commit/2750ce9b17ee373b6d46e6d15d21d2e6c63f6d4d my hardware is a Kabylake Dell Inspiron 2in1. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d6ba096b-c871-937f-bb41-58c84219a4f5>