From owner-freebsd-hackers Fri Jun 5 13:29:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06393 for freebsd-hackers-outgoing; Fri, 5 Jun 1998 13:29:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06343 for ; Fri, 5 Jun 1998 13:28:50 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA09631; Fri, 5 Jun 1998 13:27:27 -0700 (PDT) Message-Id: <199806052027.NAA09631@implode.root.com> To: wayne@msen.com cc: hackers@FreeBSD.ORG Subject: Re: Page fault in kernel In-reply-to: Your message of "Fri, 05 Jun 1998 14:13:38 EDT." From: David Greenman Reply-To: dg@root.com Date: Fri, 05 Jun 1998 13:27:27 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Based upon the various charters, I assume this is the correct place to >discuss kernel-level problems, if not I'm sure someone will correct me :-) > >We're looking at moving our Diablo-based nntp server from BSD/OS to >FreeBSD. Everything appears mostly OK, except that the machine reboots >every 36 hours or so. Did a bit of digging into the kernel and found >that the MGETHDR at line 432 of kern/uipc_socket.c is returning with >m = 0, which obviously causes the problem two lines later when it's >trying to be used. > >Before I go thrashing around trying to locate this, is this a known >problem with a patch avail? That indicates that you've run out of mbuf clusters. You don't want to do that. You can increase the number with the kernel option: options "NMBCLUSTERS=" Where is a number that is several thousand. You can see the current peak since the system was started with "netstat -m" (the second number in the mbuf clusters ratio is the peak, not the limit). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message