misc/133264: [build] make buildworld on RELENG_6_4 is broken on SMP machines

John Baldwin jhb at freebsd.org
Mon Apr 13 11:00:12 PDT 2009


The following reply was made to PR misc/133264; it has been noted by GNATS.

From: John Baldwin <jhb at freebsd.org>
To: Victor Sudakov <sudakov at sibptus.tomsk.ru>
Cc: bug-followup at freebsd.org
Subject: Re: misc/133264: [build] make buildworld on RELENG_6_4 is broken on SMP machines
Date: Mon, 13 Apr 2009 13:21:56 -0400

 On Wednesday 08 April 2009 1:30:02 am Victor Sudakov wrote:
 > John Baldwin wrote:
 > > > > > > tree.  If that is the case, a build without -j4 should also fail 
 and 
 > > > > should 
 > > > > > > show you where you have object files lying around.
 > > > > > 
 > > > > > Building on VMWare ESXi 3.5.0 Update 3 (FreeBSD as a guest OS) still
 > > > > > fails occasionally if more than 1 CPU is allocated to the virtual
 > > > > > machine. The failures are due to processes like sh, sed or cc1 
 dupming
 > > > > > core on signal 11 during the build.
 > > > > > 
 > > > > > I am using a pristine source tree now.
 > > > > > 
 > > > > > The problem seems to be SMP related because enabling only 1 virtual
 > > > > > CPU removes the problem.
 > > > > > 
 > > > > > Should I open a new PR?
 > > > > 
 > > > > Yes, this seems to be a different problem. :(  Do you see this 
 building other 
 > > > > source trees as well?  (e.g. RELENG_6 or RELENG_7).
 > > > 
 > > > RELENG_7_1 is not affected.
 > > > RELENG_6 is not affected.
 > > 
 > > This is all while running the same kernel?
 > 
 > Each its own kernel.
 > 
 > On the 6.4-RELEASE SMP kernel, any large compilation will crash
 > eventually with signal 11. Using "-j4" or higher seems to aggravate
 > the problem.
 
 Hmm, ok.  I'm not really sure why you are seeing this.  I don't know of 
 anything in RELENG_6 that isn't in 6.4 that would explain that.  Are you sure 
 your hardware is ok?
 
 -- 
 John Baldwin


More information about the freebsd-bugs mailing list