Re: Atheros 9287 - no carrier . revision 249623.
Hi, I've just committed some changes to -HEAD. Please update to the latest -HEAD and paste me the ath0 dmesg output. It will include the chainmask information. Thanks, Adrian ___ 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: Cannot unmount nullfs in current
On Thu, Apr 18, 2013 at 4:27 PM, Craig Rodrigues rodr...@freebsd.orgwrote: Hi, I am trying to build some software which uses nanobsd, and mounts/unmounts many nullfs mounts while it runs. I am hitting failures where I cannot unmount nullfs file systems. I cannot figure out why. I forgot to run fstat. :( fstat /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME rodrigc gam_server 2275 37 /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles 3194579 drwxr-xr-x 196 r /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles Since I run the GNOME desktop, gnome has a dependency on the gamin port. The gamin port contains gam_server. gamin monitors file system activity. It looks like gam_server gets triggered when things are mounted, and for some reason, sometimes fails to go away. I need to read http://people.gnome.org/~veillard/gamin/config.html and figure out how to disable gamin, or just remove gamin from my system. Annoying. :( -- Craig ___ 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: ipfilter(4) needs maintainer
2013/4/14 Gary Palmer gpal...@freebsd.org: On Sun, Apr 14, 2013 at 09:48:33AM -0600, Warren Block wrote: Is it possible to move ipfilter into a port? That may work short term, but the ENOMAINTAINER problem will quickly creep up again as kernel APIs change. If the author has lost interest in maintaining the FreeBSD port of ipfilter then unless someone steps forward to carry on the work, I don't see much of a future for ipfilter in FreeBSD Do we honestly need three packet filters? No, for me only one should be present. I completely understand that some users still use IPFilter and IPFW but why providing three packet filters? The answer should be: use one and document only one. If at the beginning we started documenting only one all users should have used the only one present. Now we really need to remove the ancestral ipfilter and tell people switching to pf(4). Everything in life change, if we need to maintain all code from the past we will have a lot of compat code that pollute the full source tree and we will never improve the code just because of old bits My $0.02, Regards -- Demelier David ___ 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 9287 - no carrier . revision 249623.
Adrian, I found the problem. I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define ATH_ENABLE_11N - everything work. Artyom Mirgorodskiy On Friday 19 April 2013 13:27:21 wrote: Updated. However I did not see chainmask information. See attached On Friday 19 April 2013 00:57:12 Adrian Chadd wrote: Hi, I've just committed some changes to -HEAD. Please update to the latest -HEAD and paste me the ath0 dmesg output. It will include the chainmask information. Thanks, Adrian -- Artyom Mirgorodskiy -- Artyom Mirgorodskiy ___ 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 9287 - no carrier . revision 249623.
oo good to know! let me setup the chainmask info whether or not the 11n option is set. thanks! adrian On 19 April 2013 04:08, Artyom Mirgorodskiy artyom.mirgorod...@gmail.com wrote: Adrian, I found the problem. I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define ATH_ENABLE_11N - everything work. Artyom Mirgorodskiy On Friday 19 April 2013 13:27:21 wrote: Updated. However I did not see chainmask information. See attached On Friday 19 April 2013 00:57:12 Adrian Chadd wrote: Hi, I've just committed some changes to -HEAD. Please update to the latest -HEAD and paste me the ath0 dmesg output. It will include the chainmask information. Thanks, Adrian -- Artyom Mirgorodskiy -- Artyom Mirgorodskiy ___ 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: Cannot unmount nullfs in current
On Apr 18, 2013 7:04 PM, Craig Rodrigues rodr...@freebsd.org wrote: Hi, I am trying to build some software which uses nanobsd, and mounts/unmounts many nullfs mounts while it runs. I am hitting failures where I cannot unmount nullfs file systems. I cannot figure out why. I am also getting similar failures while trying to build freenas. Here is more info. SYSTEM == I am running amd64, current build at this revision: 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r249181: Sat Apr 6 03:07:32 UTC 2013 amd64 STEPS TO REPRODUCE === (1) Create a directory, /opt2/branches. Make sure that /opt2/branches is on ZFS (2) mkdir -p /opt2/branches/freenas mkdir -p /opt2/branches/freenas-cache (3) git clone git://github.com/freenas/freenas.git /opt2/branches/freenas git clone git:// github.com/freenas/ports.git/opt2/branches/freenas-cache/ports git clone git:// github.com/trueos/trueos.git/opt2/branches/freenas-cache/trueos (4) sudo to root (5) cd /opt2/branches/freenas (6) script build.log env GIT_REPO=/opt2/branches/freenas-cache/trueos \ GIT_PORTS_REPO=/opt2/branches/freenas-cache/ports \ sh build/do_build.sh The build cranks for a while, and then I get this error: 00:02:37 ### log: /opt2/branches/freenas/os-base/amd64/_.cust.add_pkg_archivers_lzo2 I do not get this. do_build.sh: ERROR: FreeNAS /opt2/branches/freenas/nanobsd/os-base build FAILED; please check above log for more details I get this which looks like a generic build failure message. I do not have gnome or any X related things. If I look in .cust.add_pkg_archivers_lzo2, I see this error: + umount /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles umount: unmount of /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles failed: Device busy Where do you find/see logs for the build? Another weird thing. Somehow my /sbin was wiped out and only had some pbi-* files in it. This happened to me on 2 different machines while trying to build freenas. I will try to take a closer look today when time permits. Thanks, Hiren If I try to do this manually: # umount /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles umount: unmount of /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles failed: Device busy I can't figure out why this mount is busy. If I do: umount -f /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles it unmounts, but I don't like using the '-f' flag to force the unmount. Any ideas? I am attaching some of my logs. -- Craig ___ 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: Cannot unmount nullfs in current
on 19/04/2013 02:27 Craig Rodrigues said the following: I can't figure out why this mount is busy. If I do: umount -f /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles it unmounts, but I don't like using the '-f' flag to force the unmount. Any ideas? fstat? -- Andriy Gapon ___ 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 i386/pc98
TB --- 2013-04-19 09:39:55 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-19 09:39:55 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-04-19 09:39:55 - starting HEAD tinderbox run for i386/pc98 TB --- 2013-04-19 09:39:55 - cleaning the object tree TB --- 2013-04-19 09:39:55 - /usr/local/bin/svn stat /src TB --- 2013-04-19 09:40:04 - At svn revision 249637 TB --- 2013-04-19 09:40:05 - building world TB --- 2013-04-19 09:40:05 - CROSS_BUILD_TESTING=YES TB --- 2013-04-19 09:40:05 - MAKEOBJDIRPREFIX=/obj TB --- 2013-04-19 09:40:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-04-19 09:40:05 - SRCCONF=/dev/null TB --- 2013-04-19 09:40:05 - TARGET=pc98 TB --- 2013-04-19 09:40:05 - TARGET_ARCH=i386 TB --- 2013-04-19 09:40:05 - TZ=UTC TB --- 2013-04-19 09:40:05 - __MAKE_CONF=/dev/null TB --- 2013-04-19 09:40:05 - cd /src TB --- 2013-04-19 09:40:05 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Fri Apr 19 09:40:10 UTC 2013 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 Apr 19 12:54:48 UTC 2013 TB --- 2013-04-19 12:54:48 - generating LINT kernel config TB --- 2013-04-19 12:54:48 - cd /src/sys/pc98/conf TB --- 2013-04-19 12:54:48 - /usr/bin/make -B LINT TB --- 2013-04-19 12:54:48 - cd /src/sys/pc98/conf TB --- 2013-04-19 12:54:48 - /usr/sbin/config -m LINT TB --- 2013-04-19 12:54:48 - building LINT kernel TB --- 2013-04-19 12:54:48 - CROSS_BUILD_TESTING=YES TB --- 2013-04-19 12:54:48 - MAKEOBJDIRPREFIX=/obj TB --- 2013-04-19 12:54:48 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-04-19 12:54:48 - SRCCONF=/dev/null TB --- 2013-04-19 12:54:48 - TARGET=pc98 TB --- 2013-04-19 12:54:48 - TARGET_ARCH=i386 TB --- 2013-04-19 12:54:48 - TZ=UTC TB --- 2013-04-19 12:54:48 - __MAKE_CONF=/dev/null TB --- 2013-04-19 12:54:48 - cd /src TB --- 2013-04-19 12:54:48 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Apr 19 12:54:48 UTC 2013 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 [...] ^~~~ ./machine/bus.h:362:1: note: passing argument to parameter 'bsh' here _BUS_SPACE_WRITE(u_int32_t,4) ^ ./machine/bus.h:347:64: note: expanded from macro '_BUS_SPACE_WRITE' bus_space_write_##BWN (bus_space_tag_t tag, bus_space_handle_t bsh, \ ^ 4 errors generated. *** [uart_dev_lpc.o] Error code 1 Stop in /src/sys/modules/uart. *** [all] Error code 1 Stop in /src/sys/modules. *** [modules-all] Error code 1 Stop in /obj/pc98.i386/src/sys/LINT. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-04-19 13:19:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-04-19 13:19:15 - ERROR: failed to build LINT kernel TB --- 2013-04-19 13:19:15 - 10573.87 user 1488.54 system 13160.05 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-pc98.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
no boot 91stable-last april13(486no acpi
486! system.stop after init. boot safe mode (only kernel enable?(no acpi -- fname lname oper...@operamail.com -- http://www.fastmail.fm - A fast, anti-spam email service. ___ 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: ipfilter(4) needs maintainer
On Fri, Apr 19, 2013 at 11:45:57AM +0200, David Demelier wrote: 2013/4/14 Gary Palmer gpal...@freebsd.org: Do we honestly need three packet filters? No, for me only one should be present. I completely understand that some users still use IPFilter and IPFW but why providing three packet filters? The answer should be: use one and document only one. If at the beginning we started documenting only one all users should have used the only one present. Now we really need to remove the ancestral ipfilter and tell people switching to pf(4). IPFW. It is more logical and easy to use in complex context. Everything in life change, if we need to maintain all code from the past we will have a lot of compat code that pollute the full source tree and we will never improve the code just because of old bits ___ 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: Cannot unmount nullfs in current
On Fri, 2013-04-19 at 01:12 -0700, Craig Rodrigues wrote: On Thu, Apr 18, 2013 at 4:27 PM, Craig Rodrigues rodr...@freebsd.orgwrote: Hi, I am trying to build some software which uses nanobsd, and mounts/unmounts many nullfs mounts while it runs. I am hitting failures where I cannot unmount nullfs file systems. I cannot figure out why. I forgot to run fstat. :( fstat /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME rodrigc gam_server 2275 37 /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles 3194579 drwxr-xr-x 196 r /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles Since I run the GNOME desktop, gnome has a dependency on the gamin port. The gamin port contains gam_server. gamin monitors file system activity. It looks like gam_server gets triggered when things are mounted, and for some reason, sometimes fails to go away. I need to read http://people.gnome.org/~veillard/gamin/config.html and figure out how to disable gamin, or just remove gamin from my system. Annoying. :( I worked around this kind of problem by putting a single entry in /usr/local/etc/gamin/gaminrc: poll /* It might be slightly less efficient to have gamin polling all mounts instead of getting change notices from the kernel, but I've never really noticed any performance hit, even with dozens of nullfs and devfs mounts in various chroots. -- Ian ___ 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: ipfilter(4) needs maintainer
On 19 Apr 2013 10:46, David Demelier demelier.da...@gmail.com wrote: 2013/4/14 Gary Palmer gpal...@freebsd.org: On Sun, Apr 14, 2013 at 09:48:33AM -0600, Warren Block wrote: Is it possible to move ipfilter into a port? That may work short term, but the ENOMAINTAINER problem will quickly creep up again as kernel APIs change. If the author has lost interest in maintaining the FreeBSD port of ipfilter then unless someone steps forward to carry on the work, I don't see much of a future for ipfilter in FreeBSD Do we honestly need three packet filters? No, for me only one should be present. I completely understand that some users still use IPFilter and IPFW but why providing three packet filters? The answer should be: use one and document only one. If at the beginning we started documenting only one all users should have used the only one present. Now we really need to remove the ancestral ipfilter and tell people switching to pf(4). Everything in life change, if we need to maintain all code from the past we will have a lot of compat code that pollute the full source tree and we will never improve the code just because of old bits These so called old bits are both maintained, and have different strengths. Removing dead unmaintained code yes, but having choice makes transition easier from other OSes; the fewer parts to change at a time, the better. Chris ___ 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
sysctl -a: Crashes CURRENT
trying to read the temperature on an Intel Core-i7 3930K box (10.0-CURRENT #2 r249647: Fri Apr 19 13:22:41 CEST 2013 amd64) via sysctl -a|grep tempe crashes sporadically the system due to panic/page fault and dumps core. I'm not able to reproduces this behaviour by intention, as I stated at the beginning, the crash occurs sporadically. That also happened once on a Core2Duo based box (Intel E8400), but also not being reproducable. First occurence was over Easter. Since all the boxes in question use the Intel temperature sensor driver in-core, the question is whether there is a known issue and I better do not use the driver (device coretemp). Since I'm also incapable of triggering this error by will, I'm sorry not providing more informations. the last incident was during kernel compilation, but at this very moment, I recompile also a kernel and try trigering the crash - but it doesn't work. Oliver ___ 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: Cannot unmount nullfs in current
Can we pretend an user-friendly-os and spam to syslog corresponding blocking file and process whenever umount going to fail ? :) Like, make this to be default ( or with some key at least ) behavior of umount. Regards, Alexander Yerenkow ___ 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: sysctl -a: Crashes CURRENT
On Fri, Apr 19, 2013 at 02:01:29PM +0200, O. Hartmann wrote: trying to read the temperature on an Intel Core-i7 3930K box (10.0-CURRENT #2 r249647: Fri Apr 19 13:22:41 CEST 2013 amd64) via sysctl -a|grep tempe crashes sporadically the system due to panic/page fault and dumps core. I'm not able to reproduces this behaviour by intention, as I stated at the beginning, the crash occurs sporadically. That also happened once on a Core2Duo based box (Intel E8400), but also not being reproducable. First occurence was over Easter. Since all the boxes in question use the Intel temperature sensor driver in-core, the question is whether there is a known issue and I better do not use the driver (device coretemp). Why do you think this has anything to do with coretemp? What backtraces are you getting? Since I'm also incapable of triggering this error by will, I'm sorry not providing more informations. the last incident was during kernel compilation, but at this very moment, I recompile also a kernel and try trigering the crash - but it doesn't work. Oliver ___ 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: Cannot unmount nullfs in current
On Fri, Apr 19, 2013 at 7:30 AM, hiren panchasara hi...@freebsd.org wrote: 00:02:37 ### log: /opt2/branches/freenas/os-base/amd64/_.cust.add_pkg_archivers_lzo2 I do not get this. do_build.sh: ERROR: FreeNAS /opt2/branches/freenas/nanobsd/os-base build FAILED; please check above log for more details I get this which looks like a generic build failure message. I do not have gnome or any X related things. Where do you find/see logs for the build? When building freenas, instead of doing: sh build/do_build.sh if you do: sh build/do_build.sh -x This enables a lot of tracing output. Also, when you see an error message such as: do_build.sh: ERROR: FreeNAS /opt2/branches/freenas/nanobsd/os-base build FAILED; please check above log for more details Then you need to scroll up a bit to see which log file it is referring to. -- Craig ___ 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: Cannot unmount nullfs in current
On Fri, Apr 19, 2013 at 11:17 AM, Craig Rodrigues rodr...@freebsd.org wrote: On Fri, Apr 19, 2013 at 7:30 AM, hiren panchasara hi...@freebsd.org wrote: 00:02:37 ### log: /opt2/branches/freenas/os-base/amd64/_.cust.add_pkg_archivers_lzo2 I do not get this. do_build.sh: ERROR: FreeNAS /opt2/branches/freenas/nanobsd/os-base build FAILED; please check above log for more details I get this which looks like a generic build failure message. I do not have gnome or any X related things. Where do you find/see logs for the build? When building freenas, instead of doing: sh build/do_build.sh if you do: sh build/do_build.sh -x This enables a lot of tracing output. Also, when you see an error message such as: do_build.sh: ERROR: FreeNAS /opt2/branches/freenas/nanobsd/os-base build FAILED; please check above log for more details Then you need to scroll up a bit to see which log file it is referring to. I had tried that without success. I did not get any pointer to where the error might be. I may have failed well before starting any building. One of the reasons might be that I had git port without svn support. Some of the buildscripts magic for git-svn interaction may have failed because of that. I am trying to fix that right now and give this another try. cheers, Hiren -- Craig ___ 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: Cannot unmount nullfs in current
On Fri, Apr 19, 2013 at 11:36 AM, hiren panchasara hi...@freebsd.orgwrote: I had tried that without success. I did not get any pointer to where the error might be. I may have failed well before starting any building. One of the reasons might be that I had git port without svn support. Some of the buildscripts magic for git-svn interaction may have failed because of that. I am trying to fix that right now and give this another try. Yes, you are right. I found that to the hard way. You need devel/git-subversion and not devel/git port installed. Somewhere in the build git svn is invoked, and will fail if you don't have devel/git-subversion installed. -- Craig ___ 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: Cannot unmount nullfs in current
On Fri, Apr 19, 2013 at 6:35 AM, Ian Lepore i...@freebsd.org wrote: I worked around this kind of problem by putting a single entry in /usr/local/etc/gamin/gaminrc: poll /* That's one option. I used a hammer approach, and after reading http://people.gnome.org/~veillard/gamin/config.html, I put this in my /usr/local/etc/gamin/gaminrc: fsset nullfs none fsset ufs none fsset zfs none I think that is supposed to turn off gamin for any nullfs, ufs, or zfs file system. :) It seems to work for me. -- Craig ___ 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 i386/pc98
TB --- 2013-04-19 20:40:33 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-04-19 20:40:33 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-04-19 20:40:33 - starting HEAD tinderbox run for i386/pc98 TB --- 2013-04-19 20:40:33 - cleaning the object tree TB --- 2013-04-19 20:42:18 - /usr/local/bin/svn stat /src TB --- 2013-04-19 20:42:32 - At svn revision 249650 TB --- 2013-04-19 20:42:33 - building world TB --- 2013-04-19 20:42:33 - CROSS_BUILD_TESTING=YES TB --- 2013-04-19 20:42:33 - MAKEOBJDIRPREFIX=/obj TB --- 2013-04-19 20:42:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-04-19 20:42:33 - SRCCONF=/dev/null TB --- 2013-04-19 20:42:33 - TARGET=pc98 TB --- 2013-04-19 20:42:33 - TARGET_ARCH=i386 TB --- 2013-04-19 20:42:33 - TZ=UTC TB --- 2013-04-19 20:42:33 - __MAKE_CONF=/dev/null TB --- 2013-04-19 20:42:33 - cd /src TB --- 2013-04-19 20:42:33 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Fri Apr 19 20:42:38 UTC 2013 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 [...] c++ -O2 -pipe -I/src/lib/clang/libclangast/../../../contrib/llvm/include -I/src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/lib/AST -I. -I/src/lib/clang/libclangast/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd10.0\ -DLLVM_HOSTTRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\/obj/pc98.i386/src/tmp\ -I/obj/pc98.i386/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/lib/AST/ASTDiagnostic.cpp -o ASTDiagnostic.o c++ -O2 -pipe -I/src/lib/clang/libclangast/../../../contrib/llvm/include -I/src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/lib/AST -I. -I/src/lib/clang/libclangast/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd10.0\ -DLLVM_HOSTTRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\/obj/pc98.i386/src/tmp\ -I/obj/pc98.i386/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/lib/AST/ASTDumper.cpp -o ASTDumper.o c++ -O2 -pipe -I/src/lib/clang/libclangast/../../../contrib/llvm/include -I/src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/lib/AST -I. -I/src/lib/clang/libclangast/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd10.0\ -DLLVM_HOSTTRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\/obj/pc98.i386/src/tmp\ -I/obj/pc98.i386/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/lib/AST/ASTImporter.cpp -o ASTImporter.o /src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/lib/AST/ASTImporter.cpp: In destructor 'virtual clang::ASTImporter::~ASTImporter()': /src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/lib/AST/ASTImporter.cpp:4333: internal compiler error: in var_ann, at tree-flow-inline.h:127 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** [ASTImporter.o] Error code 1 Stop in /src/lib/clang/libclangast. *** [all] Error code 1 Stop in /src/lib/clang. *** [cross-tools] Error code 1 Stop in /src. *** [_cross-tools] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-04-19 20:55:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-04-19 20:55:31 - ERROR: failed to build world TB --- 2013-04-19 20:55:31 - 559.82 user 146.30 system 897.91 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-pc98.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: Cannot unmount nullfs in current
On Fri, Apr 19, 2013 at 12:07 PM, Craig Rodrigues rodr...@freebsd.org wrote: On Fri, Apr 19, 2013 at 11:36 AM, hiren panchasara hi...@freebsd.org wrote: I had tried that without success. I did not get any pointer to where the error might be. I may have failed well before starting any building. One of the reasons might be that I had git port without svn support. Some of the buildscripts magic for git-svn interaction may have failed because of that. I am trying to fix that right now and give this another try. Yes, you are right. I found that to the hard way. You need devel/git-subversion and not devel/git port installed. Somewhere in the build git svn is invoked, and will fail if you don't have devel/git-subversion installed. I believe that was the problem. Installing devel/git-subversion fixed it for me. I will poke freenas folks to add this instruction on their git page for not-so-smart souls like myself. :-) Thanks, Hiren -- Craig ___ 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: Cannot unmount nullfs in current
On Fri, Apr 19, 2013 at 2:36 PM, hiren panchasara hi...@freebsd.org wrote: I believe that was the problem. Installing devel/git-subversion fixed it for me. I will poke freenas folks to add this instruction on their git page for not-so-smart souls like myself. :-) Thanks, Hiren See: https://github.com/freenas/freenas/pull/11 -- Craig ___ 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 9287 - no carrier . revision 249623.
Hi! Ok, please update to -HEAD and retest! adrian On 19 April 2013 06:26, Adrian Chadd adrian.ch...@gmail.com wrote: oo good to know! let me setup the chainmask info whether or not the 11n option is set. thanks! adrian On 19 April 2013 04:08, Artyom Mirgorodskiy artyom.mirgorod...@gmail.com wrote: Adrian, I found the problem. I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define ATH_ENABLE_11N - everything work. Artyom Mirgorodskiy On Friday 19 April 2013 13:27:21 wrote: Updated. However I did not see chainmask information. See attached On Friday 19 April 2013 00:57:12 Adrian Chadd wrote: Hi, I've just committed some changes to -HEAD. Please update to the latest -HEAD and paste me the ath0 dmesg output. It will include the chainmask information. Thanks, Adrian -- Artyom Mirgorodskiy -- Artyom Mirgorodskiy ___ 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: Cannot unmount nullfs in current
On Fri, Apr 19, 2013 at 2:56 PM, Craig Rodrigues rodr...@freebsd.org wrote: On Fri, Apr 19, 2013 at 2:36 PM, hiren panchasara hi...@freebsd.org wrote: I believe that was the problem. Installing devel/git-subversion fixed it for me. I will poke freenas folks to add this instruction on their git page for not-so-smart souls like myself. :-) Thanks, Hiren See: https://github.com/freenas/freenas/pull/11 Awesome! Thanks, Hiren -- Craig ___ 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: My incremental buildworlds started failing
On Tue, 16 Apr 2013, Tijl Coosemans wrote:
On 2013-04-16 18:39, Dimitry Andric wrote:
On Apr 16, 2013, at 18:08, Bjoern A. Zeeb wrote:
I have been seeing this on incremental buildworlds for a day or two now?
ANyone can throw the cluebat at me?
If that means building with NO_CLEAN=yes then the problem is r249484.
It creates a symlink: ln -fs ../include ${DESTDIR}/usr/lib/include
But if ${DESTDIR}/usr/lib/include already exists it creates
${DESTDIR}/usr/include/include - ../include.
I'm thinking of reverting that commit.
=== rescue/rescue/routed/rtquery (depend)
{standard input}: Assembler messages:
{standard input}:2: Warning: unterminated string; newline inserted
{standard input}:3: Warning: unterminated string; newline inserted
=== kerberos5/usr.bin/kcc (all)
In file included from
/scratch/tmp/bz/head.svn/sbin/rtsol/../../usr.sbin/rtsold/rtsol.c:51:
/storage/head/obj//sparc64.sparc64/scratch/tmp/bz/head.svn/tmp/usr/include/netinet6/ip6_var.h:245:
error: 'IP6S_MAXRULES' undeclared here (not in a function)
*** [rtsol.o] Error code 1
1 error
*** [rtsol_make] Error code 2
1 error
Probably http://svnweb.freebsd.org/changeset/base/249543
This has been fixed in r249552 now.
But if the problem is there once and you never remove your obj
directory it's not really gone even with a full (no NOCLEAN) rebuild,
right? SO time to kill the obj directory...
--
Bjoern A. Zeeb Charles Haddon Spurgeon:
Friendship is one of the sweetest joys of life. Many might have failed
beneath the bitterness of their trial had they not found a friend.
___
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
