All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathew Brown" <mathewbrown@fastmail.fm>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Preventing ACPI from Damaging Your CPU
Date: Thu, 12 Oct 2006 09:51:13 -0700	[thread overview]
Message-ID: <1160671873.29653.273188134@webmail.messagingengine.com> (raw)
In-Reply-To: <200610121646.19668.rjw@sisk.pl>

Thanks for your reply Rafael.  However, I was looking for a generic
solution.  I don't have an nx6325 but was thinking of purchasing a
laptop and was afraid that ACPI could damage / overheat by CPUs.  I
think the link you provided is specific to the nx6325 unless I'm
mistaken.  Is there any generic solution?  Would recompiling the DSDT
and re-inserting it guarantee that no overheat / damage happens
regardless of the laptop / machine?  Thanks.


On Thu, 12 Oct 2006 16:46:19 +0200, "Rafael J. Wysocki" <rjw@sisk.pl>
said:
> On Thursday, 12 October 2006 16:26, Mathew Brown wrote:
> > Hi,
> >   I've been reading an alarming article on getting Gentoo to work on the
> >   HP Compaq nx6325
> >   (http://gentoo-wiki.com/HARDWARE_Gentoo_on_HP_Compaq_nx6325) and the
> >   serious ACPI problems that were encountered.  The author states after
> >   mentioning how to apply certain patches, "Without that, the CPU might
> >   overheat and get damaged during heavy load (such as compiling a Gentoo
> >   stage ...)!"
> > 
> >   What would be the safest way to ensure that ACPI doesn't do this to
> >   your machine / laptop without disabling ACPI?  Would recompiling the
> >   DSDT using the Intel compiler and re-inserting it be enough to ensure
> >   that ACPI doesn't cause your CPU to overheat or get damaged?  Thanks
> >   for your help.
> 
> Please see http://bugzilla.kernel.org/show_bug.cgi?id=7122, especially
> http://bugzilla.kernel.org/show_bug.cgi?id=7122#c27 and below.
> 
> Greetings,
> Rafael
> 
> 
> -- 
> You never change things by fighting the existing reality.
> 		R. Buckminster Fuller
-- 
  Mathew Brown
  mathewbrown@fastmail.fm

-- 
http://www.fastmail.fm - A fast, anti-spam email service.


  reply	other threads:[~2006-10-12 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 14:26 Preventing ACPI from Damaging Your CPU Mathew Brown
2006-10-12 14:46 ` Rafael J. Wysocki
2006-10-12 16:51   ` Mathew Brown [this message]
2006-10-12 19:34     ` Rafael J. Wysocki
2006-10-13  1:24 ` Matthew Garrett
2006-10-13  4:41   ` Mathew Brown
2006-10-13  4:53     ` Matthew Garrett
2006-10-13  4:56       ` Mathew Brown
2006-10-13 11:31         ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2006-10-15 14:16 Mathew Brown

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=1160671873.29653.273188134@webmail.messagingengine.com \
    --to=mathewbrown@fastmail.fm \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.