From owner-freebsd-current Mon Jun 3 3:53:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 714AB37B406; Mon, 3 Jun 2002 03:53:22 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id B4D695307; Mon, 3 Jun 2002 12:53:18 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Ruslan Ermilov Cc: current@FreeBSD.org, admins@FreeBSD.org Subject: Re: i386 tinderbox failure References: <200206020436.g524ae9Z003471@ref5.freebsd.org> <20020603074326.GC37191@sunbay.com> From: Dag-Erling Smorgrav Date: 03 Jun 2002 12:53:17 +0200 In-Reply-To: <20020603074326.GC37191@sunbay.com> Message-ID: Lines: 13 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ruslan Ermilov writes: > I'm doing the daily (-j8) snapshots on a 2-CPU SMP machine for > i386, pc98, alpha, ia64, and sparc64, and never saw this problem. > Could it be that you have a faulty hardware on your tinderbox, > as I already saw a few reports from you, always in a different > place? I was wondering about that too... Admins, any signs of faulty RAM or cooling problems in ref5? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message