From owner-freebsd-current Thu Jun 6 10:40:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA19713 for current-outgoing; Thu, 6 Jun 1996 10:40:40 -0700 (PDT) Received: from relay-4.mail.demon.net (relay-4.mail.demon.net [158.152.1.108]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA19703 for ; Thu, 6 Jun 1996 10:40:35 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id ai07968; 6 Jun 96 17:10 GMT Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa23625; 6 Jun 96 18:04 +0100 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id CAA11652; Thu, 6 Jun 1996 02:06:46 GMT Date: Thu, 6 Jun 1996 02:06:46 GMT Message-Id: <199606060206.CAA11652@jraynard.demon.co.uk> From: James Raynard To: jehamby@lightside.com MMDF-Warning: Unable to confirm address in preceding line at relay-4.mail.demon.net CC: Gary.Jennejohn@munich.netsurf.de, freebsd-current@freebsd.org In-reply-to: (message from Jake Hamby on Wed, 5 Jun 1996 15:40:38 -0700 (PDT)) Subject: Re: More on VM, swap leaks Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Looks to me like you might have a bad SIMM, Greg. > > Another possibility is a bad emacs binary. Especially since as part of > the compilation process, emacs runs itself, loads in a bunch of LISP, > then pukes itself out as a new executable. I shudder to think what could > happen if a buggy kernel or bad SIMM decided to rear its head at that point. I'm having the same problems as well, and the Emacs binary was the first thing I suspected. I have rebuilt it several times, with various combinations of debug and optimisation flags (including none), with no apparent difference whatsoever. I've also swapped around SIMMs as well - I have 6 different SIMMs here, and have tried all the possible permutations of those as well. I accept that it may possibly be a problem with my system, but I think it's unlikely, as the problems started as soon as I ran the new VM code and none of the "obvious" solutions have fixed them. The only time I've tried running outside X, the kernel panicked at the point where Emacs would normally crash, with "freeing page held". Incidentally, it's not exclusively Emacs that crashes - I have had atrun exiting with a SIGBUS a couple of times as well, according to the logs. -- James Raynard, Edinburgh, Scotland | http://freefall.freebsd.org/~jraynard/ james@jraynard.demon.co.uk | jraynard@freebsd.org