Date: Mon, 16 Jul 2007 08:43:56 -0700 From: Nate Lawson <nate@root.org> To: hartzell@alerce.com Cc: freebsd-acpi@freebsd.org, Doug Barton <dougb@FreeBSD.org> Subject: Re: acpi_smbus_read_2: AE_ERROR 0x10 on a Mac Pro running -STABLE Message-ID: <469B923C.9090805@root.org> In-Reply-To: <18075.35687.203548.890195@almost.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?469B923C.9090805>