From owner-freebsd-stable Thu Jul 26 21:54:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from luke.cpl.net (luke.cpl.net [63.169.72.3]) by hub.freebsd.org (Postfix) with ESMTP id 6BE7E37B403 for ; Thu, 26 Jul 2001 21:54:50 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.11.4/8.11.3) id f6R4tjD10630 for stable@freebsd.org; Thu, 26 Jul 2001 21:55:45 -0700 (PDT) Date: Thu, 26 Jul 2001 21:55:45 -0700 From: Shawn Ramsey To: stable@freebsd.org Subject: Crashing every two hours! Message-ID: <20010726215545.A10382@cpl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just upgraded one of our servers from 4.1.1. That server had never crashed, or even needed to be rebooted. We just upgraded it to 4.3-Stable. It was CVSupp'd around 10:00am yesterday. The world built w/o a hitch and no errors during installation. Now, about every 2 and half hours, the system is panicking. :( This is the error it gets : panic: vm_fault fault on nofault entry, address d0b24000 I am about ready to try downgrading to 4.2-RELEASE. Will this be a problem? Or does anyone know if telnetd in 4.1.1 can be patched against the recent root exploit? This is the worst I have ever seen a FreeBSD machine act... especially when the previous released OS had never crashed or even hippoced once. Thanks for any insight... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message