[head tinderbox] failure on sparc64/sparc64
TB --- 2010-03-26 20:49:09 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-03-26 20:49:09 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2010-03-26 20:49:09 - cleaning the object tree TB --- 2010-03-26 20:49:27 - cvsupping the source tree TB --- 2010-03-26 20:49:27 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2010-03-26 20:49:57 - building world TB --- 2010-03-26 20:49:57 - MAKEOBJDIRPREFIX=/obj TB --- 2010-03-26 20:49:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-03-26 20:49:57 - TARGET=sparc64 TB --- 2010-03-26 20:49:57 - TARGET_ARCH=sparc64 TB --- 2010-03-26 20:49:57 - TZ=UTC TB --- 2010-03-26 20:49:57 - __MAKE_CONF=/dev/null TB --- 2010-03-26 20:49:57 - cd /src TB --- 2010-03-26 20:49:57 - /usr/bin/make -B buildworld >>> World build started on Fri Mar 26 20:49:57 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Mar 26 21:46:30 UTC 2010 TB --- 2010-03-26 21:46:30 - generating LINT kernel config TB --- 2010-03-26 21:46:30 - cd /src/sys/sparc64/conf TB --- 2010-03-26 21:46:30 - /usr/bin/make -B LINT TB --- 2010-03-26 21:46:30 - building LINT kernel TB --- 2010-03-26 21:46:30 - MAKEOBJDIRPREFIX=/obj TB --- 2010-03-26 21:46:30 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-03-26 21:46:30 - TARGET=sparc64 TB --- 2010-03-26 21:46:30 - TARGET_ARCH=sparc64 TB --- 2010-03-26 21:46:30 - TZ=UTC TB --- 2010-03-26 21:46:30 - __MAKE_CONF=/dev/null TB --- 2010-03-26 21:46:30 - cd /src TB --- 2010-03-26 21:46:30 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Mar 26 21:46:30 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Mar 26 22:06:42 UTC 2010 TB --- 2010-03-26 22:06:42 - building GENERIC kernel TB --- 2010-03-26 22:06:42 - MAKEOBJDIRPREFIX=/obj TB --- 2010-03-26 22:06:42 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-03-26 22:06:42 - TARGET=sparc64 TB --- 2010-03-26 22:06:42 - TARGET_ARCH=sparc64 TB --- 2010-03-26 22:06:42 - TZ=UTC TB --- 2010-03-26 22:06:42 - __MAKE_CONF=/dev/null TB --- 2010-03-26 22:06:42 - cd /src TB --- 2010-03-26 22:06:42 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Mar 26 22:06:43 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] objcopy --strip-debug --add-gnu-debuglink=firmware.ko.symbols firmware.ko.debug firmware.ko ===> fxp (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sparc64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -I/obj/sparc64/src/sys/GENERIC -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/fxp/../../dev/fxp/if_fxp.c /src/sys/modules/fxp/../../dev/fxp/if_fxp.c: In function 'fxp_start_body': /src/sys/modules/fxp/../../dev/fxp/if_fxp.c:1321: internal compiler error: in var_ann, at tree-flow-inline.h:128 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. *** Error code 1 Stop in /src/sys/modules/fxp. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sparc64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-03-26 22:14:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-03-26 22:14:06 - ERROR: failed to build GENERIC kernel TB --- 2010-03-26 22:14:06 - 4030.82 user 694.20 system 5097.63 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: atheros card with lots of Ierrs in `netstat -i`
On 26 Mar 2010, at 17:24, Alexander Best wrote: > hi there, > > `netstat -i` reports: > > NameMtu Network Address Ipkts Ierrs IdropOpkts > Oerrs Coll > ath0 2290 00:0f:b5:82:07:c8 6046435 691159 0 654080 > 0 0 > lo0 16384 1280796 0 0 1280796 > 0 0 > lo0 16384 your-net localhost.otaku1280796 - - 1280796 > - - > wlan0 1500 00:0f:b5:82:07:c8 821650 0 0 635461 > 20 0 > wlan0 1500 192.168.1.0 localhost.otaku 821223 - - 635140 > - - > > are the Ierrs for ath0 normal or is this something to worry about? i'm running > HEAD (r205561) on amd64. this is my card: > > a...@pci0:5:1:0:class=0x02 card=0x5a001385 chip=0x0013168c > rev=0x01 hdr=0x00 >vendor = 'Atheros Communications Inc.' >device = '802.11a/b/g Wireless Adapter (AR2312)' >class = network >subclass = ethernet You have a 9% error rate, which can be common on some scenarios. If you're not experiencing connection problems, there's no need to worry. -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: atheros card with lots of Ierrs in `netstat -i`
On Fri, Mar 26, 2010 at 12:24 PM, Alexander Best wrote: > hi there, > > `netstat -i` reports: > > Name Mtu Network Address Ipkts Ierrs Idrop Opkts > Oerrs Coll > ath0 2290 00:0f:b5:82:07:c8 6046435 691159 0 654080 > 0 0 > lo0 16384 1280796 0 0 1280796 > 0 0 > lo0 16384 your-net localhost.otaku 1280796 - - 1280796 > - - > wlan0 1500 00:0f:b5:82:07:c8 821650 0 0 635461 > 20 0 > wlan0 1500 192.168.1.0 localhost.otaku 821223 - - 635140 > - - ath0 2290 00:0f:b5:4f:9a:94 11057975 2376009 0 219466 0 0 > are the Ierrs for ath0 normal or is this something to worry about? i'm running > HEAD (r205561) on amd64. this is my card: > > a...@pci0:5:1:0: class=0x02 card=0x5a001385 chip=0x0013168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = '802.11a/b/g Wireless Adapter (AR2312)' > class = network > subclass = ethernet a...@pci0:6:0:0:class=0x02 card=0x5a001385 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = '802.11a/b/g Wireless Adapter (AR5212)' class = network subclass = ethernet I've noticed that Ierrs never stay at 0 on ath0 for a while now and I haven't had any noticeable problems with my network. I run my card in hostap mode on r204812. -- Chris - http://twitter.com/chrisattack http://chrisattack.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
atheros card with lots of Ierrs in `netstat -i`
hi there, `netstat -i` reports: NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll ath0 2290 00:0f:b5:82:07:c8 6046435 691159 0 654080 0 0 lo0 16384 1280796 0 0 1280796 0 0 lo0 16384 your-net localhost.otaku1280796 - - 1280796 - - wlan0 1500 00:0f:b5:82:07:c8 821650 0 0 635461 20 0 wlan0 1500 192.168.1.0 localhost.otaku 821223 - - 635140 - - are the Ierrs for ath0 normal or is this something to worry about? i'm running HEAD (r205561) on amd64. this is my card: a...@pci0:5:1:0:class=0x02 card=0x5a001385 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = '802.11a/b/g Wireless Adapter (AR2312)' class = network subclass = ethernet -- Alexander Best ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
On Mon, 22 Mar 2010, Xin LI wrote: A MFC of this update is planned, but we will have to make some rather aggressive changes against the library and more testing. Please make sure that you have at least libxml2-2.7.6_2 in your ports tree before even thinking about updating your ports tree. Older libxml2 uses some knowledge of zlib internals that has been changed in this update which is known to cause problem. While the update sounds like a good idea (as does moving to symbol verisoning for this library), I'm not yet convinced an MFC is a good idea given the compatibility issues you describe. Perhaps you could clarify a bit the failure mode: this affects only people who rebuild their ports using exactly the same ports versions, but after having done an upgrade that includes this update? It sounds like existing binaries will continue to work since they will reference the old library version? Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FYI: v4l-linuxulator support in FreeBSD-current now [panic]
Quoting Hans Petter Selasky (from Thu, 18 Feb 2010 09:14:20 +0100): On Tuesday 12 January 2010 18:49:48 Hans Petter Selasky wrote: I tried to fix something, but it was apparently not enough. I committed something similar. Bye, Alexander. -- Corrupt, adj.: In politics, holding an office of trust or profit. http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
