From owner-freebsd-current@FreeBSD.ORG Thu Jun 26 10:55:02 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 7975637B401 for ; Thu, 26 Jun 2003 10:55:02 -0700 (PDT) Received: from sccrmhc11.attbi.com (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DED843FDD for ; Thu, 26 Jun 2003 10:55:01 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([12.233.125.100]) by attbi.com (sccrmhc11) with ESMTP id <2003062617550001100s51f5e>; Thu, 26 Jun 2003 17:55:00 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA12106; Thu, 26 Jun 2003 10:54:59 -0700 (PDT) Date: Thu, 26 Jun 2003 10:54:59 -0700 (PDT) From: Julian Elischer To: Kevin Oberman In-Reply-To: <20030626155513.5112C5D08@ptavv.es.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Christoph Kukulies cc: Tobias Roth cc: current@freebsd.org Subject: Re: world build fails since yesterday 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, 26 Jun 2003 17:55:02 -0000 On Thu, 26 Jun 2003, Kevin Oberman wrote: > > Date: Thu, 26 Jun 2003 12:19:42 +0200 > > From: Tobias Roth > > Sender: owner-freebsd-current@freebsd.org > > > > Hi > > > > I get the same behaviour on my T30. Although the indications for a > > hardware problem are very strong, I am not yet convinced that this > > really is one. > > > > My suspicion is that there are problems with current (as well with > > 5.1 and probably 5.0) with power management that will result in > > overheating, which will then look like a hardware problem. > > > > I am currently running continuous buildworlds on stable, and so far > > they all succeeded. > > > > This is what is left to do: > > > > run buildworld on current or 5.1 until it fails a couple of times > > with the below errors, then reboot to 4.8 and run a few buildworlds. > > > > if they also fail -> hardware problem very likely > > if they do not fail -> run again a few buldworlds on current. > > if these fail again -> software problem very likely > > > > could you please also set up this test scenario and report the > > outcome? my results will be available some time tomorrow > One thing to do would be to do the buildworld in a 4.x jail/chroot on a 5.x system..