Nouveau - Jul 2019 - [Bug 111110] New: Nvidia quadro + nouveau : second terminal wake up but doesn't more display

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

            Bug ID: 111110
           Summary: Nvidia quadro + nouveau : second terminal wake up but
                    doesn't more display
           Product: Mesa
           Version: 19.1
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: conde.philippe at skynet.be
        QA Contact: nouveau at lists.freedesktop.org

Created attachment 144764
  --> https://bugs.freedesktop.org/attachment.cgi?id=144764&action=edit
output of dmesg

I have a OpenSUSE tumbleweed system with a nvidia quadro K4200 on which 2
screens are connected 
- one on the DVI port
- the second on the display port 1 (DP1)
the two screens use resolution 1920*1080 and are defined as a  virtual screen
of 3480*1080.
I use nouveau as driver; DE is KDE

This worked form years without problem. After installation of snapshot 20190708
I rebooted and the second screen doesn't more display anything.

in journalctl I find this error
Jul 11 08:30:04 hpprol2 kernel: nouveau 0000:0a:00.0: disp: outp 03:0006:0f42:
training failed

The second screens wake up on some action (boot, starting xorg, login etc...)
but after some seconds display " Display port: no signal"

As requested by OpenSUSE support I installed the last kernel , Mesa et
xf86-video-nouveau

rpm -qa Mesa*
Mesa-libGL1-19.1.2-977.1.x86_64
Mesa-KHR-devel-19.1.2-977.1.x86_64
Mesa-libGL-devel-19.1.2-977.1.x86_64
Mesa-gallium-32bit-19.1.2-977.1.x86_64
Mesa-libGL1-32bit-19.1.2-977.1.x86_64
Mesa-libGLESv2-2-19.1.1-223.1.x86_64
Mesa-libva-19.1.1-223.1.x86_64
Mesa-19.1.2-977.1.x86_64
Mesa-dri-19.1.2-977.1.x86_64
Mesa-libglapi0-19.1.1-223.1.x86_64
Mesa-libEGL1-19.1.2-977.1.x86_64
Mesa-gallium-19.1.2-977.1.x86_64
Mesa-demo-x-8.4.0-1.6.x86_64
Mesa-dri-nouveau-19.1.2-977.1.x86_64
Mesa-dri-32bit-19.1.2-977.1.x86_64
Mesa-libEGL1-32bit-19.1.1-223.1.x86_64
Mesa-32bit-19.1.2-977.1.x86_64
Mesa-libEGL-devel-19.1.2-977.1.x86_64
Mesa-libglapi0-32bit-19.1.1-223.1.x86_64

uname -a
Linux hpprol2 5.2.0-2.gfd43abf-default #1 SMP Thu Jul 11 05:19:05 UTC 2019
(fd43abf) x86_64 x86_64 x86_64 GNU/Linux

rpm -qa xf86-video-nouveau
xf86-video-nouveau-1.0.15-40.11.x86_64

The problem remains. I attach here the output of dmesg.

See also https://bugzilla.opensuse.org/show_bug.cgi?id=1141041

Regards
Philippe Condé

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

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

--- Comment #1 from Philippe Condé <conde.philippe at skynet.be> ---
Hello,

with the last Mesa from OpenSUSE factory this regression is still present
# rpm -qa Mesa*
Mesa-32bit-19.1.2-225.1.x86_64
Mesa-dri-19.1.2-225.1.x86_64
Mesa-libglapi0-19.1.2-225.1.x86_64
Mesa-demo-x-8.4.0-1.7.x86_64
Mesa-libGLESv2-2-19.1.2-225.1.x86_64
Mesa-libEGL1-19.1.2-225.1.x86_64
Mesa-dri-nouveau-19.1.2-225.1.x86_64
Mesa-libGL1-19.1.2-225.1.x86_64
Mesa-libva-19.1.2-225.1.x86_64
Mesa-libGL1-32bit-19.1.2-225.1.x86_64
Mesa-19.1.2-225.1.x86_64
Mesa-libglapi0-32bit-19.1.2-225.1.x86_64
Mesa-gallium-32bit-19.1.2-225.1.x86_64
Mesa-dri-32bit-19.1.2-225.1.x86_64
Mesa-gallium-19.1.2-225.1.x86_64
Mesa-KHR-devel-19.1.2-225.1.x86_64
Mesa-libEGL-devel-19.1.2-225.1.x86_64
Mesa-libGL-devel-19.1.2-225.1.x86_64
Mesa-libEGL1-32bit-19.1.2-225.1.x86_64

