mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>,
	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 10:45:59 +0300	[thread overview]
Message-ID: <87sht2sz48.fsf@intel.com> (raw)
In-Reply-To: <87y42vrkwl.fsf@intel.com>

On Wed, 14 Sep 2016, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Wed, 14 Sep 2016, Pavel Machek <pavel@ucw.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

  reply	other threads:[~2016-09-14  7:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 20:23 Pavel Machek
2016-09-13 20:38 ` Martin Steigerwald
2016-09-14  7:43   ` Pavel Machek
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 [this message]
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=87sht2sz48.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome