* periodic wakeup from DPMS suspend @ 2015-10-06 15:10 Johannes Stezenbach 2015-10-07 3:04 ` Alex Deucher 0 siblings, 1 reply; 5+ messages in thread From: Johannes Stezenbach @ 2015-10-06 15:10 UTC (permalink / raw) To: intel-gfx; +Cc: dri-devel Hi, I have a NEC EA244WMi monitor connected to an Asus P8H77-V mainboard with Ivy Bridge Core i5-3550 via DVI. If DPMS suspend is enabled (by xscreensaver, or for testing by "xset dpms force off/suspend/standby"), the monitor enters standby mode but wakes up every 10...30 seconds for 6 seconds to display a "DVI-D: no signal" message. How can I find out if this is an issue of the NEC monitor or the Intel graphics? - when I pull the DVI cable the monitor stays in suspend - I tried to use drm.debug=6 and ftrace to see if something is periodically accessing DDC or similar, but it didn't reveal anything to me, but then I know nothing about graphics drivers and probably didn't do it right I noticed there is some hotplug detection code, my initial thought was that this could cause the wakeup. But since the period is somewhat irregular maybe it is some floating signal line causing the monitor to misdetect activity? Currently I'm running 4.2.3, but the same issue happens with older kernels, I tried 3.17+. Let me know if you have any ideas what to try. BTW, in sysfs the output shows up as HDMI-A-2: (the board has VGA, DVI, HDMI and DP) $ find /sys -name edid /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-2/edid /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-3/edid /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1/edid /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/edid /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/edid /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-3/edid Another observation is that the HDMI-A-* outputs don't have an i2c node to link the matching DDC channel, while the DP outputs have? $ grep . /sys/class/i2c-dev/i2c-*/name /sys/class/i2c-dev/i2c-0/name:i915 gmbus ssc /sys/class/i2c-dev/i2c-1/name:i915 gmbus vga /sys/class/i2c-dev/i2c-2/name:i915 gmbus panel /sys/class/i2c-dev/i2c-3/name:i915 gmbus dpc /sys/class/i2c-dev/i2c-4/name:i915 gmbus dpb /sys/class/i2c-dev/i2c-5/name:i915 gmbus dpd /sys/class/i2c-dev/i2c-6/name:DPDDC-B /sys/class/i2c-dev/i2c-7/name:DPDDC-C /sys/class/i2c-dev/i2c-8/name:DPDDC-D The monitor brightness can be controlled via /dev/i2c-3 with ddccontrol. TIA, Johannes _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: periodic wakeup from DPMS suspend 2015-10-06 15:10 periodic wakeup from DPMS suspend Johannes Stezenbach @ 2015-10-07 3:04 ` Alex Deucher 2015-10-07 11:26 ` Johannes Stezenbach 0 siblings, 1 reply; 5+ messages in thread From: Alex Deucher @ 2015-10-07 3:04 UTC (permalink / raw) To: Johannes Stezenbach Cc: Intel Graphics Development, Maling list - DRI developers On Tue, Oct 6, 2015 at 11:10 AM, Johannes Stezenbach <js@sig21.net> wrote: > Hi, > > I have a NEC EA244WMi monitor connected to an Asus P8H77-V > mainboard with Ivy Bridge Core i5-3550 via DVI. > If DPMS suspend is enabled (by xscreensaver, or for testing by > "xset dpms force off/suspend/standby"), the monitor > enters standby mode but wakes up every 10...30 seconds for > 6 seconds to display a "DVI-D: no signal" message. > > How can I find out if this is an issue of the NEC monitor > or the Intel graphics? > > - when I pull the DVI cable the monitor stays in suspend > > - I tried to use drm.debug=6 and ftrace to see if something > is periodically accessing DDC or similar, but it didn't > reveal anything to me, but then I know nothing about > graphics drivers and probably didn't do it right > > I noticed there is some hotplug detection code, > my initial thought was that this could cause the > wakeup. But since the period is somewhat irregular > maybe it is some floating signal line causing the > monitor to misdetect activity? > > Currently I'm running 4.2.3, but the same issue > happens with older kernels, I tried 3.17+. > > Let me know if you have any ideas what to try. Some monitors periodically scan all of their inputs if they are not actively being driven by anything to try and automatically switch to the connected input. When the monitor scans the DVI input, it sees load on the pins and turns on, only to realize it's not getting a signal and then turns off. If your monitor has an option to turn off input probing, that might help. Alex > > > > > > BTW, in sysfs the output shows up as HDMI-A-2: > (the board has VGA, DVI, HDMI and DP) > > $ find /sys -name edid > /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-1/edid > /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-2/edid > /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-3/edid > /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1/edid > /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/edid > /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/edid > /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-3/edid > > Another observation is that the HDMI-A-* outputs don't > have an i2c node to link the matching DDC channel, > while the DP outputs have? > > $ grep . /sys/class/i2c-dev/i2c-*/name > /sys/class/i2c-dev/i2c-0/name:i915 gmbus ssc > /sys/class/i2c-dev/i2c-1/name:i915 gmbus vga > /sys/class/i2c-dev/i2c-2/name:i915 gmbus panel > /sys/class/i2c-dev/i2c-3/name:i915 gmbus dpc > /sys/class/i2c-dev/i2c-4/name:i915 gmbus dpb > /sys/class/i2c-dev/i2c-5/name:i915 gmbus dpd > /sys/class/i2c-dev/i2c-6/name:DPDDC-B > /sys/class/i2c-dev/i2c-7/name:DPDDC-C > /sys/class/i2c-dev/i2c-8/name:DPDDC-D > > The monitor brightness can be controlled via > /dev/i2c-3 with ddccontrol. > > > TIA, > Johannes > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: periodic wakeup from DPMS suspend 2015-10-07 3:04 ` Alex Deucher @ 2015-10-07 11:26 ` Johannes Stezenbach 2015-10-08 10:44 ` Johannes Stezenbach 0 siblings, 1 reply; 5+ messages in thread From: Johannes Stezenbach @ 2015-10-07 11:26 UTC (permalink / raw) To: Alex Deucher; +Cc: Intel Graphics Development, Maling list - DRI developers On Tue, Oct 06, 2015 at 11:04:53PM -0400, Alex Deucher wrote: > On Tue, Oct 6, 2015 at 11:10 AM, Johannes Stezenbach <js@sig21.net> wrote: > > > > I have a NEC EA244WMi monitor connected to an Asus P8H77-V > > mainboard with Ivy Bridge Core i5-3550 via DVI. > > If DPMS suspend is enabled (by xscreensaver, or for testing by > > "xset dpms force off/suspend/standby"), the monitor > > enters standby mode but wakes up every 10...30 seconds for > > 6 seconds to display a "DVI-D: no signal" message. > > Some monitors periodically scan all of their inputs if they are not > actively being driven by anything to try and automatically switch to > the connected input. When the monitor scans the DVI input, it sees > load on the pins and turns on, only to realize it's not getting a > signal and then turns off. If your monitor has an option to turn off > input probing, that might help. It's not like I didn't try to twiddle just about every available menu item, and also used the monitor's "Reset to Factory Defaults" to no avail. However, while trying again I found a hidden menu item which is only available during the short time the "No Signal" message is displayed, where the left/right touch buttons open a "Scan Time" setting with "Normal" and "Slow" options. After I changed it, the issue was solved. I changed it back and the issue doesn't reproduce. So it looks some internal configuration of the monitor was messed up and is now fixed by twiddling the hidden menu item. "Scan Time" is not documented in the manual nor is there an indication in the "No Signal" popup. Case closed. Thanks, Johannes _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: periodic wakeup from DPMS suspend 2015-10-07 11:26 ` Johannes Stezenbach @ 2015-10-08 10:44 ` Johannes Stezenbach 2015-10-08 15:51 ` Daniel Vetter 0 siblings, 1 reply; 5+ messages in thread From: Johannes Stezenbach @ 2015-10-08 10:44 UTC (permalink / raw) To: Alex Deucher; +Cc: Intel Graphics Development, Maling list - DRI developers On Wed, Oct 07, 2015 at 01:26:32PM +0200, Johannes Stezenbach wrote: > On Tue, Oct 06, 2015 at 11:04:53PM -0400, Alex Deucher wrote: > > On Tue, Oct 6, 2015 at 11:10 AM, Johannes Stezenbach <js@sig21.net> wrote: > > > > > > I have a NEC EA244WMi monitor connected to an Asus P8H77-V > > > mainboard with Ivy Bridge Core i5-3550 via DVI. > > > If DPMS suspend is enabled (by xscreensaver, or for testing by > > > "xset dpms force off/suspend/standby"), the monitor > > > enters standby mode but wakes up every 10...30 seconds for > > > 6 seconds to display a "DVI-D: no signal" message. > > > > Some monitors periodically scan all of their inputs if they are not > > actively being driven by anything to try and automatically switch to > > the connected input. When the monitor scans the DVI input, it sees > > load on the pins and turns on, only to realize it's not getting a > > signal and then turns off. If your monitor has an option to turn off > > input probing, that might help. > > It's not like I didn't try to twiddle just about every > available menu item, and also used the monitor's > "Reset to Factory Defaults" to no avail. > However, while trying again I found a hidden menu item > which is only available during the short time the > "No Signal" message is displayed, where the left/right > touch buttons open a "Scan Time" setting with "Normal" > and "Slow" options. After I changed it, the issue was > solved. I changed it back and the issue doesn't reproduce. > So it looks some internal configuration of the monitor > was messed up and is now fixed by twiddling the hidden > menu item. "Scan Time" is not documented in the manual > nor is there an indication in the "No Signal" popup. > > Case closed. And I just came back to see the monitor doing the wakeup cycling again. To try something differerent I unplugged the charger of the laptop sitting nearby in suspend. Bingo! So it looks like an EMI issue. I tried a few times and could reproduce twice and then no more :-( Now the monitor wakes up once every 5min or so... Which brings me back to a previous question: > maybe it is some floating signal line causing the > monitor to misdetect activity? Does the Intel hardware have the capability to switch the DVI signal lines from high-z to ground during DPMS suspend, and if so, does the driver do the right thing? Obviously I have no clue about DVI and intel-gfx, but I thought to ask anyway. Johannes _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: periodic wakeup from DPMS suspend 2015-10-08 10:44 ` Johannes Stezenbach @ 2015-10-08 15:51 ` Daniel Vetter 0 siblings, 0 replies; 5+ messages in thread From: Daniel Vetter @ 2015-10-08 15:51 UTC (permalink / raw) To: Johannes Stezenbach Cc: Alex Deucher, Intel Graphics Development, Maling list - DRI developers On Thu, Oct 08, 2015 at 12:44:09PM +0200, Johannes Stezenbach wrote: > On Wed, Oct 07, 2015 at 01:26:32PM +0200, Johannes Stezenbach wrote: > > On Tue, Oct 06, 2015 at 11:04:53PM -0400, Alex Deucher wrote: > > > On Tue, Oct 6, 2015 at 11:10 AM, Johannes Stezenbach <js@sig21.net> wrote: > > > > > > > > I have a NEC EA244WMi monitor connected to an Asus P8H77-V > > > > mainboard with Ivy Bridge Core i5-3550 via DVI. > > > > If DPMS suspend is enabled (by xscreensaver, or for testing by > > > > "xset dpms force off/suspend/standby"), the monitor > > > > enters standby mode but wakes up every 10...30 seconds for > > > > 6 seconds to display a "DVI-D: no signal" message. > > > > > > Some monitors periodically scan all of their inputs if they are not > > > actively being driven by anything to try and automatically switch to > > > the connected input. When the monitor scans the DVI input, it sees > > > load on the pins and turns on, only to realize it's not getting a > > > signal and then turns off. If your monitor has an option to turn off > > > input probing, that might help. > > > > It's not like I didn't try to twiddle just about every > > available menu item, and also used the monitor's > > "Reset to Factory Defaults" to no avail. > > However, while trying again I found a hidden menu item > > which is only available during the short time the > > "No Signal" message is displayed, where the left/right > > touch buttons open a "Scan Time" setting with "Normal" > > and "Slow" options. After I changed it, the issue was > > solved. I changed it back and the issue doesn't reproduce. > > So it looks some internal configuration of the monitor > > was messed up and is now fixed by twiddling the hidden > > menu item. "Scan Time" is not documented in the manual > > nor is there an indication in the "No Signal" popup. > > > > Case closed. > > And I just came back to see the monitor doing the > wakeup cycling again. To try something differerent > I unplugged the charger of the laptop sitting nearby > in suspend. Bingo! So it looks like an EMI issue. > I tried a few times and could reproduce twice and > then no more :-( Now the monitor wakes up once > every 5min or so... > > Which brings me back to a previous question: > > > maybe it is some floating signal line causing the > > monitor to misdetect activity? > > Does the Intel hardware have the capability to switch > the DVI signal lines from high-z to ground during DPMS > suspend, and if so, does the driver do the right thing? > Obviously I have no clue about DVI and intel-gfx, but > I thought to ask anyway. We have already known fun with EMI from laptop chargers: i915 hase a hotpug storm detection logic to combat badly-shielded boards. Could just be another form of that problem. Afaik there's nothing we can do in the driver about this (except trying to filter out bad noise, which we do already). -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-10-08 15:51 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2015-10-06 15:10 periodic wakeup from DPMS suspend Johannes Stezenbach 2015-10-07 3:04 ` Alex Deucher 2015-10-07 11:26 ` Johannes Stezenbach 2015-10-08 10:44 ` Johannes Stezenbach 2015-10-08 15:51 ` Daniel Vetter
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.