https://bugs.freedesktop.org/show_bug.cgi?id=105687
--- Comment #4 from Stefano Biagiotti ---
Created attachment 138821
--> https://bugs.freedesktop.org/attachment.cgi?id=138821&action=edit
journalctl -k
Bug still present with kernel-4.15.15-300.fc27.x86_64.
--
You are receiving this mail be
This is useful for drivers (which will probably be all of them soon)
which need to track state that is exclusive to the topology, and not a
specific connector on said topology. This includes things such as the
link rate and lane count that are shared by all of the connectors on the
topology.
Signe
Next version of https://patchwork.freedesktop.org/series/41576/
All changes in this patch series are just to make checkpatch a little
happier, no functional changes.
Lyude Paul (10):
drm/atomic: Print debug message on atomic check failure
drm/i915: Move DP modeset retry work into intel_dp
d
This is useful for drivers (which will probably be all of them soon)
which need to track state that is exclusive to the topology, and not a
specific connector on said topology. This includes things such as the
link rate and lane count that are shared by all of the connectors on the
topology.
Signe
Latest version of PW series 39642, hopefully this should also actually
come up on intel-gfx and go through CI.
No changes other than rebasing to the current drm-intel-next-queued
Lyude Paul (10):
drm/atomic: Print debug message on atomic check failure
drm/i915: Move DP modeset retry work into
This is useful for drivers (which will probably be all of them soon)
which need to track state that is exclusive to the topology, and not a
specific connector on said topology. This includes things such as the
link rate and lane count that are shared by all of the connectors on the
topology.
Signe
Next version of https://patchwork.freedesktop.org/series/41576/
Only changes are removing duplicate SoBs that git send-email annoyingly
added. Sorry about that :(
Lyude Paul (10):
drm/atomic: Print debug message on atomic check failure
drm/i915: Move DP modeset retry work into intel_dp
drm/
Somehow I didn't manage to notice this the last time I looked at my
mmiotraces, these seem to be all valid registers.
Forwarding this to stable, as there's a small chance that not having
these could cause clockgating to be unstable.
Signed-off-by: Lyude Paul
Fixes: a0f79082bd174 ("drm/nouveau: A
https://bugs.freedesktop.org/show_bug.cgi?id=106041
Bug ID: 106041
Summary: Nvidia GeForce GTX 970M blank screen after resume
Product: Mesa
Version: 18.0
Hardware: Other
OS: Linux (All)
Status: NEW
Severit
