From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 15 22:43:17 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D44D737B401 for ; Tue, 15 Jul 2003 22:43:17 -0700 (PDT) Received: from mail.econolodgetulsa.com (mail.econolodgetulsa.com [198.78.66.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7357B43F85 for ; Tue, 15 Jul 2003 22:43:17 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Received: from mail (mail [198.78.66.163])h6G5hJnW040655 for ; Tue, 15 Jul 2003 22:43:19 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Date: Tue, 15 Jul 2003 22:43:19 -0700 (PDT) From: Josh Brooks To: freebsd-hackers@freebsd.org Message-ID: <20030715223653.Y36933-100000@mail.econolodgetulsa.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: running 5.1-RELEASE with no procfs mounted (lockups?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 05:43:18 -0000 Hello, I have loaded two 5.1-RELEASE systems, both of them have PROCFS and PSEUDOFS in the kernel, and yet neither of them have a procfs mounted. There is no procfs line in /etc/fstab by default, and no procfs is mounted on the system in any way. Question 1: Is this intentional ? Is it no longer needed/recommended to run a procfs ? One of the systems, the one I am doing all the work on, is an SMP system, and it keeps locking up on me - the lockups are always the same - things are going fine, and suddenly a process fails to complete - maybe it is "pwd", maybe I type :q! in "vi" and it just sticks there - either way, randomly, processes just begin to lock up ... if I log in on another session, I can see the PID, but I cannot kill it - I can kill -9 (PID) 100 times and it will still exist. Eventually the entire system will lock up, although you can always ping the system. Question 2: Is this because I am running without procfs ? Or have these type of problems been seen in 5.1-RELEASE by other causes ? thank!