linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Wilde <wilde@sha-bang.de>
To: linux-kernel@vger.kernel.org
Cc: Salvatore Sisinni <s.sisinni@gmail.com>,
	Roberto Oppedisano <roberto.oppedisano@infracom.it>
Subject: Re: regression in linux 3.7 - fan speed at 100% after suspend/resume at 100%
Date: Sun, 10 Mar 2013 16:47:00 +0100	[thread overview]
Message-ID: <m2d2v76yvf.fsf@kenny.lan.sha-bang.de> (raw)
In-Reply-To: <m2vc90798h.fsf@kenny.lan.sha-bang.de> (Sascha Wilde's message of "Sat, 09 Mar 2013 18:50:54 +0100")

Sascha Wilde <wilde@sha-bang.de> wrote:
[...]
> [2]  FWIW², I'm under the stron impression that the whole fan control
>      changed in the latest vanilla kernels on my 6910p even before doing
>      a suspend/resume -- it seems to be more "binary" if you will, in
>      that the fan is not running at all for a while and then at a 100%
>      to return back to 0% after doing some serious cooling.  With 3.6.11
>      and older it is more "analogue", with slow fan when only a bit
>      cooling is needed.  No idea if this is related to the issue at
>      hand.

For that part of the problem I just discovered something that might be a
hint on the cause, there is no governor set for the thermal zones:

/sys/devices/virtual/thermal/thermal_zone0/policy : (null)
/sys/devices/virtual/thermal/thermal_zone1/policy : (null)
/sys/devices/virtual/thermal/thermal_zone2/policy : (null)
/sys/devices/virtual/thermal/thermal_zone3/policy : (null)
/sys/devices/virtual/thermal/thermal_zone4/policy : (null)

to my understanding this policies should default default to the
CONFIG_THERMAL_DEFAULT_GOV_*
configured in the kernel.  But it is always (null) for me.  And
something like 
# echo fair_share >/sys/devices/virtual/thermal/thermal_zone0/policy
does not work either.

Or is this expected behavior?

cheers
sascha
-- 
Sascha Wilde : "There are 10 types of people in the world. 
             : Those who understand binary and those who don't."

  reply	other threads:[~2013-03-10 15:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 17:50 regression in linux 3.7 - fan speed at 100% after suspend/resume at 100% Sascha Wilde
2013-03-10 15:47 ` Sascha Wilde [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-04 12:57 Roberto Oppedisano
2012-12-04 14:11 ` Zhang Rui
2012-12-05  7:30   ` Roberto Oppedisano
2012-12-19 14:30     ` Roberto Oppedisano
2013-02-19 17:54       ` Salvatore Sisinni
2013-02-20  0:20         ` Zhang Rui
2013-02-20 13:41           ` Roberto Oppedisano
2013-02-21 17:17             ` Salvatore Sisinni
2013-03-06 14:44               ` Salvatore Sisinni
2013-02-15 23:30   ` Michael Grosshaeuser
2013-02-16  6:55     ` auxsvr
2013-03-03  0:22 ` Ville Syrjala
2013-03-04 12:29   ` Roberto Oppedisano
2013-03-04 13:25     ` Roberto Oppedisano

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=m2d2v76yvf.fsf@kenny.lan.sha-bang.de \
    --to=wilde@sha-bang.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roberto.oppedisano@infracom.it \
    --cc=s.sisinni@gmail.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 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).