From owner-freebsd-current  Mon Nov  9 06:47:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA08830
          for freebsd-current-outgoing; Mon, 9 Nov 1998 06:47:31 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08823
          for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 06:47:27 -0800 (PST)
          (envelope-from jfieber@fallout.campusview.indiana.edu)
Received: from localhost (jfieber@localhost)
	by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA07111;
	Mon, 9 Nov 1998 09:45:37 -0500 (EST)
Date: Mon, 9 Nov 1998 09:45:37 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Brian Feldman <green@unixhelp.org>
cc: garman@earthling.net, current@FreeBSD.ORG, julian@whistle.com,
        wollman@khavrinen.lcs.mit.edu
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.4.05.9811082226380.11650-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811090932230.462-100000@fallout.campusview.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, 8 Nov 1998, Brian Feldman wrote:

> Device      1K-blocks     Used    Avail Capacity  Type
> /dev/wd0s1b    102400    12300    89972    12%    Interleaved
> /dev/wd1s1b    102400    12408    89864    12%    Interleaved
> Total          204544    24708   179836    12%
>  This is normal usage after
> swap_pager: suggest more swap space: 157 MB
> swap_pager: out of swap space
> pid 5795 (memory), uid 1000, was killed: out of swap space

I don't think this illustrates bug we are trying to smoke out
though. This is showing the "memory" process as being killed,
presumably because it went overboard on memory consumption.

The dying daemon bug seems to manifists itself in the death of
innocent bystander processes and usually by a signal 11, not by
"out of swap space".  Note these two observations:

   Date: Sun, 8 Nov 1998 15:26:48 -0800 (PST)
   From: Julian Elischer <julian@whistle.com>
   Message-ID: <Pine.BSF.3.95.981108152353.12341D-100000@current1.whistle.com>

   It's been a while since we looked at it closely but it appeared
   that a page of useful memeory was suddenly unmapped from the
   process.

   Date: Sun, 8 Nov 1998 23:17:00 -0500 (EST)
   From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
   Message-Id: <199811090417.XAA13563@khavrinen.lcs.mit.edu>

   It seems, so far as I was able to characterize, to happen to
   daemons which are *swapped out* at the time of the memory
   shortage.  If it's active enough to still be in core, it doesn't
   get spammed.

-john


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message