From owner-freebsd-hackers Mon Sep 24 16:48: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 9B3EF37B407 for ; Mon, 24 Sep 2001 16:48:03 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA52161; Mon, 24 Sep 2001 17:27:41 -0700 (PDT) Date: Mon, 24 Sep 2001 17:27:40 -0700 (PDT) From: Julian Elischer To: Matt Dillon Cc: Ian Dowse , hackers@freebsd.org Subject: Re: VM Corruption - stumped, anyone have any ideas? In-Reply-To: <200109242322.f8ONMaT97469@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG not, I believe in 4.x we do in 5.x On Mon, 24 Sep 2001, Matt Dillon wrote: > > :>The pointers in the last few entries of the vm_page_buckets array got > :>corrupted when an agument to a function that manipulated whatever was next > :>in ram was 0, and it turned out that it was 0 because > :> of some PTE flushing thing (you are the one that found it... remember?) > : > :I think I've also seen a few reports of programs exiting with > :"Profiling timer expired" messages with 4.4. These can be caused > :by stack overflows, since the p_timer[] array in struct pstats is > :one of the things that I think lives below the per-process kernel > :stack. I wonder if they are related? Stack overflows could result > :in corruption of local variables, after which anything could happen. > : > :That said, hardware problems are still a possiblilty. > : > :Ian > > Hmm. Do we have a guard page at the base of the per process kernel > stack? > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message