From: Jani Nikula <jani.nikula@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>, Martin Steigerwald <martin@lichtvoll.de>
Cc: kernel list <linux-kernel@vger.kernel.org>,
daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Date: Wed, 14 Sep 2016 13:03:32 +0300 [thread overview]
Message-ID: <87poo6re6j.fsf@intel.com> (raw)
In-Reply-To: <20160914074354.GA7132@amd>
On Wed, 14 Sep 2016, Pavel Machek <pavel@ucw.cz> wrote:
> Intel folks, any ideas? Can you reproduce it?
It's possible (but not confirmed yet) we've seen this in our CI, but has
slipped through because it's sporadic.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-09-14 10:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 20:23 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Pavel Machek
2016-09-13 20:38 ` Martin Steigerwald
2016-09-13 20:38 ` Martin Steigerwald
2016-09-14 7:43 ` Pavel Machek
2016-09-14 7:43 ` Pavel Machek
2016-09-14 10:03 ` Jani Nikula [this message]
2016-09-13 21:04 ` Pavel Machek
2016-09-14 7:38 ` Jani Nikula
2016-09-14 7:38 ` Jani Nikula
2016-09-14 7:45 ` Jani Nikula
2016-09-14 7:45 ` Jani Nikula
2016-09-14 7:54 ` Pavel Machek
2016-09-14 7:54 ` Pavel Machek
2016-09-14 9:17 ` Jani Nikula
2016-09-14 11:14 ` Jani Nikula
2016-09-14 11:14 ` Jani Nikula
2016-09-15 15:34 ` Martin Steigerwald
2016-09-15 15:34 ` Martin Steigerwald
2016-09-16 6:57 ` Jani Nikula
2016-10-18 14:13 ` Pavel Machek
2016-10-18 14:13 ` Pavel Machek
2016-09-14 11:32 ` Martin Steigerwald
2016-09-14 11:32 ` Martin Steigerwald
2016-09-14 10:33 ` [Intel-gfx] " Chris Wilson
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=87poo6re6j.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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.