From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/4] Fix G5 thermal shutdown
Date: Tue, 09 Feb 2010 11:55:05 +1100 [thread overview]
Message-ID: <1265676905.8287.254.camel@pasglop> (raw)
In-Reply-To: <20100205135216.GH12001@hansolo.jdub.homelinux.org>
On Fri, 2010-02-05 at 08:52 -0500, Josh Boyer wrote:
> This changes the thresholds for the liquid cooled G5 thermal
> shutdown mechanism to prevent an errant shutdown.
>
> This has been carried since about Fedora Core 5. I have no idea
> if it's really needed or not.
Can we have a SoB ?
Cheers,
Ben.
> ---
>
> --- linux-2.6.15/drivers/macintosh/therm_pm72.c.orig 2006-04-02 21:34:48.000000000 +0100
> +++ linux-2.6.15/drivers/macintosh/therm_pm72.c 2006-04-02 22:33:27.000000000 +0100
> @@ -924,10 +925,16 @@ static void do_monitor_cpu_combined(void
> printk(KERN_WARNING "Warning ! Temperature way above maximum (%d) !\n",
> temp_combi >> 16);
> state0->overtemp += CPU_MAX_OVERTEMP / 4;
> - } else if (temp_combi > (state0->mpu.tmax << 16))
> + } else if (temp_combi > (state0->mpu.tmax << 16)) {
> state0->overtemp++;
> - else
> + printk(KERN_WARNING "Temperature %d above max %d. overtemp %d\n",
> + temp_combi >> 16, state0->mpu.tmax, state0->overtemp);
> + } else {
> + if (state0->overtemp)
> + printk(KERN_WARNING "Temperature back down to %d\n",
> + temp_combi >> 16);
> state0->overtemp = 0;
> + }
> if (state0->overtemp >= CPU_MAX_OVERTEMP)
> critical_state = 1;
> if (state0->overtemp > 0) {
> @@ -999,10 +1015,16 @@ static void do_monitor_cpu_split(struct
> " (%d) !\n",
> state->index, temp >> 16);
> state->overtemp += CPU_MAX_OVERTEMP / 4;
> - } else if (temp > (state->mpu.tmax << 16))
> + } else if (temp > (state->mpu.tmax << 16)) {
> state->overtemp++;
> - else
> + printk(KERN_WARNING "CPU %d temperature %d above max %d. overtemp %d\n",
> + state->index, temp >> 16, state->mpu.tmax, state->overtemp);
> + } else {
> + if (state->overtemp)
> + printk(KERN_WARNING "CPU %d temperature back down to %d\n",
> + state->index, temp >> 16);
> state->overtemp = 0;
> + }
> if (state->overtemp >= CPU_MAX_OVERTEMP)
> critical_state = 1;
> if (state->overtemp > 0) {
> @@ -1061,10 +1097,16 @@ static void do_monitor_cpu_rack(struct c
> " (%d) !\n",
> state->index, temp >> 16);
> state->overtemp = CPU_MAX_OVERTEMP / 4;
> - } else if (temp > (state->mpu.tmax << 16))
> + } else if (temp > (state->mpu.tmax << 16)) {
> state->overtemp++;
> - else
> + printk(KERN_WARNING "CPU %d temperature %d above max %d. overtemp %d\n",
> + state->index, temp >> 16, state->mpu.tmax, state->overtemp);
> + } else {
> + if (state->overtemp)
> + printk(KERN_WARNING "CPU %d temperature back down to %d\n",
> + state->index, temp >> 16);
> state->overtemp = 0;
> + }
> if (state->overtemp >= CPU_MAX_OVERTEMP)
> critical_state = 1;
> if (state->overtemp > 0) {
> --- linux-2.6.15/drivers/macintosh/therm_pm72.h~ 2006-01-03 03:21:10.000000000 +0000
> +++ linux-2.6.15/drivers/macintosh/therm_pm72.h 2006-04-02 22:25:58.000000000 +0100
> @@ -243,7 +243,7 @@ struct dimm_pid_state
> #define CPU_TEMP_HISTORY_SIZE 2
> #define CPU_POWER_HISTORY_SIZE 10
> #define CPU_PID_INTERVAL 1
> -#define CPU_MAX_OVERTEMP 30
> +#define CPU_MAX_OVERTEMP 90
>
> #define CPUA_PUMP_RPM_INDEX 7
> #define CPUB_PUMP_RPM_INDEX 8
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2010-02-09 0:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 13:35 [PATCH 0/4] Fedora kernel patch review Josh Boyer
2010-02-05 13:42 ` [PATCH 1/4] Add ps3_storage module alias Josh Boyer
2010-02-05 13:49 ` Geert Uytterhoeven
2010-02-05 14:03 ` Josh Boyer
2010-02-05 14:39 ` Geert Uytterhoeven
2010-02-23 12:47 ` David Woodhouse
2010-02-05 13:52 ` [PATCH 2/4] Fix G5 thermal shutdown Josh Boyer
2010-02-09 0:55 ` Benjamin Herrenschmidt [this message]
2010-02-09 2:06 ` Josh Boyer
2010-02-23 12:48 ` David Woodhouse
2010-02-24 2:54 ` Benjamin Herrenschmidt
2010-02-05 13:53 ` [PATCH 0/4] Fedora kernel patch review Josh Boyer
2010-02-05 13:59 ` Josh Boyer
2010-02-23 12:50 ` [PATCH 3/4] Provide VIO modalias David Woodhouse
2010-02-24 0:05 ` Brian King
2010-02-05 13:55 ` [PATCH 4/4] Fix iMac iSight PCI bridge setup Josh Boyer
2010-02-05 20:57 ` Benjamin Herrenschmidt
2010-02-06 1:03 ` Josh Boyer
2010-02-06 1:48 ` Benjamin Herrenschmidt
2010-02-23 12:50 ` David Woodhouse
2010-02-05 14:04 ` [PATCH 0/4] Fedora kernel patch review Josh Boyer
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=1265676905.8287.254.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jwboyer@gmail.com \
--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 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.