Re: Request for review/testing: switching the default installer
On Fri, 4 Mar 2011 12:24:20 -0800 Freddie Cash fjwc...@gmail.com wrote about Re: Request for review/testing: switching the default installer: FC Or, does anyone have instructions on how to convert the ISO images FC into memstick images? Preferably using a Linux station, not a FreeBSD FC station. I use unetbootin (http://unetbootin.sourceforge.net/) to create usb install media from iso images. Works for me. cu Gerrit ___ 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: please (re) test if_ath in -HEAD
hello! FreeBSD 9.0-900033-CURRENT #0 r219338M: Mon Mar 7 11:31:40 VLAT 2011 All fine with AR9285, WPA2 is used stable 36/48/54Mbps with my AP 07.03.2011, 06:14, Adrian Chadd adrian.ch...@gmail.com: On 7 March 2011 03:21, Ian FREISLICH i...@clue.co.za; wrote: Adrian Chadd wrote: I'd like to establish at least a range of subversion revisions so we can start binary searching which one(s) caused instabilities. Is this all the source? Old: $FreeBSD: src/sys/dev/ath/if_ath.c,v 1.300 2011/02/21 19:22:45 adrian Exp $ New: $FreeBSD: src/sys/dev/ath/if_ath.c,v 1.302 2011/03/02 17:19:54 adrian Exp $ Ok, so between r219318 (today) and r218779 (2011-02-18). Would you please first test r218779 and verify that performance is (back to) fine? -- Dima Panov (flu...@freebsd.org) KDE@FreeBSD team Facebook: http://www.facebook.com/?id=10181104157 ___ 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
[head tinderbox] failure on mips/mips
TB --- 2011-03-07 12:33:53 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-07 12:33:53 - starting HEAD tinderbox run for mips/mips TB --- 2011-03-07 12:33:53 - cleaning the object tree TB --- 2011-03-07 12:34:00 - cvsupping the source tree TB --- 2011-03-07 12:34:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2011-03-07 12:34:14 - building world TB --- 2011-03-07 12:34:14 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-07 12:34:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-07 12:34:14 - TARGET=mips TB --- 2011-03-07 12:34:14 - TARGET_ARCH=mips TB --- 2011-03-07 12:34:14 - TZ=UTC TB --- 2011-03-07 12:34:14 - __MAKE_CONF=/dev/null TB --- 2011-03-07 12:34:14 - cd /src TB --- 2011-03-07 12:34:14 - /usr/bin/make -B buildworld World build started on Mon Mar 7 12:34:15 UTC 2011 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 [...] cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/lzf.c cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/metadata.c cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/nv.c cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c parse.c cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/pjdlog.c cc1: warnings being treated as errors /src/sbin/hastctl/../hastd/pjdlog.c: In function 'pjdlog_printf_render_sockaddr': /src/sbin/hastctl/../hastd/pjdlog.c:110: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/sbin/hastctl. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-03-07 13:24:20 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-03-07 13:24:20 - ERROR: failed to build world TB --- 2011-03-07 13:24:20 - 2174.50 user 520.83 system 3026.96 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.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
[head tinderbox] failure on sparc64/sparc64
TB --- 2011-03-07 13:14:32 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-07 13:14:32 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2011-03-07 13:14:32 - cleaning the object tree TB --- 2011-03-07 13:14:47 - cvsupping the source tree TB --- 2011-03-07 13:14:47 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2011-03-07 13:14:59 - building world TB --- 2011-03-07 13:14:59 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-07 13:14:59 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-07 13:14:59 - TARGET=sparc64 TB --- 2011-03-07 13:14:59 - TARGET_ARCH=sparc64 TB --- 2011-03-07 13:14:59 - TZ=UTC TB --- 2011-03-07 13:14:59 - __MAKE_CONF=/dev/null TB --- 2011-03-07 13:14:59 - cd /src TB --- 2011-03-07 13:14:59 - /usr/bin/make -B buildworld World build started on Mon Mar 7 13:14:59 UTC 2011 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 [...] cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/lzf.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/metadata.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/nv.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c parse.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/pjdlog.c cc1: warnings being treated as errors /src/sbin/hastctl/../hastd/pjdlog.c: In function 'pjdlog_printf_render_sockaddr': /src/sbin/hastctl/../hastd/pjdlog.c:110: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/sbin/hastctl. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-03-07 14:09:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-03-07 14:09:04 - ERROR: failed to build world TB --- 2011-03-07 14:09:04 - 2466.27 user 544.53 system 3272.01 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
[head tinderbox] failure on sparc64/sun4v
TB --- 2011-03-07 13:24:21 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-07 13:24:21 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2011-03-07 13:24:21 - cleaning the object tree TB --- 2011-03-07 13:24:30 - cvsupping the source tree TB --- 2011-03-07 13:24:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2011-03-07 13:24:44 - building world TB --- 2011-03-07 13:24:44 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-07 13:24:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-07 13:24:44 - TARGET=sun4v TB --- 2011-03-07 13:24:44 - TARGET_ARCH=sparc64 TB --- 2011-03-07 13:24:44 - TZ=UTC TB --- 2011-03-07 13:24:44 - __MAKE_CONF=/dev/null TB --- 2011-03-07 13:24:44 - cd /src TB --- 2011-03-07 13:24:44 - /usr/bin/make -B buildworld World build started on Mon Mar 7 13:24:44 UTC 2011 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 [...] cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/lzf.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/metadata.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/nv.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c parse.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/pjdlog.c cc1: warnings being treated as errors /src/sbin/hastctl/../hastd/pjdlog.c: In function 'pjdlog_printf_render_sockaddr': /src/sbin/hastctl/../hastd/pjdlog.c:110: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/sbin/hastctl. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-03-07 14:18:27 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-03-07 14:18:27 - ERROR: failed to build world TB --- 2011-03-07 14:18:27 - 2461.78 user 538.27 system 3245.94 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.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: Request: AR9285 EEPROM dumps (was Re: More if_ath churn coming your way!)
2011/3/7 Adrian Chadd adrian.ch...@gmail.com: Which version of the driver are you using? Adrian # $FreeBSD: src/sys/modules/ath/Makefile,v 1.19 2011/03/02 17:19:54 adrian Exp $ 2011/3/7 Vinícius Zavam egyp...@googlemail.com 2011/1/23 Adrian Chadd adrian.ch...@gmail.com: You'll have to compile in the diag api. Just add these: options ATH_DIAGAPI Adrian 2011/1/23 Dima Panov flu...@fluffy.khv.ru: Hello! 23.01.2011, 09:47, Adrian Chadd adrian.ch...@gmail.com: Hi all, I've just committed a new tool in src/tools/tools/ath/ called ath_prom_dump . It dumps the contents of the atheros EEPROM into a text file for later analysis. I don't have any AR9285's handy; if you have an AR9285, would you please send me a hexdump of the EEPROM along with the contents of pciconf and dmesg | grep ath (so I can get the MAC/PHY version numbers?) You meant ath_prom_read? [root@Beastie] ~# ath_prom_read -h ath_prom_read: illegal option -- h ath_prom_read [-i ifname] -d dumpfile [root@Beastie] ~# ath_prom_read -d ar9285 ath_prom_read: ath0: Invalid argument [root@Beastie] ~# FreeBSD 9.0-900030-CURRENT #0 r217695M: Sat Jan 22 13:57:57 VLAT 2011 -- Dima Panov (flu...@freebsd.org) _AR9285.txt = associated ath0: bb hang detected (0x80), resetting -- Vinícius Zavam -- Vinícius Zavam profiles.google.com/egypcio ___ 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
[head tinderbox] failure on ia64/ia64
TB --- 2011-03-07 16:25:38 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-07 16:25:38 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-03-07 16:25:38 - cleaning the object tree TB --- 2011-03-07 16:25:50 - cvsupping the source tree TB --- 2011-03-07 16:25:50 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2011-03-07 16:26:01 - building world TB --- 2011-03-07 16:26:01 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-07 16:26:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-07 16:26:01 - TARGET=ia64 TB --- 2011-03-07 16:26:01 - TARGET_ARCH=ia64 TB --- 2011-03-07 16:26:01 - TZ=UTC TB --- 2011-03-07 16:26:01 - __MAKE_CONF=/dev/null TB --- 2011-03-07 16:26:01 - cd /src TB --- 2011-03-07 16:26:01 - /usr/bin/make -B buildworld World build started on Mon Mar 7 16:26:02 UTC 2011 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 [...] cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/lzf.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/metadata.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/nv.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c parse.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/pjdlog.c cc1: warnings being treated as errors /src/sbin/hastctl/../hastd/pjdlog.c: In function 'pjdlog_printf_render_sockaddr': /src/sbin/hastctl/../hastd/pjdlog.c:110: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/sbin/hastctl. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-03-07 17:33:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-03-07 17:33:04 - ERROR: failed to build world TB --- 2011-03-07 17:33:04 - 3201.30 user 600.96 system 4045.51 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.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: More if_ath churn coming your way!
2011/1/22 Adrian Chadd adrian.ch...@gmail.com: So it's all completely stable for you too right now? adrian 2011/1/22 Dima Panov flu...@fluffy.khv.ru: Hello! 22.01.2011, 13:56, Adrian Chadd adrian.ch...@gmail.com: On 20 January 2011 13:51, Adrian Chadd adrian.ch...@gmail.com; wrote: Hi everyone, I'm in the process of merging in the non-intrusive changes to the if_ath code into -HEAD. Ok, so I lied - the ANI changes were slightly intrusive. But all in all the code was just shuffled around a bit. Someone's reported that the AR9285 was once stable but now isn't. I'd really appreciate it if others who are using AR9280/AR9285 chipsets would test this out and get back to me. FreeBSD 9.0-900030-CURRENT #0 r217695M: Sat Jan 22 13:57:57 VLAT 2011 ath0: Atheros 9285 mem 0xf000-0xf000 irq 19 at device 0.0 on pci9 ath0: AR9285 mac 192.2 RF5133 phy 14.0 Signal strength is fine, no packets loss. ath 9285 was stable for me last months. Acer Ferrari One 200 laptop with half-sized atheros wifi card. it's true. works for me, but i need to put my netbook less than 1meter from my access point, when using freebsd ;( somewhere else i've tryed to send icmp echo requests to my gw got nothing but bb hang detected. my `ifconfig wlan0 list scan` returns just one wireless network... mine. I'd like to make sure I fix all regressions before I start bringing over more code from ath9k in preparation for enabling the basic 802.11n support for testing. -- Dima Panov (flu...@freebsd.org) ath0: Atheros 9285 mem 0xfbff-0xfbff irq 17 at device 0.0 on pci2 ath0: AR9285 mac 192.2 RF5133 phy 14.0 ath0@pci0:2:0:0:class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'Atheros AR9285 Wireless LAN 802.11 a/b/g/n Controller (AR928x)' class = network FreeBSD minimoose 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Mon Mar 7 14:16:58 BRT 2011 root@minimoose:/usr/obj/usr/src/sys/MINIMOOSE i386 # $FreeBSD: src/sys/modules/ath/Makefile,v 1.19 2011/03/02 17:19:54 adrian Exp $ 2399 ?? Is 0:00.10 wpa_supplicant -c /etc/wpa_supplicant.conf -i wlan0 -d -s -D bsd -B minimoose# egrep -i '(wpa_supplicant|ath)' /var/log/messages Mar 6 23:14:44 minimoose kernel: ath0: Atheros 9285 mem 0xfbff-0xfbff irq 17 at device 0.0 on pci2 Mar 6 23:14:44 minimoose kernel: ath0: AR9285 mac 192.2 RF5133 phy 14.0 Mar 6 23:14:44 minimoose kernel: alc0: Atheros AR8132 PCIe Fast Ethernet port 0xec00-0xec7f mem 0xf7fc-0xf7ff irq 19 at device 0.0 on pci1 Mar 6 23:14:44 minimoose kernel: atphy0: Atheros F1 10/100/1000 PHY PHY 0 on miibus0 Mar 6 23:16:23 minimoose wpa_supplicant[2424]: Trying to associate with 00:26:5a:b1:da:92 (SSID='Zavam' freq=2412 MHz) Mar 6 23:16:23 minimoose wpa_supplicant[2424]: Associated with 00:26:5a:b1:da:92 Mar 6 23:16:23 minimoose wpa_supplicant[2424]: WPA: Key negotiation completed with 00:26:5a:b1:da:92 [PTK=CCMP GTK=TKIP] Mar 6 23:16:23 minimoose wpa_supplicant[2424]: CTRL-EVENT-CONNECTED - Connection to 00:26:5a:b1:da:92 completed (auth) [id=1 id_str=] Mar 6 23:20:46 minimoose kernel: ath0: bb hang detected (0x80), resetting Mar 6 23:24:29 minimoose wpa_supplicant[2424]: WPA: Group rekeying completed with 00:26:5a:b1:da:92 [GTK=TKIP] Mar 6 23:26:06 minimoose kernel: ath0: bb hang detected (0x80), resetting Mar 7 14:07:55 minimoose kernel: ath0: Atheros 9285 mem 0xfbff-0xfbff irq 17 at device 0.0 on pci2 Mar 7 14:07:55 minimoose kernel: ath0: AR9285 mac 192.2 RF5133 phy 14.0 Mar 7 14:07:55 minimoose kernel: alc0: Atheros AR8132 PCIe Fast Ethernet port 0xec00-0xec7f mem 0xf7fc-0xf7ff irq 19 at device 0.0 on pci1 Mar 7 14:07:55 minimoose kernel: atphy0: Atheros F1 10/100/1000 PHY PHY 0 on miibus0 Mar 7 14:21:20 minimoose kernel: ath0: Atheros 9285 mem 0xfbff-0xfbff irq 17 at device 0.0 on pci2 Mar 7 14:21:20 minimoose kernel: ath0: AR9285 mac 192.2 RF5133 phy 14.0 Mar 7 14:21:20 minimoose kernel: alc0: Atheros AR8132 PCIe Fast Ethernet port 0xec00-0xec7f mem 0xf7fc-0xf7ff irq 19 at device 0.0 on pci1 Mar 7 14:21:20 minimoose kernel: atphy0: Atheros F1 10/100/1000 PHY PHY 0 on miibus0 Mar 7 14:24:00 minimoose wpa_supplicant[2398]: Trying to associate with 00:26:5a:b1:da:92 (SSID='Zavam' freq=2412 MHz) Mar 7 14:24:00 minimoose wpa_supplicant[2398]: Associated with 00:26:5a:b1:da:92 Mar 7 14:24:00 minimoose wpa_supplicant[2398]: WPA: Key negotiation completed with 00:26:5a:b1:da:92 [PTK=CCMP GTK=TKIP] Mar 7 14:24:00 minimoose wpa_supplicant[2398]: CTRL-EVENT-CONNECTED - Connection to 00:26:5a:b1:da:92 completed (auth) [id=1 id_str=] Mar 7 14:24:12 minimoose kernel: ath0: bb hang detected (0x80), resetting Mar 7 14:24:34 minimoose wpa_supplicant[2398]: WPA: Group rekeying completed with 00:26:5a:b1:da:92 [GTK=TKIP] Mar 7 14:36:20 minimoose kernel: ath0: Atheros 9285 mem 0xfbff-0xfbff irq 17 at device 0.0 on pci2 Mar 7
[head tinderbox] failure on mips/mips
TB --- 2011-03-07 17:33:05 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-07 17:33:05 - starting HEAD tinderbox run for mips/mips TB --- 2011-03-07 17:33:05 - cleaning the object tree TB --- 2011-03-07 17:33:10 - cvsupping the source tree TB --- 2011-03-07 17:33:10 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2011-03-07 17:33:23 - building world TB --- 2011-03-07 17:33:23 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-07 17:33:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-07 17:33:23 - TARGET=mips TB --- 2011-03-07 17:33:23 - TARGET_ARCH=mips TB --- 2011-03-07 17:33:23 - TZ=UTC TB --- 2011-03-07 17:33:23 - __MAKE_CONF=/dev/null TB --- 2011-03-07 17:33:23 - cd /src TB --- 2011-03-07 17:33:23 - /usr/bin/make -B buildworld World build started on Mon Mar 7 17:33:24 UTC 2011 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 [...] cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/lzf.c cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/metadata.c cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/nv.c cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c parse.c cc -O -pipe -G0 -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/pjdlog.c cc1: warnings being treated as errors /src/sbin/hastctl/../hastd/pjdlog.c: In function 'pjdlog_printf_render_sockaddr': /src/sbin/hastctl/../hastd/pjdlog.c:110: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/sbin/hastctl. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-03-07 18:22:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-03-07 18:22:26 - ERROR: failed to build world TB --- 2011-03-07 18:22:26 - 2168.57 user 531.71 system 2960.99 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.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
[head tinderbox] failure on sparc64/sparc64
TB --- 2011-03-07 18:36:15 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-07 18:36:15 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2011-03-07 18:36:15 - cleaning the object tree TB --- 2011-03-07 18:36:23 - cvsupping the source tree TB --- 2011-03-07 18:36:23 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2011-03-07 18:36:37 - building world TB --- 2011-03-07 18:36:37 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-07 18:36:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-07 18:36:37 - TARGET=sparc64 TB --- 2011-03-07 18:36:37 - TARGET_ARCH=sparc64 TB --- 2011-03-07 18:36:37 - TZ=UTC TB --- 2011-03-07 18:36:37 - __MAKE_CONF=/dev/null TB --- 2011-03-07 18:36:37 - cd /src TB --- 2011-03-07 18:36:37 - /usr/bin/make -B buildworld World build started on Mon Mar 7 18:36:37 UTC 2011 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 [...] cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/lzf.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/metadata.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/nv.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c parse.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/pjdlog.c cc1: warnings being treated as errors /src/sbin/hastctl/../hastd/pjdlog.c: In function 'pjdlog_printf_render_sockaddr': /src/sbin/hastctl/../hastd/pjdlog.c:110: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/sbin/hastctl. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-03-07 19:30:45 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-03-07 19:30:45 - ERROR: failed to build world TB --- 2011-03-07 19:30:45 - 2466.42 user 544.89 system 3269.65 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
[head tinderbox] failure on sparc64/sun4v
TB --- 2011-03-07 18:36:19 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-07 18:36:19 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2011-03-07 18:36:19 - cleaning the object tree TB --- 2011-03-07 18:36:25 - cvsupping the source tree TB --- 2011-03-07 18:36:25 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2011-03-07 18:36:38 - building world TB --- 2011-03-07 18:36:38 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-07 18:36:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-07 18:36:38 - TARGET=sun4v TB --- 2011-03-07 18:36:38 - TARGET_ARCH=sparc64 TB --- 2011-03-07 18:36:38 - TZ=UTC TB --- 2011-03-07 18:36:38 - __MAKE_CONF=/dev/null TB --- 2011-03-07 18:36:38 - cd /src TB --- 2011-03-07 18:36:38 - /usr/bin/make -B buildworld World build started on Mon Mar 7 18:36:40 UTC 2011 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 [...] cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/lzf.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/metadata.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/nv.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c parse.c cc -O2 -pipe -I/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-format -c /src/sbin/hastctl/../hastd/pjdlog.c cc1: warnings being treated as errors /src/sbin/hastctl/../hastd/pjdlog.c: In function 'pjdlog_printf_render_sockaddr': /src/sbin/hastctl/../hastd/pjdlog.c:110: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/sbin/hastctl. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-03-07 19:30:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-03-07 19:30:48 - ERROR: failed to build world TB --- 2011-03-07 19:30:48 - 2467.21 user 549.08 system 3268.88 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.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: Request for review/testing: switching the default installer
On Mon, Feb 28, 2011 at 6:49 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: BSDinstall has acquired at this point its final form (prior to a future merge with pc-sysinstall), and I believe is ready to replace sysinstall on the 9.0 snapshot ISOs. Barring any objections, I would like to pull this switch 2 weeks from today, on the 14th of March. snip Bug reports would be very appreciated at this time. There are three known bugs currently, which will be fixed soon, so please don't report these: error reporting is not graceful if there are no writable disks in the system, you must select at least one optional component, and the doc build is not currently connected to the releases. snip After much finnaggling and gnashing of teeth around hardware (not related to installer), I have managed to get a bootable 9-CURRENT image with BSDInstall, and used it to get a bootable install of FreeBSD 9-CURRENT. :) Here are my thought and experiences using the new installer. Things I really like: - that the install CD is a LiveCD with a fully functional system; while it won't replace a Frenzy CD, it's very close - very streamlined install without a lot of extra fluff that just gets skipped anyway (like everything underneath Standard in the first sysinstall screen) - the ability to use features like GPT, gmirror, zfs right from the get-go - the ability to drop to a fully functional shell at various stages of the install, with access to proper man pages Things that irritated me: - when you drop to a shell from the disk editor screen, it lists the instructions at the top, but then never repeats them ever again - if you get lost in the disk editor shell and type exit to get back to the disk editor ... it thinks you are finished partitioning and carries on with the install, which then errors out due to no writable filesystems, requiring you to restart the entire process - the disk editor is very limited, especially in its error handling; I found myself stuck in a loop trying to exit the screen without a / filesystem listed, but I was doing everything from the shell - screen flips between a nice blue background (the curses interface?) and a black background (running shell commands?) which is quite jarring and slightly confusing; - screen elements go from nicely centred (curses interface?) and then jump to the top-left corner of the screen (shell commands?) which is also quite jarring and slightly confusing The last two may be limitations in the curses setup? But it would be nice if shell command I/O could be centred like the rest, and if the background could remain a single colour. Not huge issues, just things that irritated me. :) Overall, I am quite impressed with the new installer, as it is *just* an installer and not a system configuration creator (or breaker) like sysinstall. Now that I understand the new world order of GPT-based partitioning and booting, I think I'm going to like FreeBSD 9.0 a heck of a lot. ... off to play with dedupe and other ZFSv28 goodies ... -- Freddie Cash fjwc...@gmail.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
r219385 build error.
Hi, The following error occurs when i try to build r219385. cc -O2 -pipe -march=core2 -DHAVE_CONFIG_H -I/usr/src/kerberos5/tools/make-roken/../../include -std=gnu99 -c make-roken.c make-roken.c:1: error: bad value (core2) for -march= switch make-roken.c:1: error: bad value (core2) for -mtune= switch /usr/src/kerberos5/tools/make-print-version/../../../crypto/heimdal/lib/vers/make-print-version.c:1: error: bad value (core2) for -march= switch /usr/src/kerberos5/tools/make-print-version/../../../crypto/heimdal/lib/vers/make-print-version.c:1: error: bad value (core2) for -mtune= switch *** Error code 1 1 error *** Error code 2 *** Error code 1 1 error *** Error code 2 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Sure enough i have CPUTYPE?=core2 in make.conf which it doesn' t expand to nocona after the latest patches. Regards ___ 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: r219385 build error.
On Mon Mar 7 11, George Liaskos wrote: Hi, The following error occurs when i try to build r219385. cc -O2 -pipe -march=core2 -DHAVE_CONFIG_H -I/usr/src/kerberos5/tools/make-roken/../../include -std=gnu99 -c make-roken.c make-roken.c:1: error: bad value (core2) for -march= switch make-roken.c:1: error: bad value (core2) for -mtune= switch /usr/src/kerberos5/tools/make-print-version/../../../crypto/heimdal/lib/vers/make-print-version.c:1: error: bad value (core2) for -march= switch /usr/src/kerberos5/tools/make-print-version/../../../crypto/heimdal/lib/vers/make-print-version.c:1: error: bad value (core2) for -mtune= switch *** Error code 1 1 error *** Error code 2 *** Error code 1 1 error *** Error code 2 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Sure enough i have CPUTYPE?=core2 in make.conf which it doesn' t expand to nocona after the latest patches. that's because the latest gcc commits have support for core2 and thus it no longer is being expanded to nocona. please note that having core2 in make.conf has always been *wrong*. hence the need to reset it to nocona. the best way to fix this would be to set CPUYTYPE?=native. if you want core2 support now's the chance to actually get it. just update world and you can use CPUTYPE?=core2 and this time it *really* is supported. ;) cheers. alex Regards -- a13x ___ 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: r219385 build error.
What process did you follow to get here? I did a make toolchain followed by make buildworld. that's because the latest gcc commits have support for core2 and thus it no longer is being expanded to nocona. please note that having core2 in make.conf has always been *wrong*. hence the need to reset it to nocona. the best way to fix this would be to set CPUYTYPE?=native. if you want core2 support now's the chance to actually get it. just update world and you can use CPUTYPE?=core2 and this time it *really* is supported. ;) I saw the relevant commits about core2, this is the reason i decided to do a rebuild. I didn't know that core2 was wrong, it's in the make.conf documentation, native it's not and after serious googling i found out that i should actually avoid it. I always believed that core2 was there [make.conf] as a future proof upgrade path for when the base toolchain actually supports core2. So, should i use native cputype? ___ 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: r219385 build error.
On Mon, Mar 07, 2011 at 11:19:40PM +0200, George Liaskos wrote: What process did you follow to get here? I did a make toolchain followed by make buildworld. that's because the latest gcc commits have support for core2 and thus it no longer is being expanded to nocona. please note that having core2 in make.conf has always been *wrong*. hence the need to reset it to nocona. the best way to fix this would be to set CPUYTYPE?=native. if you want core2 support now's the chance to actually get it. just update world and you can use CPUTYPE?=core2 and this time it *really* is supported. ;) I saw the relevant commits about core2, this is the reason i decided to do a rebuild. I didn't know that core2 was wrong, it's in the make.conf documentation, native it's not and after serious googling i found out that i should actually avoid it. I always believed that core2 was there [make.conf] as a future proof upgrade path for when the base toolchain actually supports core2. So, should i use native cputype? You did not shown the actual point where the error was raised. Applying some psychic powers, I could guess that it happens at the bootstrap stage. And this would be reasonable indeed, since bootstrap needs to use the system compiler, until the new cross toolchain is ready. And obviously system compiler not yet supports -march=core2, since you are only compiling the code that supports. Of course, all this assuming that error indeed happens at bootstrap, and the referenced commit does not introduce regressions, which I think is the case. I believe the solution for you would be to remove any CPU model settings from make.conf, make and install new world, then try new buildworld with desired settings. As a side note, I do not believe that you would get any measurable changes. pgpmOjzyCpfmm.pgp Description: PGP signature
Re: r219385 build error.
On Mon Mar 7 11, George Liaskos wrote: What process did you follow to get here? I did a make toolchain followed by make buildworld. that's because the latest gcc commits have support for core2 and thus it no longer is being expanded to nocona. please note that having core2 in make.conf has always been *wrong*. hence the need to reset it to nocona. the best way to fix this would be to set CPUYTYPE?=native. if you want core2 support now's the chance to actually get it. just update world and you can use CPUTYPE?=core2 and this time it *really* is supported. ;) I saw the relevant commits about core2, this is the reason i decided to do a rebuild. I didn't know that core2 was wrong, it's in the make.conf documentation, native it's not and after serious googling i found out that i should actually avoid it. I always believed that core2 was there [make.conf] as a future proof upgrade path for when the base toolchain actually supports core2. So, should i use native cputype? either native or nocona (actually native should evaluate to nocona): touch _native_test.c gcc -march=native -### _native_test.c should tell which -march and -mtune settings gcc assumes for native. indeed there are some known problems with native, but i think those are limited to architectures such as mips and arm. with i386 or amd64 native shouldn't cause any problems. i think core2 was always wrong to set in make.conf, because the base gcc simply does not support it. however so many people are trying to boost speed etc. by adding make.conf options they find scattered over the internet and on various linux dist wikis, that core2 was added as a workaround so people could use it (even though it wasn't supported). cheers. alex -- a13x ___ 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: r219385 build error.
either native or nocona (actually native should evaluate to nocona): touch _native_test.c gcc -march=native -### _native_test.c should tell which -march and -mtune settings gcc assumes for native. indeed there are some known problems with native, but i think those are limited to architectures such as mips and arm. with i386 or amd64 native shouldn't cause any problems. i think core2 was always wrong to set in make.conf, because the base gcc simply does not support it. however so many people are trying to boost speed etc. by adding make.conf options they find scattered over the internet and on various linux dist wikis, that core2 was added as a workaround so people could use it (even though it wasn't supported). I still don't understand how bsd.cpu.mk is going to handle native as value to set CPUTYPE / MACHINE_CPU, or this is irrelevant? Would it be better to use the following? CPUTYPE?=nocona NO_CPU_CFLAGS=yes NO_CPU_COPTFLAGS=yes CFLAGS+= -march=native Thank you for your clarifications. ___ 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: r219385 build error.
On Tue Mar 8 11, George Liaskos wrote:
either native or nocona (actually native should evaluate to nocona):
touch _native_test.c gcc -march=native -### _native_test.c
should tell which -march and -mtune settings gcc assumes for native.
indeed there are some known problems with native, but i think those are
limited to architectures such as mips and arm. with i386 or amd64 native
shouldn't cause any problems.
i think core2 was always wrong to set in make.conf, because the base gcc
simply
does not support it. however so many people are trying to boost speed etc.
by
adding make.conf options they find scattered over the internet and on
various
linux dist wikis, that core2 was added as a workaround so people could use
it
(even though it wasn't supported).
I still don't understand how bsd.cpu.mk is going to handle native as
value to set CPUTYPE / MACHINE_CPU, or this is irrelevant?
Would it be better to use the following?
native doesn't get handled by bsd.cpu.mk at all! it gets passed to gcc
directly and gcc choses -m{tune,arch} on it's own.
don't add -march=* directly to CFLAGS. this is bound to go wrong at some
point. use CPUTYPE to set the cpu and CFLAGS for -O*, -pipe, etc.
also please keep in mind that the optimisations that can be achieved by
finetuning make.conf are rather minor. some people think that with
cflags and cpu juju they can boost the OS. i don't believe that's true. the
chances are much greater that you're adding a problematic switch and end up
with binaries during installworld that segfault. so it's not really worth
getting into this kinda trouble just for the sake of optimisation.
a simple
CPUTYPE ?= native
COPTFLAGS = -O0 -pipe
CFLAGS = -O2 -pipe
should be close to perfekt. ;)
cheers.
alex
CPUTYPE?=nocona
NO_CPU_CFLAGS=yes
NO_CPU_COPTFLAGS=yes
CFLAGS+= -march=native
Thank you for your clarifications.
--
a13x
___
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: r219385 build error.
native doesn't get handled by bsd.cpu.mk at all! it gets passed to gcc
directly and gcc choses -m{tune,arch} on it's own.
don't add -march=* directly to CFLAGS. this is bound to go wrong at some
point. use CPUTYPE to set the cpu and CFLAGS for -O*, -pipe, etc.
also please keep in mind that the optimisations that can be achieved by
finetuning make.conf are rather minor. some people think that with
cflags and cpu juju they can boost the OS. i don't believe that's true. the
chances are much greater that you're adding a problematic switch and end up
with binaries during installworld that segfault. so it's not really worth
getting into this kinda trouble just for the sake of optimisation.
a simple
CPUTYPE ?= native
COPTFLAGS = -O0 -pipe
CFLAGS = -O2 -pipe
should be close to perfekt. ;)
cheers.
alex
Thank you again.
It's not so much about the base system but the ports. Now that the
assembler and binutils support newer SIMD commands it makes sense to
exploit them, I know that they are not used during kernel compilation.
Using newer / different compiler from ports makes things more complicated.
.
___
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: missing files in readdir(3) on NFS export of ZFS volume (since v28?)
Hello, I'm running a 9-current server as compiled on Sat Mar 5 02:17:14 CET 2011. Since I upgraded to ZFS v28 I noticed missing files from NFS. The files are still accessible through NFS but they don't show up on a readdir(3). Oh, I forgot to mention that the business related to VFS_VGET() only applies to ReaddirPlus. If your client is using regular Readdir, then I have no idea what it might be? (Assuming that is setting its file system type to zfs so that the cookies don't have to be monotonically increasing values. rick ___ 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: missing files in readdir(3) on NFS export of ZFS volume (since v28?)
Hello, I'm running a 9-current server as compiled on Sat Mar 5 02:17:14 CET 2011. Since I upgraded to ZFS v28 I noticed missing files from NFS. The files are still accessible through NFS but they don't show up on a readdir(3). Readdir (in both NFS servers) depends on ZFS to reply EOPNOTSUPP for VFS_VGET() when it cannot be done, so that Readdir will switch to using VP_LOOKUP(). Just a wild guess, but maybe ZFS v28 isn't doing this? rick On the NFS server (files are stored on a ZFS v15 volume, not yet upgraded to the v28 format): % cd /usr/ports/devel/autoconf % ls -i 311401 Makefile 204505 files 204509 pkg-plist 204504 distinfo 204508 pkg-descr On the NFS client side (FreeBSD 8.2-RELEASE): % cd /usr/ports/devel/autoconf % ls -i 204504 distinfo 204508 pkg-descr 204505 files 204509 pkg-plist Yet the missing file can be accessed: % head -3 Makefile # New ports collection makefile for: autoconf # Date created: 7th December 2006 # Whom: a...@freebsd.org Note that the missing files are scattered throughout the volume, no relation to the inode number, as shown on a diff: @@ -1,8 +1,6 @@ 3 7 drwxr-xr-x 70 pb staff 93 4 mar 19:11 /usr/ports - 4 2 -rw-r--r-- 1 pb staff 241 24 jan 2007 /usr/ports/astro/tclgeomap/pkg-plist 5 3 drwxr-xr-x 2 pb staff 6 22 fév 12:04 /usr/ports/astro/tkgeomap 6 3 drwxr-xr-x 4 pb staff 6 29 jul 2008 /usr/ports/Tools - 7 5 drwxr-xr-x 33 pb staff 34 25 nov 15:59 /usr/ports/accessibility 8 3 drwxr-xr-x 12 pb staff 14 9 fév 2009 /usr/ports/arabic 11 51 drwxr-xr-x 900 pb staff 901 6 mar 14:36 /usr/ports/audio 12 3 -rw-r--r-- 1 pb staff 584 25 aoû 2006 /usr/ports/astro/tkgeomap/pkg-descr @@ -16,10 +14,8 @@ 23 3 drwxr-xr-x 3 pb staff 7 24 mar 2010 /usr/ports/astro/wcslib 24 4 -rw-r--r-- 1 pb staff 1414 5 jan 2010 /usr/ports/astro/wcslib/Makefile 25 5 drwxr-xr-x 31 pb staff 33 1 jan 23:16 /usr/ports/french - 26 2 -rw-r--r-- 1 pb staff 197 5 jan 2010 /usr/ports/astro/wcslib/distinfo 27 63 drwxr-xr-x 1110 pb staff 23 fév 15:37 /usr/ports/games 28 3 drwxr-xr-x 2 pb staff 4 24 mar 2010 /usr/ports/astro/wcslib/files - 29 2 -rw-r--r-- 1 pb staff 236 5 jan 2010 /usr/ports/astro/wcslib/files/6-patch-configure 30 3 -rw-r--r-- 1 pb staff 677 5 jan 2010 /usr/ports/astro/wcslib/files/patch-GNUmakefile 31 2 -rw-r--r-- 1 pb staff 401 17 jul 2009 /usr/ports/astro/wcslib/pkg-descr 32 4 -rw-r--r-- 1 pb staff 1515 5 jan 2010 /usr/ports/astro/wcslib/pkg-plist ... Reverting to an old 9-current kernel (January 10, before the ZFS v28 patches) fixes the problem... -- Sent from my FreeBSD server Pierre Beyssac p...@fasterix.frmug.org ___ 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 ___ 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: r219385 build error.
This actually does not happen at the bootstrap stage, but when building 32-bit compat libs under amd64. It looks like the system compiler is used here instead (should it be this way, isn't it a bug somewhere around Makefile.inc1?). Yes, building + installing world without this optimization makes it work again (you can build the whole world). And generally, I am putting the LIB32CPUFLAGS in question, why are we using here a 64-bit cpu type at all? In bsd.cpu.mk we map nocona and core2 to prescott for i386. Dňa 07.03.2011 22:29, Kostik Belousov wrote / napísal(a): On Mon, Mar 07, 2011 at 11:19:40PM +0200, George Liaskos wrote: What process did you follow to get here? I did a make toolchain followed by make buildworld. that's because the latest gcc commits have support for core2 and thus it no longer is being expanded to nocona. please note that having core2 in make.conf has always been *wrong*. hence the need to reset it to nocona. the best way to fix this would be to set CPUYTYPE?=native. if you want core2 support now's the chance to actually get it. just update world and you can use CPUTYPE?=core2 and this time it *really* is supported. ;) I saw the relevant commits about core2, this is the reason i decided to do a rebuild. I didn't know that core2 was wrong, it's in the make.conf documentation, native it's not and after serious googling i found out that i should actually avoid it. I always believed that core2 was there [make.conf] as a future proof upgrade path for when the base toolchain actually supports core2. So, should i use native cputype? You did not shown the actual point where the error was raised. Applying some psychic powers, I could guess that it happens at the bootstrap stage. And this would be reasonable indeed, since bootstrap needs to use the system compiler, until the new cross toolchain is ready. And obviously system compiler not yet supports -march=core2, since you are only compiling the code that supports. Of course, all this assuming that error indeed happens at bootstrap, and the referenced commit does not introduce regressions, which I think is the case. I believe the solution for you would be to remove any CPU model settings from make.conf, make and install new world, then try new buildworld with desired settings. As a side note, I do not believe that you would get any measurable changes. ___ 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: r219385 build error.
This change did NOT add SSSE3 or any other new instruction sets to our
base compiler.
The only change of using -march=core2 vs -march=nocona is actually
different instruction costs that may result
in binaries more optimized for your core2 and later CPUs (and less
optimized for nocona and earlier CPUs - but they will run there if the
CPU supports sse3).
We support newer instruction sets for base compiling starting with the
latest base binutils upgrade and
that is available only in CURRENT.
I might take a look at the possibility of backporting SSSE3, but that is
a way more intrusive change than this one. I will also run some more
benchmarks.
Dňa 08.03.2011 00:14, George Liaskos wrote / napísal(a):
native doesn't get handled by bsd.cpu.mk at all! it gets passed to gcc
directly and gcc choses -m{tune,arch} on it's own.
don't add -march=* directly to CFLAGS. this is bound to go wrong at some
point. use CPUTYPE to set the cpu and CFLAGS for -O*, -pipe, etc.
also please keep in mind that the optimisations that can be achieved by
finetuning make.conf are rather minor. some people think that with
cflags and cpu juju they can boost the OS. i don't believe that's true. the
chances are much greater that you're adding a problematic switch and end up
with binaries during installworld that segfault. so it's not really worth
getting into this kinda trouble just for the sake of optimisation.
a simple
CPUTYPE ?= native
COPTFLAGS = -O0 -pipe
CFLAGS = -O2 -pipe
should be close to perfekt. ;)
cheers.
alex
Thank you again.
It's not so much about the base system but the ports. Now that the
assembler and binutils support newer SIMD commands it makes sense to
exploit them, I know that they are not used during kernel compilation.
Using newer / different compiler from ports makes things more complicated.
.
___
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
___
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: r219385 build error.
On 03/07/2011 14:56, Alexander Best wrote:
native doesn't get handled by bsd.cpu.mk at all! it gets passed to gcc
directly and gcc choses -m{tune,arch} on it's own.
don't add -march=* directly to CFLAGS. this is bound to go wrong at some
point. use CPUTYPE to set the cpu and CFLAGS for -O*, -pipe, etc.
also please keep in mind that the optimisations that can be achieved by
finetuning make.conf are rather minor. some people think that with
cflags and cpu juju they can boost the OS. i don't believe that's true. the
chances are much greater that you're adding a problematic switch and end up
with binaries during installworld that segfault. so it's not really worth
getting into this kinda trouble just for the sake of optimisation.
a simple
CPUTYPE ?= native
COPTFLAGS = -O0 -pipe
CFLAGS = -O2 -pipe
should be close to perfekt.;)
Does any of this pertain to clang?
Doug
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.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
Re: Request for review/testing: switching the default installer
On 03/07/11 14:14, Freddie Cash wrote: On Mon, Feb 28, 2011 at 6:49 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: BSDinstall has acquired at this point its final form (prior to a future merge with pc-sysinstall), and I believe is ready to replace sysinstall on the 9.0 snapshot ISOs. Barring any objections, I would like to pull this switch 2 weeks from today, on the 14th of March. snip Bug reports would be very appreciated at this time. There are three known bugs currently, which will be fixed soon, so please don't report these: error reporting is not graceful if there are no writable disks in the system, you must select at least one optional component, and the doc build is not currently connected to the releases. snip After much finnaggling and gnashing of teeth around hardware (not related to installer), I have managed to get a bootable 9-CURRENT image with BSDInstall, and used it to get a bootable install of FreeBSD 9-CURRENT. :) Thanks for testing, and sympathies for the hardware trouble! Here are my thought and experiences using the new installer. Things I really like: - that the install CD is a LiveCD with a fully functional system; while it won't replace a Frenzy CD, it's very close - very streamlined install without a lot of extra fluff that just gets skipped anyway (like everything underneath Standard in the first sysinstall screen) - the ability to use features like GPT, gmirror, zfs right from the get-go - the ability to drop to a fully functional shell at various stages of the install, with access to proper man pages Things that irritated me: - when you drop to a shell from the disk editor screen, it lists the instructions at the top, but then never repeats them ever again Can you suggest a better way to do this? In other words, when and in what circumstances would you want to see them again? - if you get lost in the disk editor shell and type exit to get back to the disk editor ... it thinks you are finished partitioning and carries on with the install, which then errors out due to no writable filesystems, requiring you to restart the entire process This is bad. I can modify it to check if a filesystem has been mounted at /mnt, and maybe if the fstab file exists and restart the disk editor menu if they have not. - the disk editor is very limited, especially in its error handling; I found myself stuck in a loop trying to exit the screen without a / filesystem listed, but I was doing everything from the shell That's a clear bug. It should probably only validate the setup if 'Save' is selected. The issue of whether it should allow you to save without defining a / partition when invoked from a shell is a more complicated one, and one I'll have to think about (suggestions welcome). - screen flips between a nice blue background (the curses interface?) and a black background (running shell commands?) which is quite jarring and slightly confusing; - screen elements go from nicely centred (curses interface?) and then jump to the top-left corner of the screen (shell commands?) which is also quite jarring and slightly confusing Yes, this should be prettified. It's running a few things (passwd, adduser) in a chroot, and I figured getting things working there was more important than making them pretty for now. The last two may be limitations in the curses setup? But it would be nice if shell command I/O could be centred like the rest, and if the background could remain a single colour. Not huge issues, just things that irritated me. :) Overall, I am quite impressed with the new installer, as it is *just* an installer and not a system configuration creator (or breaker) like sysinstall. Now that I understand the new world order of GPT-based partitioning and booting, I think I'm going to like FreeBSD 9.0 a heck of a lot. ... off to play with dedupe and other ZFSv28 goodies ... Thanks! -Nathan ___ 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: Request for review/testing: switching the default installer
On Mon, Mar 7, 2011 at 4:56 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 03/07/11 14:14, Freddie Cash wrote: Things that irritated me: - when you drop to a shell from the disk editor screen, it lists the instructions at the top, but then never repeats them ever again Can you suggest a better way to do this? In other words, when and in what circumstances would you want to see them again? It follows along with the next item, so I'll address them both below. - if you get lost in the disk editor shell and type exit to get back to the disk editor ... it thinks you are finished partitioning and carries on with the install, which then errors out due to no writable filesystems, requiring you to restart the entire process This is bad. I can modify it to check if a filesystem has been mounted at /mnt, and maybe if the fstab file exists and restart the disk editor menu if they have not. If something like the above is done, then the first item above is also handled. :) As in, if you forget the instructions, just exit the shell to go back to the disk editor, which then complains you don't have a mounted filesystem to install to, and then you can drop back to the shell. Maybe loop back to the beginning of the disk editor, where it asks you if you want to do it Guided, Manual, or Shell? Or something like that. Something needs to go here to check for a mounted, writable filesystem to install to. :) On the flip side, the entire install process is short enough that it's not too onerous to restart it. - the disk editor is very limited, especially in its error handling; I found myself stuck in a loop trying to exit the screen without a / filesystem listed, but I was doing everything from the shell That's a clear bug. It should probably only validate the setup if 'Save' is selected. The issue of whether it should allow you to save without defining a / partition when invoked from a shell is a more complicated one, and one I'll have to think about (suggestions welcome). I don't recall there being a Save option, but maybe I skipped over it and just went to Exit. I'll have to look at this screen again. Using Save probably would have helpded. :) - screen flips between a nice blue background (the curses interface?) and a black background (running shell commands?) which is quite jarring and slightly confusing; - screen elements go from nicely centred (curses interface?) and then jump to the top-left corner of the screen (shell commands?) which is also quite jarring and slightly confusing Yes, this should be prettified. It's running a few things (passwd, adduser) in a chroot, and I figured getting things working there was more important than making them pretty for now. It's a minor nit, as sysinstall does the same. Maybe there's a way to use text input fields (like the DHCP screens, and adduser screens from sysinstall), then run the commands in the background, and just show error/success messages? [shrug] I know nothing about curses programming. :) -- Freddie Cash fjwc...@gmail.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
Re: Request for review/testing: switching the default installer
On 03/07/11 19:27, Freddie Cash wrote: On Mon, Mar 7, 2011 at 4:56 PM, Nathan Whitehornnwhiteh...@freebsd.org wrote: On 03/07/11 14:14, Freddie Cash wrote: Things that irritated me: - when you drop to a shell from the disk editor screen, it lists the instructions at the top, but then never repeats them ever again Can you suggest a better way to do this? In other words, when and in what circumstances would you want to see them again? It follows along with the next item, so I'll address them both below. - if you get lost in the disk editor shell and type exit to get back to the disk editor ... it thinks you are finished partitioning and carries on with the install, which then errors out due to no writable filesystems, requiring you to restart the entire process This is bad. I can modify it to check if a filesystem has been mounted at /mnt, and maybe if the fstab file exists and restart the disk editor menu if they have not. If something like the above is done, then the first item above is also handled. :) As in, if you forget the instructions, just exit the shell to go back to the disk editor, which then complains you don't have a mounted filesystem to install to, and then you can drop back to the shell. Maybe loop back to the beginning of the disk editor, where it asks you if you want to do it Guided, Manual, or Shell? Or something like that. The Guided, Manual, Shell is what I meant by disk editor menu, so I agree with you entirely :) Something needs to go here to check for a mounted, writable filesystem to install to. :) On the flip side, the entire install process is short enough that it's not too onerous to restart it. - the disk editor is very limited, especially in its error handling; I found myself stuck in a loop trying to exit the screen without a / filesystem listed, but I was doing everything from the shell That's a clear bug. It should probably only validate the setup if 'Save' is selected. The issue of whether it should allow you to save without defining a / partition when invoked from a shell is a more complicated one, and one I'll have to think about (suggestions welcome). I don't recall there being a Save option, but maybe I skipped over it and just went to Exit. I'll have to look at this screen again. Using Save probably would have helpded. :) If you press Exit, it asks whether you want to Save, Abort, or Cancel. Abort exits the partitioner without making changes. I just modified this so that it will only try to validate the disk setup if you press Save -- you don't need a valid setup if you are bailing on the partitioner, after all. - screen flips between a nice blue background (the curses interface?) and a black background (running shell commands?) which is quite jarring and slightly confusing; - screen elements go from nicely centred (curses interface?) and then jump to the top-left corner of the screen (shell commands?) which is also quite jarring and slightly confusing Yes, this should be prettified. It's running a few things (passwd, adduser) in a chroot, and I figured getting things working there was more important than making them pretty for now. It's a minor nit, as sysinstall does the same. Maybe there's a way to use text input fields (like the DHCP screens, and adduser screens from sysinstall), then run the commands in the background, and just show error/success messages? [shrug] I know nothing about curses programming. :) Yeah, I need to find time/a good way to do this (or someone else can: patches are always welcome). Text fields would work well, and I think even just making the banner at the top of the screen blue would help. -Nathan ___ 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
Request to test if_ath - TX power control changes
Hi everyone, This patch introduces open-loop TX power control for the AR9280 (Merlin) and tidies up some of the code duplication between the AR5416 and AR9285 power control code. If you're using an AR9280 then please, -please- test this out and get back to me. I'd also appreciate EEPROM dumps (via ath_prom_read) so I can see what your card has programmed in it. Doubly so if you're using an AR9280 in 5ghz mode. If you're using a non-AR9280 chip (ie, AR5416, AR9160, AR9285), then i'd also appreciate further testing. I'd like to make sure I haven't introduced regressions here! Although legacy rate TX'ing seems to work with this patch, if your AR9280 uses open-loop TX power control then the output from your card is very likely going to be quite distorted. It's bad for you, bad for your card and bad for your surroundings. Besides some further code restructuring (which won't change functionality), I'm going to take a break from making any further changes that aren't bugfixes until the AR9285 related bugs Ian was seeing are found/fixed, along with any and all regressions people report with the driver. This is your opportunity to get me to find/fix performance, stability and other issues that have crept up, so it's in the best interests of everyone (including you!) to test this stuff as thoroughly as possible before 9.0-RELEASE comes out. Thanks! Adrian On 8 March 2011 14:59, Adrian Chadd adr...@freebsd.org wrote: Author: adrian Date: Tue Mar 8 06:59:59 2011 New Revision: 219393 URL: http://svn.freebsd.org/changeset/base/219393 Log: Implement open-loop TX power control (OLC) for Merlin (AR9280) and generally tidy up the TX power programming code. Enforce that the TX power offset for Merlin is -5 dBm, rather than any other value programmable in the EEPROM. This requires some further code to be ported over from ath9k, so until that is done and tested, fail to attach NICs whose TX power offset isn't -5 dBm. This improves both legacy and HT transmission on my merlin board. It allows for stable MCS TX up to MCS15. Specifics: * Refactor out a bunch of the TX power calibration code - setting/obtaining the power detector / gain boundaries, programming the PDADC * Take the -5 dBm TX power offset into account on Merlin - 0 in the per-rate TX power register means -5 dBm, not 0 dBm * When doing OLC * Enforce min (0) and max (AR5416_MAX_RATE_POWER) when fiddling with the TX power, to avoid the TX power values from wrapping when low. * Implement the 1 dBm cck power offset when doing OLC * Implement temperature compensation for 2.4ghz mode when doing OLC * Implement an AR9280 specific TX power calibration routine which includes the OLC twiddles, leaving the earlier chipset path (AR5416, AR9160) alone Whilst here, use these refactored routines for the AR9285 TX power calibration/programming code and enforce correct overflow/underflow handling when fiddling with TX power values. Obtained from:linux ath9k ___ 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: missing files in readdir(3) on NFS export of ZFS volume (since v28?)
Hello Rick, Thanks for your reply. On Mon, Mar 07, 2011 at 06:12:43PM -0500, Rick Macklem wrote: Readdir (in both NFS servers) depends on ZFS to reply EOPNOTSUPP for VFS_VGET() when it cannot be done, so that Readdir will switch to using VP_LOOKUP(). Just a wild guess, but maybe ZFS v28 isn't doing this? My client was plain and simple ls(1). I said readdir(3) because I wrongly assumed ls used that, but actually from looking at the code it looks like it uses fts_open(3) and friends instead... -- Sent from my FreeBSD server Pierre Beyssac p...@fasterix.frmug.org ___ 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
