similar to: [Bug 58428] New: X crashes when running opengl application after reclocking nouveau driver to use highest speed

https://bugs.freedesktop.org/show_bug.cgi?id=60175 Priority: medium Bug ID: 60175 Assignee: nouveau at lists.freedesktop.org Summary: Repeatable kernel panics when visiting websites with adobe flash enabled QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All

http://bugs.freedesktop.org/show_bug.cgi?id=24780 Summary: 2 second delay during boot using nouveau Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

Hi . For some time now i have had problems with video on this system . from dmesg iget the following 6.408406] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x0a5000a2 [ 6.408411] nouveau [ DEVICE][0000:01:00.0] Chipset: GT216 (NVA5) [ 6.408414] nouveau [ DEVICE][0000:01:00.0] Family : NV50 [ 6.409206] nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image... [ 6.513939]

https://bugs.freedesktop.org/show_bug.cgi?id=73473 Priority: medium Bug ID: 73473 Assignee: nouveau at lists.freedesktop.org Summary: Potential crash bug in src/gallium/auxiliary/rtasm/rtasm_execmem.c Severity: critical Classification: Unclassified OS: Linux (All) Reporter: jaak at ristioja.ee

https://bugs.freedesktop.org/show_bug.cgi?id=35475 Summary: asus laptop boots to blank screen 2 out of 3 times Product: xorg Version: 7.6 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: high Component: Driver/nouveau AssignedTo: nouveau at

> Samuel Pitoiset <samuel.pitoiset at gmail.com> hat am 13. Januar 2016 um 13:43 > geschrieben: > > Hi! > > Did you check on different Fermi chipsets or only with one variant? currently I only checked that on my nvc1, but I thought I could just send the patches and it is easier for others to try it out this way. > > Are you sure that engine reclocking works as

https://bugs.freedesktop.org/show_bug.cgi?id=104784 Bug ID: 104784 Summary: Unable to do reclocking manually Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

On Fri, May 16, 2014 at 11:17 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > On 17 May 2014 02:43, "Ilia Mirkin" <imirkin at alum.mit.edu> wrote: >> >> Adds a NvReclock boolean option to allow the user to enable (or disable) >> reclocking. All chipsets default to off, except NVAA/NVAC, which are >> reportedly complete. > Hey Ilia, > > I

https://bugs.freedesktop.org/show_bug.cgi?id=89273 Bug ID: 89273 Summary: [NVA8] nouveau screen corruption and X lockup when reclocking Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

Although memory reclocking seems to be completely broken on my GF119, we can at least allow users to enable reclocking for the core clock. Signed-off-by: Samuel Pitoiset <samuel.pitoiset at gmail.com> --- drm/nouveau/nvkm/subdev/fb/ramgf100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/subdev/fb/ramgf100.c b/drm/nouveau/nvkm/subdev/fb/ramgf100.c

On Fri, May 16, 2014 at 11:54 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > On 17 May 2014 13:39, "Ilia Mirkin" <imirkin at alum.mit.edu> wrote: >> >> On Fri, May 16, 2014 at 11:17 PM, Ben Skeggs <skeggsb at gmail.com> wrote: >> > On 17 May 2014 02:43, "Ilia Mirkin" <imirkin at alum.mit.edu> wrote: >> >> >>

This should probably be folded into the previous patch to avoid breaking bisectability on nve0 On Thu, Sep 4, 2014 at 10:58 AM, Roy Spliet <rspliet at eclipso.eu> wrote: > This used to be done implicitly > > Signed-off-by: Roy Spliet <rspliet at eclipso.eu> > --- > drivers/gpu/drm/nouveau/core/subdev/fb/ramnve0.c | 5 +++++ > 1 file changed, 5 insertions(+) >

some chipset have working engine reclocking, but broken memory reclocking like Fermi. We should for now, add the functionality to allow partly reclocking for those. Allthough this doesn't give as much performance as one might wish, it is till noticeable and may improve performance enough to be noted. Karol Herbst (2): clk: seperate engine and memory reclock toggles clk: allow engine

https://bugs.freedesktop.org/show_bug.cgi?id=88890 Bug ID: 88890 Summary: Reclocking of core speed fails on non-reference ASUS GeForce GTX650 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

Adds a NvReclock boolean option to allow the user to enable (or disable) reclocking. All chipsets default to off, except NVAA/NVAC, which are reportedly complete. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Ben, I know you've been saying that reclocking is in a pretty bad state, but I do think that there are going to be groups of people for whom the current code can work

First patch fixes a potential vbios parsing bug on Fermi GPUs, but it may also affect Kepler ones. Second patch wakes the GPU up whenever the user tries to reclock to prevent the write to the pstate file from freezing. Karol Herbst (2): bios/vpstate: There are some fermi vbios with no boost or tdp entry debugfs: Wake up GPU before doing any reclocking drm/nouveau/nouveau_debugfs.c

On 17/11/17 02:04, Karol Herbst wrote: > Fixes various reclocking related issues on prime systems. Is that the only place that was not covered? Could you check if other places would need this code too? In any case, this patch is (assuming you are calling the right functions to prevent the GPU from sleeping): Signed-off-by: Martin Peres <martin.peres at free.fr> > > Signed-off-by:

What is the meaning of messages of this form in dmesg: [158362.148203] [drm] nouveau 0000:06:00.0: PMFB0_SUBP0: 0x037f0040 [158362.148208] [drm] nouveau 0000:06:00.0: PMFB0_SUBP1: 0x037f0000 They seem to always appear in pairs. Out of 1702 lines in dmesg, 286 of them are of the above form. I don't recall having ever seen them with Mageia 1, kernel 2.6.38.8-server-10.mga. However, there

On 07/10/2014 06:43 PM, Peter De Schrijver wrote: > On Thu, Jul 10, 2014 at 09:34:34AM +0200, Alexandre Courbot wrote: >> This series adds support for reclocking on GK20A. The first two patches touch >> the clock subsystem to allow GK20A to operate, by making the presence of the >> thermal and voltage devices optional, and allowing pstates to be provided >> directly

Reclocking of NVAA/NVAC is substantially different from NV50+, enough to justify a separate clock implementation. This code is a forward-port of reclocking code that has been sitting in a branch for a while, and has been tested on my NVAC. Traces show no significant reasons why this shouldn't work on NVAA, but testers are always welcome. And since these are IGPs without dedicated RAM to