From owner-freebsd-current@FreeBSD.ORG Fri Oct 17 06:19:22 2003 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 0B8B416A4B3 for ; Fri, 17 Oct 2003 06:19:22 -0700 (PDT) Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1DDA43FCB for ; Fri, 17 Oct 2003 06:19:18 -0700 (PDT) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: from zibbi.icomtek.csir.co.za (localhost [IPv6:::1]) h9HDJFqs071765; Fri, 17 Oct 2003 15:19:15 +0200 (SAST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.12.9/8.12.9/Submit) id h9HDJDMR071764; Fri, 17 Oct 2003 15:19:13 +0200 (SAST) (envelope-from jhay) Date: Fri, 17 Oct 2003 15:19:12 +0200 From: John Hay To: Alexander Leidinger Message-ID: <20031017131912.GA71602@zibbi.icomtek.csir.co.za> References: <20031009095934.GA11841@zibbi.icomtek.csir.co.za> <20031016205443.GA41359@zibbi.icomtek.csir.co.za> <20031017113721.53828fd6.Alexander@Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031017113721.53828fd6.Alexander@Leidinger.net> User-Agent: Mutt/1.4i cc: current@freebsd.org Subject: Re: panic: vm_map_wire: lookup failed 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: Fri, 17 Oct 2003 13:19:22 -0000 > > > > > > The latest development source of ntpd started to use setrlimit() before > > > using mlockall(). This combination proves fatal on -current. The code > > > in ntpd/ntpd.c looks like this: > > > > Ok, I found an easier way to provoke the panic. Just compile the following > > program like this: > > > if (mlockall(MCL_CURRENT|MCL_FUTURE) < 0) > > perror("mlockall()"); > > Did you tested it on a recent -current? It is supposed to be fixed > (since a day or two, I think). Nope it is still not fixed. I have tried again just now and it still throw a panic on both UP and SMP. Try for yourself if you are brave. :-))) John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org