From owner-freebsd-hackers Mon Sep 24 16: 1:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 364F137B425 for ; Mon, 24 Sep 2001 16:01:12 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 Sep 2001 00:01:11 +0100 (BST) To: Julian Elischer Cc: Matt Dillon , hackers@freebsd.org Subject: Re: VM Corruption - stumped, anyone have any ideas? In-Reply-To: Your message of "Mon, 24 Sep 2001 15:44:15 PDT." Date: Tue, 25 Sep 2001 00:01:10 +0100 From: Ian Dowse Message-ID: <200109250001.aa92227@salmon.maths.tcd.ie> 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 > >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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message