From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 16:30:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E23F637B404 for ; Wed, 2 Jul 2003 16:30:07 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 26F3C43FE5 for ; Wed, 2 Jul 2003 16:30:07 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 90756 invoked by uid 1000); 2 Jul 2003 23:30:08 -0000 Date: Wed, 2 Jul 2003 16:30:08 -0700 (PDT) From: Nate Lawson To: John Baldwin In-Reply-To: Message-ID: <20030702162816.Q90754@root.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi-jp@jp.freebsd.org cc: current@freebsd.org Subject: RE: Updated ec-burst.diff patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2003 23:30:08 -0000 On Wed, 2 Jul 2003, John Baldwin wrote: > On 01-Jul-2003 Nate Lawson wrote: > > Please download and try the new version. It correctly implements burst > > mode to the best of the 2.0 spec. Like the previous message, please > > report the appropriate dmesgs ("acpi_ec0*" and "EC Waited*") and any > > errors or regression. I've tested "du -a /" while plugging/unplugging the > > power cable on my laptop many times with no errors. > > > > I haven't received any feedback yet. This WILL hit the tree in a few > > weeks because it fixes known problems. Test it now or test it then. :) > > This made my machine a LOT worse. Previously I would occasionally get > failed EcRead's do to timeout reading the battery and thermal status after > the machine had been up for a while, but battery status still worked. > Setting the event_driven tunable made no difference. With this patch, the > EC is very, very broke. I now get spammed during bootup with a flood of > failures from EcCommand: > > EC Waited max 16 cycles, event occurred > acpi_ec0: EcCommand: no response to 80, disabling burst mode It appears your machine does not properly support burst mode. I suspected that may be the case, which is what I was checking. I'll be doing some more work on the patch and post it again. > This has seriously hosed my machine. Um, you can go back to the old acpi module and I doubt it caused any loss. Thanks for testing. -Nate