On 05/14/2018 01:18, Niclas Zeising wrote:
On 05/13/18 21:44, Pete Wright wrote:
On 05/13/2018 10:27, Pete Wright wrote:
On 05/13/2018 08:58, Theron wrote:
Hi!
I'm also seeing issues, not as severe as Pete, but after I resume
(which works, with drm-next and DMC firmware), the system becomes
sluggish. It feels like I/O takes more time, and graphics are
sluggish (very sientific, I know, but for instance git operations
are much slower after a resume). I know there's been an update to
acpica between my system updates, when this started to happen, but
I haven't had time to revert that update and test again. I will
try to do that and report back.
Regards
Hi Niclas,
I used drm-next on Skylake with issues which sound similar.
Resuming from suspend, or simply switching the laptop display
output off and on from xrandr, resulted in graphics sluggishness
(drop to 30fps in glxgears) and graphical corruption in Xorg apps,
which persisted even after restarting these apps. Switching to
drm-stable made the problems go away; I haven't had time to figure
out what -next is doing differently to cause them.
Pete's issue sounds more severe, and unrelated as it happens
without drm loaded. My kernel is two weeks out of date (r333093),
so I need to check whether the more recent changes affect my system
as well.
so i've done a bit more debugging on my end. i've even installed
the 11.2-BETA branch last night since 11-STABLE worked without
issues about a month or so ago.
i've set "debug.acpi.resume_beep=1" and when resuming after entering
an S3 sleep state the bell rings and does not stop until i do a hard
reset (both with i915kms loaded and unloaded).
kinda at a loss as to how this could break both CURRENT and
basically 11-STABLE. i'm going to make a ubuntu live image and test
that, my laptop is a System76 laptop that shipped with ubuntu
originally. if that is broken as well then i guess this could be a
hardware issue.
ubuntu live image suspends/resumes without issue so this certainly
seems to be a freebsd issue unfortunately. i guess next step is to
attempt to find a working CURRENT snapshot that does suspend/resume
without issue then start looking at commits?
Hi!
It's a bit worrisome that your regression occurs both on CURRENT and
STABLE. There was an update to both drm-next-kmod and drm-stable-kmod
last week, but both are very minor. One question, did you install
from pkg or compile from ports?
i create a package directly from the github mirror of the ports tree
(i.e. make package; pkg install...).
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
_______________________________________________
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"