# rpm -qa xf86-video-nouveau
xf86-video-nouveau-1.0.15-40.12.x86_64

# uname -a
Linux hpprol2 5.2.1-1-default #1 SMP Mon Jul 15 05:32:47 UTC 2019 (bf5c01b)
x86_64 x86_64 x86_64 GNU/Linux

the same error is present in journalctl.
Jul 25 08:29:02 hpprol2 kernel: nouveau 0000:0a:00.0: disp: outp 03:0006:0f42:
training failed

Not sure if Mesa is involved or alone nouveau?

Regards

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

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

--- Comment #2 from Philippe Condé <conde.philippe at skynet.be> ---
Created attachment 145022
  --> https://bugs.freedesktop.org/attachment.cgi?id=145022&action=edit
Xorg.0.log

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

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

--- Comment #3 from Philippe Condé <conde.philippe at skynet.be> ---
Hello I tested with the last available kernel
"Linux hpprol2 5.3.0-rc3-4.g7de292a-default #1 SMP Fri Aug 9 16:17:27 UTC
2019
(7de292a) x86_64 x86_64 x86_64 GNU/Linux
"

This regression is still present.

I have attached the Xorg.0.log. Do you need other information?

Many thanks in advance
Philippe

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

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

--- Comment #4 from Philippe Condé <conde.philippe at skynet.be> ---
Created attachment 145027
  --> https://bugs.freedesktop.org/attachment.cgi?id=145027&action=edit
journalctl with debug

hello,

I added the parameters "drm.debug=14  log_buf_len=16M" on the boot
option
here the output of journalctl -b 0

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

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

--- Comment #5 from Philippe Condé <conde.philippe at skynet.be> ---
Created attachment 145028
  --> https://bugs.freedesktop.org/attachment.cgi?id=145028&action=edit
dmesg output with debug

hello,

I added the parameters "drm.debug=14  log_buf_len=16M" on the boot
option
here the output of dmesg

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

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

--- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> ---
What was a working kernel, and what's a non-working kernel?

The most effective way to determine the problematic change is to do a git
bisect between those two kernels.

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

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

--- Comment #7 from Philippe Condé <conde.philippe at skynet.be> ---
Created attachment 145029
  --> https://bugs.freedesktop.org/attachment.cgi?id=145029&action=edit
Xorg.0.log with debug

hello,

I added the parameters "drm.debug=14  log_buf_len=16M" on the boot
option
here the Xorg.0.log

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

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

--- Comment #8 from Philippe Condé <conde.philippe at skynet.be> ---
(In reply to Ilia Mirkin from comment #6)
> What was a working kernel, and what's a non-working kernel?
> 
> The most effective way to determine the problematic change is to do a git
> bisect between those two kernels.
I think that it is not the kernel because when I saw the problem I rebooted the
preceding kernel and the problem was then also present.
On july, 10 I installed.a snapshot with a lot of component. looking in the
zypper log in see that the kernel:
Old = 5.1.15-1.1
New = 5.1.16-1.2

libdrm-nouveau2 
Old: 2.4.98-1.3 (installed on 2019-06-17) ==> no probelm
New: 2.4.99-1.1  ==> problem is present 

I never did a bisect. I'll try to find some info about this but no sure if I
can do it.

Regards
Philippe

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

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

--- Comment #9 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Perhaps I don't quite understand the issue then, but display modesets are
controlled by the kernel. The error you're seeing is with link training. So
it
seems likely that a kernel update is responsible.

Could also be a userspace update which makes use of the kernel differently,
triggering a pre-existing bug. libdrm_nouveau/mesa and such are not at all
involved in this though -- that's just for 2d/3d accelerated rendering.

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

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

GitLab Migration User <gitlab-migration at fdo.invalid> changed:

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

--- Comment #10 from GitLab Migration User <gitlab-migration at
fdo.invalid> ---
-- 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/mesa/mesa/issues/1186.

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