Nouveau - Mar 2014 - [Bug 76483] New: [NV50, bisected, RFC patch] xset dpms force {on, off} does not work over DP

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

          Priority: medium
            Bug ID: 76483
          Assignee: nouveau at lists.freedesktop.org
           Summary: [NV50, bisected, RFC patch] xset dpms force {on,off}
                    does not work over DP
        QA Contact: xorg-team at lists.x.org
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: dd at crosstwine.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Driver/nouveau
           Product: xorg

Created attachment 96206
  --> https://bugs.freedesktop.org/attachment.cgi?id=96206&action=edit
RFC patch on top of 34d59508 (drm/nouveau: fix TTM_PL_TT memtype on pre-nv50)

Commit 0a0afd28 (drm/nv50-/disp: move DP link training to core and
train from supervisor) removed a call to 'nouveau_dp_dpms' at the
bottom of nv50_display.c.

Without this call, 'xset dpms force {on,off}' does not have any effect
on my DP-attached monitor.

The attached proof-of-concept patch re-adds the call, as well as a partial
version of nouveau_dp_dpms which causes 'force off' to work again.

It is not clear to me how to trigger link training in the supervisor,
so nouveau_dp_dpms skips that step when handling DRM_MODE_DPMS_ON.
The result is that 'force on' does not cause the monitor to wake up,
and the connection is effectively dead.

Could somebody familiar with the driver could comment on the next
steps to undertake to restore the full {on,off} functionality?

-- 
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/20140322/d69ebe1e/attachment.html>

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

--- Comment #1 from Ben Skeggs <skeggsb at gmail.com> ---
Ah yes, I've been aware of this issue for a while, it just hasn't made
it to
the top of the list yet.  I'll try and address it for the 3.15 cycle, and
backport the fixes to earlier kernels if possible.

-- 
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/20140324/95871d51/attachment.html>

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

--- Comment #2 from Damien Diederen <dd at crosstwine.com> ---
Created attachment 96281
  --> https://bugs.freedesktop.org/attachment.cgi?id=96281&action=edit
[WIP,BROKEN] drm/nv50: Hack FORCE_DP_TRAIN method for DPMS  power-on

Hi Ben,

Excellent!  (FYI: I, for one, don't need any backports.)

In the meantime, I tried to kludge my way into getting the monitor to
wake up with another horrible hack (attached), but did not succeed
before running out of time.  Any idea?

I understand that both patches suffer from the race condition you were
trying to avoid in the first place, but an always on/off monitor is a
bit of a handicap :)

Alternatively/in addition, I would welcome hints on how to make Nouveau
survive power-cycling the monitor (e.g. by running a command over SSH to
reset the display).  The current behaviour is:

             [On, displaying]
                    ?           Turn off
                  [Off]
                    ?           Turn on
                [Booting]
                    ?
      [OSD: No input; shutting down]
                    ?
                [Standby]

Of course, feel free to suggest proper fixes, docs to read, and/or
patches to test.

Cheers, -D

-- 
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/20140324/4bebe373/attachment-0001.html>

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

--- Comment #3 from Karl Schendel <schendel at kbcomputer.com> ---
I think I'm seeing this too.  Mac Pro (2009) with GT120 (G96/NV50) and 24
inch
Apple Cinema display via MDP connection.  powersave blanking used to work in
3.6.3 which was the last kernel I used (opensuse 12.3 otherwise).  Now it does
nothing in opensuse 13.1 which has 3.11.10, also notwork with a 3.14.1 kernel. 
X thinks that it's turned off the display (according to xset q) but nothing
happened.

I would be happy to test a fix if and when a trial is ready.  I have all sorts
of trouble with nouveau on this hardware so I suspect it's not a common
setup.
:-)
Fortunately, recent versions seem pretty good other than the lack of powersave.

-- 
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/20140428/598137ca/attachment.html>

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

