Re: mystery kernel spew
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mystery kernel spew
On Sat, 13 Sep 2003, masta wrote: For some time now I've have an issue with a dell laptop I use. It spews a bunch of kernel junk after init is spawned, and the spew causes my dmesg to become too full to actually produce a file I can send to the list that is meaningfull. I remember this :) This is probably because you have a syntax error in sysctl.conf. The stuff thats printed is the sysctl tree. Its a debugging feature, although I've forgotten what exactly triggers it. sysctl.conf should be name=value pairs like this: kern.maxfiles=16384 -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mystery kernel spew
I owe you a beer Doug (or a soda-pop)! ;) You were correct about the sysctl.conf being the root-cause of the kernel spew. My sysctl.conf is having these lines: #security.bsd.see_other_uids=0 sysctl net.inet.tcp.blackhole=1 sysctl net.inet.udp.blackhole=1 See the fau paux? I must have decided to yank/paste the example incorrectly from the BLACKHOLE(4) manual, because I also included the sysctl word at the begining of the two lines. To error is human, but this is utter comedy if you ask me. =) I'm now able to use dmesg again, wuhoo! Thanks! -masta Allegedly Doug Whitesaid On Sat, 13 Sep 2003, masta wrote: For some time now I've have an issue with a dell laptop I use. It spews a bunch of kernel junk after init is spawned, and the spew causes my dmesg to become too full to actually produce a file I can send to the list that is meaningfull. I remember this :) This is probably because you have a syntax error in sysctl.conf. The stuff thats printed is the sysctl tree. Its a debugging feature, although I've forgotten what exactly triggers it. sysctl.conf should be name=value pairs like this: kern.maxfiles=16384 -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org __ __ _ | \/ | __ _ ___| |_ __ _ | |\/| |/ _` / __| __/ _` | | | | | (_| \__ \ || (_| | |_| |_|\__,_|___/\__\__,_| [EMAIL PROTECTED] http://wifibsd.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mystery kernel spew
On Sun, 14 Sep 2003, masta wrote: I owe you a beer Doug (or a soda-pop)! ;) hehe :) You were correct about the sysctl.conf being the root-cause of the kernel spew. Mike Smith ran into it one day and we spent some time debugging it. Someone made the observation that they were sysctl items and not function calls and that tipped us off. 'sysctl sysctl' is a magic incantation to dump the sysctl tree. There's a couple of other magic words. #security.bsd.see_other_uids=0 sysctl net.inet.tcp.blackhole=1 sysctl net.inet.udp.blackhole=1 Heh, you even had an example :) 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. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
mystery kernel spew
Howdy list, For some time now I've have an issue with a dell laptop I use. It spews a bunch of kernel junk after init is spawned, and the spew causes my dmesg to become too full to actually produce a file I can send to the list that is meaningfull. But I'm tired of the spew, so I've decided to proved the info I have at hand. Hopefully somebody will understand what the mystery kernel spew is and give me a clue. Later on I'll see if I can do the old ctrl+alt+esc debuger trick while it spews to get a backtrace thingy. In the mean time does anybody know how to increase the buffer used by dmesg so I can have it include the entire kerenel output? Thanks in advance =) __ __ _ | \/ | __ _ ___| |_ __ _ | |\/| |/ _` / __| __/ _` | | | | | (_| \__ \ || (_| | |_| |_|\__,_|___/\__\__,_| [EMAIL PROTECTED] http://wifibsd.org dmesg.boot Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
