On Wed, Mar 25, 2015 at 6:44 PM, Adrian Chadd adr...@freebsd.org wrote:
I honestly have no idea, and this is kind of why I didn't want to
commit it to stable/10 without it getting a whole lot more testing.
Does -HEAD also fail to suspend for you?
-a
Good news! Head works and, now that
Sometime in the past 6 months I lost the ability to suspend my ThinkPad
T520. I don't often suspend this system, so I just noticed it today when I
had it away from AC power for a while. It used to work just fine.
10.1-STABLE FreeBSD 10.1-STABLE #0 r280293: Fri Mar 20 11:28:08 PDT
2015
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
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
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?
I honestly have no idea, and this is kind of why I didn't want to
commit it to stable/10 without it getting a whole lot more testing.
Does -HEAD also fail to suspend for you?
-a
___
freebsd-stable@freebsd.org mailing list
