All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Jean Delvare <jdelvare@suse.de>,
	Manuel Krause <manuelkrause@netscape.net>
Cc: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [lm-sensors] 3.13.?: Strange / dangerous fan policy...
Date: Sat, 08 Mar 2014 07:59:08 -0800	[thread overview]
Message-ID: <531B3E4C.2040105@roeck-us.net> (raw)
In-Reply-To: <20140308120831.328e0179@endymion.delvare>

On 03/08/2014 03:08 AM, Jean Delvare wrote:
> On Fri, 7 Mar 2014 14:52:30 -0800, Guenter Roeck wrote:
>> On Fri, Mar 07, 2014 at 11:04:29PM +0100, Manuel Krause wrote:
>>> Hi, and thanks for the quick response!
>>> No special fancy "fan control policy". 'fancontrol' isn't up or
>>> running.
>>> Vanilla kernels 3.11.* and 3.12.* had been working on here without
>>> any extra work.
>>> --
>>> # sensors
>>> acpitz-virtual-0
>>> Adapter: Virtual device
>>> temp1:        +71.0°C  (crit = +256.0°C)
>>> temp2:        +69.0°C  (crit = +110.0°C)
>>> temp3:        +52.0°C  (crit = +105.0°C)
>>> temp4:        +25.0°C  (crit = +110.0°C)
>>> temp5:        +58.0°C  (crit = +110.0°C)
>>>
>>> coretemp-isa-0000
>>> Adapter: ISA adapter
>>> Core 0:       +62.0°C  (high = +105.0°C, crit = +105.0°C)
>>> Core 1:       +60.0°C  (high = +105.0°C, crit = +105.0°C)
>>> --
>>> My notebook (HP/Compaq 6730b) does not have a seperate fan sensor.
>>> This is with 3.12.13 with my normal workload.
>>>
>>> Please, trust my above mentionned values of 94 °C vs. 74°C as I
>>> don't like to boot 3.13.6 anymore, to avoid harm to the notebook's
>>> casing.
>>
>> Understood. Unfortunately, we'll need to get information
>> from the new kernel to be able to track down the problem.
>
> Indeed. Not only the run-time temperatures, but also the high and crit
> limits.
>
>>> But I'd do to test any improvement-patch.
>>
>> So far I have no idea what is going on. I don't see anything in the
>> drivers providing above data that would explain the behavior,
>> but I might be missing something.
>
> Looks like a regression in the acpi subsystem or in power management,
> not hwmon. Hwmon is merely reporting the temperatures, it's not
> responsible for the actual temperatures.
>

I would agree. I don't think we have enough information to be sure,
though. There might be some unintended interaction or interference.

gpu is a good hint ... for example, look at commit b9ed919f1c8
(drm/nouveau/drm/pm: remove everything except the hwmon interfaces
to THERM). nouveau does export pwm and fan control information,
so any change in that code may have unintended side effects.
Similar, I don't know how ec39f64bba (drm/radeon/dpm: Convert to
use devm_hwmon_register_with_groups) could have the observed impact,
as it is purely passive, but I prefer to be rather safe than sorry.

This problem has now been submitted into bugzilla as
https://bugzilla.kernel.org/show_bug.cgi?id=71711.

Guenter


WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Jean Delvare <jdelvare@suse.de>,
	Manuel Krause <manuelkrause@netscape.net>
Cc: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [lm-sensors] 3.13.?: Strange / dangerous fan policy...
Date: Sat, 08 Mar 2014 15:59:08 +0000	[thread overview]
Message-ID: <531B3E4C.2040105@roeck-us.net> (raw)
In-Reply-To: <20140308120831.328e0179@endymion.delvare>

On 03/08/2014 03:08 AM, Jean Delvare wrote:
> On Fri, 7 Mar 2014 14:52:30 -0800, Guenter Roeck wrote:
>> On Fri, Mar 07, 2014 at 11:04:29PM +0100, Manuel Krause wrote:
>>> Hi, and thanks for the quick response!
>>> No special fancy "fan control policy". 'fancontrol' isn't up or
>>> running.
>>> Vanilla kernels 3.11.* and 3.12.* had been working on here without
>>> any extra work.
>>> --
>>> # sensors
>>> acpitz-virtual-0
>>> Adapter: Virtual device
>>> temp1:        +71.0°C  (crit = +256.0°C)
>>> temp2:        +69.0°C  (crit = +110.0°C)
>>> temp3:        +52.0°C  (crit = +105.0°C)
>>> temp4:        +25.0°C  (crit = +110.0°C)
>>> temp5:        +58.0°C  (crit = +110.0°C)
>>>
>>> coretemp-isa-0000
>>> Adapter: ISA adapter
>>> Core 0:       +62.0°C  (high = +105.0°C, crit = +105.0°C)
>>> Core 1:       +60.0°C  (high = +105.0°C, crit = +105.0°C)
>>> --
>>> My notebook (HP/Compaq 6730b) does not have a seperate fan sensor.
>>> This is with 3.12.13 with my normal workload.
>>>
>>> Please, trust my above mentionned values of 94 °C vs. 74°C as I
>>> don't like to boot 3.13.6 anymore, to avoid harm to the notebook's
>>> casing.
>>
>> Understood. Unfortunately, we'll need to get information
>> from the new kernel to be able to track down the problem.
>
> Indeed. Not only the run-time temperatures, but also the high and crit
> limits.
>
>>> But I'd do to test any improvement-patch.
>>
>> So far I have no idea what is going on. I don't see anything in the
>> drivers providing above data that would explain the behavior,
>> but I might be missing something.
>
> Looks like a regression in the acpi subsystem or in power management,
> not hwmon. Hwmon is merely reporting the temperatures, it's not
> responsible for the actual temperatures.
>

