Date: Thu, 14 Jul 2011 08:31:13 -0700 From: Ed VanderPloeg <edv@agile.bc.ca> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-acpi@FreeBSD.org Subject: Re: Atom N270 - ACPI Error: [RTMP] Namespace lookup failure Message-ID: <4E1F0BC1.4030802@agile.bc.ca> In-Reply-To: <4E117FE8.9030703@FreeBSD.org> References: <4E0A50AA.5000003@agile.bc.ca> <4E0AF27B.3030600@FreeBSD.org> <4E0B6873.6010901@agile.bc.ca> <4E0B80BE.6080605@FreeBSD.org> <4E0CA533.5030104@agile.bc.ca> <4E0CE39C.5050307@FreeBSD.org> <4E0D4A15.6000904@agile.bc.ca> <4E0D5EA0.1020704@FreeBSD.org> <4E0E7F91.2050408@agile.bc.ca> <4E117FE8.9030703@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Could the system overheat, or get incorrectly shut down when acpi fails to get the current temperature? What is the best way to work around this problem? Setting a very high polling rate or disabling it inside loader.conf: debug.acpi.disable="thermal" In 2008 Kevin Foo thought it might not be safe to disable it: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2008-01/msg00791.html Or do I need to boot with ACPI disabled until a BIOS fix is available? Ed On 2011-07-04 1:55 AM, Andriy Gapon wrote: > on 02/07/2011 05:16 Ed VanderPloeg said the following: >> >> # egrep '(^| )est' dmesg.8-release >> est0:<Enhanced SpeedStep Frequency Control> on cpu0 >> est: CPU supports Enhanced Speedstep, but is not recognized. >> est: cpu_vendor GenuineIntel, msr 60f0c270600060f >> device_attach: est0 attach returned 6 >> est1:<Enhanced SpeedStep Frequency Control> on cpu1 >> est: CPU supports Enhanced Speedstep, but is not recognized. >> est: cpu_vendor GenuineIntel, msr 60f0c270600060f >> device_attach: est1 attach returned 6 >> >> # egrep '(^| )est' dmesg.8-stable >> est0:<Enhanced SpeedStep Frequency Control> on cpu0 >> est1:<Enhanced SpeedStep Frequency Control> on cpu1 > > So this was improved. Thanks! >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E1F0BC1.4030802>