Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1483167

Re: [Intel-gfx] 4.8-rc1: it is now common that machine needs re-run of xrandr after resume

Show all headers | View raw

On Tue, Sep 13, 2016 at 11:04:37PM +0200, 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.
> 
> X log is attached as delme, kernel log as delme2. Nothing too
> suspicious :-(.

[   234.547] (EE) intel(0): failed to set mode: Permission denied
upon resume.

There is a VT switch so there should be a DropMaster, SetMaster combo
across resume, but that didn't flag any errors. I couldn't see any sign
of logind (so no revocation), so just some breakage in the setmaster
reauthentication?
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

4.8-rc1: it is now common that machine needs re-run of xrandr after  resume Pavel Machek <pavel@ucw.cz> - 2016-09-13 22:30 +0200
  Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Martin Steigerwald <martin@lichtvoll.de> - 2016-09-13 22:50 +0200
    Re: 4.8-rc1: it is now common that machine needs re-run of xrandr  after resume Pavel Machek <pavel@ucw.cz> - 2016-09-14 09:50 +0200
      Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 12:10 +0200
  Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 09:40 +0200
    Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 09:50 +0200
    Re: 4.8-rc1: it is now common that machine needs re-run of xrandr  after resume Pavel Machek <pavel@ucw.cz> - 2016-09-14 10:00 +0200
      Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 11:20 +0200
        Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 13:20 +0200
          Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Martin Steigerwald <martin@lichtvoll.de> - 2016-09-15 17:40 +0200
            Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-16 09:00 +0200
        Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Martin Steigerwald <martin@lichtvoll.de> - 2016-09-14 13:40 +0200
  Re: [Intel-gfx] 4.8-rc1: it is now common that machine needs re-run  of xrandr after resume Chris Wilson <chris@chris-wilson.co.uk> - 2016-09-14 12:40 +0200

csiph-web