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 95044] [NVA0] [Reclocking] GPU doesn't relax memory clocks
Date: Thu, 21 Apr 2016 23:12:49 +0000	[thread overview]
Message-ID: <bug-95044-8800-cyO9TC1FFA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95044-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #4 from debianlinuxero1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ---
Hello.

This is what I nvapeek'ed :

001002c0: 00000652

001002c4: 001002c8

001002e0: 0020001b



I tried to do the mmiotrace procediment as explained here :
https://wiki.ubuntu.com/X/MMIOTracing

The command choosen was "xinit nvidia-settings", with the intention to force
clocks with the "Prefer Maximum Performance" option, then relaxing with
"Adaptive Mode".

But all what I got was 40 minutes of black screen.
The system didn't shutdown neither with magic sysrq.

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

[-- Attachment #1.2: Type: text/html, Size: 1489 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-04-21 23:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 21:41 [Bug 95044] New: [NVA0] [Reclocking] GPU doesn't relax memory clocks bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-95044-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-04-20 21:43   ` [Bug 95044] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 11:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 13:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 23:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-04-22 20:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-22 20:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-08 21:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-09 18:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-16 16:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-16 16:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:12   ` 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-95044-8800-cyO9TC1FFA@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.