[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160914074354.GA7132@amd>
Date: Wed, 14 Sep 2016 09:43:54 +0200
From: Pavel Machek <pavel@....cz>
To: Martin Steigerwald <martin@...htvoll.de>
Cc: kernel list <linux-kernel@...r.kernel.org>,
daniel.vetter@...el.com, jani.nikula@...ux.intel.com,
intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: 4.8-rc1: it is now common that machine needs re-run of xrandr
after resume
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
Powered by blists - more mailing lists