From: Pavel Machek <pavel@ucw.cz>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: intel-gfx@lists.freedesktop.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
kernel list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, daniel.vetter@intel.com
Subject: Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Date: Wed, 14 Sep 2016 09:43:54 +0200 [thread overview]
Message-ID: <20160914074354.GA7132@amd> (raw)
In-Reply-To: <2521657.mCnHBphecV@merkaba>
On Tue 2016-09-13 22:38:45, Martin Steigerwald wrote:
> Hi.
>
> Am Dienstag, 13. September 2016, 22:23:50 CEST schrieb Pavel Machek:
> > I have
> >
> > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller (rev 03)
>
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation
> Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
>
> Phoronix Test Suite system-info:
...
> > In previous kernels, resume worked ok. With 4.8-rc1, I quite often (1
> > in 10 resumes?) get in state where primary monitor (DVI) is dead (in
> > powersave) and all windows move to secondary monitor (VGA). Running
> > "xrandr" fixes that.
>
> I have seen this in 4.8 up to rc5 as well. I am not sure yet about rc6 which I
> am currently running.
Ok, it happened again today, with yesterdays version of 4.8-rc6. I'm
glad I'm not the only one.
Intel folks, any ideas? Can you reproduce it?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-14 7:43 UTC|newest]
Thread overview: 15+ 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-14 7:43 ` Pavel Machek [this message]
2016-09-14 10:03 ` Jani Nikula
2016-09-13 21:04 ` Pavel Machek
2016-09-14 7:38 ` Jani Nikula
2016-09-14 7:45 ` Jani Nikula
2016-09-14 7:54 ` Pavel Machek
2016-09-14 9:17 ` Jani Nikula
2016-09-14 11:14 ` Jani Nikula
2016-09-15 15:34 ` Martin Steigerwald
2016-09-16 6:57 ` Jani Nikula
2016-10-18 14:13 ` Pavel Machek
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=20160914074354.GA7132@amd \
--to=pavel@ucw.cz \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).