From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 107167] New: constantly firing events while screen attached to NVIDIA card is disabled
Date: Mon, 09 Jul 2018 14:10:10 +0000 [thread overview]
Message-ID: <bug-107167-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1710 bytes --]
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-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: sam-qkiumcfQ8OTe9xe1eoZjHA@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.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.
[-- Attachment #1.2: Type: text/html, Size: 3213 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2018-07-09 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 14:10 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-107167-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-07-09 14:13 ` [Bug 107167] constantly firing events while screen attached to NVIDIA card is disabled bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-09 14:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-09 16:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-09 16:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-09 16:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-28 9:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-107167-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox