From owner-freebsd-current Sat Jan 25 12:38:38 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFAFF37B401 for ; Sat, 25 Jan 2003 12:38:37 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 1C2E943EB2 for ; Sat, 25 Jan 2003 12:38:33 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 80294 invoked by uid 1000); 25 Jan 2003 20:38:28 -0000 Date: Sat, 25 Jan 2003 12:38:28 -0800 (PST) From: Nate Lawson To: Morten Rodal Cc: current@FreeBSD.ORG Subject: Re: panic in fork() on SMP 5.0-RELEASE In-Reply-To: <20030125202206.GA590@slurp.rodal.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 25 Jan 2003, Morten Rodal wrote: > The system is running 5.0-RELEASE with a pretty standard kernel (just > removed all the drivers I don't use and added SMP support). I think > the load of the system might have been high at the moment as I had > just started > > cd /usr/ports && make -j8 clean The problem is uap is invalid in this frame: #15 0xc01bd2f0 in fork (td=0xc5144000, uap=0xe3ac4d10) at /usr/src/sys/kern/kern_fork.c:124 The question is, why? I suspect something to do with memory due to the second two bytes being a valid kernel address. How about a dmesg? -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message