From owner-freebsd-current@FreeBSD.ORG Wed Jul 15 22:12:47 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97BBB106566B for ; Wed, 15 Jul 2009 22:12:47 +0000 (UTC) (envelope-from edwinlculp@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by mx1.freebsd.org (Postfix) with ESMTP id 4BD5E8FC1D for ; Wed, 15 Jul 2009 22:12:47 +0000 (UTC) (envelope-from edwinlculp@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so543922qwe.7 for ; Wed, 15 Jul 2009 15:12:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=g2unyAJpuGddxYPRqrMOofgRQX2oosECQZgexE8H5Xg=; b=kr2p/al3E5D/FiVyOiGlnS7eOOpXCk14YugJva/dvOPspVA9p1qzBl/yH5ga/cCb/f lIHK3jGkBQapd2cx/oVqd27AQhiusHnyHrPTilmfB4OWUKNzfhDpm6gh1Savb+ACc4ef e6lcXtIGMDC7nIvzO6uEnrbDxDJujZu3tvO3U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=nmUNqKUnpdzNQ8TtkZjEZ5olDNpbyonGpgV8ub9xQOt+s4nqlDdgDhUzY5iH3Ic528 De6/0hMfafooYk6Bs6FKvG8WqWW39wP9X72Ju7uf0bsATfwXsn/dLtQP7K9a9sib3gPw rdVC2afl/gWCgr2hLLyyMVbxxNBf1PMCTWCf4= MIME-Version: 1.0 Received: by 10.229.70.141 with SMTP id d13mr1661162qcj.70.1247695965956; Wed, 15 Jul 2009 15:12:45 -0700 (PDT) In-Reply-To: <1247682869.1298.32.camel@RabbitsDen> References: <7affaed60907141654h29f748cdm95532aa83c4ac08d@mail.gmail.com> <1247682869.1298.32.camel@RabbitsDen> Date: Wed, 15 Jul 2009 17:12:45 -0500 Message-ID: <7affaed60907151512q24ce3df6j5ee9989907dd6739@mail.gmail.com> From: "Edwin L. Culp W." To: Alexandre Sunny Kovalenko Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current Subject: Re: Acer Laptop overheating with ACPI error that I don't understand. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2009 22:12:48 -0000 On Wed, Jul 15, 2009 at 1:34 PM, Alexandre "Sunny" Kovalenko < gaijin.k@gmail.com> wrote: > On Tue, 2009-07-14 at 18:54 -0500, Edwin L. Culp W. wrote: > > I am having overheating problems with my Acer Aspire laptop. > > # uname -a > > FreeBSD ed.local.net.mx 8.0-BETA1 FreeBSD 8.0-BETA1 #256: Thu Jul 9 > > 07:05:20 CDT 2009 root@ed.local.net.mx: > /usr/obj/usr/src/sys/ENCONTACTO > > i386 > > > > I've been having this problem for several months and compensating by > > reducing dev.cpu.0.freq from 1900 to 1200 and 800 in warm offices. > > > > The errors I'm seeing in the log files are: > > > > +acpi_ec0: EcRead: failed waiting to get data > > +ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for > > [EmbeddedControl] 20090521 evregion-531 > > +ACPI Error (psparse-0633): Method parse/execution failed > [\\_TZ_.THRM._TMP] > > (Node 0xc4e75960), AE_NO_HARDWARE_RESPONSE > > > > I'm afraid that I don't understand them. > This means that FreeBSD tried to execute method, provided by your ACPI > BIOS, that is supposed to return current temperature, and execution did > not complete within certain time limit (I do not have -CURRENT system > handy to tell you what the limit is). I would recommend taking this to > acpi@ mailing list, unless it used to work under -STABLE and ceased > under -CURRENT. > > Output of 'sysctl hw.acpi' should give you a clue, especially > temperature field. > > Next steps could be: > -- see if there is BIOS update for your hardware. > -- boot some kind of live CD of the system, you are familiar with, and > check temperature value(s). They should be reasonable and should change > with the load. > -- If your BIOS is up-to-date and nothing gives you reasonable > temperature readout, it might be hardware problem. Alternatively, it > might be that your ACPI BIOS was never designed to work with anything > but Windows -- I have seen few of those in the past. If latter is the > case, disassembling your ASL (see handbook for instructions) and reading > through it with ACPI spec at hand, starting with the _TMP method above, > might get you somewhere. Thermal section of the ACPI spec is > self-sufficient, well-written and has documented example. > -- ask on acpi@ whether there is tunable and/or hack which can extend > timeout value -- it could be that whatever hardware your ASL is talking > to just takes its own time to respond.. > > HTH, Excellent advice. As soon as I get back home I'm going to check out a BIOS update. I hadn't though about that and also look closer at ACPI that I've not done either but that will take a little more time but well spent, I would say. Thanks, ed > > -- > Alexandre Kovalenko (=EF=CC=C5=CB=D3=C1=CE=C4=D2 =EB=CF=D7=C1=CC=C5=CE=CB= =CF) > > >