From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 78543] New: NV28M running at 1/8th GPU clock when using nouveau
Date: Sat, 10 May 2014 20:28:46 +0000 [thread overview]
Message-ID: <bug-78543-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4539 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=78543
Priority: medium
Bug ID: 78543
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: NV28M running at 1/8th GPU clock when using nouveau
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: nv28m-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org
Hardware: x86 (IA32)
Status: NEW
Version: 7.7 (2011)
Component: Driver/nouveau
Product: xorg
See https://bugs.freedesktop.org/show_bug.cgi?id=54700 some details. I've
opened this as the speed problem has nothing to do with the distortion, but
I've noticed it when debugging that problem. I've e-mailed two dumps for that
thread for this machine.
In short nouveau is slow normally, unless I insert the nvidia module in one
kernel and kexec into another kernel. Then nouveau is fast until I suspend to
RAM. After resume it's slow again. And I can't fix it ;)
Long version:
I've played a bit with nvclock and found something interesting. When using the
nvidia driver in X I get:
================================
-- General info --
Card: nVidia Geforce 4 4000 GO
Architecture: NV28 A2
PCI id: 0x286
NVPLL_COEFF=00010d01
m=1 n=13 p=1
GPU clock: 175.500 MHz
Bustype: AGP
-- Memory info --
Amount: 32 MB
Type: 128 bit DDR
MPLL_COEFF=00001d02
m=2 n=29 p=0
Clock: 391.500 MHz
-- AGP info --
Status: Enabled
Rate: 4X
AGP rates: 1X 2X 4X
Fast Writes: Disabled
SBA: Disabled
-- VideoBios information --
Version: 04.28.20.31
Signon message: NV28 P138 Mobile Reference VGA BIOS
================================
When I switch to console, then it's:
================================
-- General info --
Card: nVidia Geforce 4 4000 GO
Architecture: NV28 A2
PCI id: 0x286
NVPLL_COEFF=00040d01
m=1 n=13 p=4
GPU clock: 21.937 MHz
Bustype: AGP
================================
When I do the same using nouveau in X (after nvidia kexec):
================================
-- General info --
Card: nVidia Geforce 4 4000 GO
Architecture: NV28 A2
PCI id: 0x286
NVPLL_COEFF=00040d01
m=1 n=13 p=4
GPU clock: 21.937 MHz
Bustype: AGP
-- Memory info --
Amount: 32 MB
Type: 128 bit DDR
MPLL_COEFF=00000f01
m=1 n=15 p=0
Clock: 405.000 MHz
-- AGP info --
Status: Enabled
Rate: 4X
AGP rates: 1X 2X 4X
Fast Writes: Enabled
SBA: Enabled
-- VideoBios information --
Version: 04.28.20.31
Signon message: NV28 P138 Mobile Reference VGA BIOS
================================
Nouveau on console (after nvidia kexec):
================================
-- General info --
Card: nVidia Geforce 4 4000 GO
Architecture: NV28 A2
PCI id: 0x286
NVPLL_COEFF=00010d01
m=1 n=13 p=1
GPU clock: 175.500 MHz
Bustype: AGP
================================
And what is interesting if I do a "nvclock -i -d | cat" on console then it's:
================================
-- General info --
Card: nVidia Geforce 4 4000 GO
Architecture: NV28 A2
PCI id: 0x286
NVPLL_COEFF=00040d01
m=1 n=13 p=4
GPU clock: 21.937 MHz
Bustype: AGP
================================
There's no difference with nvidia between redirecting to file or not.
The POST values are 175 MHz GPU and 405 MHz RAM (same as nouveau console). I've
checked the nvidia dump I've made, it's set up to 100 MHz GPU and 199 MHz RAM,
but for some reason that's not the speed it's actually reported later (see
above, 175/391).
When I do a suspend to RAM then I get 22 MHz GPU consistently on console and X
with nouveau, independent of redirecting or not. I guess that the 22 MHz in X
after nvidia kexec is probably false and it's more like 175 MHz as on console
without redirection.
If I directly poke the PLL and read it back then it's not the same. It's always
1/8 of what was requested (actually +3). When I change it on nvidia it's the
same as what I write there. Also after nvidia kexec, on the nouveau console
it's matching. But not after a suspend to RAM or otherwise. The same 1/8 is
there in X when nouveau is running fast after kexec.
Any ideas what is causing this 1/8 speed limit sometimes? Or why it's different
if I redirect/not with nouveau?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6012 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-05-10 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 20:28 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-78543-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-05-10 20:32 ` [Bug 78543] NV28M running at 1/8th GPU clock when using nouveau bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-10 23:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-26 22:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:45 ` 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-78543-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.