--- Comment #4 from Randy Andy <gugelhuepf at googlemail.com> ---
(In reply to comment #1)
> Ah yes, I've been aware of this issue for a while, it just hasn't
made it to
> the top of the list yet.  I'll try and address it for the 3.15 cycle,
and
> backport the fixes to earlier kernels if possible.
Thanks for your work, Ben.

A little feedback from my side.

I tried this yesterday with the 3.15.0-rc6 Kernel, but this misbehaviour
regarding the none working power management is still the same with my 
NVIDIA Corporation GT200GL [Quadro FX 4800] (rev a1) with NV50 Chipset(NVA0).

So it would be great to get this functionality asap ;-)

Regards, Andy.

-- 
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/20140524/49c26fb6/attachment.html>

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

--- Comment #5 from Ilia Mirkin <imirkin at alum.mit.edu> ---
There is a substantial DP rework bound for 3.16. Can you give
http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next a shot? It should
add proper support for 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/20140611/59891270/attachment.html>

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

--- Comment #6 from Damien Diederen <dd at crosstwine.com> ---
(In reply to comment #5)
> There is a substantial DP rework bound for 3.16. Can you give
> http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next a shot? It
should
> add proper support for DPMS.
I will.  ASAP, but probably not today.

Thanks!  -D

-- 
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/20140612/a3c2d484/attachment-0001.html>

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

--- Comment #7 from Randy Andy <gugelhuepf at googlemail.com> ---
(In reply to comment #5)
> There is a substantial DP rework bound for 3.16. Can you give
> http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next a shot? It
should
> add proper support for DPMS.
Forget to mention,

my monitor is connected via DVI and I have the same problem.
Is the rework you mentioned also valid for the DVI output, so is it worth fo me
to giv it a trial?

Nevertheless thanks for your work and best regards, Andy.

-- 
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/20140612/08a4f32e/attachment.html>

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

--- Comment #8 from Damien Diederen <dd at crosstwine.com> ---
(In reply to comment #5)

Hi Ilia, Ben,

I gave a shot at drm-next as of the following commit:
> commit bc1dfff04a5d4064ba0db1fab13f84ab4f333d2b
> Merge: c1a6e9f 1ae5a62
> Author: Dave Airlie <airlied at redhat.com>
> Date:   Wed Jun 11 16:28:10 2014 +1000
> 
>     Merge branch 'drm-nouveau-next' of
git://anongit.freedesktop.org/git/nouveau
>     
>     display rework fixes lots of displayport issues.
I have been running that kernel for a large part of a work day, and, so
far, it has worked pretty well.

Many thanks!

Below are a couple remaining issues, none of which are blocking in my
case (GeForce 9400/DP/Dell U2711), but which may be worth investigating
if they also happen with other hardware combinations:

 1. The display does not wake up from (timed-out or forced) sleep on
    keypress or mouse move as it used to.  Activating the OSD menu wakes
    up the panel; Nouveau seems to pick that up as a hint to get going;

 2. The panel's backlight flickers very noticeably after a soft power
    cycle.  It also flickers, but less noticeably, after a hard unplug/
    re-plug.  Force-switching to an unconnected input source and back
    makes it stable again.

Let me know if there's any way I can assist you further.  In the
meantime, thanks again?it seems I'm not stuck with 3.8 anymore!

Cheers, -D

-- 
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/20140613/5163c6b1/attachment.html>

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

--- Comment #9 from Karl Schendel <schendel at kbcomputer.com> ---
I tried the same commit as Damien did on my hardware (2009 Mac Pro, GT120,
24"
Apple LCD, Mini-Displayport) and it's half a loaf.  DPMS kicks in and the
backlight turns off as it should -- yay!  Unfortunately it doesn't go back
on
-- boo.  I tried keyboard, mouse movement, xset dpms force on;  nothing turned
the display back on.  Power cycling the monitor restores the display but
obviously that's not how it's supposed to work.

-- 
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/20140619/aa8c560c/attachment.html>

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

--- Comment #10 from Karl Schendel <schendel at kbcomputer.com> ---
Meant to add:  when the display goes off, xset q from a remote login shows the
monitor in Standby.  If one moves the mouse or presses keys, xset q says that
the monitor is On, but it isn't.

-- 
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/20140619/2f280f81/attachment.html>

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

--- Comment #11 from Ilia Mirkin <imirkin at alum.mit.edu> ---
First off, while I doubt that this has been fixed, it would be best to try the
latest drm-next, which has some additional nouveau fixes. Assuming the issue
still isn't resolved, could you boot with

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

And go through a DPMS cycle (and then powercycle the monitor to get it to turn
it back on), taking care to note where in the log the various (external) events
happen. I think you can actually just write to /dev/kmsg directly.

-- 
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/20140619/daba4b74/attachment-0001.html>

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

--- Comment #12 from Karl Schendel <schendel at kbcomputer.com> ---
Ok.  Not sure what the latest drm-next is, I found a recent looking
drm-nouveau-next and it did the same thing.

Monitor is blanked (backlight off) via:
[  225.790860] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 8: 0x00000600 1
[  225.790894] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000002
[  225.790897] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  225.790899] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  225.790901] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  225.791037] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 00 0x01108000
0x10000000

