Re: RELENG_6_3 build fail -- signal 13 consistently
On Thu, 2008-01-24 at 09:17 -0500, Brian A. Seklecki wrote: This is 6.3/amd64 release as a guest inside a vmware server (free) host: It happens randomly. First time I've seen it. amd64 and i386 under vmware 1.x server (Free Version). I guess I'll use physical hardware for build farms. ~BAS IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6_3 build fail -- signal 13 consistently
On Wed, 2008-02-20 at 14:33 -0500, Brian A. Seklecki wrote: On Thu, 2008-01-24 at 09:17 -0500, Brian A. Seklecki wrote: This is 6.3/amd64 release as a guest inside a vmware server (free) host: It happens randomly. First time I've seen it. amd64 and i386 under vmware 1.x server (Free Version). I guess I'll use physical hardware for build farms. This could have been two things: 1) The VM was originally FreeBSD 32bit -- so it emulated lnc(4), it was then switched to FreBSD64 -- em(4), then back to 32 -- who knows -- it's commercial software. 2) The VM had a non exponent/power of 2 sized RAM allocation (it was set to 216mb -- probably a GUI blooper) -- although this generally hasn't been a problem for 10 years since video cards started arbitrarily stealing physical DRAM for their frame-buffer. lnc(4) problem originates from this error: kernel: lnc0: Missed packet -- no receive buffer ~BAS IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6_3 build fail -- signal 13 consistently
Brian A. Seklecki [EMAIL PROTECTED] writes: This is 6.3/amd64 release as a guest inside a vmware server (free) host: === gnu/usr.bin/binutils/ar (install) install -s -o root -g wheel -m 555 ar /opt/relchroot/usr/bin *** Signal 13 Make.conf has some sparing NO_ knobs set and: COPTS=-pipe CFLAG=-pipe CFLAGS rather than CFLAG? COPTFLAGS rather than COPTS? 13 is SIGPIPE, so one of those is probably related. If you are setting CPUTYPE, don't set those, as you're overriding default settings... When you say consistently do you mean consistently in the same place? If not, that would be very different than I'm interpreting the situation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RELENG_6_3 build fail -- signal 13 consistently
This is 6.3/amd64 release as a guest inside a vmware server (free) host: === gnu/usr.bin/binutils/ar (install) install -s -o root -g wheel -m 555 ar /opt/relchroot/usr/bin *** Signal 13 Make.conf has some sparing NO_ knobs set and: COPTS=-pipe CFLAG=-pipe Other than that, its a vanilla source tree: FreeBSD fbsdbuild-amd64-63 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:45:45 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 kern.hz=100 in loader.conf as well. Pretty crazy. ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
