From owner-freebsd-current@FreeBSD.ORG Wed Jul 15 18:56:23 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 72793106567C for ; Wed, 15 Jul 2009 18:56:23 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from mail-pz0-f193.google.com (mail-pz0-f193.google.com [209.85.222.193]) by mx1.freebsd.org (Postfix) with ESMTP id 408E98FC21 for ; Wed, 15 Jul 2009 18:56:23 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by pzk31 with SMTP id 31so2940248pzk.3 for ; Wed, 15 Jul 2009 11:56:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=XB3xcfz/LQIywEGSthYMeq0fP5AA9RvUuQ6guXivav8=; b=u4+o7qhA1Xy2HTuvyXKTqGYXu0aY3gehQlQAo+B6PzdbXD9eRgifnUtEF4Fjh4m+Vx UcENGxEZjyzSvGUk6M27424wf6pq2VkB2HLkv/Wco1xVNfdDUypB3IoficWp2oTw0d9U jQg6BKTbTq7CIGSWSSRdFphhKuWX/EuynDS4Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=mlCesrFLtRXeFJaStaZiIimonLIvl6SMBrOEYdayNYnsSz0LcXqKmzcSUKxukKtFf5 tE8i4J9s72gooJePstXIkLxS1WufVwc6gFEj8GSojJOj00gexBQv4W+TtokQ0Z1K8t6X ZegQzZ8e8ePZh8SjuJxOVIVGUy1nmXvF0AvPo= Received: by 10.114.73.14 with SMTP id v14mr13155360waa.104.1247682929067; Wed, 15 Jul 2009 11:35:29 -0700 (PDT) Received: from ?10.0.3.231? (pool-70-111-8-172.nwrk.east.verizon.net [70.111.8.172]) by mx.google.com with ESMTPS id v9sm14417705wah.36.2009.07.15.11.35.26 (version=SSLv3 cipher=RC4-MD5); Wed, 15 Jul 2009 11:35:28 -0700 (PDT) From: "Alexandre \"Sunny\" Kovalenko" To: "Edwin L. Culp W." In-Reply-To: <7affaed60907141654h29f748cdm95532aa83c4ac08d@mail.gmail.com> References: <7affaed60907141654h29f748cdm95532aa83c4ac08d@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 15 Jul 2009 14:34:29 -0400 Message-Id: <1247682869.1298.32.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit 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 18:56:23 -0000 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, -- Alexandre Kovalenko (Олександр Коваленко)