From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 9 22:33:11 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 9FB1916A4CE for ; Tue, 9 Nov 2004 22:33:11 +0000 (GMT) Received: from chons.visualtech.com (b.mx.visualtech.com [208.16.19.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32C3843D2F for ; Tue, 9 Nov 2004 22:33:11 +0000 (GMT) (envelope-from adamk@voicenet.com) Received: from [192.168.0.99] (pcp04364354pcs.glstrt01.nj.comcast.net [68.44.156.246]) by chons.visualtech.com (Postfix) with ESMTP id 705C4A1AF; Tue, 9 Nov 2004 17:33:10 -0500 (EST) Message-ID: <419145A7.3000406@voicenet.com> Date: Tue, 09 Nov 2004 17:33:11 -0500 From: Adam K Kirchhoff User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5 X-Accept-Language: en MIME-Version: 1.0 To: Nate Lawson References: <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org> <41911D01.1090303@voicenet.com> <4191201A.4080406@root.org> <4191330A.7040707@voicenet.com> <41913F15.9060701@root.org> In-Reply-To: <41913F15.9060701@root.org> 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:33:11 -0000 Nate Lawson wrote: > 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 This one would appear to be the culprit. When I tried it, it locked up immediately. I rebooted, tried the throttle_state one, waited a few minutes, and all was fine. Tried the cx_lowest one, and it locked up again within a few seconds. > 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. > Unfortunately, that's proving difficult. Even with the "option BREAK_TO_DEBUGGER" line in the kernel config, ctrl-alt-backspace isn't dropping me to the debugger. Adam