search for: fanning

This is an oversight that made use of the trip-point-based fan managenent on cards that never expose those. This led the fan to stay at fan_min. Fortunately, the emergency code would kick when the temperature would reach 90°C. Reported-by: Tom Englund <tomenglund26 at gmail.com> Tested-by: Tom Englund <tomenglund26 at gmail.com> Signed-off-by: Martin Peres <martin.peres at

On 17/12/15 19:18, Martin Peres wrote: > > > On 29/11/15 16:10, Martin Peres wrote: >> This is an oversight that made use of the trip-point-based fan >> managenent on >> cards that never expose those. This led the fan to stay at fan_min. >> >> Fortunately, the emergency code would kick when the temperature would >> reach >> 90°C. >>

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:

Let me preface by saying i''m a total noob at ruby/rails. :-) For some reason, I am just not grasping the concept of has_one & belongs_to... I''m working on a project that includes user authentication, and 3 different types of user profiles. User profiles are either "fan", "band", or "venue" objects, and user logins are "user"

On 04/01/16 18:42, Emil Velikov wrote: > On 4 January 2016 at 14:56, Martin Peres <martin.peres at free.fr> wrote: >> On 17/12/15 19:18, Martin Peres wrote: >>> On 29/11/15 16:10, Martin Peres wrote: >>>> This is an oversight that made use of the trip-point-based fan managenent >>>> on >>>> cards that never expose those. This led the fan

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. Reported-by: Marcin Slusarz <marcin.slusarz at gmail.com>

I just replaced my fan in my nc2400. It was a 5hour job. Had to pull EVERYTHING to get to where they have the fan in the thing. Now I want to know if it is working. It is suppose to be thermostatically controlled, and it takes time to heat up. So how can I find out what Centos knows about the system temp and fan state? It was hard to tell if I put the connector in the right way. At least

From: Martin Peres <martin.peres at labri.fr> Re-use the therm-exported fan structure with only two minor modifications: - pwm_freq: u16 -> u32; - add fan_type (toggle or PWM) Signed-off-by: Martin Peres <martin.peres at free.fr> --- drm/Kbuild | 1 + drm/core/include/subdev/bios/fan.h | 1 + drm/core/subdev/bios/fan.c | 1 +

I am new to Using R for data analysis. I have an incomplete time series dataset that is in daily format. I want to extract only Friday data from it. However, there are two problems with it. First, if Friday data is missing in that week, I need to extract the data of the day prior to that Friday (e.g. Thursday). Second, sometimes there are duplicate Friday data (say Friday morning and

On 29/11/15 16:10, Martin Peres wrote: > This is an oversight that made use of the trip-point-based fan managenent on > cards that never expose those. This led the fan to stay at fan_min. > > Fortunately, the emergency code would kick when the temperature would reach > 90°C. > > Reported-by: Tom Englund <tomenglund26 at gmail.com> > Tested-by: Tom Englund

On 4 January 2016 at 14:56, Martin Peres <martin.peres at free.fr> wrote: > On 17/12/15 19:18, Martin Peres wrote: >> On 29/11/15 16:10, Martin Peres wrote: >>> >>> This is an oversight that made use of the trip-point-based fan managenent >>> on >>> cards that never expose those. This led the fan to stay at fan_min. >>> >>>

On 01/05/2016 06:35 PM, Martin Peres wrote: > On 04/01/16 18:42, Emil Velikov wrote: >> On 4 January 2016 at 14:56, Martin Peres <martin.peres at free.fr> wrote: >>> On 17/12/15 19:18, Martin Peres wrote: >>>> On 29/11/15 16:10, Martin Peres wrote: >>>>> This is an oversight that made use of the trip-point-based fan >>>>> managenent

https://bugs.freedesktop.org/show_bug.cgi?id=107447 Bug ID: 107447 Summary: regression in thermal management of Quadro FX 1500 Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

(I sent this yesterday but it never made it through) I've got a remote system where I think I need to replace the CPU fan. in the output of dmidecode, I get... Processor Information Socket Designation: CPU 1 Type: Central Processor Family: <OUT OF SPEC> Manufacturer: Intel ID: 47 0F 00 00 FF FB EB BF

Hello folks, I'm having a difficult time trying to figure out why the CPU cooling fans run at full speed on my Supermicro X8DAL-3 motherboard. There doesn't seem to be any variable speed (the fans are PWM compatible) ... they either idle at almost nothing, or suddenly burst into a high-pitched scream that gets my ears bleeding after a few seconds. Once they jump to warp-10, they

I've got a remote system where I think I need to replace the CPU fan. in the output of dmidecode, I get... Processor Information Socket Designation: CPU 1 Type: Central Processor Family: <OUT OF SPEC> Manufacturer: Intel ID: 47 0F 00 00 FF FB EB BF Version: Intel(R) Pentium(R) D CPU 2.66GHz

This seems to be absolutely necessary for a lot of NV40. Reported-by: gsgf on IRC/freenode Signed-off-by: Martin Peres <martin.peres at free.fr> --- drm/nouveau/nvkm/subdev/therm/base.c | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/drm/nouveau/nvkm/subdev/therm/base.c b/drm/nouveau/nvkm/subdev/therm/base.c index 8894fee..df949fa 100644 ---

Has anyone come across a device that could cancel out the noise from servers, ie. the fan noise? I have a server rack near my office and would like to see if i can decrease the noise level. It would seem to me that the steady drone of the fans could be cancelled out to a large extent.

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

https://bugs.freedesktop.org/show_bug.cgi?id=66177 Priority: medium Bug ID: 66177 Assignee: nouveau at lists.freedesktop.org Summary: pwm1 value not restored during hibernate/restore cycle in the event of manual fan management mode QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified