Date: Sat, 24 Jan 2009 23:30:50 +0300 From: Alex Keda <admin@lissyara.su> To: "Paul B. Mahol" <onemda@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: acpi_throttle1: failed to attach P_CNT Message-ID: <497B7A7A.3080103@lissyara.su> In-Reply-To: <3a142e750901240847o652c581erd1fe90c776824fbe@mail.gmail.com> References: <497A159B.5050404@lissyara.su> <497B24D5.3010200@lissyara.su> <3a142e750901240847o652c581erd1fe90c776824fbe@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul B. Mahol пишет: > On 1/24/09, Alex Keda <admin@lissyara.su> wrote: >> Alex Keda pishet: >>> After last update I have in dmesg >>> >>> acpi_throttle1: <ACPI CPU Throttling> on cpu1 >>> acpi_throttle1: failed to attach P_CNT >>> device_attach: acpi_throttle1 attach returned 6 >>> >>> When I build somesing - laptop shutdown, because CPU temp > 105 Celsius >>> >>> HP# uname -a >>> FreeBSD HP.lissyara.su 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Thu Jan 22 >>> 19:49:57 MSK 2009 root@HP.lissyara.su:/usr/obj/usr/src/sys/HP amd64 >>> HP# >> HP$ dmesg > .... > > I get this one: > > GEOM: ad0s1: geometry does not match label (15h,63s != 16h,63s). > Trying to mount root from ufs:/dev/ad0s1a > ACPI Exception (utmutex-0376): AE_TIME, Thread 186B0 could not acquire > Mutex [0] [20070320] > ACPI Error (exutils-0180): Could not acquire AML Interpreter mutex [20070320] > ACPI Error (utmutex-0421): Mutex [0] is not acquired, cannot release [20070320] > ACPI Error (exutils-0250): Could not release AML Interpreter mutex [20070320] > ACPI Exception (utmutex-0376): AE_TIME, Thread 186B0 could not acquire > Mutex [0] [20070320] > ACPI Error (exutils-0180): Could not acquire AML Interpreter mutex [20070320] > ACPI Error (utmutex-0421): Mutex [0] is not acquired, cannot release [20070320] > ACPI Error (exutils-0250): Could not release AML Interpreter mutex [20070320] > > The problem is it doesnt happens always, but with soft reset there is > (perceived) > bigger chance to happen. Also kernel without WITNESS and other debug > options have much bigger > chance for this error to happen. nooptions KDB nooptions DDB nooptions GDB nooptions INVARIANTS nooptions INVARIANT_SUPPORT nooptions WITNESS nooptions WITNESS_SKIPSPIN no changes =( any idea?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?497B7A7A.3080103>