From owner-freebsd-current Tue May 13 03:25:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA13243 for current-outgoing; Tue, 13 May 1997 03:25:54 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA13238 for ; Tue, 13 May 1997 03:25:52 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id MAA29112; Tue, 13 May 1997 12:26:58 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id MAA03900; Tue, 13 May 1997 12:26:31 +0200 (MEST) From: Christoph Kukulies Message-Id: <199705131026.MAA03900@gil.physik.rwth-aachen.de> Subject: Re: weirdo NFS (?) ld problem ? In-Reply-To: from Doug Rabson at "May 13, 97 11:15:58 am" To: dfr@nlsystems.com (Doug Rabson) Date: Tue, 13 May 1997 12:26:31 +0200 (MEST) Cc: kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-current@freefall.FreeBSD.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Tue, 13 May 1997, Christoph Kukulies wrote: > > > > > I upgraded our NIS/YP NFS cluster of FreeBSD machines to 3.0-current > > recently (to have real world test conditions :). > > > > One machine acts as NIS and NFS server. When one of my 'power' users is > > compiling and linking a big physics program on the nfs client > > (The executable is 8.5 MB in size) and he's starting it for the first time > > he gets a Bus error. Starting it a second time he gets > > the normal behaviour like printing the startup screen of the program. > > > > When he does the same thing on the server the program behaves fine. > > > > The client is a PPRO/200. The server is a P5/150. The directories the > > program sources,objects and binaries reside in are in a mounted > > /home tree. So I'm suspecting a NFS/VM/cache problem. I could reproduce it on a 486 client in the same configuration. Same picture. > > I am pretty sure there is at least one NFS/VM bug since there are plenty > of PRs about mmap not working properly in NFS. I have been putting off > looking for this one since the VM system scares me. I'll have to get to > it soon though :-(. OK. Fine. If you need my environment for reproducing the problem I could either give you access to my machine or send you the tree with the program to reproduce the problem. I don't know whether ld uses mmap. And it seems to occur always the first time after the binary image has been built (ld). Or where do you think mmap comes into the game? > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 951 1891 > > -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de