similar to: Request for nv40-c0 testing thermal/fan management

Changes: - Change the maintainer's address (the labri address will expire soon); - Drop the note about not all families supporting all fan modes; - Add a note about the reported RPM not being accurate when driven outside the vbios-defined PWM range. Signed-off-by: Martin Peres <martin.peres at free.fr> --- Documentation/thermal/nouveau_thermal | 7 ++++--- 1 file changed, 4

From: Martin Peres <martin.peres at labri.fr> This should enable automatic fan management for all cards by default, at boot time. However, this commit actually affects only nv40-c0 as nvc0+ cards already have vbios's PDAEMON fw already taking care of fan management. Signed-off-by: Martin Peres <martin.peres at labri.fr> --- drivers/gpu/drm/nouveau/core/subdev/therm/base.c | 2 +-

From: Martin Peres <martin.peres at labri.fr> This is safe because ptherm hasn't been configured yet and will be a little further down the initialization path. Ptherm should be safe regarding to runtime reconfiguration. v2: - do not limit this patch to nv84-a3 and make it nv84+ v3: - move the ack to fini() - disable IRQs on fini() - silently ignore un-requested IRQs

On 11/12/2017 06:29 PM, Martin Peres wrote: > Hello, > > Some users have been complaining for years about their GPU sounding like > a jet engine at take off. Last year, I finally laid my hand on one of > these GPUs and have been trying to fix this issue on and off since then. Some early feedback: can you tell us the exact SKUs you have? And are these production boards with

https://bugs.freedesktop.org/show_bug.cgi?id=83587 Priority: medium Bug ID: 83587 Assignee: nouveau at lists.freedesktop.org Summary: 3.14.18: FAN control: none / external -- 3.16.2: FAN control: PWM QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

This adds basic support for driving sensor chips off the nvidia i2c buses, along with basic support for reading the internal GPU sensor on supported chipsets. It's heavily cribbed off nvclock. Having scanned a large number of bioses, I'm pretty convinced that the appropriate i2c bus is always number 2 in the list on <g80 - I'm not sure about later cards yet. There's still a lot

https://bugs.freedesktop.org/show_bug.cgi?id=78106 Priority: medium Bug ID: 78106 Assignee: nouveau at lists.freedesktop.org Summary: Reported fan rpm is twice the actual value (NVC0) QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mdop at

From: Martin Peres <martin.peres at labri.fr> Signed-off-by: Martin Peres <martin.peres at free.fr> --- drm/Kbuild | 1 + drm/core/subdev/therm/gm107.c | 1 + nvkm/engine/device/gm100.c | 4 +- nvkm/include/subdev/therm.h | 1 + nvkm/subdev/therm/Makefile.am | 3 +- nvkm/subdev/therm/fan.c | 9 ++++- nvkm/subdev/therm/gm107.c | 93

+ the same for shutdown threshold - seems impossible, but shutdown can fail. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/core/subdev/therm/temp.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/nouveau/core/subdev/therm/temp.c b/drivers/gpu/drm/nouveau/core/subdev/therm/temp.c index bf9b3ce..8f27b44

Hello, Some users have been complaining for years about their GPU sounding like a jet engine at take off. Last year, I finally laid my hand on one of these GPUs and have been trying to fix this issue on and off since then. After failing to find anything in the HW, I figured out that the duty cycle set by nvidia's proprietary driver would be way under the expected value. By randomly changing

From: Martin Peres <martin.peres at labri.fr> This should fix a deadlock that has been reported to us where fan_update() would hold the fan lock and try to grab the alarm_program_lock to reschedule an update. On an other CPU, the alarm_program_lock would have been taken before calling fan_update(), leading to a deadlock. We should Cc: <stable at vger.kernel.org> # 3.9+ Reported-by:

http://bugs.freedesktop.org/show_bug.cgi?id=16675 Summary: Request for working fan speed adjustment on NV40 Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Dear Samba list, I have an issue with what seems to be group permissions, when using a stand-alone Samba file server. I have a directory where files are meant to be writable to a group of users. The permissions on Linux are: root# ls -ld /users/misc/teaching /users/misc/teaching/* drwxrws--- 2 teaching csos 4096 May 15 08:47 /users/misc/teaching -rw-rw---- 1 teaching csos 17 May 15

Since commit 5e120f6e4b3f35b741c5445dfc755f50128c3c44 "drm/nouveau/fence: convert to exec engine, and improve channel sync" nouveau fence sync implementation for nv17-50 and nvc0+ started to rely on state of fence buffer left by previous sync operation. But as pinned bo's (where fence state is stored) are not saved+restored across suspend/resume, we need to do it manually. nvc0+ was

Current uninitialized sensor detection does not work for me on nv4b and sensor returns crazy values (>190?C). It stabilises later, but it's too late - therm code shutdowns the machine... Let's just reset it on init. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/core/subdev/therm/nv40.c | 12 +++++++++++- 1 file changed, 11

On 11/06/2014 13:59, Roy Spliet wrote: > Dear Mr. Dew, > > I hereby wish to propose the X.org EVoC project "REclock - > Reverse-engineer and implement NVA3/5/8 Voltage- and Frequency Scaling > in Nouveau" for which I am willing to participate, and apply for the > associated funding. Full details below or on > http://nouveau.spliet.org/evoc.html . For any further

Hi Martin, I was asked to clarify a few things: (1) Are all the user reports of loud fans on Fermi-era GPUs? (2) When the VBIOS POSTs the card, it loads initial ucode onto the Falcon processor (PMU), which will do basic fan management on its own. We call this init ucode "IFR" (Init From ROM). nvidia.ko will restore the IFR ucode when unloaded. I assume the loud fan symptom occurs

From: Martin Peres <martin.peres at labri.fr> I spent some time this weekend trying to find in the vbios the number of pulses per revolutions in the vbios but couldn't find it. It would seem all my cards have 2 pulses per revolution so let's stick to that until further notice. Thermal table's id 0x48 may indicate this information but it would seem that changing the value

https://bugs.freedesktop.org/show_bug.cgi?id=57988 Priority: medium Bug ID: 57988 Assignee: nouveau at lists.freedesktop.org Summary: [regression][bisected][NV4E] LVDS output has offset to the right, part falling of is painted on the left QA Contact: xorg-team at lists.x.org Severity: normal Classification:

On 15/08/16 11:53, Pierre Moreau wrote: > Hello everyone, > > Same place as FOSDEM? XDC is in Helsinki and FOSDEM was in Brussels… (IIRC, > FOSDEM is always located in Brussels.) I would prefer picking an hotel in > Helsinki rather than traveling every day between Helsinki and Brussels. :-p Or > was that what you meant by "more or less"? :-D > > I’ve taken days