Date: Wed, 15 Jul 2009 22:39:26 +0200 (CEST) From: Alexander Best <alexbestms@math.uni-muenster.de> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-current@freebsd.org Subject: Re: strange verbose boot log entry Message-ID: <permail-2009071520392680e26a0b00004335-a_best01@message-id.uni-muenster.de> In-Reply-To: <20090715195909.GK63413@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
thanks for the hint. that kernel option solved the problem. alex Dan Nelson schrieb am 2009-07-15: > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?permail-2009071520392680e26a0b00004335-a_best01>