From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 9 19:53:01 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 4153816A4CE for ; Tue, 9 Nov 2004 19:53:01 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id F38AA43D1D for ; Tue, 9 Nov 2004 19:53:00 +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 iA9JqxFp017600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Nov 2004 11:53:00 -0800 Message-ID: <4191201A.4080406@root.org> Date: Tue, 09 Nov 2004 11:52:58 -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> In-Reply-To: <41911D01.1090303@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 19:53:01 -0000 Adam K Kirchhoff wrote: > Nate Lawson wrote: >> What happens if you boot single-user? > > So far, it's been fine. I've been in single user long enough to run > fsck on my filesystems... I launched sshd manually once (without any > problems) since that's where it appeared to lockup most frequently. > When I then continued into multi-user mode, it locked up around the time > it loaded the linux compat module. It's important to isolate this more. Try running some of the rc.d scripts to see if you can trigger it. I think there's an rc.d debug mode that prints everything before it does it also. Then just enable that feature and send me the last few lines it prints before hanging. >> >> You can't break to the debugger with ctrl-alt-backspace? > > Nope. Didn't realize that was usually a possibility, but when I tried it > just now, it didn't break into the debugger. Well, you have to have options BREAK_TO_DEBUGGER in the kernel for this to work. If you have it but this doesn't work, then it's a harder hang. If not, we can get debug info as to what's hung. >> Try a boot -v -s with the bad kernel and see how long it takes to hang >> while sitting there idle. >> > Well, so far so good. I've booted up with -s and -v... fsck'ed the > filesystems, and I'm now sitting at the single user prompt. I > ifconfiged my wireless card, and all seems well. I'm about to leave > work for the day. I'll leave it like this during my drive home and see > if it stays running the entire time. > > When I'm home, I'll reboot with -v -s and dump the kernel output to the > serial port, and then post it here. 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. -- Nate