Date: Wed, 25 Mar 2015 16:37:12 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Adrian Chadd <adrian@freebsd.org> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: 10-STABLE suspend failure Message-ID: <CAN6yY1t9EP=j255wQVrzoY4M=9dT4X9nu5zs_H=x3=A5mBDYXA@mail.gmail.com> In-Reply-To: <CAJ-VmokwAfBsnW77VViZnL00vd82bJoJ7N9qC4TvJiGn_25bGw@mail.gmail.com> References: <CAN6yY1t7_CxXa7qW96jW1Kahdzk=Yzs3Ve-HmbVYSRbVq3_i_w@mail.gmail.com> <CAJ-VmokwAfBsnW77VViZnL00vd82bJoJ7N9qC4TvJiGn_25bGw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adrian, Thanks! I can confirm that rolling back the intel_opregion commit 279961 restores suspend. I only rolled back this commit, so there is no doubt this is the culprit. Of course, rolling it back also breaks brightness control. Does it look like there is a reasonable explanation for this? Without looking at the Linux code (which I probably would not understand anyway), I'd guess something is missing that is needed for suspend to work. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com On Wed, Mar 25, 2015 at 1:13 PM, Adrian Chadd <adrian@freebsd.org> wrote: > Hi, > > that GEM idle fail is problematic. > > Try backing it out say, 1 month or so? I think that's before the drm > merge from head to stable/10. > > > -a >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1t9EP=j255wQVrzoY4M=9dT4X9nu5zs_H=x3=A5mBDYXA>