From owner-freebsd-current Mon Nov 29 13:47:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (assurance.rstcorp.com [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id A4CE615415 for ; Mon, 29 Nov 1999 13:47:15 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id QAA31813; Mon, 29 Nov 1999 16:48:40 -0500 Received: from proxy.rstcorp.com(216.112.242.5) by assurance.rstcorp.com via smap (V2.0) id xma031804; Mon, 29 Nov 99 21:47:52 GMT Received: from jabberwock.rstcorp.com (jabberwock.rstcorp.com [192.168.2.98]) by sandbox.rstcorp.com (8.8.8+Sun/8.8.8) with ESMTP id QAA28496; Mon, 29 Nov 1999 16:44:03 -0500 (EST) Received: by jabberwock.rstcorp.com (Postfix, from userid 93) id 722AB5AF0; Mon, 29 Nov 1999 16:46:25 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14402.62513.189527.729294@jabberwock.rstcorp.com> Date: Mon, 29 Nov 1999 16:46:25 -0500 (EST) From: "Viren R.Shah" To: Greg Lehey Cc: freebsd-current@FreeBSD.ORG Subject: Re: repeatable crash in -current (softupdates, NFS) In-Reply-To: <19991127195332.36233@mojave.sitaranetworks.com> References: <14399.63511.296802.242618@jabberwock.rstcorp.com> <19991127195332.36233@mojave.sitaranetworks.com> X-Mailer: VM 6.72 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R.Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Greg" == Greg Lehey writes: Greg> On Saturday, 27 November 1999 at 10:26:15 -0500, Viren R.Shah wrote: >> >> I'm running a -current system from Nov 26th (approx 4am EST). >> >> I can currently reliably crash the system by doing: >> >> ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html >> >> >> The crash only works when I do it on a NFS mounted filesystem. I'm >> using NFSv2/UDP. The server is a 3.2-STABLE FreeBSD box, running >> softupdates on the exported filesystem. I just checked that local >> filesystem on the server, and it is a 100% full. Can this just be put >> down to the known "softupdates full filesystem bug"? Greg> Not based on the (non-existent) evidence you've supplied. Where does Greg> it crash? not having DDB compiled into the kernel I can't answer that. However I'm willing to give any suggestions a go. >> [BTW: the server hasn't crashed, it's only the FreeBSD client that >> crashes] Greg> Do you mean the client process or the client operating system? The client OS -- immediately after creating the symlink. This is the panic I got (taken before Eivind's nfs_vnops.c commit (rev 1.146) : fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0163a05 stack pointer = 0x10:0xc9d77e40 code segment = base 0x0; limit 0xfffff, type 0x1b = DPL0, pres 1, def32.1, gran 1 processor flags = interrupt enabled, resume, 10PL = 0 current process = 1230 (ln) interrupt mask = none trap number = 12 panic: page fault I'm not sure that it helps any... Greg> Greg Viren -- Viren Shah | "You can't trust code that you did not totally Research Associate, RST Inc. | create yourself. (Especially code from viren@rstcorp.com | companies that employ people like me.)" http://www.rstcorp.com/~vshah | - Ken Thompson "Reflections on Trusting Trust" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message