From owner-freebsd-current@FreeBSD.ORG Wed Jan 7 21:38:30 2004 Return-Path: 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 C75D716A4CE; Wed, 7 Jan 2004 21:38:30 -0800 (PST) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0859E43D2D; Wed, 7 Jan 2004 21:38:29 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from localhost (localhost [127.0.0.1]) by cs.rice.edu (Postfix) with ESMTP id A025D4A9CD; Wed, 7 Jan 2004 23:38:28 -0600 (CST) Received: from cs.rice.edu ([127.0.0.1]) by localhost (cs.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 12007-01-16; Wed, 7 Jan 2004 23:38:27 -0600 (CST) Received: by cs.rice.edu (Postfix, from userid 19572) id 1BF9D4A9AE; Wed, 7 Jan 2004 23:38:27 -0600 (CST) Date: Wed, 7 Jan 2004 23:38:27 -0600 From: Alan Cox To: Yu-Shun Wang Message-ID: <20040108053827.GJ7891@cs.rice.edu> References: <200312220101.hBM11WgL071526@repoman.freebsd.org> <3FFCA854.7040707@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FFCA854.7040707@isi.edu> User-Agent: Mutt/1.3.28i X-Virus-Scanned: by amavis-20030616-p5 at rice.edu cc: Alan Cox cc: current@freebsd.org Subject: Re: Immediate reboot after memory probe X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 05:38:30 -0000 On Wed, Jan 07, 2004 at 04:46:12PM -0800, Yu-Shun Wang wrote: > ... > With a bit of digging and luck (not debugging, I am new to > kernel debugging and don't have the environment setup to > generate tracebacks), I managed to find the probable cause: > sys/i386/i386/pmap.c from the commit log included below. > After reversed the diff between 1.456 and 1.457, the problem > was fixed. Please restore this diff and try increasing UMA_BOOT_PAGES. Don't be overly conservative; try doubling UMA_BOOT_PAGES. > Weird thing is, it seems like I am the only one hit by > this problem. I couldn't find any message on CURRENT > list regarding this. Anyways, dmesg & kernel conf files are > also attached. Please let me know if you need more info. I suspect it is related to the number of modules that you loading. Regards, Alan