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 107016] Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02)
Date: Mon, 25 Jun 2018 14:25:33 +0000	[thread overview]
Message-ID: <bug-107016-8800-KQQ5WaWx4F@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107016-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #13 from Roy <nouveau-NQbd8FSOZ1kdnm+yROfE0A@public.gmane.org> ---
(In reply to atirage21 from comment #12)
> Created attachment 140326 [details]
> attachment-20771-0.html
> 
> But also is question: Why i had only 405 Mhz of core under kernel 4.x,
> if under kernel 3.19 was more options to see (and same more options is
> with propretiary driver):
> 
> [    4.311074] nouveau  [     CLK][0000:01:00.0] 07: core 270-405 MHz
> memory 810 MHz
> [    4.311090] nouveau  [     CLK][0000:01:00.0] 0f: core 270-745 MHz
> memory 1800 MHz
> [    4.311233] nouveau  [     CLK][0000:01:00.0] --: core 405 MHz memory 648
> MHz
> 

That's just reduced verbosity of the driver in newer kernels. There's no need
to report that during boot, just clutters the log. You'll find all those
entries in /sys/kernel/debug/dri/<number>/pstate.

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

[-- Attachment #1.2: Type: text/html, Size: 2143 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-06-25 14:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-24 19:18 [Bug 107016] New: Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-107016-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-06-24 19:18   ` [Bug 107016] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 21:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 21:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 21:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 21:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25  3:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25  3:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 10:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 12:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 12:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 14:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 14:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-06-25 14:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 15:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 16:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 16:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 17:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 17:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-01  8:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-09-06  8:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-04 18:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-04 18:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-10 13:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-16  8:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:43   ` 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-107016-8800-KQQ5WaWx4F@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.