https://bugs.freedesktop.org/show_bug.cgi?id=95031
--- Comment #5 from Lucas Ribeiro ---
Created attachment 123105
--> https://bugs.freedesktop.org/attachment.cgi?id=123105=edit
vbios
Yea, finally managed to hang the system at 07 pstate with 1.09V (+0.1V), with a
corrupted
https://bugs.freedesktop.org/show_bug.cgi?id=95031
--- Comment #4 from Lucas Ribeiro ---
OK, some interesting findings.
07 pstate on Linux has:
core 324 MHz memory 648 MHz AC DC
GPU core: +0.99 V
Increasing GPU core voltage to 1.09V has wielded a stable system so far.
On 21/04/16 00:46, karol herbst wrote:
2016-04-20 20:53 GMT+00:00 Martin Peres :
On 18/04/16 22:14, Karol Herbst wrote:
we will access the current set cstate at least every second and this safes
us
saves
some CPU cycles looking them up every second.
Signed-off-by:
On 18/04/16 22:14, Karol Herbst wrote:
This option can be used to adjust the calculated voltage or the cstate voltage
calculation
Signed-off-by: Karol Herbst
---
bin/nv_cmp_volt.c | 2 +-
drm/nouveau/include/nvkm/subdev/volt.h | 4 +++-
On 18/04/16 22:14, Karol Herbst wrote:
this gk104 volt implementation has to be reworked a little, because the speedo
readout in maxwell doesn't need those strange 0 and 41 writes into 0x122634,
but it needs this PWM thing.
Maybe Maxwell is PWM only and we could just simplify it there, but
On 18/04/16 22:14, Karol Herbst wrote:
Signed-off-by: Karol Herbst
Reviewed-by: Martin Peres
---
drm/nouveau/nvkm/subdev/clk/base.c | 19 +++
drm/nouveau/nvkm/subdev/clk/gf100.c | 4 ++--
drm/nouveau/nvkm/subdev/clk/nv40.c
On 18/04/16 22:14, Karol Herbst wrote:
Signed-off-by: Karol Herbst
---
drm/nouveau/nvkm/subdev/mc/base.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drm/nouveau/nvkm/subdev/mc/base.c
b/drm/nouveau/nvkm/subdev/mc/base.c
index
On 18/04/16 22:14, Karol Herbst wrote:
depending on the temperature, cstates might become unreachable or the maped
voltage of a cstate changes. We want to adjust to that.
Yeah! That was a lot of plumbing to get to this, but it is here!
Reviewed-by: Martin Peres
On 18/04/16 22:14, Karol Herbst wrote:
we don't want to reclock to the same pstate or cstate over and over again, so
only do things we actually have to do.
v4: move into gf100
Reviewed-by: Martin Peres
Signed-off-by: Karol Herbst
---
On 18/04/16 22:14, Karol Herbst wrote:
this code will change for gf100 and newer
Reviewed-by: Martin Peres
Signed-off-by: Karol Herbst
---
drm/nouveau/nvkm/subdev/clk/base.c | 14 ++
drm/nouveau/nvkm/subdev/clk/g84.c | 1 +
sepArate
On 18/04/16 22:14, Karol Herbst wrote:
Would be nice to say what for.
With a better commit message and the typo fixed:
Reviewed-by: Martin Peres
Signed-off-by: Karol Herbst
---
drm/nouveau/nvkm/subdev/clk/base.c | 16
On 18/04/16 22:14, Karol Herbst wrote:
this makes the code easier, because we can compare the id with pstate->pstate
and safe us the trouble iterating over the entire pstate list
save us.
Not the easiest patch to read, but it seems alright and it has been
tested, so:
Reviewed-by: Martin
2016-04-20 20:53 GMT+00:00 Martin Peres :
> On 18/04/16 22:14, Karol Herbst wrote:
>>
>> we will access the current set cstate at least every second and this safes
>> us
>
> saves
>>
>> some CPU cycles looking them up every second.
>>
>> Signed-off-by: Karol Herbst
https://bugs.freedesktop.org/show_bug.cgi?id=95044
--- Comment #1 from Ilia Mirkin ---
Please attach your vbios (/sys/kernel/debug/dri/0/vbios.rom)
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=95044
Bug ID: 95044
Summary: [NVA0] [Reclocking] GPU doesn't relax memory clocks
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On 18/04/16 22:14, Karol Herbst wrote:
Signed-off-by: Karol Herbst
---
drm/nouveau/include/nvkm/subdev/clk.h | 5 +
drm/nouveau/nvkm/subdev/clk/base.c| 32 +---
2 files changed, 30 insertions(+), 7 deletions(-)
diff --git
On 18/04/16 22:14, Karol Herbst wrote:
we will access the current set cstate at least every second and this safes us
saves
some CPU cycles looking them up every second.
Signed-off-by: Karol Herbst
---
drm/nouveau/include/nvkm/subdev/clk.h | 2 +-
https://bugs.freedesktop.org/show_bug.cgi?id=95031
--- Comment #2 from Lucas Ribeiro ---
Different kernel log with some nouveau info.
So far tried pstate 07 with boost 0, 1 and 2.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=95031
--- Comment #3 from Lucas Ribeiro ---
Created attachment 123098
--> https://bugs.freedesktop.org/attachment.cgi?id=123098=edit
another log with different info
--
You are receiving this mail because:
You are the assignee
On 18/04/16 22:14, Karol Herbst wrote:
we will need a always running therm daemon to adjust the voltage/clocks on the
fly.
Signed-off-by: Karol Herbst
Reviewed-by: Martin Peres
---
drm/nouveau/nvkm/subdev/therm/base.c | 9 ++---
1 file
On 20/04/16 23:45, Martin Peres wrote:
On 18/04/16 22:13, Karol Herbst wrote:
we won't need them, because we will adjust the clocks depending on engine loads
later on anyway. It also simplifies the clocking logic.
You can also say that the code was just mocked up anyway.
Forgot to give my
On 18/04/16 22:13, Karol Herbst wrote:
we won't need them, because we will adjust the clocks depending on engine loads
later on anyway. It also simplifies the clocking logic.
You can also say that the code was just mocked up anyway.
Signed-off-by: Karol Herbst
---
On 18/04/16 22:13, Karol Herbst wrote:
this function will be used to update the current clock state.
This will happen for various reasons:
* temperature changes (may change cstate and/or voltage)
* user changes boost mode
* load changes
v2: add wait parameter
Signed-off-by: Karol Herbst
https://bugs.freedesktop.org/show_bug.cgi?id=94990
--- Comment #15 from mirkorol...@googlemail.com ---
Created attachment 123096
--> https://bugs.freedesktop.org/attachment.cgi?id=123096=edit
sys.log after booting with nvidia gtx970 only
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=59069
Matt Whitlock changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=95031
Lucas Ribeiro changed:
What|Removed |Added
Summary|[NVE4] Random GPU lockups |[NVE4] 660 Ti Random
Hi,
On 15-04-16 00:29, Samuel Pitoiset wrote:
On 04/12/2016 12:04 PM, Hans de Goede wrote:
Hi,
On 08-04-16 18:14, Samuel Pitoiset wrote:
On 04/08/2016 12:17 PM, Hans de Goede wrote:
Hi,
On 23-03-16 23:10, Samuel Pitoiset wrote:
Are you sure this won't break compute shaders on fermi?
https://bugs.freedesktop.org/show_bug.cgi?id=94990
--- Comment #14 from mirkorol...@googlemail.com ---
I removed the /lib/firmware directory, still black screen.
--
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=94990
--- Comment #13 from mirkorol...@googlemail.com ---
Yes, iam booting with intel-gpu and nvidia-gtx970 card activated. There is a
picture on the intel screen. If i disable the intel gpu in the bios, there is
no output on the nvidia screen.
I try
https://bugs.freedesktop.org/show_bug.cgi?id=94948
--- Comment #4 from Carsten Pfeiffer ---
Thank you for your hints, Ilia. This made try one more thing I hadn't checked
before: use one output on the dock and another directly on the notebook. And
this does work, so I get eDP-1,
https://bugs.freedesktop.org/show_bug.cgi?id=69882
--- Comment #22 from Lucas Ribeiro ---
Forget what I just said, the hangs still happen. Opened a new bug #95031
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=95031
--- Comment #1 from Lucas Ribeiro ---
Forgot to add: did not try earlier kernels, so this behaviour might exist since
the card was supported. On Windows it works well.
It hangs on normal browsing or opening a video on VLC.
https://bugs.freedesktop.org/show_bug.cgi?id=95031
Bug ID: 95031
Summary: [NVE4] Random GPU lockups
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
33 matches
Mail list logo