From: Daniel Vetter <daniel@ffwll.ch>
To: Johannes Stezenbach <js@sig21.net>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: periodic wakeup from DPMS suspend
Date: Thu, 8 Oct 2015 17:51:40 +0200 [thread overview]
Message-ID: <20151008155140.GE3383@phenom.ffwll.local> (raw)
In-Reply-To: <20151008104409.GA18653@sig21.net>
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
prev parent reply other threads:[~2015-10-08 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=20151008155140.GE3383@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=js@sig21.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 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.