From owner-cvs-all@FreeBSD.ORG Tue Aug 17 21:07:01 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14A8B16A4CE; Tue, 17 Aug 2004 21:07: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 C624043D4C; Tue, 17 Aug 2004 21:07:00 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i7HL6x8U019317; Tue, 17 Aug 2004 14:06:59 -0700 Message-ID: <41227373.4090800@root.org> Date: Tue, 17 Aug 2004 14:06:59 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "David W. Chapman Jr." References: <200408171836.i7HIa7SQ079437@repoman.freebsd.org> <20040817191227.GA54933@minubian.inethouston.net> In-Reply-To: <20040817191227.GA54933@minubian.inethouston.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: cvs-src@FreeBSD.org cc: Nate Lawson cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi_cmbat.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2004 21:07:01 -0000 David W. Chapman Jr. wrote: > On Tue, Aug 17, 2004 at 06:36:07PM +0000, Nate Lawson wrote: > >>njl 2004-08-17 18:36:07 UTC >> >> FreeBSD src repository >> >> Modified files: >> sys/dev/acpica acpi_cmbat.c >> Log: >> Fix a deadlock on boot for some systems where reading the battery status >> also generates a notify. Since we held the lock over this call, the >> notify never got to run and the battery status read never returned. >> Document this also. >> > > I've had a problem booting -CURRENT on my laptop for quite some > time. It would completely lock the machine while loading the kernel. Might this > fix that? > Depends when "quite some time" was and what you mean by "loading the kernel". If it appeared on Aug. 12 and happens at the end of boot right after starting init, this is likely to fix your problem. -- Nate