[Bug 200274] buildworld bus error MachineLICM.o for i386 targets 10.1S r283021

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun May 17 23:33:00 UTC 2015


            Bug ID: 200274
           Summary: buildworld bus error MachineLICM.o for i386 targets
                    10.1S r283021
           Product: Base System
           Version: 10.1-STABLE
          Hardware: i386
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: dewayne at heuristicsystems.com.au

Bus error from MachineLICM.o arises during buildworld of i386 pentium3 systems
on (uname -aKU) 
FreeBSD hathor 10.1-STABLE FreeBSD 10.1-STABLE #0 r282448M: Wed May  6 02:20:33
AEST 2015    
root at hathor:/usr/obj/prod/100102/D/K8/usr/src/sys/hqdev-amd64-smp-vga          
               amd64 1001514 1001514

from svnlite, Last Changed Rev: 283021

I perform a build sequence which includes using CPUTYPE's c3-2, pentium3,
prescott (plus a few amd64 worlds).  During the last three cycles (about 2
weeks apart) only ONE of the i386 build worlds will fail (none fail for amd64

They use a common set of scripts where MAKEOBJPREFIX, CPUTYPE, TARGET_CPUTYPE 
and -march= or -mtune= variables are changed.

Aside typically each has 4 kernels, also all of these build without error.

The following is taken from the pentium3 failure which occurred last night. 
Yesterday if failed for the c3-2 build.  Very puzzling.

Hardware: Xeon E3-1230L, build disk SSD (Kingston SV300).
smartctl reports overall health: Passed

--- MachineLICM.o ---
Stack dump:
0.      Program arguments: /usr/bin/c++ -cc1 -triple x86_64-unknown-freebsd10.1
-emit-obj -disable-free -disable-llvm-verifier -main-file-name MachineLICM.cpp
-mrelocation-model static -mdisable-fp-elim -relaxed-aliasing -masm-verbose
-mconstructor-aliases -munwind-tables -target-cpu x86-64 -coverage-file
-resource-dir /usr/bin/../lib/clang/3.4.1 -D STRIP_FBSDID -U DEBUGGING -U DEBUG
LLVM_DEFAULT_TARGET_TRIPLE="i386-unknown-freebsd10.1" -D
LLVM_HOST_TRIPLE="x86_64-unknown-freebsd10.1" -D
DEFAULT_SYSROOT="/usr/obj/prod/100102/P/P3/i386.i386/usr/src/tmp" -D NDEBUG -I
/usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/include -I
/usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/tools/clang/include -I
/usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/lib/CodeGen -I . -I
-I /usr/obj/prod/100102/P/P3/i386.i386/usr/src/tmp/legacy/usr/include
-internal-isystem /usr/include/c++/v1 -O2 -fdeprecated-macro
-ferror-limit 19 -fmessage-length 0 -mstackrealign -fno-rtti
-fobjc-runtime=gnustep -fdiagnostics-show-option -vectorize-loops
-vectorize-slp -o MachineLICM.o -x c++
1.      <eof> parser at end of file
2.      Per-module optimization passes
3.      Running pass 'CallGraph Pass Manager' on module
4.      Releasing pass 'Scalar Evolution Analysis'
c++: error: unable to execute command: Bus error
c++: error: clang frontend command failed due to signal (use -v to see
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd10.1
Thread model: posix
c++: note: diagnostic msg: PLEASE submit a bug report to
https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed
source, and associated run script.
--- all_subdir_libllvmmcparser ---
--- MCTargetAsmParser.o ---
c++  -O2 -pipe -g0 -ggdb0 -DSTRIP_FBSDID -UDEBUGGING -UDEBUG
-I/usr/src/lib/clang/libllvmmcparser/../../../contrib/llvm/lib/MC/MCParser -I.
-DNDEBUG -fno-strict-aliasing
-DDEFAULT_SYSROOT=\"/usr/obj/prod/100102/P/P3/i386.i386/usr/src/tmp\" -DNDEBUG
-fno-exceptions -fno-rtti -c
-o MCTargetAsmParser.o
--- all_subdir_libllvmmc ---
--- MCObjectFileInfo.o ---
--- all_subdir_libllvmcodegen ---
c++: note: diagnostic msg:

Preprocessed source(s) and associated run script(s) are located at:
c++: note: diagnostic msg: /tmp/MachineLICM-6b8ca7.cpp
c++: note: diagnostic msg: /tmp/MachineLICM-6b8ca7.sh
c++: note: diagnostic msg:

*** [MachineLICM.o] Error code 254

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-bugs mailing list