From owner-freebsd-alpha Wed Jun 6 9:57:44 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 8F6BB37B403; Wed, 6 Jun 2001 09:57:41 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f56Gv6108102; Wed, 6 Jun 2001 09:57:06 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15134.14841.825808.882824@grasshopper.cs.duke.edu> Date: Wed, 06 Jun 2001 09:57:09 -0700 (PDT) From: John Baldwin To: Andrew Gallatin Subject: Re: -current kernel still considered dangerous Cc: Freebsd-alpha@FreeBSD.org, alfred@FreeBSD.org, obrien@FreeBSD.org 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 On 06-Jun-01 Andrew Gallatin wrote: > > 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. For now, yes. In theory they perhaps shouldn't require it. *sigh* The vm locking isn't done yet unfortunately. > 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. Not really, and it is in a state of flux right now. On my todo list is to change the vm_map's to be locked by a sx lock, and once that is done I will change those mtx_assert's to simply require the sx lock rather than the vm_mtx lock. However, I'm still not sure how vm_page's will be locked. vm_object's will probably have their own mutex or sx lock though. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message