From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 21 22:13:44 2006 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C198216A4DA; Mon, 21 Aug 2006 22:13:44 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 765AE43D45; Mon, 21 Aug 2006 22:13:44 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.6/8.13.6) with ESMTP id k7LMDiiN001200; Mon, 21 Aug 2006 15:13:44 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.6/8.13.6/Submit) id k7LMDiJe001199; Mon, 21 Aug 2006 15:13:44 -0700 (PDT) (envelope-from sgk) Date: Mon, 21 Aug 2006 15:13:44 -0700 From: Steve Kargl To: John Baldwin Message-ID: <20060821221343.GA1099@troutmask.apl.washington.edu> References: <200608151701.46724.jhb@freebsd.org> <200608181700.25539.jhb@freebsd.org> <20060818223653.GA5626@troutmask.apl.washington.edu> <200608211309.40737.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200608211309.40737.jhb@freebsd.org> User-Agent: Mutt/1.4.2.2i Cc: amd64@freebsd.org Subject: Re: linux32 breakage in current.. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Aug 2006 22:13:44 -0000 > > > > > > Ok. Can you walk it back further? > > > > > > > I've gone as far back as 15 Jul 06, and the problem is still > > there. I ran out of time to go back to earlier versions. I'll > > try again on Monday. > > Wow, thanks! > John, All previous attempts have been reverting only the kernel back to previous dates. I tried a 01 Jun 06 kernel, which led to an instant panic. I believe the kernel panic is due to a too old kernel with a too new world, so I reverted my system (kernel+world) to 01 Jun 06. Out of 15 attempts to use acroread, it started with no segfaults. I'll move forward in time by 1 week intervals and install new kernel+world until I see the failure. -- Steve