All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Dave Airlie <airlied@gmail.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: WARNING: /usr/projects/linux/linux/drivers/gpu/drm/i915/intel_pm.c:6585 intel_display_power_put+0x4b/0x116 [i915]()
Date: Sun, 7 Dec 2014 23:08:29 -0500	[thread overview]
Message-ID: <20141208040829.GA5142@thunk.org> (raw)
In-Reply-To: <CAPM=9txGrrqYPg9EbpC+9OAB5VCt36vWFRMmoAOvJZV-RSQ2-A@mail.gmail.com>

On Mon, Dec 08, 2014 at 12:32:01PM +1000, Dave Airlie wrote:
> 
> I suspect a lot of the problems are just that xfce isn't sufficiently handling
> randr events, and it is getting out of sync, it is like hotplug networking
> before NetworkManager etc.

Yes, I've seen this on XFCE 4.11 (in Ubuntu), although I haen't seen
it in XFCE 4.10 (in Debian).  In 4.11, when xfce gets out of sync,
xrandr --auto will allow me to enable the display, even when
xfce4-display-settings does not.

However, on my T540p with the monitors connected via the dock, which
is the problem I was describing here, xrandr --auto does *not* fix
things up.  So I think it's a different problem, since I can see this
problem even if I don't use xfce4-display-settings, and just use
xrandr directly.

						- Ted
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Ts'o" <tytso@mit.edu>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jani Nikula <jani.nikula@intel.com>
Subject: Re: WARNING: /usr/projects/linux/linux/drivers/gpu/drm/i915/intel_pm.c:6585 intel_display_power_put+0x4b/0x116 [i915]()
Date: Sun, 7 Dec 2014 23:08:29 -0500	[thread overview]
Message-ID: <20141208040829.GA5142@thunk.org> (raw)
In-Reply-To: <CAPM=9txGrrqYPg9EbpC+9OAB5VCt36vWFRMmoAOvJZV-RSQ2-A@mail.gmail.com>

On Mon, Dec 08, 2014 at 12:32:01PM +1000, Dave Airlie wrote:
> 
> I suspect a lot of the problems are just that xfce isn't sufficiently handling
> randr events, and it is getting out of sync, it is like hotplug networking
> before NetworkManager etc.

Yes, I've seen this on XFCE 4.11 (in Ubuntu), although I haen't seen
it in XFCE 4.10 (in Debian).  In 4.11, when xfce gets out of sync,
xrandr --auto will allow me to enable the display, even when
xfce4-display-settings does not.

However, on my T540p with the monitors connected via the dock, which
is the problem I was describing here, xrandr --auto does *not* fix
things up.  So I think it's a different problem, since I can see this
problem even if I don't use xfce4-display-settings, and just use
xrandr directly.

						- Ted

  reply	other threads:[~2014-12-08  4:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  4:05 [REGRESSION] i915: failure to see Dell 30" monitor connected to a Lenovo Haswell docking station Theodore Ts'o
2014-09-02  4:15 ` Dave Airlie
2014-09-02 11:03   ` Theodore Ts'o
2014-09-02 11:03     ` Theodore Ts'o
2014-09-02 11:23     ` Dave Airlie
2014-09-02 11:23       ` Dave Airlie
2014-09-02 13:13       ` Theodore Ts'o
2014-09-02 13:13         ` Theodore Ts'o
2014-09-26  2:24   ` Theodore Ts'o
2014-09-26  2:24     ` Theodore Ts'o
2014-12-08  0:34 ` WARNING: /usr/projects/linux/linux/drivers/gpu/drm/i915/intel_pm.c:6585 intel_display_power_put+0x4b/0x116 [i915]() Theodore Ts'o
2014-12-08  2:32   ` Dave Airlie
2014-12-08  2:32     ` Dave Airlie
2014-12-08  4:08     ` Theodore Ts'o [this message]
2014-12-08  4:08       ` Theodore Ts'o
2014-12-15 13:26       ` Theodore Ts'o
2014-12-15 13:26         ` Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141208040829.GA5142@thunk.org \
    --to=tytso@mit.edu \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.