From owner-freebsd-alpha Wed Jun 6 7:11:39 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4861F37B406; Wed, 6 Jun 2001 07:11:36 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA04395; Wed, 6 Jun 2001 10:11:35 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f56EB5o34575; Wed, 6 Jun 2001 10:11:05 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15134.14841.825808.882824@grasshopper.cs.duke.edu> Date: Wed, 6 Jun 2001 10:11:05 -0400 (EDT) To: obrien@FreeBSD.ORG Cc: John Baldwin , alfred@FreeBSD.ORG, Freebsd-alpha@FreeBSD.ORG Subject: Re: -current kernel still considered dangerous In-Reply-To: <20010605183942.G95616@dragon.nuxi.com> References: <20010605170234.B95616@dragon.nuxi.com> <15133.30473.480681.753965@grasshopper.cs.duke.edu> <20010605174808.F95616@dragon.nuxi.com> <20010605183942.G95616@dragon.nuxi.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org David O'Brien writes: > On Tue, Jun 05, 2001 at 05:48:08PM -0700, David O'Brien wrote: > > On Tue, Jun 05, 2001 at 08:19:21PM -0400, Andrew Gallatin wrote: > > > Its almost certainly a module loaded after boot, since the address > > > does not lie in K0SEG. Could this be the linulator running ldconfig? > > I am going to go with osf1 compat module. Running the dnetc binary > triggers the panic. The dnetc installation that I have can be found at > http://people.freebsd.org/~obrien/dnetc-axp-panics.tar.gz > > Since kgdb is hitting "heuristic-fence-post", how should I proceed in > debugging this? I just built a kernel statically & found it. Apparently, the vm_mtx must be held around vm_map_find(), vm_map_findspace(), and vm_map_lookup_entry(), and probably others. Is there any documentation what the locking requirements of various vm functions are now? I tested osf1 after my initial set of commits to catch alpha up to x86, but an assert must have been added since then. Anyway, grab 1.16 of osf1_misc.c and 1.6 of imgact_osf1.c I can now run netscape with a top-of-the tree kernel. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message