Date: Wed, 8 Apr 2009 05:40:03 GMT From: Victor Sudakov <sudakov@sibptus.tomsk.ru> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/133264: [build] make buildworld on RELENG_6_4 is broken on SMP machines Message-ID: <200904080540.n385e3ls063508@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/133264; it has been noted by GNATS. From: Victor Sudakov <sudakov@sibptus.tomsk.ru> To: John Baldwin <jhb@freebsd.org> Cc: bug-followup@freebsd.org Subject: Re: misc/133264: [build] make buildworld on RELENG_6_4 is broken on SMP machines Date: Wed, 8 Apr 2009 12:30:02 +0700 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. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200904080540.n385e3ls063508>