On 2020-09-16 10:51, Eirik Øverby wrote:
On 9/16/20 9:07 AM, Li-Wen Hsu wrote:
On Wed, Sep 16, 2020 at 2:30 PM Andriy Gapon <a...@freebsd.org> wrote:
On 15/09/2020 23:13, Eirik Øverby wrote:
On 9/15/20 9:50 PM, Andriy Gapon wrote:
On 15/09/2020 22:36, Eirik Øverby wrote:
Now, since I updated from r365358 to r365688, I have not once been able to wake
from sleep.
Is that the only thing that changed?
Any port / package upgrades?
There have been updates to packages, yes - but it didn't even occur to me that
these could impact the resume process at such an early stage. Not sure which
that would be; obviously the drm module has been rebuilt each time I upgraded,
but I don't have any other kernel modules installed from packages.
Which version of drm module are you using?
13.0-CURRENT FreeBSD 13.0-CURRENT #7 r365688
drm-devel-kmod-5.4.62.g20200905_1
Built against the running kernel sources, of course.
Yes, I specifically had drm modules in mind.
I also use X1C 6th and it was working perfectly after updating BIOS to
1.30 (which I'm currently using) in Sep. 2018 [1]. I don't remember
any suspend/resume failures. But since late 2019, it has exactly the
same symptom as yours. Suspending is fine, but upon resuming, there is
about a 50% probability that the power LDE continues pulsating with
all other LDEs like FnLock and CapsLock are on like the machine is
awake.
Right-o.
To make sure suspend/resume is not blocked by USB you can try setting:
sysctl hw.usb.no_suspend_wait=1
--HPS
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
