linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Manuel Krause <manuelkrause@netscape.net>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	lm-sensors@lm-sensors.org
Subject: Re: 3.13.?: Strange / dangerous fan policy...
Date: Fri, 7 Mar 2014 14:52:30 -0800	[thread overview]
Message-ID: <20140307225230.GA31135@roeck-us.net> (raw)
In-Reply-To: <531A426D.6080100@netscape.net>

On Fri, Mar 07, 2014 at 11:04:29PM +0100, Manuel Krause wrote:
> On 2014-03-07 21:55, Guenter Roeck wrote:
> >On Fri, Mar 07, 2014 at 08:33:02PM +0100, Manuel Krause wrote:
> >>Please have a short look at the following BUG report + the comments
> >>-- this message here is a kind of FWD-ing it:
> >>https://bugs.archlinux.org/task/39005
> >>
> >>I came late to test kernel 3.13 with the .5 one, as it was the time
> >>that the related -CK/BFS patch became available.
> >>
> >>I'm not using Archlinux, but openSUSE, and my problems are quite the
> >>same. Especially these with smelling melting plastics.
> >>
> >>My own reports went to Con Kolivas' Blog first:
> >>"I get weird temperatures and abrupt 100% fan actions with vanilla
> >>3.13.5 with this CK and most recent BFQ at my HP Notebook.
> >>In gkrellm the highest T had been @74°C, so far (3.12.13), and is
> >>now growing to 94°C. Then, the fan goes to 100% for 10~30secs
> >>cooling it to approx. 82°C.
> >>That is not good, if I compare 74 to 94 °C.
> >>Have I missed a .CONFIG option for 3.13, especially?"
> >>
> >>I'd get the same without (Con's && BFQ's) patches.
> >>
> >>Machine:           HP Notebook with Core2Duo CPU (Penryn)
> >>Distro:            openSUSE 13.1, 64bit, continuously updated
> >>Desktop:           KDE 4.12.3
> >>MESA & drm & Xorg: most recent ones from:
> >>http://download.opensuse.org/repositories/home:/pontostroy:/X11/openSUSE_13.1/x86_64/
> >>
> >>Current kernel:    3.13.6 vanilla from openSUSE repos, with
> >>                    -ck1 and BFQ patches
> >>Same behaviour:    without these patches
> >>
> >>Last good kernel:  3.12.13 vanilla + CK2 + BFQ
> >>
> >
> >Can you add more information about your fan control policy ?
> >Do you rely on the hardware for automatic fan speed control,
> >or do you run the fancontrol script ?
> >
> >What is the output from the 'sensors' command ?
> >
> >Thanks,
> >Guenter
> >
> 
> 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.

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

Of course, if output is different in 3.13, that would be important
to know. Maybe someone else can post related information for both
kernel versions on an affected system.

Guenter

  reply	other threads:[~2014-03-07 22:52 UTC|newest]

Thread overview: 22+ 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 22:04   ` Manuel Krause
2014-03-07 22:52     ` Guenter Roeck [this message]
2014-03-08 11:08       ` [lm-sensors] " Jean Delvare
2014-03-08 12:36         ` Rafael J. Wysocki
2014-03-08 15:59         ` Guenter Roeck
2014-03-09  0:10           ` Manuel Krause
2014-03-09 17:28             ` Guenter Roeck
2014-03-09 17:58             ` Rafael J. Wysocki
2014-03-10  1:49               ` Manuel Krause
2014-03-11 21:59                 ` Manuel Krause
     [not found]                   ` <532B4DC5.4010705@netscape.net>
2014-03-31 23:37                     ` Manuel Krause
2014-03-31 23:47                       ` Guenter Roeck
2014-04-06  2:37                         ` Manuel Krause
2014-04-06  2:43                           ` Guenter Roeck
2014-04-06 23:17                             ` Manuel Krause
2014-04-07 11:45                               ` Rafael J. Wysocki
2014-04-10 22:51                                 ` Manuel Krause
2014-04-13  0:05                                   ` Manuel Krause
2014-04-16 18:32                                     ` Zhang Rui
2014-04-16 22:17                                       ` 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=20140307225230.GA31135@roeck-us.net \
    --to=linux@roeck-us.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).