From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 16 15:14:46 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 C0F8C16A402 for ; Mon, 16 Jul 2007 15:14:46 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id 99B3E13C481 for ; Mon, 16 Jul 2007 15:14:46 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 3DFC633C62; Mon, 16 Jul 2007 08:15:25 -0700 (PDT) Received: from postfix.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "satchel.alerce.com", Issuer "alerce.com" (verified OK)) by merlin.alerce.com (Postfix) with ESMTP id F124A33C5B; Mon, 16 Jul 2007 08:15:24 -0700 (PDT) Received: by postfix.alerce.com (Postfix, from userid 501) id 78C78FB98D; Mon, 16 Jul 2007 08:14:47 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18075.35687.203548.890195@almost.alerce.com> Date: Mon, 16 Jul 2007 08:14:47 -0700 To: Doug Barton In-Reply-To: <469B0776.4090600@FreeBSD.org> References: <18074.33681.27885.568308@almost.alerce.com> <469AA815.9060906@root.org> <18074.44281.478078.454771@almost.alerce.com> <469B0776.4090600@FreeBSD.org> X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-acpi@freebsd.org 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 Reply-To: hartzell@alerce.com 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:14:46 -0000 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? 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...). g.