similar to: [Bug 110997] New: NV50 fan runs at full speed after resume from suspend on kernels 5.1.8, 4.19.49

https://bugs.freedesktop.org/show_bug.cgi?id=60704 Priority: medium Bug ID: 60704 Assignee: nouveau at lists.freedesktop.org Summary: [nouveau, git regression] - I2C PWM fan control broken on nv50 adt7475 on kernels 3.3.x+ QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified

Hi Mar, Could you file a bug (bugs.freedesktop.org under xorg -> Driver/nouveau) with a summary of this info (i.e. a problem statement, that reverting the commit in question fixes it, the lspci output) and additionally, your VBIOS. You can obtain this with nouveau loaded by doing cp /sys/kernel/debug/dri/0/vbios.rom /tmp This will help centralize all the info. Thanks, -ilia On Sun, Jun

https://bugs.freedesktop.org/show_bug.cgi?id=67597 Priority: medium Bug ID: 67597 Assignee: nouveau at lists.freedesktop.org Summary: nouveau E Xorg failed to idle channel on NVA0 QA Contact: xorg-team at lists.x.org Severity: critical Classification: Unclassified OS: Linux (All) Reporter: m.meledandri at

Thanks for finding this Emil! The change you point out also landed on 4.19.49 and I am able to reproduce the fan speed issue with that kernel as well, whereas previous 4.19.x series kernels were fine. I'll attempt to build both the latest 4.19.x and 5.1.x stable kernels with that patch reverted and see if it's the sole culprit. On Friday, June 21, 2019, 1:32:19 PM EDT, Emil Velikov

Mar - can you provide the output of lspci -nn -d 10de: On Sat, Jun 22, 2019 at 2:17 PM Lyude Paul <lyude at redhat.com> wrote: > Hi, is this actually an nv50 GPU, or some other model? I can try to take a > closer look at this > > On Sun, 2019-06-16 at 10:28 -0400, Ilia Mirkin wrote: > > I don't really see anything between v5.0..v5.1 which would account for > this.

I don't really see anything between v5.0..v5.1 which would account for this. Could have been a subtle change to the i2c logic somewhere. The fastest way to identify the problem would be to do a bisect on the kernel to identify the commit that caused this. There are many guides for this online. On Sat, Jun 15, 2019 at 12:17 PM Mar Mel <marmel6942 at yahoo.com> wrote: > Unfortunately,

It turns out that while disabling i2c bus access from software when the GPU is suspended was a step in the right direction with: commit 342406e4fbba ("drm/nouveau/i2c: Disable i2c bus access after ->fini()") We also ended up accidentally breaking the vbios init scripts on some older Tesla GPUs, as apparently said scripts can actually use the i2c bus. Since these scripts are executed

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

On 29/09/16 03:41, Martin Peres wrote: > 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> I of course forgot to tag this patch for stable. The thing has been broken on some nv40 ... forever? > --- > drm/nouveau/nvkm/subdev/therm/base.c | 22 +++++++++++++++++++--- >

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>

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

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)

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

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

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

There (yet) another discussion going on on the O''Reilly web logs about J E5, complexity and the competitors (i.e. Rails et al). See http://www.oreillynet.com/windows/blog/2006/07/the_beginning_of_the_end_for_j.html. Seems this was spawned by my own article available at: http://www.soaranch.com/articles/2006/7/11/soa-and-rails-part-1.html. My response to this discussion is at:

I''m a ruby nuby trying to get through my first Facebooker application. I have two issues I need support with. First is that another user of the application was accessing it find and now all of a sudden he gets: Facebooker::Session::SessionExpired (Session key invalid or no longer valid): How do we go about solving that? Second is that facebook has an api call for pages.isFan

Hi, I noticed that the fan of my centrino is very often running since I use Xen (the load is very low still). Also the cpufreq is always at 600MHz (the max is 1500MHz), regardless of what of what heavy computations I do (e.g. calculating md5sums). I heard that it is not possible to run a cpufreq scheduler like powernowd or cpufreqd, but would it be possible to set the cpu frequency at least