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 104784] Unable to do reclocking manually
Date: Thu, 25 Jan 2018 09:39:01 +0000	[thread overview]
Message-ID: <bug-104784-8800-CShXWEPUsy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104784-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #1 from Pierre Moreau <pierre.morrow-GANU6spQydw@public.gmane.org> ---
Hello,

> AC: core 0 MHz memory 0 MHz

means your GPU is actually suspended: since you have an Optimus configuration,
the NVIDIA GPU will suspend automatically if it hasn’t received any work to do
in a short while. Try for example to run `DRI_PRIME=1 glxgears`, keep it
running and reissue the cat command: you should not see actual clocks for on
the AC line.
Have a look at https://nouveau.freedesktop.org/wiki/Optimus/ to learn how to
configure Prime.

As for the system hang when trying to reclock a suspended GPU, patches have
been sent to the Nouveau mailing list, but haven’t been merged yet. You can
find them here:
https://github.com/karolherbst/nouveau/commits/clk_cleanup_for_real

> And when i launch a game (Tyranny), it does not work.

What is not working? If you didn’t specify anything, the game should run on the
“primary” GPU by default, which quite often tends to be the Intel GPU.

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

[-- Attachment #1.2: Type: text/html, Size: 2083 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:[~2018-01-25  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  7:16 [Bug 104784] New: Unable to do reclocking manually bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-104784-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-01-25  9:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-01-25 10:40   ` [Bug 104784] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:35   ` 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-104784-8800-CShXWEPUsy@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.