All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 02 Dec 2016 09:52:40 +0000	[thread overview]
Message-ID: <bug-94725-8800-V0FUsTaXtC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94725-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2853 bytes --]

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

--- Comment #26 from Orsiris de Jong <info-3cfOhUhRyghWj0EZb7rXcA@public.gmane.org> ---
I too have a optimus laptop with GM107 / intel graphics card, and I have not
been able to use nouveau driver since I bought the laptop (using kernels 4.3.5
up to 4.8.10 on Fedora 23-25 x64).

I have searched for multiple solutions so far, and always finished by
blacklisting nouveau in order to be able to use that laptop.
I could not even able to launch lspci without rendering my system unresponsive
(process then takes 100% cpu and I get cpu softlocks)

I've tried nouveau.runpm=0 and well, I can at least boot without having nouveau
totally disabled :)

When not using runpm=0, I get the following when launching lspci / or
DRI_PRIME=1 glxgears

[ 1470.121123] nouveau 0000:01:00.0: Refused to change power state, currently
in D3
[ 1470.193738] nouveau 0000:01:00.0: Refused to change power state, currently
in D3
[ 1470.205762] nouveau 0000:01:00.0: Refused to change power state, currently
in D3
[ 1470.205766] nouveau 0000:01:00.0: DRM: resuming kernel object tree...
[ 1470.205792] nouveau 0000:01:00.0: pci: failed to adjust cap speed
[ 1470.205793] nouveau 0000:01:00.0: pci: failed to adjust lnkctl speed

So I guess the nouveau driver cannot send to sleep / wake my nvidia card for
whatever reason.

I am actually trying rely on the discrete graphics in order to reduce power
consumption by default.

I noticed that I can't use vgaswitcheroo in order to chose my primary graphic
card. Also noticed the following error messages on boot.
[    1.795356] [drm] Initialized drm 1.1.0 20060810
[    1.881362] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch -
Found [Buffer], ACPI requires [Package] (20160422/nsarguments-95)
[    1.881428] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20160422/nsarguments-95)
[    1.881552] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20160422/nsarguments-95)
[    1.881753] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.PEGP
handle
[    1.881753] nouveau: detected PR support, will not use DSM

So far, when I switch graphic cards, I get the following in dmesg:

[ 1174.921195] nouveau 0000:01:00.0: DRM: resuming kernel object tree...
[ 1174.921209] nouveau 0000:01:00.0: DRM: resuming client object trees...
[ 1174.921226] nouveau 0000:01:00.0: fifo: BIND_ERROR 01 [BIND_NOT_UNBOUND]
[ 1317.637168] vga_switcheroo: client 0 refused switch

I guess that nouveau driver does not allow to disable the nvidia card when
runpm=0 is passed as argument ?

Anything I could try please ?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3643 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2016-12-02  9:52 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
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 [this message]
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-V0FUsTaXtC@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.