From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 9 22:05:24 2004 Return-Path: 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 221A716A4D2 for ; Tue, 9 Nov 2004 22:05:24 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30C7243D48 for ; Tue, 9 Nov 2004 22:05:12 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iA9M5AFp021524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Nov 2004 14:05:11 -0800 Message-ID: <41913F15.9060701@root.org> Date: Tue, 09 Nov 2004 14:05:09 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam K Kirchhoff References: <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org> <41911D01.1090303@voicenet.com> <4191201A.4080406@root.org> <4191330A.7040707@voicenet.com> In-Reply-To: <4191330A.7040707@voicenet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: Laptop troubles... X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2004 22:05:24 -0000 Adam K Kirchhoff wrote: >> The -v is just to get more info from right before the hang. Try doing >> things like sysctl -a, kldload linux, or whatever to see if you can >> isolate what's triggering this. >> > > Woohoo... It's /etc/rc.d/devd: > # ./cron start > Starting cron. > # ./devd start > Starting devd. > hw.acpi.cpu.cx_lowest: C1 -> C3 > hw.acpi.cpu.throttle_state: 8 -> 8 > > And then, immediately, the lockup. Want me to try adding the > BREAK_TO_DEBUGGER option in the kernel and see if I can get a backtrace? Ok, this is helpful. That's actually /etc/rc.d/power_profile switching based on input from devd as to the AC line state. Try manually running the sysctls: sysctl hw.acpi.cpu.cx_lowest=C3 sysctl hw.acpi.cpu.throttle_state=8 ...waiting after each one for a minute to see if there's a hang. Getting a backtrace would help, yes. -- Nate