Nouveau - Oct 2018 - [Bug 108615] New: [NVE7] changing resolution causes blank screen

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

            Bug ID: 108615
           Summary: [NVE7] changing resolution causes blank screen
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: jbytecoder at gmail.com
        QA Contact: xorg-team at lists.x.org

Created attachment 142308
  --> https://bugs.freedesktop.org/attachment.cgi?id=142308&action=edit
Xorg server log just after resolution switch

Using latest software ( linux-4.19.0, xf86-video-nouveau-1.0.15, mesa-18.2.3,
libdrm-2.4.96, xorg-server-1.20.3 ). When I try to change screen resolution
using xrandr to anything below native resolution the screen goes blank. To be
exact 
issuing xrandr -s 1024x768 causes the flowing:
1) screen turns completely black right away
2) after some time  ( no more that 500ms ), the screen changes to black with
backlight on. Looks a lot like no modesetting console without any content 
3) this situation persists, indefinitely

What is interesting is that switching to console works. The console just works.
However when I switch back to X, the above procedure repeats with one detail -
for a brief moment ( at the same moment as step 1) ) the content of desktop in
selected resolution is visible. It seems that the desktop content is somewhere
in memory but the driver decides to render some other area of memory

The only resolution to this problem that is working is to use older kernel,
linux-4.9.95 to be precise  

I discovered the issue, playing games through wine. But to isolate the cause I
gathered dmesg & xorg.log, running only an openbox and using xrandr to cause
the issue

I don't know what further info could be usefull

-- 
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/20181031/5af7c5b2/attachment.html>

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

--- Comment #1 from jbytecoder at gmail.com ---
Created attachment 142309
  --> https://bugs.freedesktop.org/attachment.cgi?id=142309&action=edit
Kernel log just after the issue

-- 
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/20181031/3033d2ec/attachment.html>

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

--- Comment #2 from jbytecoder at gmail.com ---
Created attachment 142310
  --> https://bugs.freedesktop.org/attachment.cgi?id=142310&action=edit
Video bios of the faulty card

-- 
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/20181031/c519ef1a/attachment.html>

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

--- Comment #3 from Phil Turmel <philip at turmel.org> ---
I have what is likely a related problem -- any change to resolution or
re-enabling an output on my system, via xrandr or the equivalent KDE dialog,
yields a black screen and/or artifacts from the framebuffer console.  When
multiple monitors are enabled, the affected outputs are black until the mouse
pointer moves in their region, yielding artifacts plus *correct* mouse pointer.

Until recently, operation was restored solely by restarting X.  With kernel
4.19.3, operation can be restored by switching to a text console (all connected
outputs turn on) and switching back to X.  The phenomenon occurs on all monitor
ports, on the dock or not, whether docked or not, and both before and after
suspend/resume.

Laptop is an HP ZBook 17 with GK107GLM (K1100M) with gentoo unstable:

Linux corvus 4.19.3 #305 SMP PREEMPT Wed Nov 21 12:21:12 EST 2018 x86_64
Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz GenuineIntel GNU/Linux

x11-base/xorg-server-1.20.3
x11-drivers/xf86-video-nouveau-1.0.15-r1
media-libs/mesa-18.3.0_rc3
x11-libs/libdrm-2.4.96

-- 
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/20181121/8fb3e834/attachment.html>

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

--- Comment #4 from Phil Turmel <philip at turmel.org> ---
Created attachment 142552
  --> https://bugs.freedesktop.org/attachment.cgi?id=142552&action=edit
View of display artifacts with mouse pointer.

-- 
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/20181121/21b68ed6/attachment.html>

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

Phil Turmel <philip at turmel.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |philip at turmel.org

--- Comment #5 from Phil Turmel <philip at turmel.org> ---
Created attachment 142553
  --> https://bugs.freedesktop.org/attachment.cgi?id=142553&action=edit
View of X's complete framebuffer (triple head) screenshotted with artifacts
visible

Note the mouse cursor on the right-hand monitor that had been disabled then
re-enabled.

-- 
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/20181121/0f6c2b85/attachment.html>

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

--- Comment #6 from Phil Turmel <philip at turmel.org> ---
Created attachment 142554
  --> https://bugs.freedesktop.org/attachment.cgi?id=142554&action=edit
Kernel log including a disable/re-enable cycle

Note that no events appeared in dmesg during the xrandr changes.

-- 
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/20181121/f270cffa/attachment-0001.html>

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

--- Comment #7 from jbytecoder at gmail.com ---
I have tested the issue against linux-5.3 and it stil persists. I also
attempted to narrow down the commit that did introduce the problem. 

Using kernel sources at https://github.com/torvalds/linux.git i detected that
between tags v4.9 and v4.10  The kernel breaks @ 9439b3710df6 - this is a big
change commit that intorduces drm changes planned for linux-4.10. 

I guess the issue has to do with "atomic modesseting" it would appear
that for
nv50 the atomic modesseting works only for default resolution, but not for any
other

Can someone suggest any way to further narrow down the culprit ?
logging has no effect ( no errors appear in log )

-- 
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/20190921/26903f62/attachment.html>

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

jbytecoder at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|medium                      |high
            Version|unspecified                 |7.7 (2012.06)
           Severity|normal                      |major

-- 
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/20190921/1660287f/attachment.html>

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

jbytecoder at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |regression

-- 
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/20190921/8173f06f/attachment.html>

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

Maris Nartiss <maris.nartiss at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |maris.nartiss at gmail.com

--- Comment #8 from Maris Nartiss <maris.nartiss at gmail.com> ---
Created attachment 145527
  --> https://bugs.freedesktop.org/attachment.cgi?id=145527&action=edit
Kernel log with a switch from native to lower resolution

Phil Turmel – I am not certain if your issue is the same as the reporter has.
I do have exactly same symptoms – after changing resolution to not native, I
get black screen with backlight on. It is not an DE or WM issue, as I was
testing with bare xinit session. If there are other outputs active, they still
show picture just fine (split screen or clone mode). Thus, as jbytecoder wrote,
X is still fine, just nothing goes to particular output device.

G98M (NV50 family) card tested with kernel 5.0 and 5.3.

Attached dmesg was generated after a reboot, stopping sddm, starting xinit
session and changing resolution to 1024x768 (native is 1440x900).

-- 
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/20190926/43d611de/attachment.html>

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

Martin Peres <martin.peres at free.fr> changed:

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

--- Comment #9 from Martin Peres <martin.peres at free.fr> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/464.

-- 
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/20191204/4f767389/attachment.html>