From owner-freebsd-current Tue Mar 25 21:41:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA17367 for current-outgoing; Tue, 25 Mar 1997 21:41:51 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA17359 for ; Tue, 25 Mar 1997 21:41:48 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id VAA00552 for ; Tue, 25 Mar 1997 21:41:44 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA25237; Wed, 26 Mar 1997 16:09:06 +1030 (CST) From: Michael Smith Message-Id: <199703260539.QAA25237@genesis.atrad.adelaide.edu.au> Subject: Re: SIGTERMs killing X In-Reply-To: <199703260450.VAA27126@phaeton.artisoft.com> from Terry Lambert at "Mar 25, 97 09:50:50 pm" To: terry@lambert.org (Terry Lambert) Date: Wed, 26 Mar 1997 16:09:05 +1030 (CST) Cc: drussell@saturn-tech.com, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > in the last few days for no apparent reason. > > > > Mar 24 12:22:23 586quick166 /kernel: pid 218 (XF86_SVGA), uid 0: exited on signal 6 > > Mar 25 11:27:22 586quick166 /kernel: pid 7136 (XF86_SVGA), uid 0: exited on signal 6 > > > > I can't for the life of me determine why it would have got an ABORT > > signal.... Where would that be coming from? The machine is just sitting > > there idle (AFAIK, anyway... :)) and when I get home from work, for > > example, it's no longer running X. > > It is because FreeBSD is overcommiting memory in it's VM system. > > I am sorry for you that you got this error... > > I am glad you got this error, because you are a real-world example > of a need for a tunable which I have been lobbying for for four years. > Now I have a sample case, and I am happy because I can flagellate > the powers that be every time the topic comes up in the future. 8-). > > > What it means is that your VM space for your process has been > destroyed (you can see this by looking in /sys/kern/kern_exec.c). Actually, in all my (few) years of abusing FreeBSD systems, I have never, to my knowledge, received a SIGABRT for any reason other than memory corruption, either through VM breakage or good old PC memory crap. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[