From owner-freebsd-acpi@FreeBSD.ORG Mon Aug 21 07:28:18 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F78216A4DD for ; Mon, 21 Aug 2006 07:28:18 +0000 (UTC) (envelope-from acpi.dettloff@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id A591343D94 for ; Mon, 21 Aug 2006 07:28:11 +0000 (GMT) (envelope-from acpi.dettloff@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1470147wxd for ; Mon, 21 Aug 2006 00:28:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cveQrwO0GJyL1jFpMh85qf9G8UK+MyUdxhn9gtr4a72Y3eT3PTxo19gCS8PKfAwc6q8v7kF5LHLfEewQ6XbKvjdXtkp5Eofj7Xe03nl8OXHguKKYBi/e7eeYP+p7IlmY/cSUTFmzh2fdpFvJkdha4aTsJObOjregn0+YSJs9qgg= Received: by 10.90.71.12 with SMTP id t12mr92383aga; Mon, 21 Aug 2006 00:20:52 -0700 (PDT) Received: by 10.90.93.12 with HTTP; Mon, 21 Aug 2006 00:20:52 -0700 (PDT) Message-ID: Date: Mon, 21 Aug 2006 17:20:52 +1000 From: "Tim Dettloff" To: "Nate Lawson" In-Reply-To: <44E9498F.8030208@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44E9498F.8030208@root.org> Cc: freebsd-acpi@freebsd.org Subject: Re: Powerd makes computer hang X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Aug 2006 07:28:18 -0000 On 21/08/06, Nate Lawson wrote: > dmesg would be a good start. Is there some cpufreq driver running > besides acpi_throttle? Add hint.acpi_throttle.0.disabled="1" in > loader.conf, reboot, and then retry your test. > > My guess is acpi_throttle is just a wrapper around p4-tcc on your system. dmesg with and without cpufreq.ko loaded: http://www.studentergaarden.dk/~tim/FreeBSD/dmesg_cpufreq.txt http://www.studentergaarden.dk/~tim/FreeBSD/dmesg.txt If I set hint.acpi_throttle.0.disabled=1 i need to have cpufreq.ko loaded to be able to change the frequency, but in this case I have not been able to get it to hang. With acpi_throttle enabled it hangs both with and without cpufreq.ko loaded. Another interesting thing is that different configurations lists different freq_leves. acpi_throttle: dev.cpu.0.freq_levels: 1799/-1 1574/-1 1349/-1 1124/-1 899/-1 674/-1 449/-1 224/ -1 acpi_throttle and cpufreq: dev.cpu.0.freq_levels: 1800/25000 1600/20700 1400/18112 1200/15525 1000/12937 800/8600 700/7525 600/6450 500/5375 400/4300 300/3225 200/2150 100/1075 cpufreq: dev.cpu.0.freq_levels: 1791/25000 1592/20700 796/8600 (I think these are the values used in Windows, where it doesn't hang) One last thing. If I load cpufreq after having changed the cpufreq via acpi_throttle the values gets weird: dev.cpu.0.freq_levels: 7362/25000 6544/20700 5726/18112 4908/15525 4090/12937 3272/8600 2863/7525 2454/6450 2045/5375 1636/4300 1227/3225 818/2150 409/1075 Cheers, Tim