From owner-freebsd-bugs Fri Jan 8 16:00:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14260 for freebsd-bugs-outgoing; Fri, 8 Jan 1999 16:00:08 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14251 for ; Fri, 8 Jan 1999 16:00:06 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id QAA07817; Fri, 8 Jan 1999 16:00:01 -0800 (PST) Received: (from nobody@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13677; Fri, 8 Jan 1999 15:53:14 -0800 (PST) (envelope-from nobody) Message-Id: <199901082353.PAA13677@hub.freebsd.org> Date: Fri, 8 Jan 1999 15:53:14 -0800 (PST) From: bellcanada@hotmail.com To: freebsd-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: www-1.0 Subject: kern/9399: If all memory fills up (VM and Real), nothing will run even if apps are closed to free up ram. Shutdown will not always work, and kernel reboot is common without a message. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 9399 >Category: kern >Synopsis: If all memory fills up (VM and Real), nothing will run even if apps are closed to free up ram. Shutdown will not always work, and kernel reboot is common without a message. >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 8 16:00:00 PST 1999 >Closed-Date: >Last-Modified: >Originator: Bell Guy >Release: 2.2.6 >Organization: >Environment: FreeBSD 2.2.6 >Description: I noticed this (and many more oddities) after installing FreeBSD from a 4 cd dist. I originaly started with 20Megs of Ram, and a 5M swap. The resason for the small swap is because of drive space limitations. Even thought the docs say 8M will work, that is not the case. If the machine uses up all the ram and swap, it basicly hangs. You can type, and it is responsive, but you cannot run anything, not even ls. All fail with an error message like : Cannot malloc - out of memmory .... or somthing like that. I did notice thought after increasing my swap from 5 to 15M, the machine still didn't do anything after running out of ram, but it did recover EVENTUALLY after closing everything (down to just a standard outside of X prompt). This is severe because of DoS attacks. >How-To-Repeat: Fill up all your memory ... :) .. >Fix: Don't allow ANYONE to use up all memory.... >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message