Bug 85472 - xrandr --off on all display outputs causes X to shutdown
Summary: xrandr --off on all display outputs causes X to shutdown
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-26 09:37 UTC by Sree Harsha Totakura
Modified: 2014-10-26 16:27 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log (41.56 KB, text/plain)
2014-10-26 09:37 UTC, Sree Harsha Totakura
no flags Details

Description Sree Harsha Totakura 2014-10-26 09:37:26 UTC
Created attachment 108437 [details]
Xorg log

I have a multi-monitor setup with 3 displays: 2 monitors connected via a DP MST dock and my notebook's native display.  I also have some udev rules and scripts which enable/disable displays when I hotplug them.

With linux-3.17.1 with xf86-video-intel-2.99.916 I am observing that X shuts down normally when the scripts have all the displays disabled (this happens when the scripts are enabling the native display when the notebook is undocked).  Someone on IRC pointed me that this is not expected behavior.

In the Xorg, I see the following error message when I undock the notebook and before the server terminates:
(EE) intel(0): sna_mode_check: invalid state found on pipe 1, disabling CRTC:11
Comment 1 Chris Wilson 2014-10-26 12:39:00 UTC
It's a normal shutdown. You need to ask why your desktop environment is shutting down. I was expecting a crash or similar inside X to explain the abnormal behaviour, but that doesn't appear to be the case.

(In reply to Sree Harsha Totakura from comment #0)
> In the Xorg, I see the following error message when I undock the notebook
> and before the server terminates:
> (EE) intel(0): sna_mode_check: invalid state found on pipe 1, disabling
> CRTC:11

It's not fatal, just an oddity with the hotplug behaviour of MST. It is more likely an indication of a kernel bug that the fb/mode on the CRTC is lost - the expectation is that it remains set even on unconnected pipes and it is userspaces responsibility to turn off unwanted pipes. (This is to handle the case where we want to keep driving the pipe after disconnection to speed up reconnection.)
Comment 2 Sree Harsha Totakura 2014-10-26 14:06:48 UTC
(In reply to Chris Wilson from comment #1)
> It's a normal shutdown. You need to ask why your desktop environment is
> shutting down. I was expecting a crash or similar inside X to explain the
> abnormal behaviour, but that doesn't appear to be the case.

OK.  I will checkup with DE devs will report back.  Thanks.
Comment 3 Sree Harsha Totakura 2014-10-26 16:27:19 UTC
Looks like this is a bug in i3 window manager I am using (http://bugs.i3wm.org/report/ticket/926).  Thank you for your hints.  I am closing this as a no bug.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.