Date: Thu, 14 Jun 2001 11:59:42 -0400 From: Alfred Perlstein <alfred@freebsd.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: jhb@freebsd.org;, freebsd-alpha@freebsd.org Subject: Re: alpha pmap corruption continues Message-ID: <20010614115942.B1832@superconductor.rush.net> In-Reply-To: <15144.55776.3763.28141@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Jun 14, 2001 at 11:36:00AM -0400 References: <15144.55776.3763.28141@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
* Andrew Gallatin <gallatin@cs.duke.edu> [010614 11:36] wrote: > > John, > > With your http://people.freebsd.org/~jhb/patches/vm.patch and > with rev 1.60 of alpha/trap.c reverted, I'm still seeing what > looks like pmap corruption with a (mostly) GENERIC kernel on a UP > alpha a few minutes into a -j32 buildworld. [snip] > > db> e vm_faults_no_vm_mtx > vm_faults_no_vm_mtx: b7c70 > db> e vm_faults_no_giant > vm_faults_no_giant: 0 > db> > > > So.. maybe this is a dumb question, but it looks like the vm_mtx was > locked in vm_map_lookup as part of the vm fault path. But, it SHOULD > have gotten locked in exit1(), around pmap_remove_pages, shouldn't it? So, > shouldn't there have been a lock-recursion message in there? > > I don't understand. Since John has made giant required by all vm code again, the only panics you should see relating to vm_mtx are failed assertions, that is unless John missed a spot where giant was needed. -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010614115942.B1832>