Nouveau - Jan 2018 - [Bug 104784] New: Unable to do reclocking manually

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

            Bug ID: 104784
           Summary: Unable to do reclocking manually
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: berillions at gmail.com
        QA Contact: xorg-team at lists.x.org

Hi,

I have a laptop with Optimus technology, my Nvidia card is a GTX 640MX. I use
Debian Unstable x86_64 with nouveau 1.0.15 and Mesa 17.3.3

Unfortunatly, it's impossible to do reclocking with Nouveau and my GPU.

When i launch "cat /sys/kernel/debug/dri/1/pstate", i have these
results :
07: core 270-405 MHz memory 648 MHz
0a: core 270-601 MHz memory 1600 MHz
0f: core 270-614 MHz memory 2800 MHz
AC: core 0 MHz memory 0 MHz

------

It's anormal to have these line "AC: core 0 MHz memory 0 MHz",
right ?
Because when i set "echo 0f > /sys/kernel/debug/dri/1/pstate", the
console (not
the system) hangs. And when i launch a game (Tyranny), it does not work.

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

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

--- Comment #1 from Pierre Moreau <pierre.morrow at free.fr> ---
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20180125/7225a7b2/attachment.html>

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

--- Comment #2 from Max <berillions at gmail.com> ---
(In reply to Pierre Moreau from comment #1)
> 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
I added to my ~/.xinitrc this line « xrandr --setprovideroffloadsink nouveau
Intel »
I see correctly the Intel GPU when i launch « glxinfo | grep « OpenGL vendor
string » » and the Nvidia GPU if i add DRI_PRIME=1.
> > 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.
In fact the games runs with Nouveau and DRI_PRIME=1.
It does not work after to do the reclocking => the game’s process exist but
the
game’s window does not appear.

Are you French, if yes it’s easiest to explain :
Lorsque je lance la commande pour faire le reclocking, je n’ai plus accès au
prompt, comme si la commande continue de travailler en arrière plan. Si je
verifie l’état de pstate dans une autre commande, le reclocking a l’air d’avoir
été  fait.

-- 
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/20180125/30067216/attachment-0001.html>

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

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

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

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

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