From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 16 15:44:02 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A31CE16A401 for ; Mon, 16 Jul 2007 15:44:02 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 6EBCC13C48E for ; Mon, 16 Jul 2007 15:44:02 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 55849 invoked from network); 16 Jul 2007 15:44:02 -0000 Received: from ppp-71-139-42-13.dsl.snfc21.pacbell.net (HELO ?10.0.0.15?) (nate-mail@71.139.42.13) by root.org with ESMTPA; 16 Jul 2007 15:44:02 -0000 Message-ID: <469B923C.9090805@root.org> Date: Mon, 16 Jul 2007 08:43:56 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.4 (X11/20070620) MIME-Version: 1.0 To: hartzell@alerce.com References: <18074.33681.27885.568308@almost.alerce.com> <469AA815.9060906@root.org> <18074.44281.478078.454771@almost.alerce.com> <469B0776.4090600@FreeBSD.org> <18075.35687.203548.890195@almost.alerce.com> In-Reply-To: <18075.35687.203548.890195@almost.alerce.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, Doug Barton Subject: Re: acpi_smbus_read_2: AE_ERROR 0x10 on a Mac Pro running -STABLE X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2007 15:44:02 -0000 George Hartzell wrote: > Doug Barton writes: > > George Hartzell wrote: > > > > > The top of the dmesg -v output seems to have scrolled out of the > > > buffer. > > > > You may be able to find what you're looking for in > > /var/run/dmesg.boot, or you could enable the console log facility in > > syslog.conf. > > dmesg.boot is also missing a lot of stuff off the top. enabling > console.* in syslog.conf doesn't pick up anything until fairly late in > the boot process. > > It looks like I can add a MSGBUF_SIZE option to my kernel config and > bump up the size of the buffer. Don't know what the downside would be > if I make it too big, but I'll give it a try if it's useful. > > Nate, is there info that you're missing up at the top of my verbose > dmesg output? No, it's fine. However, we do need to reduce bootverbose since it's grown a bit too large lately. > Is it odd that my mac pro (a workstation) is trying to talk to a smart > battery (I don't know that it has *any* battery...). Hmm. I'll see what I can find in the ASL. -Nate