From owner-freebsd-questions@FreeBSD.ORG  Sat Dec  2 17:40:04 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id E62F616A40F
	for <freebsd-questions@freebsd.org>;
	Sat,  2 Dec 2006 17:40:04 +0000 (UTC) (envelope-from spork@bway.net)
Received: from xena.bway.net (xena.bway.net [216.220.96.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E57DF43C9D
	for <freebsd-questions@freebsd.org>;
	Sat,  2 Dec 2006 17:39:42 +0000 (GMT) (envelope-from spork@bway.net)
Received: (qmail 68853 invoked by uid 0); 2 Dec 2006 17:40:03 -0000
Received: from unknown (HELO white.nat.fasttrackmonkey.com)
	(spork@bway.net@216.220.116.154)
	by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP;
	2 Dec 2006 17:40:03 -0000
Date: Sat, 2 Dec 2006 12:40:16 -0500 (EST)
From: Charles Sprickman <spork@bway.net>
X-X-Sender: spork@white.nat.fasttrackmonkey.com
To: freebsd-questions@freebsd.org
Message-ID: <Pine.OSX.4.61.0612021238420.13208@white.nat.fasttrackmonkey.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: very odd log entries (sysctl)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Dec 2006 17:40:05 -0000

Hi all,

Had a machine lock up recently.  When I got into it, I found that 
/var/log/messages and the dmesg buffer were filled with stuff like this:

Dec  1 18:17:14 h19 /kernel: 8 sendspace RW *Handler Int
Dec  1 18:17:14 h19 /kernel: 9 recvspace RW *Handler Int
Dec  1 18:17:14 h19 /kernel: 10 keepinit RW *Handler Int
Dec  1 18:17:14 h19 /kernel: 11 pcblist R  *Handler
Dec  1 18:17:14 h19 /kernel: 12 delacktime RW *Handler Int
Dec  1 18:17:14 h19 /kernel: 100 log_in_vain RW *Handler Int
Dec  1 18:17:14 h19 /kernel: 101 blackhole RW *Handler Int
Dec  1 18:17:14 h19 /kernel: 102 delayed_ack RW *Handler Int
Dec  1 18:17:14 h19 /kernel: 103 insecure_rst RW *Handler Int
Dec  1 18:17:14 h19 /kernel: 104 reass RW Node
Dec  1 18:17:14 h19 /kernel: 100 maxsegments R  *Handler Int
Dec  1 18:17:15 h19 /kernel: 101 cursegments R  *Handler Int
Dec  1 18:17:15 h19 /kernel: 102 overflows R  *Handler Int

Those seem to correspond to sysctl variables.

Any idea why the kernel would start spitting out sysctl mibs to the log?

Thanks,

Charles