Nouveau - Aug 2014 - [Bug 82527] New: xset dpms force {off, standby, suspend} returns after ~20 seconds (GeForce 8400 GS)

https://bugs.freedesktop.org/show_bug.cgi?id=82527

          Priority: medium
            Bug ID: 82527
          Assignee: nouveau at lists.freedesktop.org
           Summary: xset dpms force {off,standby,suspend} returns after
                    ~20 seconds (GeForce 8400 GS)
        QA Contact: xorg-team at lists.x.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: martin at mvath.de
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

With nouveau drivers (current versions: kernel 3.15.9,
xf86-video-nouveau-1.0.10, xorg-server-1.15.0; however the issue exists since
several years)
"xset dpms force off" (or standby/suspend) does not work here as it
should:

In all three cases, the monitor switches off for about 20 seconds but then
switches on again.

The issue is completely reproducible and does not occur with the proprietary
nvidia-drivers.

I am rather sure that nothing (except perhaps nouveau drivers themselves)
causes any activity which might cancel the effect of "xset dpms force
off":
This is already proved by the fact that it works with the proprietary
nvidia-drivers, but I also checked many times that no suspectible task is
running (and besides systemd the bug has occured also with openrc and with a
minimal number of started services).

As mentioned, the problem exists since several years, so I do not think that
any of the recent changes referred to in bug 76483 is related to this.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140812/7894fb73/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> ---
The bug you reference was about DP. But display stuff got a substantial rework
in 3.16 (with an eye to DP) and even more changes are queued for 3.17. Would
you mind giving the linux-3.17 branch a shot
(http://cgit.freedesktop.org/nouveau/linux-2.6/log/?h=linux-3.17)? If that
doesn't help, please provide a boot log with

nouveau.debug=VBIOS=trace,DISP=debug,I2C=debug,DRM=debug

in the kernel commandline (or otherwise passed to the module). Also mention how
the monitor is connected.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140812/85a851de/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #2 from Martin V?th <martin at mvath.de> ---
Created attachment 104544
  --> https://bugs.freedesktop.org/attachment.cgi?id=104544&action=edit
boot.log

With kernel 3-17 (boot log attached) there is indeed a change:

Now the monitor does not react at all on "xset dpms force off".

The monitor is connected over DVI

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140813/6a6fd143/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #3 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Two comments/questions:

(1)

1:10 slim[256]: (EE) module ABI major version (13) doesn't match the
server's
version (15)

That seems a little unhappy... I hope that's not referring to the ddx's
module.
I guess you have an old module? As long as nouveau's not involved in this,
it
shouldn't matter.

(2)

Did you try to do a "xset dpms force off" in that log, or was that not
included. In case it wasn't included, could you?

Lastly, I forgot that the drm core may also provide some useful information.
Would you mind adding "drm.debug=0xe" to the kernel command line in
addition to
the nouveau.debug setting I mentioned earlier, and provide a log which also
includes you trying to "xset dpms force off"?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140813/96cc861a/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #4 from Martin V?th <martin at mvath.de> ---
(In reply to comment #3)
> 1:10 slim[256]: (EE) module ABI major version (13) doesn't match the
> server's version (15)
This was the v4l driver. I recompiled, but unsurprisingly, it does not change
anything concerning the reported problem.
> Did you try to do a "xset dpms force off" in that log
This produced no output in the log, also not with the following:
> Would you mind adding "drm.debug=0xe" to the kernel command line
This did not change the output, either. Still no output when calling
xset dpms force off

I will attach the new boot log, but it is practically the same.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140814/ca083d2b/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #5 from Martin V?th <martin at mvath.de> ---
Created attachment 104594
  --> https://bugs.freedesktop.org/attachment.cgi?id=104594&action=edit
boot.log

As in the previous log, some obviously unrelevant information (like disk or
network initialization messages) have been removed manually by me.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140814/db709b32/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> ---
You misunderstood my suggestion... you have:

nouveau.debug=VBIOS=trace,DISP=debug,I2C=debug,DRM=debug,drm.debug=0xe

You should have:

nouveau.debug=VBIOS=trace,DISP=debug,I2C=debug,DRM=debug drm.debug=0xe

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140814/0fcd56a2/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

Martin V?th <martin at mvath.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #104544|0                           |1
        is obsolete|                            |
 Attachment #104594|0                           |1
        is obsolete|                            |

--- Comment #7 from Martin V?th <martin at mvath.de> ---
Created attachment 104604
  --> https://bugs.freedesktop.org/attachment.cgi?id=104604&action=edit
boot.log

Still no output with "xdpms force off" (tried several times).

At a few minutes later (I cannot associate to an action of me) there appeared:

[kernel] nouveau T[   VBIOS][0000:01:00.0] inc() == 3
[kernel] nouveau T[   VBIOS][0000:01:00.0] dec() == 2

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140814/c264a4bf/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #8 from Martin V?th <martin at mvath.de> ---
s/xdpms/xset dpms/

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140814/64fd1a17/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

michael.weirauch at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michael.weirauch at gmail.com

--- Comment #9 from michael.weirauch at gmail.com ---
*** Bug 83244 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140930/2a869449/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #10 from michael.weirauch at gmail.com ---
My display re-enabe resume issue (#83244) resolved for me with
http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=a68e95365a4248d3f58c8663e4513c79273ac704
which references this ticket. Thus the duplicate marker. Feel free to rectify
this, if not correctly done.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140930/5b4be4b6/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #11 from Martin V?th <martin at mvath.de> ---
I do not have physical access to the machine with the card in the next months,
so I cannot confirm/test anything.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140930/e6b286fe/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #12 from Jamie Heilman <jamie at audible.transient.net> ---
I can confirm that the regression reported in comment #2 that I bisected to
d55b4af909bc16f7982c2b8b8656f0898158627b is now fixed as of
80ad99da8bd213e12b925407f1c97a303aa8f87f (which pulled in
5838ae610ff36777b8fce6f353c2417980c1a1fa).  Additionally I haven't been able
to
reproduce the case that this bug was originally opened for yet, (prior to 3.17
I could but it was always a bit finicky).  Still, it's probably too early to
say that its fixed for sure; I have a slightly different card than Martin's
(a
10de:042f, NVIDIA Corporation G86 [Quadro NVS 290] (rev a1)).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141004/7d0caf1d/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #13 from Martin Väth <martin at mvath.de> ---
By accident, I am now traveling and have access on the machine for 1 or 2 days.

I installed linux-3.17.2, and have still exactly the same faulty behaviour as
described in the original posting:

xset dpms force off holds for about 20 seconds and then switches on again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20141107/3d7ed31e/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #14 from Jimmie Mayfield <mayfield+bugzilla at sackheads.org>
---
For what it's worth, I see similar behavior with the Nouveau driver on
OpenSUSE
13.2 (kernel 3.16.7-24, xf86-video-nouveau-1.0.11-1.3)

My office machine has two displays connected to a GTS450.  Both displays go
into standby mode.  After a short delay -- I haven't measured by hand but
the
aforementioned 20-second value sounds about right -- the secondary display
comes out of standby.  Near as I can tell, this behavior only affects the
secondary display.  I can also confirm that the behavior did not occur when
using the proprietary nVidia drivers.

Another data point that may be useful when diagnosing the problem: I'm also
using the nVidia card for audio.  I'm away from the office for a few days
but
I'm reasonably confident that both displays are connected via DVI and that
my
speakers are connected to the secondary display's audio line-out jack.  Is
it
possible that the secondary display's inability to remain in standby mode is
somehow audio-related?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20150912/f568ab31/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

--- Comment #15 from Martin Väth <martin at mvath.de> ---
I don't know why this issue was marked as FIXED.
The behaviour hasn't changed since my first posting.

I am not using audio from nvidia, so at least in my case this is certainly not
related.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160626/113be223/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=82527

Martin Väth <martin at mvath.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #16 from Martin Väth <martin at mvath.de> ---
I haven't been at the nvidia machine for a while.
Sometimes during the previous months the problem has indeed been fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20170916/ce22ff95/attachment.html>