and the unsuccessful attempt to restore backlight is:

[  251.285375] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 8: 0x00000600 1
[  251.285388] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000001
[  251.285391] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  251.285393] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  251.285395] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  251.285529] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 00 0x01108000
0x10000000

Full log attached as it's rather lengthy.  ***NOTE*** lines show when things
happened.

-- 
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/20140620/17d6fbe2/attachment.html>

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

--- Comment #13 from Karl Schendel <schendel at kbcomputer.com> ---
Created attachment 101432
  --> https://bugs.freedesktop.org/attachment.cgi?id=101432&action=edit
kernel log from drm-next; backlight won't turn back on

-- 
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/20140620/15342607/attachment.html>

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

--- Comment #14 from Ben Skeggs <skeggsb at gmail.com> ---
Created attachment 101716
  --> https://bugs.freedesktop.org/attachment.cgi?id=101716&action=edit
more debugging

-- 
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/20140625/8d4642ce/attachment.html>

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

--- Comment #15 from Ben Skeggs <skeggsb at gmail.com> ---
(In reply to comment #12)
> Ok.  Not sure what the latest drm-next is, I found a recent looking
> drm-nouveau-next and it did the same thing.
> 
> Monitor is blanked (backlight off) via:
> [  225.790860] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 8: 0x00000600 1
> [  225.790894] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000002
> [  225.790897] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  225.790899] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  225.790901] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  225.791037] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 00 0x01108000
> 0x10000000
> 
> and the unsuccessful attempt to restore backlight is:
> 
> [  251.285375] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 8: 0x00000600 1
> [  251.285388] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000001
> [  251.285391] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  251.285393] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  251.285395] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  251.285529] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 00 0x01108000
> 0x10000000
> 
> Full log attached as it's rather lengthy.  ***NOTE*** lines show when
things
> happened.
Can you grab a new log with that patch I just attached applied?

-- 
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/20140625/650e9b66/attachment.html>

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

--- Comment #16 from Karl Schendel <schendel at kbcomputer.com> ---
Ok but I'm away from that machine for the week, won't be until the
weekend.

-- 
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/20140625/ea3f71c0/attachment.html>

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

--- Comment #17 from Karl Schendel <schendel at kbcomputer.com> ---
With the extra output the display on -> standby (off) transition now looks
like:

[  227.434722] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 8: 0x00000600 1
[  227.434736] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000002
[  227.434738] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  227.434741] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  227.434743] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  227.434877] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 00 0x01108000
0x10000000
[  227.434884] nouveau  [   PDISP][0000:05:00.0] nv50_sor_mthd: 0000 0184
[  227.434886] nouveau  [   PDISP][0000:05:00.0]        0200 0102
[  227.434888] nouveau  [   PDISP][0000:05:00.0]        0002 01c1
[  227.434891] nouveau  [   PDISP][0000:05:00.0]        0006 0284
[  227.434893] nouveau  [   PDISP][0000:05:00.0]        0002 0284
[  227.434913] nouveau  [   PDISP][0000:05:00.0] nv50_sor_mthd: 0006 0184
[  227.434915] nouveau  [   PDISP][0000:05:00.0]        0200 0102
[  227.434917] nouveau  [   PDISP][0000:05:00.0]        0002 01c1
[  227.434919] nouveau  [   PDISP][0000:05:00.0]        0006 0284
[  227.434921] nouveau  [   PDISP][0000:05:00.0]        0002 0284

