From owner-freebsd-stable Sun Dec 23 6:15:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 8F85537B417 for ; Sun, 23 Dec 2001 06:15:37 -0800 (PST) Received: from colt.ncptiddische.net (ppp-236.wobline.de [212.68.69.247]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fBNEFS831714; Sun, 23 Dec 2001 15:15:28 +0100 Received: from tisys.org (poison.ncptiddische.net [192.168.0.5]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fBNEHOX50807; Sun, 23 Dec 2001 15:17:25 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id fBNEFsV00217; Sun, 23 Dec 2001 15:15:54 +0100 (CET) (envelope-from nils) Date: Sun, 23 Dec 2001 15:15:19 +0100 From: Nils Holland To: Matthew Dillon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS problems in 4.5-PRERELEASE Message-ID: <20011223151519.A181@tisys.org> Mail-Followup-To: Matthew Dillon , freebsd-stable@FreeBSD.ORG References: <20011223005213.A57692@tisys.org> <200112230459.fBN4x0u99894@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112230459.fBN4x0u99894@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Dec 22, 2001 at 08:59:00PM -0800 X-Operating-System: FreeBSD poison.ncptiddische.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE X-Machine-Uptime: 2:58PM up 30 mins, 1 user, load averages: 0.00, 0.00, 0.00 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here's an update about my NFS problem: I added debug options to my kernel, and now that it crashed, I received the following output (can this be saved to file somehow? I'm typing it on another machine right now ;-) Stopped at nfs_nget+0x70: movl 0xc8(%esi),%eax Then did a "trace" at the db> prompt, and this is what I got: nfs_nget(c3d5ac00,c16e904c,1c,e028dd3c,e0d9b900) at nfs_nget+0x70 nfs_lookup(e028de08,e18b98c0,e028deac,c3ea1700,dea62860) at nfs_lookup+0xecf lookup(e028de84,dae62860,2,dea62860,dae62860) at lookup+0x291 namei(e028de84,dae62860,2,e028df80,806b000) at namei+0x19c lstat(dae62860,e028df80,807a24c,806e018,807a200) at lstat+0x41 sycall2(2f,2f,2f,807a200,806e018) at syscall2+0x1f1 Xint0x80_syscall() at Xint0x80_syscall+8x25 Well, I've never had to deal with debugging, but besides the above output, I also have a crash dump. I probably don't know how to extract useful data from there (the section in the FAQ about how to deal with panics is fairly short), however, if someone wants me to send any specific output, just say what it is and I'll send it! Two more things: First of all, the NFS copy operation does *not* always crash at the same file, as I previously said. And the second thing: I have tried Jordan's Apple's file system regression test program, and it ran successfully for three hours without a crash. Strange... If you want any more data, just tell me? I'll probably do some "amateur research" on this problem as well ;-) Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message