public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	daniel.vetter@intel.com, jani.nikula@linux.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: Tue, 13 Sep 2016 22:38:45 +0200	[thread overview]
Message-ID: <2521657.mCnHBphecV@merkaba> (raw)
In-Reply-To: <20160913202350.GA30707@amd>

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:

System Information

Hardware:
Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO 
42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB, 
Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd 
Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED, 
Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205

Software:
OS: Debian unstable, Kernel: 4.8.0-rc6-tp520-btrfstrim+ (x86_64), Desktop: KDE 
Frameworks 5, Display Server: X Server 1.18.4, Display Driver: modesetting 
1.18.4, OpenGL: 3.3 Mesa 12.0.2, Compiler: GCC 6.2.0 20160901, File-System: 
btrfs, Screen Resolution: 3840x1080

> 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.

I didn´t run xrandr by hand. But I ran systemsettings, dragged the second, 
deactivated external display back beneath the internal laptop display, 
activated it again and applied this changes. I think this has a somewhat 
similar effect as Plasma uses RANDR as well.
 
> I'll update to newer rc and see if it happens again, but if you have
> any ideas, now would be good time.

No ideas, sorry.

Thanks,
-- 
Martin

  reply	other threads:[~2016-09-13 20:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 20:23 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Pavel Machek
2016-09-13 20:38 ` Martin Steigerwald [this message]
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
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=2521657.mCnHBphecV@merkaba \
    --to=martin@lichtvoll.de \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --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