From owner-freebsd-current@FreeBSD.ORG Wed Oct 24 16:56:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C73716A46C for ; Wed, 24 Oct 2007 16:56:40 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 0FCB113C4A5 for ; Wed, 24 Oct 2007 16:56:39 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:60975 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IkjWj-0001eL-RH for freebsd-current@freebsd.org; Wed, 24 Oct 2007 16:56:17 +0000 Message-ID: <471F7931.6080807@conducive.net> Date: Wed, 24 Oct 2007 12:56:17 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20071024091418.BA6C00FC@resin17.mta.everyone.net> In-Reply-To: <20071024091418.BA6C00FC@resin17.mta.everyone.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: random panics: vm_phys_free_pages: page 0xc161f2a0 has unexpected order 10 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 24 Oct 2007 16:56:40 -0000 Brad Allen wrote: > >> --- askbill@conducive.net wrote: *snip* >> Might try replicating the problem here on other hardware & several >> different 'vintages' of builds. >> >> IF I had a few more details. I've got two servers sitting within arm's >> length that don't go into a rack for another 12 hours or so... Both Core-2 >> Quad, otherwise 'enough' different it might be helpful. >> >> I don't code "C" - but I can test... >> >> Bill >> > Currently I'm using the October snapshot, I've also tried the August & June > snapshots with the same result. I'm running an Athlon XP 2400+. > > I can _generally_ get away with compiling the smaller ports (bash, nano, > etc), however xservers and kernels, to name a couple, are guaranteed to fail. OK - I may have 'tested' some of it already. Other than NOT using 'portsnap', and having different CPU & RAM, specifically: ASUS P5K, 4 GB DDR 800, Core-2 Quad 2.4 GHz, GigaByte G33-DS3R, 4 GB DDR 800, Core-2 Quad 2.4 GHz But we DO have overlap with the FreeBSD versions you are trying, ex: i386 & AMD-64 Aug, Sep snapshots. cvsup from October onward 'til about 2 days ago. - two instances of make build~ failing to complete. OK with new cvsuping 12 hours later. Might have been OK within minutes if re-pulled. 'not known' - a few instances of pkg_add being unable to find a consenting tarball, but a make install from the ports tree working OK for the same port. - a few instances of a 'common' port refusing to build on AMD-64 at all (Opera comes to mind). Not to mention the odd few ports simply marked as 'broken'. No occcurence of the sort of error you cited. JMHO, but... "SWAG" - most likely to be stale debris in your build environment. We either nuke /usr/src, or rely on the 'delete' tag to clean it up for us. Second choice is RAM complement. Third suspect is RAM quality. Meanwhile; - Give me the *exact* commands you are using, I'll try them, too. - See if you can lay hands on another 1 GB of RAM and if it at least delays the issue. Standing by... Bill