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

2016-10-18 Thread Pavel Machek
Hi! On Wed 2016-09-14 14:14:35, Jani Nikula wrote: > On Wed, 14 Sep 2016, Jani Nikula wrote: > > On Wed, 14 Sep 2016, Pavel Machek wrote: > >> For the "sometimes need xrandr after resume": I don't think I can > >> bisect that. It only happens sometimes

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

2016-10-18 Thread Pavel Machek
Hi! On Wed 2016-09-14 14:14:35, Jani Nikula wrote: > On Wed, 14 Sep 2016, Jani Nikula wrote: > > On Wed, 14 Sep 2016, Pavel Machek wrote: > >> For the "sometimes need xrandr after resume": I don't think I can > >> bisect that. It only happens sometimes :-(. But there's something > >> helpful in

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

2016-09-16 Thread Jani Nikula
On Thu, 15 Sep 2016, Martin Steigerwald wrote: > Am Mittwoch, 14. September 2016, 14:14:35 CEST schrieb Jani Nikula: >> On Wed, 14 Sep 2016, Jani Nikula wrote: >> > On Wed, 14 Sep 2016, Pavel Machek wrote: >> >> For the "sometimes

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

2016-09-16 Thread Jani Nikula
On Thu, 15 Sep 2016, Martin Steigerwald wrote: > Am Mittwoch, 14. September 2016, 14:14:35 CEST schrieb Jani Nikula: >> On Wed, 14 Sep 2016, Jani Nikula wrote: >> > On Wed, 14 Sep 2016, Pavel Machek wrote: >> >> For the "sometimes need xrandr after resume": I don't think I can >> >> bisect

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

2016-09-15 Thread Martin Steigerwald
Am Mittwoch, 14. September 2016, 14:14:35 CEST schrieb Jani Nikula: > On Wed, 14 Sep 2016, Jani Nikula wrote: > > On Wed, 14 Sep 2016, Pavel Machek wrote: > >> For the "sometimes need xrandr after resume": I don't think I can > >> bisect that. It only

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

2016-09-15 Thread Martin Steigerwald
Am Mittwoch, 14. September 2016, 14:14:35 CEST schrieb Jani Nikula: > On Wed, 14 Sep 2016, Jani Nikula wrote: > > On Wed, 14 Sep 2016, Pavel Machek wrote: > >> For the "sometimes need xrandr after resume": I don't think I can > >> bisect that. It only happens sometimes :-(. But there's something

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

2016-09-14 Thread Martin Steigerwald
Am Mittwoch, 14. September 2016, 12:17:53 CEST schrieb Jani Nikula: > On Wed, 14 Sep 2016, Pavel Machek wrote: > > For the "sometimes need xrandr after resume": I don't think I can > > bisect that. It only happens sometimes :-(. But there's something > > helpful in the logs: > > >

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

2016-09-14 Thread Martin Steigerwald
Am Mittwoch, 14. September 2016, 12:17:53 CEST schrieb Jani Nikula: > On Wed, 14 Sep 2016, Pavel Machek wrote: > > For the "sometimes need xrandr after resume": I don't think I can > > bisect that. It only happens sometimes :-(. But there's something > > helpful in the logs: > > > > [

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

2016-09-14 Thread Jani Nikula
On Wed, 14 Sep 2016, Jani Nikula wrote: > On Wed, 14 Sep 2016, Pavel Machek wrote: >> For the "sometimes need xrandr after resume": I don't think I can >> bisect that. It only happens sometimes :-(. But there's something >> helpful in the logs: > >> [

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

2016-09-14 Thread Jani Nikula
On Wed, 14 Sep 2016, Jani Nikula wrote: > On Wed, 14 Sep 2016, Pavel Machek wrote: >> For the "sometimes need xrandr after resume": I don't think I can >> bisect that. It only happens sometimes :-(. But there's something >> helpful in the logs: > >> [ 1856.218863] [drm:drm_edid_block_valid]

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

2016-09-14 Thread Jani Nikula
On Wed, 14 Sep 2016, Pavel Machek wrote: > Intel folks, any ideas? Can you reproduce it? It's possible (but not confirmed yet) we've seen this in our CI, but has slipped through because it's sporadic. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center

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

2016-09-14 Thread Jani Nikula
On Wed, 14 Sep 2016, Pavel Machek wrote: > Intel folks, any ideas? Can you reproduce it? It's possible (but not confirmed yet) we've seen this in our CI, but has slipped through because it's sporadic. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center

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

2016-09-14 Thread Jani Nikula
On Wed, 14 Sep 2016, Pavel Machek wrote: > For the "sometimes need xrandr after resume": I don't think I can > bisect that. It only happens sometimes :-(. But there's something > helpful in the logs: > [ 1856.218863] [drm:drm_edid_block_valid] *ERROR* EDID checksum is > invalid,

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

2016-09-14 Thread Jani Nikula
On Wed, 14 Sep 2016, Pavel Machek wrote: > For the "sometimes need xrandr after resume": I don't think I can > bisect that. It only happens sometimes :-(. But there's something > helpful in the logs: > [ 1856.218863] [drm:drm_edid_block_valid] *ERROR* EDID checksum is > invalid, remainder is 130

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

2016-09-14 Thread Pavel Machek
On Wed 2016-09-14 10:38:18, 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

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

2016-09-14 Thread Pavel Machek
On Wed 2016-09-14 10:38:18, 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

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

2016-09-14 Thread Jani Nikula
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

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

2016-09-14 Thread Jani Nikula
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

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

2016-09-14 Thread Pavel Machek
On Tue 2016-09-13 22:38:45, Martin Steigerwald wrote: > 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

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

2016-09-14 Thread Pavel Machek
On Tue 2016-09-13 22:38:45, Martin Steigerwald wrote: > 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

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

2016-09-14 Thread Jani Nikula
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

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

2016-09-14 Thread Jani Nikula
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

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

2016-09-13 Thread Pavel Machek
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

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

2016-09-13 Thread Pavel Machek
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

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

2016-09-13 Thread Martin Steigerwald
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

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

2016-09-13 Thread Martin Steigerwald
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