From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933078AbcINHrA (ORCPT ); Wed, 14 Sep 2016 03:47:00 -0400 Received: from mga01.intel.com ([192.55.52.88]:21718 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933013AbcINHq4 (ORCPT ); Wed, 14 Sep 2016 03:46:56 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,333,1470726000"; d="scan'208";a="1055735306" From: Jani Nikula To: Pavel Machek , kernel list , daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, "Rafael J. Wysocki" Subject: Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume In-Reply-To: <87y42vrkwl.fsf@intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20160913202350.GA30707@amd> <20160913210437.GA4097@amd> <87y42vrkwl.fsf@intel.com> User-Agent: Notmuch/0.22.1+63~g648dcc7 (https://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Wed, 14 Sep 2016 10:45:59 +0300 Message-ID: <87sht2sz48.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 14 Sep 2016, Jani Nikula wrote: > On Wed, 14 Sep 2016, Pavel Machek 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