From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 94725] Nouveau driver fails to poweron GPU on GM204 after dynamic poweroff
Date: Sun, 05 Jun 2016 12:37:17 +0000 [thread overview]
Message-ID: <bug-94725-8800-bI408r9bgY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94725-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 791 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94725
--- Comment #19 from Tobias Jakobi <liquid.acid-hi6Y0CQ0nG0@public.gmane.org> ---
I think I'm seeing the same issue here on a Schenker XMG A506 notebook. The NV
GPU is the dedicated one. AFAIK all display hardware is connected to the Intel
iGPU.
Kernel is vanilla 4.6.1. Actually this is the first kernel (and the first time)
that I try to use the dedicated GPU.
lspci:
01:00.0 VGA compatible controller: NVIDIA Corporation GM107M [GeForce GTX 960M]
(rev a2)
Without runpm=0 even just calling DRI_PRIME=1 glxinfo leaves the system
unresponsive shortly afterwards. SysRq still works though.
Going to attach the part of the log in a second.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1589 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2016-06-05 12:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 16:28 [Bug 94725] New: Nouveau driver fails to load on GM204 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-94725-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-03-27 17:23 ` [Bug 94725] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-27 17:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-27 17:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-28 2:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-30 19:11 ` [Bug 94725] Nouveau driver fails to poweron GPU on GM204 after dynamic poweroff bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-30 22:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 3:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 3:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 6:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 6:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 7:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 8:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 13:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-01 15:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-94725-8800-0111GoOQVN-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-04-05 1:25 ` Efrem Mc
2016-04-05 1:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 1:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 4:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 4:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-06 12:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-05 12:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-06-05 12:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-05 15:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-05 15:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-01 12:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-16 17:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-20 8:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 14:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-02 9:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-02 10:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-02 15:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-04 9:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-02 10:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:11 ` 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-94725-8800-bI408r9bgY@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.