Date: Sun, 17 Feb 2008 16:02:41 +1300 From: Jonathan Chen <jonc@chen.org.nz> To: Robert Huff <roberthuff@rcn.com> Cc: questions@freebsd.org, Steven Friedrich <FreeBSD@insightbb.com> Subject: Re: Shutdown anomaly Message-ID: <20080217030241.GA34692@osiris.chen.org.nz> In-Reply-To: <18359.26373.750798.755610@jerusalem.litteratus.org> References: <200802161142.53044.FreeBSD@insightbb.com> <20080216215521.GB12555@osiris.chen.org.nz> <18359.26373.750798.755610@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 16, 2008 at 05:43:17PM -0500, Robert Huff wrote:
> Jonathan Chen writes:
>
> > > I am seeing the following messages, which appear to indicate a memory
> > > overwrite:
> > > Waiting (max 60 seconds) for system processs 'vnlru' to stop...done
> > > Waiting (max 60 seconds) for system processs 'bufdaemon' to stop...done
> > > a
> > > iStyinncgi n(gm adxi s6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr0o
> > > cess 'syncer' to stop...0 0 done
> > > All buffers synced.
> > > Uptime: 8m9s
> >
> > It's an interleaved buffer messages on SMP systems. The problem is
> > known, but I haven't heard of a proposed solution yet.
>
> There is no fix.
> The workaround is to increase the size of the kernel printf()
> buffer. I don't remember how you do that ... but this is not a new
> issue - chech the archives for details.
The PRINTF_BUFR_SIZE=128 workaround doesn't work on the few systems
I've seen the issue on; but if you're interested, one way to do it is:
include GENERIC
ident GENERIC-1
options PRINTF_BUFR_SIZE=128
Cheers
--
Jonathan Chen <jonc@chen.org.nz>
----------------------------------------------------------------------
"If everything's under control, you're going too slow"
- Mario Andretti
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080217030241.GA34692>