From owner-freebsd-stable@FreeBSD.ORG Wed Nov 23 02:36:01 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3B6A16A41F; Wed, 23 Nov 2005 02:36:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 590B243D62; Wed, 23 Nov 2005 02:35:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAN2ZuQL032449; Tue, 22 Nov 2005 19:35:57 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4383D58C.5040004@samsco.org> Date: Tue, 22 Nov 2005 19:35:56 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <4383C083.6010300@root.org> In-Reply-To: <4383C083.6010300@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: acpi@freebsd.org, stable@freebsd.org, FreeBSD Current Subject: Re: [Fwd: cvs commit: src/sys/dev/acpica acpi_cmbat.c] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 02:36:01 -0000 Nate Lawson wrote: > Here is a patch that should fix the battery hangs on RELENG_6. It was > tested to work fine, although I need testing from an affected user to > verify it fixes the problem. It was committed to HEAD and will be MFCed > if it fixes the problem. Thanks a lot! > > I'm a bit disappointed that no one reported this problem in the 2 weeks > it was present in 7-current. If you have the time to run -current on at > least one partition of your laptop, that would assist me greatly. Don't feel too bad. You committed it right after 6.0 was released, so people were either looking at 6.0 or taking a breather from the release work. Scott