Date: Fri, 17 Sep 1999 15:04:55 +0200 (MET DST) From: Nick Hibma <nick.hibma@jrc.it> To: Sheldon Hearn <sheldonh@uunet.co.za> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: i386/13765: memory problem: compilation of emacs dies during dumping Message-ID: <Pine.GS4.4.10.9909171459400.9900-100000@elect8> In-Reply-To: <199909171240.FAA98258@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I reported a memory bug in FreeBSD. > > No, you reported a problem you were having compiling emacs on FreeBSD. > > I understand that your machine locked up, but we're talking about a 486, > here. How long did you leave it alone before deciding it had locked up. Could we get back to solving / ignoring the problem, instead of discussing who's bucket is better to make sand cakes in the sand pit? I'll try and see whether I can reproduce the problem on a machine here in the office by limitting the memory size of it in the kernel. How much swap did you have allocated on the machine? You were using a GENERIC kernel? Please produce the output of uname -a. > Basically, you're using an inredibly complicated How-To-Repeat to decide > that FreeBSD has a memory management problem. I'm pretty sure there are > numerous factors that could be causing the symptoms you're seeing. How much swap did you have allocated on the machine? If there was a lot of swap, you might run into a problem of heavy disk I/O locking up the machine. Any messages on virtual screen number 0? Any unsolvable corruption of the file system after rebooting? What else were you running at that time? X, emacs, or other big programs. Hope this helps. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GS4.4.10.9909171459400.9900-100000>