When the monitor DRM status is "unknown", systemd thinks it's connected. #451
Because of a kernel issue (see https://bugzilla.kernel.org/show_bug.cgi?id=100741) my monitor DRM status is set to "unknown" instead of "connected"/"disconnected" after a resume.
Because of this, systemd refuses to suspend once more, because it thinks 4 monitors are connected. It works again if I run "xrandr" which sets the status right.
I'm not sure what is the right behavior here, but for sure this prevents my system from suspending. Of course it would be better if the kernel fixed this issue too.
I'm using systemd 215 on Debian stable (8.1), please close if this is fixed in a newer systemd.
The text was updated successfully, but these errors were encountered:
output of /sys DRM status when there is the issue:
output of /sys DRM status when there is no issue (after a clean boot or after running
Yes, v221 should handle this properly. This should still be fixed in the kernel though.
(Also, please do not report issues in such old versions of systemd upstream. We only track bugs that are in recent systemd versions upstream).
Anyway, closing, since this should already be fixed with v221.
I couldn't try v221 yet (I want to have some free time so that I can fix potential issues ;) ).
I already filed https://bugzilla.kernel.org/show_bug.cgi?id=100741 that was duped to an "invalid" bug. That "invalid" bug has a link to a thread started by @poettering, but I see no real consequence of the thread. Some people think the kernel should detect again the monitor status after a resume; some other people think userland should trigger the detect (userland should be either systemd/gnome/X ?). I'm not really qualified to decide who's right here, but for sure the status quo is wrong.
Not sure what the right next step is...
Daniel Vetter prepared a patch to fix the situation, but I never tested it, because I am too lazy. If you want the bug to be fixed, please consider testing that. The kernel bugzilla bug should really be reopened as long as that issue is not fixed there.