and the (unsuccessful) off -> on transition looks like:

[  277.955374] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 8: 0x00000600 1
[  277.955387] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000001
[  277.955389] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  277.955392] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  277.955394] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
[  277.955528] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 00 0x01108000
0x10000000
[  277.957570] nouveau  [   PDISP][0000:05:00.0] nv50_sor_mthd: 0000 0184
[  277.957574] nouveau  [   PDISP][0000:05:00.0]        0200 0102
[  277.957576] nouveau  [   PDISP][0000:05:00.0]        0002 01c1
[  277.957578] nouveau  [   PDISP][0000:05:00.0]        0006 0284
[  277.957580] nouveau  [   PDISP][0000:05:00.0]        0002 0284
[  277.957600] nouveau  [   PDISP][0000:05:00.0] nv50_sor_mthd: 0006 0184
[  277.957602] nouveau  [   PDISP][0000:05:00.0]        0200 0102
[  277.957604] nouveau  [   PDISP][0000:05:00.0]        0002 01c1
[  277.957607] nouveau  [   PDISP][0000:05:00.0]        0006 0284
[  277.957609] nouveau  [   PDISP][0000:05:00.0]        0002 0284

I'll attach the full log soon (pressed for time ATM).

-- 
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/20140629/1e0e8f66/attachment.html>

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

--- Comment #18 from Karl Schendel <schendel at kbcomputer.com> ---
Created attachment 101980
  --> https://bugs.freedesktop.org/attachment.cgi?id=101980&action=edit
kernel log with additional debug output

-- 
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/20140629/99472965/attachment.html>

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

--- Comment #19 from Ben Skeggs <skeggsb at gmail.com> ---
(In reply to comment #17)
> With the extra output the display on -> standby (off) transition now
looks
> like:
> 
> [  227.434722] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 8: 0x00000600 1
> [  227.434736] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000002
> [  227.434738] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  227.434741] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  227.434743] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  227.434877] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 00 0x01108000
> 0x10000000
> [  227.434884] nouveau  [   PDISP][0000:05:00.0] nv50_sor_mthd: 0000 0184
> [  227.434886] nouveau  [   PDISP][0000:05:00.0]        0200 0102
> [  227.434888] nouveau  [   PDISP][0000:05:00.0]        0002 01c1
> [  227.434891] nouveau  [   PDISP][0000:05:00.0]        0006 0284
> [  227.434893] nouveau  [   PDISP][0000:05:00.0]        0002 0284
> [  227.434913] nouveau  [   PDISP][0000:05:00.0] nv50_sor_mthd: 0006 0184
> [  227.434915] nouveau  [   PDISP][0000:05:00.0]        0200 0102
> [  227.434917] nouveau  [   PDISP][0000:05:00.0]        0002 01c1
> [  227.434919] nouveau  [   PDISP][0000:05:00.0]        0006 0284
> [  227.434921] nouveau  [   PDISP][0000:05:00.0]        0002 0284
> 
> and the (unsuccessful) off -> on transition looks like:
> 
> [  277.955374] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 8: 0x00000600 1
> [  277.955387] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000001
> [  277.955389] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  277.955392] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  277.955394] nouveau D[     I2C][0000:05:00.0] AUXCH(3): wr 0x00000000
> [  277.955528] nouveau D[     I2C][0000:05:00.0] AUXCH(3): 00 0x01108000
> 0x10000000
> [  277.957570] nouveau  [   PDISP][0000:05:00.0] nv50_sor_mthd: 0000 0184
> [  277.957574] nouveau  [   PDISP][0000:05:00.0]        0200 0102
> [  277.957576] nouveau  [   PDISP][0000:05:00.0]        0002 01c1
> [  277.957578] nouveau  [   PDISP][0000:05:00.0]        0006 0284
> [  277.957580] nouveau  [   PDISP][0000:05:00.0]        0002 0284
> [  277.957600] nouveau  [   PDISP][0000:05:00.0] nv50_sor_mthd: 0006 0184
> [  277.957602] nouveau  [   PDISP][0000:05:00.0]        0200 0102
> [  277.957604] nouveau  [   PDISP][0000:05:00.0]        0002 01c1
> [  277.957607] nouveau  [   PDISP][0000:05:00.0]        0006 0284
> [  277.957609] nouveau  [   PDISP][0000:05:00.0]        0002 0284
> 
> I'll attach the full log soon (pressed for time ATM).
I see what's going on, I'll push a patch in the next little while. 
Thank you.

