From owner-freebsd-current Mon Nov 23 08:36:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02905 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:36:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02797 for ; Mon, 23 Nov 1998 08:36:09 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA07035; Mon, 23 Nov 1998 11:35:22 -0500 (EST) Date: Mon, 23 Nov 1998 11:35:22 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Tom Bartol cc: Doug Rabson , freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having different problems. For instance, using FreeBSD 3.0-CURRENT (yesterday) as an NFS server, utilizing PLIP as my connection to a FreeBSD 3.0-RELEASE boot disk on an old WinBook. I was backing up the hard drive (cp /dev/rwd0a /mnt) and I tried running top because both systems were getting slow. Top on the desktop showed 8x% interrupt, is that software or hardware interrupts? After this, I wanted to see the traffic, so I did a trafshow -i lp0, and all of a sudden a flood of Fatal trap 12's happened on the desktop system. Basically, I could do nothing at this point, and had to do a hard reset. So, letting you know, something is broken here. Can I disable DDB for fatal traps, not just panic()'s, because I only wanted it enabled so I could drop into it at will to examine kernel state....? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message