From owner-freebsd-alpha Wed Nov 28 16:25:48 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 BA7C737B50E for ; Wed, 28 Nov 2001 16:25:29 -0800 (PST) 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 TAA25143; Wed, 28 Nov 2001 19:25:23 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id fAT0Ovx84044; Wed, 28 Nov 2001 19:24:57 -0500 (EST) (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: <15365.32857.392495.737510@grasshopper.cs.duke.edu> Date: Wed, 28 Nov 2001 19:24:57 -0500 (EST) To: Paul Herman Cc: FreeBSD Alpha In-Reply-To: <200111282233.fASMXUA01849@tick.sc.omation.com> References: <200111282233.fASMXUA01849@tick.sc.omation.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 Paul Herman writes: > Hi, > > My 4.4-RELEASE (alpha) paniced 4 times in a row today and all at > the same place. I don't know what to make of it, so I thought I'd > start here. > > It happens when I do a lot of NFS traffic (like "pkg_add > /nfs/mount/package.tgz") What is XentUna? Is that a trap for > unaligned access? If so, what does fxdr_unsigned() do, and why > would XentUna fail? Or does it not try to correct it? I do have > machdep.unaligned_fix=1 if that makes a difference. For a more complete response.. XentUna is the unaligned access trap entry point. Eg, where the PALcode jumps to when there's an unaligned access. All unaligned accesses in kernel mode are fatal, regardless of machdep.unaligned_fix settings. Can you characterize your environment a little more? What's the NFS server running? Are you running NFS over TCP or UDP? What mount size? Is it any file or access pattern that causes this, or just special ones? Can you get a tcpdump of the traffic that causes the crash (from the server side, obviously). There's definately a bug in the code. Perhaps we could work around it by altering your environment. At Duke, I had FreeBSD/alpha (4.0 -> 4.3) running NFSv3 over UDP against Tru64 4.0f, Solaris (2.5 -> 2.8), and FreeBSD/i386 (4.0 -> 4.3) NFS servers. I never saw this panic. I hope this helps some.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message