public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: Daniel Drake <dsd@gentoo.org>,
	linux-acpi@vger.kernel.org, eaburns@cisunix.unh.edu
Subject: Re: /proc/acpi/thermal_zone/THRM/temperature always reports 40C - is this a bug?
Date: Fri, 13 Oct 2006 13:34:47 +0200	[thread overview]
Message-ID: <200610131334.48433.rjw@sisk.pl> (raw)
In-Reply-To: <200610130117.02392.len.brown@intel.com>

On Friday, 13 October 2006 07:17, Len Brown wrote:
> On Wednesday 11 October 2006 21:03, Daniel Drake wrote:
> > Hi,
> > 
> > Ethan, at http://bugs.gentoo.org/142635 reports that the thermal zone 
> > always reads 40C. Is this something that should be filed at the kernel 
> > bugzilla for further investigation, or can we simply blame a 
> > buggy/unfixable BIOS? I understand that i2c/hwmon is the more common way 
> > of measuring temperatures.
> 
> Probably this isn't specific to a gentoo build and would happen just
> the same with a kernel.org build.  So if it is a bug, it is probably an upstream bug.
> 
> However, unless it used to work, or something bad happens,
> this is sort of an academic failure.  I suppose if you ran Windows
> on the box and it displayed a changing temperature via ACPI
> but Linux does not, then it would be more interesting.
> 
> It would be good to verify that ACPI events in general
> are working on the box -- eg. the power button etc -- as a failure
> there would also be more interesting than unchanging temperature.

I guess it may be related to http://bugzilla.kernel.org/show_bug.cgi?id=5534

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

  reply	other threads:[~2006-10-13 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12  1:03 /proc/acpi/thermal_zone/THRM/temperature always reports 40C - is this a bug? Daniel Drake
2006-10-13  5:17 ` Len Brown
2006-10-13 11:34   ` Rafael J. Wysocki [this message]
2006-10-15 19:50   ` Daniel Drake

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=200610131334.48433.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=dsd@gentoo.org \
    --cc=eaburns@cisunix.unh.edu \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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