From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jani Nikula Subject: Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Date: Wed, 14 Sep 2016 10:38:18 +0300 Message-ID: <87y42vrkwl.fsf@intel.com> References: <20160913202350.GA30707@amd> <20160913210437.GA4097@amd> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: <20160913210437.GA4097@amd> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Pavel Machek , kernel list , daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, "Rafael J. Wysocki" List-Id: dri-devel@lists.freedesktop.org T24gV2VkLCAxNCBTZXAgMjAxNiwgUGF2ZWwgTWFjaGVrIDxwYXZlbEB1Y3cuY3o+IHdyb3RlOgo+ IEhpIQo+Cj4+IEkgaGF2ZQo+PiAKPj4gMDA6MDIuMCBWR0EgY29tcGF0aWJsZSBjb250cm9sbGVy OiBJbnRlbCBDb3Jwb3JhdGlvbiA0IFNlcmllcyBDaGlwc2V0Cj4+IEludGVncmF0ZWQgR3JhcGhp Y3MgQ29udHJvbGxlciAocmV2IDAzKQo+PiAKPj4gSW4gcHJldmlvdXMga2VybmVscywgcmVzdW1l IHdvcmtlZCBvay4gV2l0aCA0LjgtcmMxLCBJIHF1aXRlIG9mdGVuICgxCj4+IGluIDEwIHJlc3Vt ZXM/KSBnZXQgaW4gc3RhdGUgd2hlcmUgcHJpbWFyeSBtb25pdG9yIChEVkkpIGlzIGRlYWQgKGlu Cj4+IHBvd2Vyc2F2ZSkgYW5kIGFsbCB3aW5kb3dzIG1vdmUgdG8gc2Vjb25kYXJ5IG1vbml0b3Ig KFZHQSkuIFJ1bm5pbmcKPj4gInhyYW5kciIgZml4ZXMgdGhhdC4KPj4gCj4+IEknbGwgdXBkYXRl IHRvIG5ld2VyIHJjIGFuZCBzZWUgaWYgaXQgaGFwcGVucyBhZ2FpbiwgYnV0IGlmIHlvdSBoYXZl Cj4+IGFueSBpZGVhcywgbm93IHdvdWxkIGJlIGdvb2QgdGltZS4KPgo+IE9rLiBXaXRoIC1yYzYs IFggYXJlIGNvbXBsZXRlbHkgYnJva2VuLiBJIGdvdCBub3RpZmljYXRpb24gImNvdWxkIG5vdAo+ IHJlc3RvcmUgQ1JUQyBjb25maWcgZm9yIHNjcmVlbiA2MyIgb3Igc29tZXRoaW5nIGxpa2UgdGhh dCwgYW5kIHdpbmRvdwo+IG1hbmFnZXIganVzdCBkb2VzIG5vdCBzdGFydC4KClVnaC4gQ2FuIHlv dSBiaXNlY3QgZnJvbSB2NC43LCBhc3N1bWluZyBpdCB3b3JrZWQ/IFRoYXQncyBwcm9iYWJseSB0 aGUKZmFzdGVzdCB3YXkgdG8gcmVzb2x2ZSB0aGlzLgoKQlIsCkphbmkuCgo+Cj4gWCBsb2cgaXMg YXR0YWNoZWQgYXMgZGVsbWUsIGtlcm5lbCBsb2cgYXMgZGVsbWUyLiBOb3RoaW5nIHRvbwo+IHN1 c3BpY2lvdXMgOi0oLgo+Cj4gCQkJCQkJCQkJUGF2ZWwKCi0tIApKYW5pIE5pa3VsYSwgSW50ZWwg T3BlbiBTb3VyY2UgVGVjaG5vbG9neSBDZW50ZXIKX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX18KSW50ZWwtZ2Z4IG1haWxpbmcgbGlzdApJbnRlbC1nZnhAbGlz dHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlzdHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4v bGlzdGluZm8vaW50ZWwtZ2Z4Cg== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760317AbcINHic (ORCPT ); Wed, 14 Sep 2016 03:38:32 -0400 Received: from mga09.intel.com ([134.134.136.24]:52421 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751152AbcINHia (ORCPT ); Wed, 14 Sep 2016 03:38:30 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,333,1470726000"; d="scan'208";a="1055732897" 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: <20160913210437.GA4097@amd> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20160913202350.GA30707@amd> <20160913210437.GA4097@amd> 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:38:18 +0300 Message-ID: <87y42vrkwl.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, 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. BR, Jani. > > X log is attached as delme, kernel log as delme2. Nothing too > suspicious :-(. > > Pavel -- Jani Nikula, Intel Open Source Technology Center