-- 
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/20140630/fc82a9a3/attachment.html>

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

--- Comment #20 from Ben Skeggs <skeggsb at gmail.com> ---
This commit[1] should hopefully make things work for you.

Let me know how you go,
Ben.

[1]
http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=55f5a9c64a638b1e14f39b43459d8eb581a479c3

-- 
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/20140630/020bfd25/attachment.html>

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

--- Comment #21 from Karl Schendel <schendel at kbcomputer.com> ---
That change alas produces a garbled display at startup.  (It's wrapped in
both
directions and jittery, like an old TV with bad sync pulse detection.)

Just for the heck of it, I tried removing the -1 (dcb->heads is 2) and the
display is fine but then it's back to DPMS on not working after 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/20140630/ef86adc3/attachment-0001.html>

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

--- Comment #22 from Ben Skeggs <skeggsb at gmail.com> ---
(In reply to comment #21)
> That change alas produces a garbled display at startup.  (It's wrapped
in
> both directions and jittery, like an old TV with bad sync pulse detection.)
> 
> Just for the heck of it, I tried removing the -1 (dcb->heads is 2) and
the
> display is fine but then it's back to DPMS on not working after off.
Can I get a debug log of that please?

-- 
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/20140630/c9026780/attachment.html>

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

--- Comment #23 from Karl Schendel <schendel at kbcomputer.com> ---
Created attachment 102016
  --> https://bugs.freedesktop.org/attachment.cgi?id=102016&action=edit
dmesg from garbled display

The interesting thing here is that I waited for the dpms timeout, and the
screen flashed and came back on more or less immediately, but clean.  It's
as
if something decided that the DPMS-off transition was "activity" and
turned the
screen back on, properly this time.  I don't think that's a driver issue
though.

-- 
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/20140630/96e14edf/attachment.html>

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

--- Comment #24 from Ben Skeggs <skeggsb at gmail.com> ---
(In reply to comment #23)
> Created attachment 102016 [details]
> dmesg from garbled display
Not sure if/why it's causing a garbled display, but I did spot one bug from
the
log that's causing link retraining when it's not needed:

http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=acc79e940a096657651980eb140176921a658e0c
> 
> The interesting thing here is that I waited for the dpms timeout, and the
> screen flashed and came back on more or less immediately, but clean. 
It's
> as if something decided that the DPMS-off transition was
"activity" and
> turned the screen back on, properly this time.  I don't think
that's a
> driver issue though.
I hope this is just the monitor being really confused as a result of whatever
went wrong before it.  If it's not, your monitor is doing the wrong thing
and
it's going to cause it to immediately resume from a power off (we can work
around the problem if it's necessary).  But, in your log, your monitor is
saying "help! i lost the link! retrain me!" in response to
DP_SET_POWER_D3,
which it is *explicitly* (according to the DP spec, and, well, common sense)
not supposed to do.

-- 
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/20140701/4e86f2e3/attachment.html>

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

--- Comment #25 from Karl Schendel <schendel at kbcomputer.com> ---
That fixed the garbled display.

The monitor off/on thing is weird.  When I was trying to get 3.14 to work
(before discovering this bug report), I tried the nvidia binary driver and got
the same flash off/on thing.  However, dpms-off was working in 3.6.3, which I
unfortunately don't have lying around any more.  It seems strange that the
monitor would break in this manner, so I guess the 3.6.x driver was doing
something to work around the monitor's response.  (Also, the monitor-off
screensaver works when I am in OS/X.)

I can get a log to verify if you like, later today.  If there's anything I
can
get from 3.6 to see if it's doing something different, let me know;  I'm
sure I
can find and build a 3.6 sometime in the next day or two if necessary.

At least it's going in the right direction - thanks!

-- 
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/20140701/d9d3d5b6/attachment.html>

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

--- Comment #26 from Ben Skeggs <skeggsb at gmail.com> ---
(In reply to comment #25)
> That fixed the garbled display.
> 
> The monitor off/on thing is weird.  When I was trying to get 3.14 to work
> (before discovering this bug report), I tried the nvidia binary driver and
> got the same flash off/on thing.  However, dpms-off was working in 3.6.3,
> which I unfortunately don't have lying around any more.  It seems
strange
> that the monitor would break in this manner, so I guess the 3.6.x driver
was
> doing something to work around the monitor's response.  (Also, the
> monitor-off screensaver works when I am in OS/X.)
If it's the same situation as Nouveau, then the binary driver probably
ignored
the HPD_IRQ pulse from the monitor.  We need to care about it now (well, we
were *supposed* to already, but anyway) for MST support particularly.  I'm
pretty sure I can work around the issue in the driver if we need to, so
that's
ok.
> 
> I can get a log to verify if you like, later today.  If there's
anything I
> can get from 3.6 to see if it's doing something different, let me know;
I'm
> sure I can find and build a 3.6 sometime in the next day or two if
necessary.
That'd be great, thanks.
> 
> At least it's going in the right direction - thanks!
-- 
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/20140701/78497b5d/attachment.html>

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

--- Comment #27 from Karl Schendel <schendel at kbcomputer.com> ---
Created attachment 102151
  --> https://bugs.freedesktop.org/attachment.cgi?id=102151&action=edit
debug output from last patch, dpms works but screen flashes back on

-- 
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/20140702/c0d0b25c/attachment.html>

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

--- Comment #28 from Karl Schendel <schendel at kbcomputer.com> ---
Created attachment 102152
  --> https://bugs.freedesktop.org/attachment.cgi?id=102152&action=edit
debug output from 3.6.3

Don't know if this will help any, but 3.6.3 was the last kernel in which I
was
able to a) run nouveau successfully and b) have the full monitor-off timeout
stuff work.

