All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Krause <manuelkrause@netscape.net>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	rui.zhang@intel.com
Cc: Guenter Roeck <linux@roeck-us.net>,
	Jean Delvare <jdelvare@suse.de>,
	lm-sensors@lm-sensors.org
Subject: Re: 3.13.?: Strange / dangerous fan policy...
Date: Tue, 01 Apr 2014 01:37:21 +0200	[thread overview]
Message-ID: <5339FC31.3040601@netscape.net> (raw)
In-Reply-To: <532B4DC5.4010705@netscape.net>

On 2014-03-20 21:21, Manuel Krause wrote:
> On 2014-03-11 22:59, Manuel Krause wrote:
>> On 2014-03-10 02:49, Manuel Krause wrote:
>>> On 2014-03-09 18:58, Rafael J. Wysocki wrote:
>>>> On Sunday, March 09, 2014 01:10:25 AM Manuel Krause wrote:
>>>>> On 2014-03-08 16:59, Guenter Roeck wrote:
>>>>>> 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:
> [SNIP]
>
> Long time no reply from you... Have I overseen a unwritten
> convention? Or were my charts that unusable for your analysis/work?
>
> Two days ago, I tried the 3.14.0-rc7-vanilla. And the problem
> persists. "Strange / dangerous fan policy..."
>
> Since kernel 3.13.6 I've managed to 'fix' the potential
> overheating problem by manually issuing a:
> "echo 1 > /sys/class/thermal/cooling_device3/cur_state" *)
> _before_ obviously critical temperatures occur. Remind: This
> particular setting may only work for my system! ...and keeps
> working for 3.14-rc.
>
> In the following I'd like to present you a modified output of my
> /sys/class/thermal, that I've written a script for (for my
> system), that shows the results in the way of
> linux/Documentation/thermal/sysfs-api.txt, point 3:
> {I've uploded the files to pastebin, to not swamp you and the
> lists with so many lines of logs.}
>
> For the last good kernel -- 3.12.14 -- in-use:
>   http://pastebin.com/HL1PNcda
> For my first bad kernel revision 3.13 -- at critical temp:
>   http://pastebin.com/98hgf1a9
> For the last bad kernel -- 3.14.0-rc7 -- at critical temp:
>   http://pastebin.com/MuTwTnjD
> For the last bad kernel -- 3.14.0-rc7 -- after issuing the
>   *) command:
>   http://pastebin.com/2peda54z
>
> Please, have a look at them! And maybe, give me hints on how I
> can help you to further debug this issue, as my manual method
> works but it's annoying.
>
> And, PLEASE CC: ME, as I'm not on the lists. Or lead this
> Email-thread to someone in charge.
>
> Thank you for your work && best regards,
> Manuel Krause
>

This is still BUG 71711
https://bugzilla.kernel.org/show_bug.cgi?id=71711

3.12.15 works very well
3.13.7 fails
3.14.0-rc8 fails

I've tried the tmon tool, now, too. Nice eyecandy and for monitoring!

I've tried to revert all "thermal" related patches from 
3.12.14->3.13.7 from 3.13.7. But they don't seem to matter. (Even 
if I apply the vice-versa patch to 3.12.15.)

So "thermal" is out?

For the failing kernels: Not any reached trip point (active) 
triggers ONE fan action!

Next would be ACPI, to be investigated,

THX for this audience,
Manuel Krause


WARNING: multiple messages have this Message-ID (diff)
From: Manuel Krause <manuelkrause@netscape.net>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	rui.zhang@intel.com
Cc: Guenter Roeck <linux@roeck-us.net>,
	Jean Delvare <jdelvare@suse.de>,
	lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] 3.13.?: Strange / dangerous fan policy...
Date: Mon, 31 Mar 2014 23:37:21 +0000	[thread overview]
Message-ID: <5339FC31.3040601@netscape.net> (raw)
In-Reply-To: <532B4DC5.4010705@netscape.net>

On 2014-03-20 21:21, Manuel Krause wrote:
> On 2014-03-11 22:59, Manuel Krause wrote:
>> On 2014-03-10 02:49, Manuel Krause wrote:
>>> On 2014-03-09 18:58, Rafael J. Wysocki wrote:
>>>> On Sunday, March 09, 2014 01:10:25 AM Manuel Krause wrote:
>>>>> On 2014-03-08 16:59, Guenter Roeck wrote:
>>>>>> 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:
> [SNIP]
>
> Long time no reply from you... Have I overseen a unwritten
> convention? Or were my charts that unusable for your analysis/work?
>
> Two days ago, I tried the 3.14.0-rc7-vanilla. And the problem
> persists. "Strange / dangerous fan policy..."
>
> Since kernel 3.13.6 I've managed to 'fix' the potential
> overheating problem by manually issuing a:
> "echo 1 > /sys/class/thermal/cooling_device3/cur_state" *)
> _before_ obviously critical temperatures occur. Remind: This
> particular setting may only work for my system! ...and keeps
> working for 3.14-rc.
>
> In the following I'd like to present you a modified output of my
> /sys/class/thermal, that I've written a script for (for my
> system), that shows the results in the way of
> linux/Documentation/thermal/sysfs-api.txt, point 3:
> {I've uploded the files to pastebin, to not swamp you and the
> lists with so many lines of logs.}
>
> For the last good kernel -- 3.12.14 -- in-use:
>   http://pastebin.com/HL1PNcda
> For my first bad kernel revision 3.13 -- at critical temp:
>   http://pastebin.com/98hgf1a9
> For the last bad kernel -- 3.14.0-rc7 -- at critical temp:
>   http://pastebin.com/MuTwTnjD
> For the last bad kernel -- 3.14.0-rc7 -- after issuing the
>   *) command:
>   http://pastebin.com/2peda54z
>
> Please, have a look at them! And maybe, give me hints on how I
> can help you to further debug this issue, as my manual method
> works but it's annoying.
>
> And, PLEASE CC: ME, as I'm not on the lists. Or lead this
> Email-thread to someone in charge.
>
> Thank you for your work && best regards,
> Manuel Krause
>

This is still BUG 71711
https://bugzilla.kernel.org/show_bug.cgi?idq711

3.12.15 works very well
3.13.7 fails
3.14.0-rc8 fails

I've tried the tmon tool, now, too. Nice eyecandy and for monitoring!

I've tried to revert all "thermal" related patches from 
3.12.14->3.13.7 from 3.13.7. But they don't seem to matter. (Even 
if I apply the vice-versa patch to 3.12.15.)

So "thermal" is out?

For the failing kernels: Not any reached trip point (active) 
triggers ONE fan action!

Next would be ACPI, to be investigated,

THX for this audience,
Manuel Krause


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

  parent reply	other threads:[~2014-03-31 23:37 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
2014-03-08 15:59           ` Guenter Roeck
2014-03-09  0:10           ` Manuel Krause
2014-03-09  0:10             ` [lm-sensors] " Manuel Krause
2014-03-09  0:10             ` 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 [this message]
2014-03-31 23:37                       ` 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                               ` [lm-sensors] " Manuel Krause
2014-04-06 23:17                               ` 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=5339FC31.3040601@netscape.net \
    --to=manuelkrause@netscape.net \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    /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.