Nouveau - Jul 2018 - [Bug 107167] New: constantly firing events while screen attached to NVIDIA card is disabled

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

            Bug ID: 107167
           Summary: constantly firing events while screen attached to
                    NVIDIA card is disabled
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: sam at robots.org.uk
        QA Contact: xorg-team at lists.x.org

Created attachment 140522
  --> https://bugs.freedesktop.org/attachment.cgi?id=140522&action=edit
output of 'udevadm monitor -p | ts' while screen is locked

I've got a Lenovo P50 with hybrid graphics cards:

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M2000M]
(rev a2)

The internal display is connected to the Intel card. External display ports are
wired to the NVIDIA card. I'm using the autobind-GPUs Xorg patch so that I
don't have to run `xrandr --setprovideroutputsource` in order to make the
external ports usable.

While I'm away from the system, the monitor gets blanked. While it's in
this
state, I see many change events from the NVIDIA device (udevadm monitor output
attached). This exacerbates a memory leak in gnome-desktop that causes clients
to consume several GiB of memory after I come back to the laptop, having left
it idle over the weekend.

-- 
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/20180709/468040de/attachment.html>

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

--- Comment #1 from Sam Morris <sam at robots.org.uk> ---
Created attachment 140523
  --> https://bugs.freedesktop.org/attachment.cgi?id=140523&action=edit
kernel log

dmesg output, interest parts between 12:00 and 13:00 and 14:50 to 15:00.

-- 
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/20180709/fdb412a1/attachment.html>

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

Roy <nouveau at spliet.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #2 from Roy <nouveau at spliet.org> ---
I suspect that more information could be useful. A good starting point would be
to attach:
- Your VBIOS (obtained from /sys/kernel/debug/dri/<number>/vbios.rom while
the
GPU is powered on), and
- A full dmesg of a booting system.

Also: is this problem a regression from earlier kernels? If so, have you tried
to pinpoint which kernel change (version, but ideally commit) led to this
undesirable behaviour?

Thanks!

-- 
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/20180709/a2d1ae5f/attachment.html>

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

--- Comment #3 from Sam Morris <sam at robots.org.uk> ---
Created attachment 140524
  --> https://bugs.freedesktop.org/attachment.cgi?id=140524&action=edit
vbios.com

I'm not sure if the card currently counts as 'powered on' given:

# cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:00:02.0
1:DIS: :DynPwr:0000:01:00.0

But here's my current vbios.rom file anyway. If you need me to somehow power
the card up and try again then let me know (I'm not sure how to do that -
writing "ON" to the file doesn't change the output).

-- 
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/20180709/26652916/attachment.html>

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

Sam Morris <sam at robots.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #140523|0                           |1
        is obsolete|                            |

--- Comment #4 from Sam Morris <sam at robots.org.uk> ---
Created attachment 140527
  --> https://bugs.freedesktop.org/attachment.cgi?id=140527&action=edit
full kernel log

Here's 'journalctl -k' which goes back to the system boot.

-- 
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/20180709/afbc7981/attachment.html>

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

Sam Morris <sam at robots.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|1                           |0
             Status|NEEDINFO                    |UNCONFIRMED

--- Comment #5 from Sam Morris <sam at robots.org.uk> ---
As for a working kernel version: I apologize for not mentioning that I'm
using
4.17.3.

    Linux version 4.17.0-1-amd64 (debian-kernel at lists.debian.org) (gcc
version
7.3.0  (Debian 7.3.0-24)) #1 SMP Debian 4.17.3-1 (2018-07-02)

While I do have 4.16.16 on the system as well, I'm almost certain that
I've
seen this behaviour since I first started using this laptop, with much older
kernels (well, at least 4.14... maybe 4.9). I remember looking into a this
gnome-settings-daemon memory leak back then, but never got to the bottom of it
because frankly the laptop was just not stable enough to stay up long enough to
reproduce the problem!

-- 
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/20180709/bd8a62f5/attachment-0001.html>

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

--- Comment #6 from Sam Morris <sam at robots.org.uk> ---
I haven't seen this since installing a newer kernel from Debian (4.17.14)
and
rebooting. Prior to the reboot I was running 4.17.8 and did observe the
problem.

I'll resolve this bug when I'm sure the problem is gone.

-- 
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/20180828/d332a818/attachment.html>

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

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

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

--- Comment #7 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/443.

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