From owner-freebsd-questions@FreeBSD.ORG Sun Sep 7 11:02:05 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9CA016A4BF for ; Sun, 7 Sep 2003 11:02:05 -0700 (PDT) Received: from typhoon.enabled.com (typhoon.enabled.com [216.218.220.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 392A643FF2 for ; Sun, 7 Sep 2003 11:02:05 -0700 (PDT) (envelope-from admin2@enabled.com) Received: from enabled.com (localhost.enabled.com [127.0.0.1]) by typhoon.enabled.com (8.12.9/8.12.9) with ESMTP id h87I240T000620 for ; Sun, 7 Sep 2003 11:02:04 -0700 (PDT) (envelope-from admin2@enabled.com) From: "admin" To: freebsd-questions@freebsd.org Date: Sun, 7 Sep 2003 10:02:04 -0800 Message-Id: <20030907175542.M69000@enabled.com> X-Mailer: Open WebMail 2.01 20030425 X-OriginatingIP: 131.161.240.206 (admin2) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: [newbie] 4.8-STABLE became unreachable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2003 18:02:06 -0000 well my machine just became unreachable and trying to figure out what to do about it. Its the first time in my history of using freeBSD to experience this. we have kernel firewall enabled and running portsentry as well. we power cycled to clear the situation as we could not log in via the console. there is nothing in the hosts.deny file to create this situation. uname -a output: FreeBSD typhoon.enabled.com 4.8-STABLE FreeBSD 4.8-STABLE #0: there was one recent modification to the Kernel to from 14 days ago. we increased PMAP_SHPGPERPROC. options PMAP_SHPGPERPROC=300 this is the post we read: http://lists.freebsd.org/pipermail/freebsd-hackers/2003-May/000695.html I am suspecting hardware issues - perhaps the RAM memory board. 512MB single board. can somebody provide documentation or suggestions of ways we can figure out what is going on here? there is simply nothing in /var/log/messages relevant to anything creating this situation. in fact the machine remained having link and stuff. - Noah