linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Jan Engelhardt <jengelh@inai.de>,
	Ben Hutchings <ben@decadent.org.uk>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: therm_pm72 units, interface
Date: Fri, 02 Aug 2013 18:52:26 +0200	[thread overview]
Message-ID: <1375462346.3852.42.camel@thor.local> (raw)
In-Reply-To: <20130802155818.GB29933@blackmetal.musicnaut.iki.fi>

On Fre, 2013-08-02 at 18:58 +0300, Aaro Koskinen wrote:
> On Fri, Aug 02, 2013 at 04:47:51PM +0200, Michel D=C3=A4nzer wrote:
> > On Fre, 2013-08-02 at 22:51 +1000, Benjamin Herrenschmidt wrote:
> > > On Fri, 2013-08-02 at 12:03 +0200, Michel D=C3=A4nzer wrote:
> > > > Could a similar change fix the same problem on desktop G5s? The sam=
e
> > > > values for slots_param in windfarm_pm112.c don't help, unfortunatel=
y.
> > >=20
> > > You have a 11,2 and a noisy fan ? Odd, mine(s) don't.... I can dbl ch=
eck
> > > the values vs. what Darwin uses tomorrow...
> >=20
> > Yes, see /proc/cpuinfo below.
> >=20
> > With older kernels (currently still using Debian's 3.2.0-4-powerpc64
> > because of this problem), the fans go basically silent as soon as the
> > windfarm modules are loaded. With current kernels, the fans stay at the
> > level OF sets them to, until after a while they go into 'airplane mode'=
.
> >=20
> > One thing I notice now is that the lines like
> >=20
> > [    9.539173] windfarm: CPUs control loops started.
> > [   16.209962] windfarm: Backside control loop started.
> > [   16.262274] windfarm: Slots control loop started.
> > [   16.371642] windfarm: Drive bay control loop started.
> >=20
> > no longer appear in dmesg with current kernels. Should they?
>=20
> Yes. They are printed once all the sensor and control modules are
> loaded and registered. If the loops are not started, it's basically
> doing nothing. Maybe something goes wrong in module loading? What lsmod
> is showing?

Thanks for the suggestion. The same windfarm modules were loaded in both
cases, but i2c_powermac wasn't loaded with the newer kernels. Loading it
manually fixes the problem.

How is i2c_powermac supposed to get loaded with current kernels?


--=20
Earthling Michel D=C3=A4nzer           |                   http://www.amd.c=
om
Libre software enthusiast         |          Debian, X and DRI developer

  reply	other threads:[~2013-08-02 16:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 17:53 therm_pm72 units, interface Jan Engelhardt
2012-08-15 21:35 ` Benjamin Herrenschmidt
2012-08-16 15:24   ` Jan Engelhardt
2012-08-16 20:51     ` Benjamin Herrenschmidt
2012-08-17 13:51       ` Jan Engelhardt
2012-08-17 20:17         ` Benjamin Herrenschmidt
2012-08-17 14:23       ` Jan Engelhardt
2012-08-15 21:36 ` Benjamin Herrenschmidt
2013-01-17 14:38   ` Jan Engelhardt
2013-01-17 23:38     ` Benjamin Herrenschmidt
2013-07-19 17:43       ` Aaro Koskinen
2013-07-19 23:16         ` Benjamin Herrenschmidt
2013-07-20 20:33           ` Aaro Koskinen
2013-07-20 23:42             ` Benjamin Herrenschmidt
2013-08-02 10:03             ` Michel Dänzer
2013-08-02 12:51               ` Benjamin Herrenschmidt
2013-08-02 14:47                 ` Michel Dänzer
2013-08-02 15:58                   ` Aaro Koskinen
2013-08-02 16:52                     ` Michel Dänzer [this message]
2013-08-02 21:02                       ` Benjamin Herrenschmidt
2013-08-05  9:13                         ` Michel Dänzer
2013-08-05  9:22                           ` Benjamin Herrenschmidt
2013-08-05 10:32                             ` Michel Dänzer
2013-08-05 10:53                               ` Benjamin Herrenschmidt
2013-09-27 15:44                                 ` Michel Dänzer
2013-08-02 20:47                   ` Benjamin Herrenschmidt
2013-08-02 20:56                     ` Ben Hutchings
2013-08-02 21:04                       ` Benjamin Herrenschmidt

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=1375462346.3852.42.camel@thor.local \
    --to=michel@daenzer.net \
    --cc=aaro.koskinen@iki.fi \
    --cc=ben@decadent.org.uk \
    --cc=jengelh@inai.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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).