Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Jul 2009 14:59:09 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Alexander Best <alexbestms@math.uni-muenster.de>
Cc:        freebsd-current@freebsd.org
Subject:   Re: strange verbose boot log entry
Message-ID:  <20090715195909.GK63413@dan.emsphone.com>
In-Reply-To: <permail-200907151952311e86ffa80000760d-a_best01@message-id.uni-muenster.de>
References:  <permail-200907151952311e86ffa80000760d-a_best01@message-id.uni-muenster.de>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 15), Alexander Best said:
> just booted r195677 (8.0-BETA1) with
> 
> verbose_loading="YES"
> boot_verbose="YES"
> 
> and noticed this strange /var/log/messages entry:
> 
> Jul 15 21:45:05 otaku syslogd: kernel boot file is /boot/kernel/kernel
> 
> Jul 15 21:45:05 otaku kernel: 8) <----------
> 
> Jul 15 21:45:05 otaku kernel: ACPI: MCFG 0x7fee7e80 0003C (v1 GBT    GBTUACPI 42302E31 GBTU 01010101)
> Jul 15 21:45:05 otaku kernel: ACPI: APIC 0x7fee7d00 00084 (v1 GBT    GBTUACPI 42302E31 GBTU 01010101)
> Jul 15 21:45:05 otaku kernel: ACPI: SSDT 0x7fee8520 003AB (v1  PmRef    CpuPm 00003000 INTL 20040311)
> 
> comments?

Your kernel message buffer is too small to store the entire verbose boot
sequence in memory before syslog can extract it.  It's a circular buffer, so
new entries overwrite the oldest ones.  The line just before the "ACPI:
MCFG" line was probably another ACPI line that happened to end in 8 and a
close-paren.  Adding this to your kernel and rebuilding should let you see
the entire boot output.  If something's still truncated, double it and try
again.

options         MSGBUF_SIZE=65536

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090715195909.GK63413>