Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Sep 2001 16:22:36 -0700 (PDT)
From:      Matt Dillon <dillon@earth.backplane.com>
To:        Ian Dowse <iedowse@maths.tcd.ie>
Cc:        Julian Elischer <julian@elischer.org>, hackers@freebsd.org
Subject:   Re: VM Corruption - stumped, anyone have any ideas? 
Message-ID:  <200109242322.f8ONMaT97469@earth.backplane.com>
References:   <200109250001.aa92227@salmon.maths.tcd.ie>

next in thread | previous in thread | raw e-mail | index | archive | help

:>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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109242322.f8ONMaT97469>