search for: fan_min

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 free.fr> --- drm/nouveau/nvkm/subdev/bios/fan....

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. >> >> Reported-by: Tom Englund <tomenglund26 at gmail.com> >> Tested-by: Tom Englund <tomenglund26 at gmail.com> > > Tested-by: Daemon32 <ln...

...r> 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. >>>> >>>> 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 <tomenglund2...

...ow Nouveau determines what fan speed to (attempt >> to) program. Oh, thanks for giving me an idea about what the other values in this table may be about :D Anyways, the current code uses the entry id 0x46 of the thermal table (bit P, offset 0x10) to find out what are the thermal points for $fan_min and $fan_max. The $fan_min and $fan_max values are found in the entry id 0x22 of the same table. If the 0x46 entry is not present in the thermal table (which seems to be the norm for Fermi), we revert to default values: 40 -> 85°C. With these 4 values, we get 2 trip points (temp_min, fan_min)...

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

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 <tomenglund26 at gmail.com> Tested-by: Daemon32 <lnf.purple at gmail.com> Bugzilla: https:/...

...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. >>> >>> 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> >>...

...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. >>>>> >>>>> Reported-by: Tom Englund <tomenglund26 at gmail.com> >>>>> Tested-by:...