I don't pretend that I tried every in-between version, but in general
between
3.7 and 3.11 I was never able to find the right magic words to get any kind of
operational display, or perhaps things were broken.  3.11 onwards works but
then we have the DP DPMS issue which is the original point of this bug report.

-- 
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/20140702/b9b77a98/attachment.html>

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

--- Comment #29 from Ben Skeggs <skeggsb at gmail.com> ---
Yeah, that's pretty much as expected.  Your monitor is broken.  I'll
come up
with some kind of workaround today.

-- 
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/20140702/a1fb1684/attachment.html>

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

--- Comment #30 from Ben Skeggs <skeggsb at gmail.com> ---
Give this a try:
http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=31080d6499d64e0578ef55f7473ed83b7bfd72af

-- 
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/20140702/1c7987b6/attachment.html>

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

--- Comment #31 from Karl Schendel <schendel at kbcomputer.com> ---
Yes, that one does the trick.  Excellent, thanks.

Who knows why Apple thought that behavior was a good idea.  I think it was
their first (mini-)display-port design, but still.  Whatever...

-- 
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/20140703/e3dd1d39/attachment.html>

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

--- Comment #32 from Damien Diederen <dd at crosstwine.com> ---
Hi Ben, Karl,

I'm very happy Karl could help diagnose this.

(In reply to comment #30)
> Give this a try:
> http://cgit.freedesktop.org/~darktama/nouveau/commit/
> ?id=31080d6499d64e0578ef55f7473ed83b7bfd72af
A janitorial mishap gave me an opportunity to (finally!) update the
affected machine.  It is now running v3.16-rc6, which includes commit
7fac4933 (matching your patch above).

The remaining issues mentioned in comment #8 appear to be fixed in my
configuration, too.  Thanks!  I think this ticket can be closed.

Cheers, -D

-- 
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/20140809/4bec89a1/attachment.html>

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

Ilia Mirkin <imirkin at alum.mit.edu> changed:

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

-- 
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/20140822/b630ff6d/attachment.html>