From: Dave Jones <davej@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: suspicious behaviour in pcwd driver.
Date: Mon, 22 Aug 2005 16:01:44 -0400 [thread overview]
Message-ID: <20050822200144.GG27344@redhat.com> (raw)
In-Reply-To: <20050822183006.GB27344@redhat.com>
On Mon, Aug 22, 2005 at 02:30:06PM -0400, Dave Jones wrote:
> drivers/char/watchdog/pcwd.c does this if it detects
> a temperature out of range..
>
> if (temp_panic) {
> printk (KERN_INFO PFX "Temperature overheat trip!\n");
> machine_power_off();
> }
>
> Two problems here are..
>
> 1. machine_power_off() isn't exported on ppc64. (patch below)
I was looking at an old tree, and this is now kernel_power_off()
so this isn't a problem for pcwd, however the export is still needed
for drivers/macintosh/therm_pm72.c
> 2. that printk will never hit the logs, so the admin will just find
> a powered off box with no idea what happened.
> Should we at least sync block devices before doing the power off ?
AFAICS, this is still a problem with kernel_power_off() though ?
Dave
next prev parent reply other threads:[~2005-08-22 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 18:30 suspicious behaviour in pcwd driver Dave Jones
2005-08-22 20:01 ` Dave Jones [this message]
2005-08-25 12:00 ` Pavel Machek
2005-08-22 23:26 ` 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=20050822200144.GG27344@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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