From owner-freebsd-current Wed Feb 23 10:33:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id AABD737B974 for ; Wed, 23 Feb 2000 10:33:50 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id FAA22281; Thu, 24 Feb 2000 05:37:54 +1100 Date: Thu, 24 Feb 2000 05:33:34 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: David Gilbert Cc: freebsd-current@FreeBSD.ORG Subject: Re: Wierd AMD panics caused by VMWare? In-Reply-To: <14515.59795.632514.748870@trooper.velocet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Feb 2000, David Gilbert wrote: >... > I have half-a-dozen crash dumps of this nature. For me, it always > happens in fdcopy(). This may be due to the fact that the machine is > running a large apache config --- so fork() is something it's doing > often. See PR 16568. pmap_remove_all() doesn't flush the TLB properly in FreeBSD-3.x on i386's. Somehow this doesn't cause many problems, but it fairly reliably breaks the free() in fdfree() when there was a file descriptor larger than about 1000 (this gives a free() of more than MAXALLOCSAVE = 2 pages) when there is a lot of fork() activity. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message