I would agree. I don't think we have enough information to be sure,
though. There might be some unintended interaction or interference.

gpu is a good hint ... for example, look at commit b9ed919f1c8
(drm/nouveau/drm/pm: remove everything except the hwmon interfaces
to THERM). nouveau does export pwm and fan control information,
so any change in that code may have unintended side effects.
Similar, I don't know how ec39f64bba (drm/radeon/dpm: Convert to
use devm_hwmon_register_with_groups) could have the observed impact,
as it is purely passive, but I prefer to be rather safe than sorry.

This problem has now been submitted into bugzilla as
https://bugzilla.kernel.org/show_bug.cgi?id=71711.

Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2014-03-08 15:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 19:33 3.13.?: Strange / dangerous fan policy Manuel Krause
2014-03-07 20:55 ` Guenter Roeck
2014-03-07 20:55   ` [lm-sensors] " Guenter Roeck
2014-03-07 22:04   ` Manuel Krause
2014-03-07 22:04     ` [lm-sensors] " Manuel Krause
2014-03-07 22:52     ` Guenter Roeck
2014-03-07 22:52       ` [lm-sensors] " Guenter Roeck
2014-03-08 11:08       ` Jean Delvare
2014-03-08 11:08         ` Jean Delvare
2014-03-08 12:36         ` Rafael J. Wysocki
2014-03-08 12:36           ` Rafael J. Wysocki
2014-03-08 15:59         ` Guenter Roeck [this message]
2014-03-08 15:59           ` Guenter Roeck
2014-03-09  0:10           ` Manuel Krause
2014-03-09  0:10             ` Manuel Krause
2014-03-09  0:10             ` [lm-sensors] " Manuel Krause
2014-03-09 17:28             ` Guenter Roeck
2014-03-09 17:28               ` [lm-sensors] " Guenter Roeck
2014-03-09 17:58             ` Rafael J. Wysocki
2014-03-09 17:58               ` [lm-sensors] " Rafael J. Wysocki
2014-03-10  1:49               ` Manuel Krause
2014-03-10  1:49                 ` [lm-sensors] " Manuel Krause
2014-03-11 21:59                 ` Manuel Krause
2014-03-11 21:59                   ` [lm-sensors] " Manuel Krause
     [not found]                   ` <532B4DC5.4010705@netscape.net>
2014-03-31 23:37                     ` Manuel Krause
2014-03-31 23:37                       ` [lm-sensors] " Manuel Krause
2014-03-31 23:47                       ` Guenter Roeck
2014-03-31 23:47                         ` [lm-sensors] " Guenter Roeck
2014-04-06  2:37                         ` Manuel Krause
2014-04-06  2:37                           ` [lm-sensors] " Manuel Krause
2014-04-06  2:43                           ` Guenter Roeck
2014-04-06  2:43                             ` [lm-sensors] " Guenter Roeck
2014-04-06 23:17                             ` Manuel Krause
2014-04-06 23:17                               ` Manuel Krause
2014-04-06 23:17                               ` [lm-sensors] " Manuel Krause
2014-04-07 11:45                               ` Rafael J. Wysocki
2014-04-07 11:45                                 ` [lm-sensors] " Rafael J. Wysocki
2014-04-10 22:51                                 ` Manuel Krause
2014-04-10 22:51                                   ` [lm-sensors] " Manuel Krause
2014-04-13  0:05                                   ` Manuel Krause
2014-04-13  0:05                                     ` [lm-sensors] " Manuel Krause
2014-04-16 18:32                                     ` Zhang Rui
2014-04-16 18:32                                       ` [lm-sensors] " Zhang Rui
2014-04-16 22:17                                       ` Manuel Krause
2014-04-16 22:17                                         ` [lm-sensors] " Manuel Krause

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=531B3E4C.2040105@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=manuelkrause@netscape.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.