From owner-freebsd-stable Wed May 31 18:30:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 960DD37BF4E for ; Wed, 31 May 2000 18:30:49 -0700 (PDT) (envelope-from daemon@mips.inka.de) Received: from bigeye.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 12xJoq-0001Na-00; Thu, 1 Jun 2000 03:30:44 +0200 Received: (from daemon@localhost) by bigeye.mips.inka.de (8.9.3/8.9.3) id CAA05857 for freebsd-stable@freebsd.org; Thu, 1 Jun 2000 02:58:18 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: -j n and -STABLE world. Date: 1 Jun 2000 02:58:17 +0200 Message-ID: <8h4cf9$5mj$1@bigeye.mips.inka.de> References: To: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bryan Bursey wrote: > Sorry to follow my own message, but I'd like to confirm that I'm dealing > with a SMP kernel on a machine that it not overclocked. Ditto. In fact, I'm pretty sure it happens in the single-CPU case for me, too. -CURRENT suffers from it, too. > The 'installworld' fails consistently in the same place. Which is in bin/ln for me. I couldn't reproduce it in isolation (outside of a installworld), though. I'm not terribly surprised about the effect. Both ln and rm are used for the installation of their respective targets. Some kind of race condition there, I guess. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message