Date: Mon, 15 Sep 2003 17:53:02 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Doug White <dwhite@gumbysoft.com> Cc: current@freebsd.org Subject: Re: mystery kernel spew Message-ID: <20030915075301.GA14775@cirb503493.alcatel.com.au> In-Reply-To: <20030914191114.C96749@carver.gumbysoft.com> References: <31929.12.238.113.137.1063485645.squirrel@mail.yazzy.org> <20030914102130.K93499@carver.gumbysoft.com> <33165.12.238.113.137.1063565187.squirrel@mail.yazzy.org> <20030914191114.C96749@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 14, 2003 at 07:13:09PM -0700, Doug White wrote: >Incidentally, if you are getting wrapping even without this, you can use a >serial console to capture the output. I've had to do this for doing nasty >ACPI debugging with lots of the options enabled. For kernel spew, you can also increase the kernel message buffer: # Size of the kernel message buffer. Should be N * pagesize. options MSGBUF_SIZE=40960 And for the VTYs, you can increase the scroll-back size: options SC_HISTORY_SIZE=200 # number of history buffer lines Both these are kernel compile-time options. Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030915075301.GA14775>