[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sht2sz48.fsf@intel.com>
Date: Wed, 14 Sep 2016 10:45:59 +0300
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Pavel Machek <pavel@....cz>,
kernel list <linux-kernel@...r.kernel.org>,
daniel.vetter@...el.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 Wed, 14 Sep 2016, Jani Nikula <jani.nikula@...ux.intel.com> wrote:
> On Wed, 14 Sep 2016, Pavel Machek <pavel@....cz> wrote:
>> Hi!
>>
>>> I have
>>>
>>> 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
>>> Integrated Graphics Controller (rev 03)
>>>
>>> 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'll update to newer rc and see if it happens again, but if you have
>>> any ideas, now would be good time.
>>
>> Ok. With -rc6, X are completely broken. I got notification "could not
>> restore CRTC config for screen 63" or something like that, and window
>> manager just does not start.
>
> Ugh. Can you bisect from v4.7, assuming it worked? That's probably the
> fastest way to resolve this.
Also, if you don't mind, please file a bug at [1], attaching the logs
there. It'll be easier for me to direct attention and priority to the
bug, which will help you too in the end.
Thanks,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
--
Jani Nikula, Intel Open Source Technology Center
Powered by blists - more mailing lists