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 111128] New: Impossible to change pstate on GT610M
Date: Sun, 14 Jul 2019 15:20:48 +0000	[thread overview]
Message-ID: <bug-111128-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 111128
           Summary: Impossible to change pstate on GT610M
           Product: Mesa
           Version: 19.1
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: gzgagz-ig2FU/hGoaU@public.gmane.org
        QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org

Hello,
I have an asus UX32VD, with a GT610M inside, which works with the Optimus
architecture, handle by PRIME. The bug is currently with the kernel 5.2.0, but
it have always been like that as far as I remember.

uname -a :
Linux ga-laptop 5.2.0-arch2-1-ARCH #1 SMP PREEMPT Mon Jul 8 18:18:54 UTC 2019
x86_64 GNU/Linux

lspci :
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M /
GT 620M/625M/630M/720M] (rev a1)

While it is not in use, nouveau shutdown the chipset as expected :
cat /sys/kernel/debug/dri/1/pstate
07: core 270 MHz memory 405 MHz
0f: core 625 MHz memory 900 MHz
DC: core 0 MHz memory 0 MHz

While an app is launched with DRI_PRIME=1, we can see that the chipset is set
to 07 :
DRI_PRIME=1 glxgears &
cat /sys/kernel/debug/dri/1/pstate
07: core 270 MHz memory 405 MHz
0f: core 625 MHz memory 900 MHz
DC: core 270 MHz memory 324 MHz

But when I tried to reclock, I have an error :
echo 0f > /sys/kernel/debug/dri/1/pstate
-bash: echo: write error: Function not implemented

And I have this in dmesg:
[  351.283183] nouveau 0000:01:00.0: bus: MMIO write of ffff8c1f FAULT at
6013d4 [ IBUS ]
[  458.362570] nouveau 0000:01:00.0: bus: MMIO write of 0000001f FAULT at
6013d4 [ IBUS ]

Thanks

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

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

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

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

             reply	other threads:[~2019-07-14 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14 15:20 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-111128-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-07-14 17:55   ` [Bug 111128] Impossible to change pstate on GT610M bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-14 19:34   ` 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-111128-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 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.