Re: ale(4) cannot negotiate as GigE
On Mon, Feb 25, 2013 at 05:23:44PM +0900, YongHyeon PYUN wrote: Then have no idea at this moment. Can you try other OS and check whether it can establish a gigabit link? I did not have a chance to try other OS, because machine paniced during tinderbuilding of a large port. Unfortunately I don't have a backtrace, as I needed to ask my friends to reboot it (I myself do not have direct access to it right now). However, after reboot ale0 come up at 1000baseT full-duplex, with patched driver (longer delays in ale_phy_reset()). I've reverted this change and rebooted again, but it again come up as GigE. I cannot power down the box completely, since there is no one around who can bring it back right now (press the power button). That said, it looks quite weird to me at this point. Previously it was rebooted a few times, and link speed was always 100mbps. Patching the driver and re-kldloading it did not help, but after reboot, link speed is 1000ish even with unpatched driver. :-/ ./danfe ___ 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: ale(4) cannot negotiate as GigE
On Sun, Mar 03, 2013 at 09:53:30AM +, Alexey Dokuchaev wrote: However, after reboot ale0 come up at 1000baseT full-duplex, with patched driver (longer delays in ale_phy_reset()). I've reverted this change and rebooted again, but it again come up as GigE. Alas, after make kernel, link come up as 100mbps again, playing with delays and rebooting (several times) did not make it GigE. I'm not sure what's actually affecting it. :-( ./danfe ___ 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: access to hard drives is blocked by writes to a flash drive
On Sun, 2013-03-03 at 15:20 +1100, Peter Jeremy wrote: On 2013-Mar-02 18:29:54 +0100, deeptech71 deeptec...@gmail.com wrote: When one of my flash drives is being heavily written to; typically by ``svn update'' on /usr/src, located on the flash drive; the following can be said about filesystem behavior: - ``svn update'' seems to be able to quickly update a bunch of files, but is then unable to continue for a period of time. This behavior is cyclical, and cycles several times, depending on the amount of updating work to be done for a particular run of ``svn update''. This sounds like normal flash behaviour: You can only write to erased blocks. The SSD firmware attempts to keep a free pool of erased blocks but if you write too fast, you empty the free pool and need to wait for the wear-levelling algorithm to move blocks around and erase them. Enabling TRIM (the '-t' flag on tunefs) will help if the drive supports TRIM (if it doesn't, it'll probably just lockup). Otherwise, you need to either put up with it or upgrade to a better SSD. I run into this regularly with the low-end SuperTalent drive in my Netbook but have never seen it with the OCZ Agility4 that I use for L2ARC in my fileserver. I run into this behavior all the time too, mostly on arm systems that have an sd card or usb thumb driver as their main/only drive. It's especially annoying when you try to launch a program that isn't in the filesystem cache already, and you have to wait 10-20 seconds for it to be read in. I stop just short of calling that normal because it seems like we should be able to do better somehow... I don't think the problem is on the flash device itself (like waiting for some big internal cache to drain), it acts more like there aren't enough buffers on the OS side (they're all tied up waiting to be written), or it's a bio-queue sort problem, or maybe it's somehow intentional that writes have precedence over reads (that might make more sense on a system without a big disparity between read and write speed, especially given that writing for the purpose of swapping is important to free up memory). The fact that a huge backlog of writes to a slow flash-based device can block reads from faster devices makes me think this is somehow related to available buffers in the OS. I wonder if this could be one of those situations where reducing the amount of buffers improves responsiveness (if not necessarily overall throughput). -- 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
[head tinderbox] failure on arm/arm
TB --- 2013-03-03 12:00:18 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 12:00:18 - 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-03-03 12:00:18 - starting HEAD tinderbox run for arm/arm TB --- 2013-03-03 12:00:18 - cleaning the object tree TB --- 2013-03-03 12:00:18 - /usr/local/bin/svn stat /src TB --- 2013-03-03 12:00:22 - At svn revision 247709 TB --- 2013-03-03 12:00:23 - building world TB --- 2013-03-03 12:00:23 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 12:00:23 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 12:00:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 12:00:23 - SRCCONF=/dev/null TB --- 2013-03-03 12:00:23 - TARGET=arm TB --- 2013-03-03 12:00:23 - TARGET_ARCH=arm TB --- 2013-03-03 12:00:23 - TZ=UTC TB --- 2013-03-03 12:00:23 - __MAKE_CONF=/dev/null TB --- 2013-03-03 12:00:23 - cd /src TB --- 2013-03-03 12:00:23 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 12:00:27 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 [...] cc -O -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -c kdigest-commands.c cc -O -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/arm.arm/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/arm.arm/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/arm.arm/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/arm.arm/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/arm.arm/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/arm.arm/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/arm.arm/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/arm.arm/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 13:35:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 13:35:18 - ERROR: failed to build world TB --- 2013-03-03 13:35:18 - 4647.85 user 820.34 system 5700.31 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-arm-arm.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 armv6/arm
TB --- 2013-03-03 12:00:18 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 12:00:18 - 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-03-03 12:00:18 - starting HEAD tinderbox run for armv6/arm TB --- 2013-03-03 12:00:18 - cleaning the object tree TB --- 2013-03-03 12:00:18 - /usr/local/bin/svn stat /src TB --- 2013-03-03 12:00:22 - At svn revision 247709 TB --- 2013-03-03 12:00:23 - building world TB --- 2013-03-03 12:00:23 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 12:00:23 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 12:00:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 12:00:23 - SRCCONF=/dev/null TB --- 2013-03-03 12:00:23 - TARGET=arm TB --- 2013-03-03 12:00:23 - TARGET_ARCH=armv6 TB --- 2013-03-03 12:00:23 - TZ=UTC TB --- 2013-03-03 12:00:23 - __MAKE_CONF=/dev/null TB --- 2013-03-03 12:00:23 - cd /src TB --- 2013-03-03 12:00:23 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 12:00:28 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 [...] cc -O -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -c kdigest-commands.c cc -O -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/arm.armv6/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/arm.armv6/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/arm.armv6/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/arm.armv6/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/arm.armv6/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/arm.armv6/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/arm.armv6/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/arm.armv6/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 13:35:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 13:35:23 - ERROR: failed to build world TB --- 2013-03-03 13:35:23 - 4643.58 user 820.38 system 5704.56 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-armv6-arm.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: access to hard drives is blocked by writes to a flash drive
Content-Type: text/plain; charset=ISO-8859-1 In message 1362317291.1195.216.ca...@revolution.hippie.lan, Ian Lepore writes : I run into this behavior all the time too, mostly on arm systems that have an sd card or usb thumb driver as their main/only drive. This is really a FAQ and I belive I have answered it N times already: There are, broadly speaking, two classes of flash-storage: Camera-grade and the real thing. Camera-grade have a very limited Flash adaptation layer which typically only can hold one flash-block open for writing at a time, and is typically found in CF and SD cards, USB sticks etc. Some of them gets further upset if the filesystem is not the FAT they expect, because they implement M-Systems (patented) trick with monitoring block deletes in FAT to simulate a TRIM facility. A number of products exist with such designs, typically a CF-style, is put behind a SATA-PATA bridge and sold as 2.5 SSD SATA devices. Transcend have done this for instance. If you use this class of devices for anything real, gstat will show you I/O write-times of several seconds in periodic pile-ups, even 100 seconds if you are doing something heavy. For various reasons (see: Lemming-syncer) FreeBSD will block all I/O traffic to other disks too, when these pileups gets too bad. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ 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: access to hard drives is blocked by writes to a flash drive
On Sun, 2013-03-03 at 13:35 +, Poul-Henning Kamp wrote: Content-Type: text/plain; charset=ISO-8859-1 In message 1362317291.1195.216.ca...@revolution.hippie.lan, Ian Lepore writes : I run into this behavior all the time too, mostly on arm systems that have an sd card or usb thumb driver as their main/only drive. This is really a FAQ and I belive I have answered it N times already: There are, broadly speaking, two classes of flash-storage: Camera-grade and the real thing. Camera-grade have a very limited Flash adaptation layer which typically only can hold one flash-block open for writing at a time, and is typically found in CF and SD cards, USB sticks etc. Some of them gets further upset if the filesystem is not the FAT they expect, because they implement M-Systems (patented) trick with monitoring block deletes in FAT to simulate a TRIM facility. A number of products exist with such designs, typically a CF-style, is put behind a SATA-PATA bridge and sold as 2.5 SSD SATA devices. Transcend have done this for instance. If you use this class of devices for anything real, gstat will show you I/O write-times of several seconds in periodic pile-ups, even 100 seconds if you are doing something heavy. For various reasons (see: Lemming-syncer) FreeBSD will block all I/O traffic to other disks too, when these pileups gets too bad. Hmmm, so the problem has been known and unfixed for 10 years. That's not encouraging. One of the messages in the lemming-syncer mail thread might explain why I've been seeing this a lot lately in hobbyist work, but not so much at $work where we use sd cards heavily... we use very short syncer timeouts on SD and CF storage at $work: kern.metadelay: 3 kern.dirdelay: 4 kern.filedelay: 5 I might play with similar settings on some of my arm boards here. -- 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: access to hard drives is blocked by writes to a flash drive
In message 1362318887.1195.221.ca...@revolution.hippie.lan, Ian Lepore writes : Hmmm, so the problem has been known and unfixed for 10 years. It's hard to fix, because a lot of stuff has been tangled up cyclically in the disk-I/O relevant layers. The umapped buf stuff which is (finally!) happening, is the path to fixing it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ 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/i386
TB --- 2013-03-03 12:00:18 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 12:00:18 - 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-03-03 12:00:18 - starting HEAD tinderbox run for i386/i386 TB --- 2013-03-03 12:00:18 - cleaning the object tree TB --- 2013-03-03 12:00:18 - /usr/local/bin/svn stat /src TB --- 2013-03-03 12:00:22 - At svn revision 247709 TB --- 2013-03-03 12:00:23 - building world TB --- 2013-03-03 12:00:23 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 12:00:23 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 12:00:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 12:00:23 - SRCCONF=/dev/null TB --- 2013-03-03 12:00:23 - TARGET=i386 TB --- 2013-03-03 12:00:23 - TARGET_ARCH=i386 TB --- 2013-03-03 12:00:23 - TZ=UTC TB --- 2013-03-03 12:00:23 - __MAKE_CONF=/dev/null TB --- 2013-03-03 12:00:23 - cd /src TB --- 2013-03-03 12:00:23 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 12:00:27 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 [...] cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -Qunused-arguments -fstack-protector -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/i386.i386/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/i386.i386/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/i386.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/i386.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/i386.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/i386.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/i386.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/i386.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 14:28:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 14:28:26 - ERROR: failed to build world TB --- 2013-03-03 14:28:26 - 7425.98 user 995.81 system .00 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-i386-i386.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 amd64/amd64
TB --- 2013-03-03 12:00:18 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 12:00:18 - 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-03-03 12:00:18 - starting HEAD tinderbox run for amd64/amd64 TB --- 2013-03-03 12:00:18 - cleaning the object tree TB --- 2013-03-03 12:00:18 - /usr/local/bin/svn stat /src TB --- 2013-03-03 12:00:22 - At svn revision 247709 TB --- 2013-03-03 12:00:23 - building world TB --- 2013-03-03 12:00:23 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 12:00:23 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 12:00:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 12:00:23 - SRCCONF=/dev/null TB --- 2013-03-03 12:00:23 - TARGET=amd64 TB --- 2013-03-03 12:00:23 - TARGET_ARCH=amd64 TB --- 2013-03-03 12:00:23 - TZ=UTC TB --- 2013-03-03 12:00:23 - __MAKE_CONF=/dev/null TB --- 2013-03-03 12:00:23 - cd /src TB --- 2013-03-03 12:00:23 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 12:00:28 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 [...] cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -Qunused-arguments -fstack-protector -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/amd64.amd64/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/amd64.amd64/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/amd64.amd64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/amd64.amd64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/amd64.amd64/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/amd64.amd64/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/amd64.amd64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/amd64.amd64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 14:28:34 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 14:28:34 - ERROR: failed to build world TB --- 2013-03-03 14:28:34 - 7427.40 user 985.48 system 8896.12 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-amd64-amd64.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 ia64/ia64
TB --- 2013-03-03 13:35:23 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 13:35:23 - 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-03-03 13:35:23 - starting HEAD tinderbox run for ia64/ia64 TB --- 2013-03-03 13:35:23 - cleaning the object tree TB --- 2013-03-03 13:35:23 - /usr/local/bin/svn stat /src TB --- 2013-03-03 13:35:26 - At svn revision 247709 TB --- 2013-03-03 13:35:27 - building world TB --- 2013-03-03 13:35:27 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 13:35:27 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 13:35:27 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 13:35:27 - SRCCONF=/dev/null TB --- 2013-03-03 13:35:27 - TARGET=ia64 TB --- 2013-03-03 13:35:27 - TARGET_ARCH=ia64 TB --- 2013-03-03 13:35:27 - TZ=UTC TB --- 2013-03-03 13:35:27 - __MAKE_CONF=/dev/null TB --- 2013-03-03 13:35:27 - cd /src TB --- 2013-03-03 13:35:27 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 13:35:31 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 [...] cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -c kdigest-commands.c cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/ia64.ia64/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/ia64.ia64/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/ia64.ia64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/ia64.ia64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/ia64.ia64/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/ia64.ia64/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/ia64.ia64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/ia64.ia64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 14:40:20 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 14:40:20 - ERROR: failed to build world TB --- 2013-03-03 14:40:20 - 3127.15 user 527.43 system 3896.68 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-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
[head tinderbox] failure on mips/mips
TB --- 2013-03-03 14:28:26 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 14:28:26 - 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-03-03 14:28:26 - starting HEAD tinderbox run for mips/mips TB --- 2013-03-03 14:28:26 - cleaning the object tree TB --- 2013-03-03 14:28:27 - /usr/local/bin/svn stat /src TB --- 2013-03-03 14:28:38 - At svn revision 247709 TB --- 2013-03-03 14:28:39 - building world TB --- 2013-03-03 14:28:39 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 14:28:39 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 14:28:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 14:28:39 - SRCCONF=/dev/null TB --- 2013-03-03 14:28:39 - TARGET=mips TB --- 2013-03-03 14:28:39 - TARGET_ARCH=mips TB --- 2013-03-03 14:28:39 - TZ=UTC TB --- 2013-03-03 14:28:39 - __MAKE_CONF=/dev/null TB --- 2013-03-03 14:28:39 - cd /src TB --- 2013-03-03 14:28:39 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 14:28:44 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 [...] cc -O -pipe -G0 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -c kdigest-commands.c cc -O -pipe -G0 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/mips.mips/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/mips.mips/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/mips.mips/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/mips.mips/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/mips.mips/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/mips.mips/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/mips.mips/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/mips.mips/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 15:16:47 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 15:16:47 - ERROR: failed to build world TB --- 2013-03-03 15:16:47 - 2090.98 user 518.67 system 2900.20 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-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 mips64/mips
TB --- 2013-03-03 14:28:35 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 14:28:35 - 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-03-03 14:28:35 - starting HEAD tinderbox run for mips64/mips TB --- 2013-03-03 14:28:35 - cleaning the object tree TB --- 2013-03-03 14:28:35 - /usr/local/bin/svn stat /src TB --- 2013-03-03 14:28:38 - At svn revision 247709 TB --- 2013-03-03 14:28:39 - building world TB --- 2013-03-03 14:28:39 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 14:28:39 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 14:28:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 14:28:39 - SRCCONF=/dev/null TB --- 2013-03-03 14:28:39 - TARGET=mips TB --- 2013-03-03 14:28:39 - TARGET_ARCH=mips64 TB --- 2013-03-03 14:28:39 - TZ=UTC TB --- 2013-03-03 14:28:39 - __MAKE_CONF=/dev/null TB --- 2013-03-03 14:28:39 - cd /src TB --- 2013-03-03 14:28:39 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 14:28:44 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 [...] cc -O -pipe -G0 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -c kdigest-commands.c cc -O -pipe -G0 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/mips.mips64/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/mips.mips64/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/mips.mips64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/mips.mips64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/mips.mips64/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/mips.mips64/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/mips.mips64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/mips.mips64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 15:16:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 15:16:46 - ERROR: failed to build world TB --- 2013-03-03 15:16:46 - 2099.05 user 521.19 system 2891.63 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-mips64-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 i386/pc98
TB --- 2013-03-03 13:35:19 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 13:35:19 - 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-03-03 13:35:19 - starting HEAD tinderbox run for i386/pc98 TB --- 2013-03-03 13:35:19 - cleaning the object tree TB --- 2013-03-03 13:35:19 - /usr/local/bin/svn stat /src TB --- 2013-03-03 13:35:22 - At svn revision 247709 TB --- 2013-03-03 13:35:23 - building world TB --- 2013-03-03 13:35:23 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 13:35:23 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 13:35:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 13:35:23 - SRCCONF=/dev/null TB --- 2013-03-03 13:35:23 - TARGET=pc98 TB --- 2013-03-03 13:35:23 - TARGET_ARCH=i386 TB --- 2013-03-03 13:35:23 - TZ=UTC TB --- 2013-03-03 13:35:23 - __MAKE_CONF=/dev/null TB --- 2013-03-03 13:35:23 - cd /src TB --- 2013-03-03 13:35:23 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 13:35:27 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 [...] cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -Qunused-arguments -fstack-protector -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/pc98.i386/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/pc98.i386/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/pc98.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/pc98.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/pc98.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/pc98.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/pc98.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/pc98.i386/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 16:08:20 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 16:08:20 - ERROR: failed to build world TB --- 2013-03-03 16:08:20 - 7676.16 user 987.78 system 9181.20 real http://tinderbox.freebsd.org/tinderbox-head-ss-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
[head tinderbox] failure on sparc64/sparc64
TB --- 2013-03-03 15:16:47 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 15:16:47 - 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-03-03 15:16:47 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2013-03-03 15:16:47 - cleaning the object tree TB --- 2013-03-03 15:16:47 - /usr/local/bin/svn stat /src TB --- 2013-03-03 15:16:50 - At svn revision 247709 TB --- 2013-03-03 15:16:51 - building world TB --- 2013-03-03 15:16:51 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 15:16:51 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 15:16:51 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 15:16:51 - SRCCONF=/dev/null TB --- 2013-03-03 15:16:51 - TARGET=sparc64 TB --- 2013-03-03 15:16:51 - TARGET_ARCH=sparc64 TB --- 2013-03-03 15:16:51 - TZ=UTC TB --- 2013-03-03 15:16:51 - __MAKE_CONF=/dev/null TB --- 2013-03-03 15:16:51 - cd /src TB --- 2013-03-03 15:16:51 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 15:16:56 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 [...] cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -fstack-protector -c kdigest-commands.c cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -fstack-protector -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/sparc64.sparc64/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/sparc64.sparc64/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/sparc64.sparc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/sparc64.sparc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/sparc64.sparc64/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/sparc64.sparc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/sparc64.sparc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/sparc64.sparc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 16:08:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 16:08:35 - ERROR: failed to build world TB --- 2013-03-03 16:08:35 - 2393.22 user 442.20 system 3107.91 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-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 powerpc/powerpc
TB --- 2013-03-03 14:40:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 14:40:20 - 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-03-03 14:40:20 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2013-03-03 14:40:20 - cleaning the object tree TB --- 2013-03-03 14:40:20 - /usr/local/bin/svn stat /src TB --- 2013-03-03 14:40:23 - At svn revision 247709 TB --- 2013-03-03 14:40:24 - building world TB --- 2013-03-03 14:40:24 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 14:40:24 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 14:40:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 14:40:24 - SRCCONF=/dev/null TB --- 2013-03-03 14:40:24 - TARGET=powerpc TB --- 2013-03-03 14:40:24 - TARGET_ARCH=powerpc TB --- 2013-03-03 14:40:24 - TZ=UTC TB --- 2013-03-03 14:40:24 - __MAKE_CONF=/dev/null TB --- 2013-03-03 14:40:24 - cd /src TB --- 2013-03-03 14:40:24 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 14:40:29 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 [...] cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -fstack-protector -c kdigest-commands.c cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -fstack-protector -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/powerpc.powerpc/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/powerpc.powerpc/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/powerpc.powerpc/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/powerpc.powerpc/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/powerpc.powerpc/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/powerpc.powerpc/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/powerpc.powerpc/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/powerpc.powerpc/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 16:43:41 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 16:43:41 - ERROR: failed to build world TB --- 2013-03-03 16:43:41 - 6364.33 user 820.51 system 7400.86 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-powerpc-powerpc.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 powerpc64/powerpc
TB --- 2013-03-03 15:16:46 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-03 15:16:46 - 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-03-03 15:16:46 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2013-03-03 15:16:46 - cleaning the object tree TB --- 2013-03-03 15:16:46 - /usr/local/bin/svn stat /src TB --- 2013-03-03 15:16:50 - At svn revision 247709 TB --- 2013-03-03 15:16:51 - building world TB --- 2013-03-03 15:16:51 - CROSS_BUILD_TESTING=YES TB --- 2013-03-03 15:16:51 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-03 15:16:51 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-03 15:16:51 - SRCCONF=/dev/null TB --- 2013-03-03 15:16:51 - TARGET=powerpc TB --- 2013-03-03 15:16:51 - TARGET_ARCH=powerpc64 TB --- 2013-03-03 15:16:51 - TZ=UTC TB --- 2013-03-03 15:16:51 - __MAKE_CONF=/dev/null TB --- 2013-03-03 15:16:51 - cd /src TB --- 2013-03-03 15:16:51 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sun Mar 3 15:16:56 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 [...] cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -fstack-protector -c kdigest-commands.c cc -O2 -pipe -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kdigest/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kdigest/../../include -std=gnu99 -fstack-protector -o kdigest kdigest.o kdigest-commands.o -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/powerpc.powerpc64/src/kerberos5/libexec/kdigest/../../lib/libsl/libsl.a /obj/powerpc.powerpc64/src/kerberos5/libexec/kdigest/../../lib/libvers/libvers.a -ledit /obj/powerpc.powerpc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetflag' /obj/powerpc.powerpc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetent' /obj/powerpc.powerpc64/src/tmp/usr/lib/libedit.so: undefined reference to `tputs' /obj/powerpc.powerpc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgoto' /obj/powerpc.powerpc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetnum' /obj/powerpc.powerpc64/src/tmp/usr/lib/libedit.so: undefined reference to `tgetstr' *** [kdigest] Error code 1 Stop in /src/kerberos5/libexec/kdigest. *** [all] Error code 1 Stop in /src/kerberos5/libexec. *** [all] Error code 1 Stop in /src/kerberos5. *** [kerberos5.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-03 17:18:19 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-03 17:18:19 - ERROR: failed to build world TB --- 2013-03-03 17:18:19 - 6426.06 user 726.63 system 7292.84 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-powerpc64-powerpc.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: HEADS UP: Capsicum overhaul.
Pawel Jakub Dawidek p...@freebsd.org writes: I just committed pretty large change that affects not only Capsicum, but also descriptor handling code in the kernel. If you will find some strange problems after r243611 (like panics, unexpected application errors, etc.) I may be at fault. I'll be looking at current@ mailing list closly, so report here if you find problems that look related to my change. tmux started to behave weirdly, sometimes failing to attach: $ printenv PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin OLDPWD=/ DISPLAY=:0 PWD=/home/foo TERM=xterm USER=foo HOME=/home/foo SHELL=/bin/sh $ ktrace -i tmux -L test -f /dev/null $ echo $? 1 $ kdump -r | pastebinit -a 'tmux fails to attach' http://pastebin.com/U3nCPrFY $ env -i TERM=$TERM ktrace -i /usr/local/bin/tmux -L test -f /dev/null $ ^D [exited] $ kdump -r | pastebinit -a 'tmux fails to attach (workaround)' http://pastebin.com/w1dsUAU4 I've tried so far: * booting allbsd.org snapshot - no joy * enabling capsicum options - no joy * reverting recent capsicum commits - works fine ___ 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: HEADS UP: Capsicum overhaul.
On Sun, Mar 03, 2013 at 10:18:02PM +0300, Jan Beich wrote: Pawel Jakub Dawidek p...@freebsd.org writes: I just committed pretty large change that affects not only Capsicum, but also descriptor handling code in the kernel. If you will find some strange problems after r243611 (like panics, unexpected application errors, etc.) I may be at fault. I'll be looking at current@ mailing list closly, so report here if you find problems that look related to my change. tmux started to behave weirdly, sometimes failing to attach: $ printenv PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin OLDPWD=/ DISPLAY=:0 PWD=/home/foo TERM=xterm USER=foo HOME=/home/foo SHELL=/bin/sh $ ktrace -i tmux -L test -f /dev/null $ echo $? 1 $ kdump -r | pastebinit -a 'tmux fails to attach' http://pastebin.com/U3nCPrFY $ env -i TERM=$TERM ktrace -i /usr/local/bin/tmux -L test -f /dev/null $ ^D [exited] $ kdump -r | pastebinit -a 'tmux fails to attach (workaround)' http://pastebin.com/w1dsUAU4 I've tried so far: * booting allbsd.org snapshot - no joy * enabling capsicum options - no joy * reverting recent capsicum commits - works fine Yes, it was already reported to me and I'm investigating the problem. Thanks. -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl pgpg0QzEgXbEG.pgp Description: PGP signature
Re: access to hard drives is blocked by writes to a flash drive
- Original Message - From: Ian Lepore i...@freebsd.org To: Poul-Henning Kamp p...@phk.freebsd.dk Cc: deeptech71 deeptec...@gmail.com; freebsd-current@FreeBSD.org; Peter Jeremy pe...@rulingia.com Sent: Sunday, March 03, 2013 1:54 PM Subject: Re: access to hard drives is blocked by writes to a flash drive On Sun, 2013-03-03 at 13:35 +, Poul-Henning Kamp wrote: Content-Type: text/plain; charset=ISO-8859-1 In message 1362317291.1195.216.ca...@revolution.hippie.lan, Ian Lepore writes : I run into this behavior all the time too, mostly on arm systems that have an sd card or usb thumb driver as their main/only drive. This is really a FAQ and I belive I have answered it N times already: There are, broadly speaking, two classes of flash-storage: Camera-grade and the real thing. Camera-grade have a very limited Flash adaptation layer which typically only can hold one flash-block open for writing at a time, and is typically found in CF and SD cards, USB sticks etc. Some of them gets further upset if the filesystem is not the FAT they expect, because they implement M-Systems (patented) trick with monitoring block deletes in FAT to simulate a TRIM facility. A number of products exist with such designs, typically a CF-style, is put behind a SATA-PATA bridge and sold as 2.5 SSD SATA devices. Transcend have done this for instance. If you use this class of devices for anything real, gstat will show you I/O write-times of several seconds in periodic pile-ups, even 100 seconds if you are doing something heavy. For various reasons (see: Lemming-syncer) FreeBSD will block all I/O traffic to other disks too, when these pileups gets too bad. Hmmm, so the problem has been known and unfixed for 10 years. That's not encouraging. One of the messages in the lemming-syncer mail thread might explain why I've been seeing this a lot lately in hobbyist work, but not so much at $work where we use sd cards heavily... we use very short syncer timeouts on SD and CF storage at $work: kern.metadelay: 3 kern.dirdelay: 4 kern.filedelay: 5 I might play with similar settings on some of my arm boards here. Interesting, are these relevant for all filesystems e.g. ZFS? Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ 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: HEADS UP: Capsicum overhaul.
On Sun, Mar 03, 2013 at 10:18:02PM +0300, Jan Beich wrote: Pawel Jakub Dawidek p...@freebsd.org writes: I just committed pretty large change that affects not only Capsicum, but also descriptor handling code in the kernel. If you will find some strange problems after r243611 (like panics, unexpected application errors, etc.) I may be at fault. I'll be looking at current@ mailing list closly, so report here if you find problems that look related to my change. tmux started to behave weirdly, sometimes failing to attach: I committed a work-around in r247740, but the root of the problem is yet to be found. -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl pgp7tAe7RGpg5.pgp Description: PGP signature
kernel build failure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 SVN r247736 prompts this .. cc -c -O2 -pipe -fno-strict-aliasing -march=pentium4 -std=c99 -Wall - -Wredundant-decls -Wnested-externs -Wstrict-prototypes - -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef - -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs - -fdiagnostics-show-option -Wno-error-tautological-compare - -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. - -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL - -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -mno-aes -mno-avx - -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror /usr/src/sys/kern/uipc_usrreq.c /usr/src/sys/kern/uipc_usrreq.c:1689:18: error: use of undeclared identifier 'fdep'; did you mean 'fde'? filecaps_free(fdep-fde_caps); ^~~~ fde /usr/src/sys/kern/uipc_usrreq.c:1682:36: note: 'fde' declared here unp_freerights(struct filedescent *fde, int fdcount) ^ 1 error generated. *** [uipc_usrreq.o] Error code 1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (FreeBSD) iEYEARECAAYFAlEz4PQACgkQQv9rrgRC1JL6KACgjI2VCpCeKJCAaZIS+EBRP93N xN8An1s0Q9CNgIP1F5Ep6ypuLQ9Agxde =2ptT -END PGP SIGNATURE- ___ 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: kernel build failure
On Sun, Mar 03, 2013 at 06:47:00PM -0500, Michael Butler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 SVN r247736 prompts this .. cc -c -O2 -pipe -fno-strict-aliasing -march=pentium4 -std=c99 -Wall - -Wredundant-decls -Wnested-externs -Wstrict-prototypes - -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef - -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs - -fdiagnostics-show-option -Wno-error-tautological-compare - -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. - -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL - -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -mno-aes -mno-avx - -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror /usr/src/sys/kern/uipc_usrreq.c /usr/src/sys/kern/uipc_usrreq.c:1689:18: error: use of undeclared identifier 'fdep'; did you mean 'fde'? filecaps_free(fdep-fde_caps); ^~~~ fde /usr/src/sys/kern/uipc_usrreq.c:1682:36: note: 'fde' declared here unp_freerights(struct filedescent *fde, int fdcount) ^ 1 error generated. This was because I divided larger change into smaller changes. r247738 should be fine. -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl pgp3VnbiqBD_t.pgp Description: PGP signature
Re: ale(4) cannot negotiate as GigE
On Sun, Mar 03, 2013 at 12:00:10PM +, Alexey Dokuchaev wrote: On Sun, Mar 03, 2013 at 09:53:30AM +, Alexey Dokuchaev wrote: However, after reboot ale0 come up at 1000baseT full-duplex, with patched driver (longer delays in ale_phy_reset()). I've reverted this change and rebooted again, but it again come up as GigE. Alas, after make kernel, link come up as 100mbps again, playing with delays and rebooting (several times) did not make it GigE. I'm not sure what's actually affecting it. :-( Would you try attached patch? ./danfe Index: sys/dev/mii/atphy.c === --- sys/dev/mii/atphy.c (revision 247382) +++ sys/dev/mii/atphy.c (working copy) @@ -287,9 +287,11 @@ atphy_reset(struct mii_softc *sc) uint32_t reg; int i; +#if 0 /* Take PHY out of power down mode. */ PHY_WRITE(sc, 29, 0x29); PHY_WRITE(sc, 30, 0); +#endif reg = PHY_READ(sc, ATPHY_SCR); /* Enable automatic crossover. */ ___ 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: ale(4) cannot negotiate as GigE
On Mon, Mar 04, 2013 at 09:50:44AM +0900, YongHyeon PYUN wrote: On Sun, Mar 03, 2013 at 12:00:10PM +, Alexey Dokuchaev wrote: Alas, after make kernel, link come up as 100mbps again, playing with delays and rebooting (several times) did not make it GigE. I'm not sure what's actually affecting it. :-( Would you try attached patch? Yes, it did help. With 2000us delays (I didn't revert them since you didn't ask), machine came up after make kernel and reboot with ale0 in GigE mode. I'll be happy to conduct more tests for you, if needed, thanks! ./danfe ___ 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: ale(4) cannot negotiate as GigE
On Mon, Mar 04, 2013 at 01:53:44AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 09:50:44AM +0900, YongHyeon PYUN wrote: On Sun, Mar 03, 2013 at 12:00:10PM +, Alexey Dokuchaev wrote: Alas, after make kernel, link come up as 100mbps again, playing with delays and rebooting (several times) did not make it GigE. I'm not sure what's actually affecting it. :-( Would you try attached patch? Yes, it did help. With 2000us delays (I didn't revert them since you didn't Great! But it seems 2ms delays is too much. ask), machine came up after make kernel and reboot with ale0 in GigE mode. I'll be happy to conduct more tests for you, if needed, thanks! Could you revert the change(2000us delays) and try it again? If that change works I still have to find a specific PHY model to exclude the blind PHY wakeup. ./danfe ___ 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: ale(4) cannot negotiate as GigE
On Mon, Mar 04, 2013 at 11:10:59AM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 01:53:44AM +, Alexey Dokuchaev wrote: Yes, it did help. With 2000us delays (I didn't revert them [...] Great! But it seems 2ms delays is too much. Could you revert the change (2000us delays) and try it again? Reverting if_ale.c, making kernel, and reboot gave me 100baseTX again; :-( second reboot (with the same kernel) did not help. Bumping delays to 2ms (just to make sure) restored GigE mode upon 1st reboot after make kernel. ./danfe ___ 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: access to hard drives is blocked by writes to a flash drive
On 3 Mar, Poul-Henning Kamp wrote: For various reasons (see: Lemming-syncer) FreeBSD will block all I/O traffic to other disks too, when these pileups gets too bad. The Lemming-syncer problem should have mostly been fixed by 231160 in head (231952 in stable/9 and 231967 in stable/8) a little over a year ago. The exceptions are atime updates, mmaped files with dirty pages, and quotas. Under certain workloads I still notice periodic bursts of seek noise. After thinking about it for a bit, I suspect that it could be atime updates, but I haven't tried to confirm that. When using TCQ or NCQ, perhaps we should limit the number of outstanding writes per device to leave some slots open for reads. We should probably also prioritize reads over writes unless we are under memory pressure. ___ 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: access to hard drives is blocked by writes to a flash drive
On 03/04/2013 04:01, Don Lewis wrote: The Lemming-syncer problem should have mostly been fixed by 231160 in head (231952 in stable/9 and 231967 in stable/8) a little over a year ago. The exceptions are atime updates, mmaped files with dirty pages, and quotas. Under certain workloads I still notice periodic bursts of seek noise. After thinking about it for a bit, I suspect that it could be atime updates, but I haven't tried to confirm that. atime is disabled on all mount points. Subversion doesn't use mmapped files, does it? No quotas are in use. atime is retarded anyway. There ought to be a kernel configuration (no)option SUPPORT_ATIME. ___ 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: ale(4) cannot negotiate as GigE
On Mon, Mar 04, 2013 at 02:46:31AM +, Alexey Dokuchaev wrote:
On Mon, Mar 04, 2013 at 11:10:59AM +0900, YongHyeon PYUN wrote:
On Mon, Mar 04, 2013 at 01:53:44AM +, Alexey Dokuchaev wrote:
Yes, it did help. With 2000us delays (I didn't revert them [...]
Great! But it seems 2ms delays is too much. Could you revert the change
(2000us delays) and try it again?
Reverting if_ale.c, making kernel, and reboot gave me 100baseTX again; :-(
second reboot (with the same kernel) did not help. Bumping delays to 2ms
(just to make sure) restored GigE mode upon 1st reboot after make kernel.
Ok, here is final diff which combines two things you've tested.
So revert any changes before applying it.
Let me know how it goes on your box.
./danfe
Index: sys/dev/ale/if_ale.c
===
--- sys/dev/ale/if_ale.c(revision 247382)
+++ sys/dev/ale/if_ale.c(working copy)
@@ -406,11 +406,11 @@ ale_phy_reset(struct ale_softc *sc)
CSR_WRITE_2(sc, ALE_GPHY_CTRL,
GPHY_CTRL_HIB_EN | GPHY_CTRL_HIB_PULSE | GPHY_CTRL_SEL_ANA_RESET |
GPHY_CTRL_PHY_PLL_ON);
- DELAY(1000);
+ DELAY(2000);
CSR_WRITE_2(sc, ALE_GPHY_CTRL,
GPHY_CTRL_EXT_RESET | GPHY_CTRL_HIB_EN | GPHY_CTRL_HIB_PULSE |
GPHY_CTRL_SEL_ANA_RESET | GPHY_CTRL_PHY_PLL_ON);
- DELAY(1000);
+ DELAY(2000);
#defineATPHY_DBG_ADDR 0x1D
#defineATPHY_DBG_DATA 0x1E
@@ -635,7 +635,7 @@ ale_attach(device_t dev)
/* Set up MII bus. */
error = mii_attach(dev, sc-ale_miibus, ifp, ale_mediachange,
ale_mediastatus, BMSR_DEFCAPMASK, sc-ale_phyaddr, MII_OFFSET_ANY,
- MIIF_DOPAUSE);
+ MIIF_DOPAUSE | MIIF_MACPRIV0);
if (error != 0) {
device_printf(dev, attaching PHYs failed\n);
goto fail;
Index: sys/dev/mii/atphy.c
===
--- sys/dev/mii/atphy.c (revision 247382)
+++ sys/dev/mii/atphy.c (working copy)
@@ -100,8 +100,14 @@ atphy_probe(device_t dev)
static int
atphy_attach(device_t dev)
{
+ struct mii_attach_args *ma;
+ u_int flags;
- mii_phy_dev_attach(dev, MIIF_NOMANPAUSE, atphy_funcs, 1);
+ ma = device_get_ivars(dev);
+ flags = MIIF_NOMANPAUSE;
+ if ((miibus_get_flags(dev) MIIF_MACPRIV0) != 0)
+ flags |= MIIF_PHYPRIV0;
+ mii_phy_dev_attach(dev, flags, atphy_funcs, 1);
return (0);
}
@@ -287,9 +293,11 @@ atphy_reset(struct mii_softc *sc)
uint32_t reg;
int i;
- /* Take PHY out of power down mode. */
- PHY_WRITE(sc, 29, 0x29);
- PHY_WRITE(sc, 30, 0);
+ if ((sc-mii_flags MIIF_PHYPRIV0) != 0) {
+ /* Take PHY out of power down mode. */
+ PHY_WRITE(sc, 29, 0x29);
+ PHY_WRITE(sc, 30, 0);
+ }
reg = PHY_READ(sc, ATPHY_SCR);
/* Enable automatic crossover. */
___
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: access to hard drives is blocked by writes to a flash drive
On Sun, Mar 03, 2013 at 07:01:27PM -0800, Don Lewis wrote: On 3 Mar, Poul-Henning Kamp wrote: For various reasons (see: Lemming-syncer) FreeBSD will block all I/O traffic to other disks too, when these pileups gets too bad. The Lemming-syncer problem should have mostly been fixed by 231160 in head (231952 in stable/9 and 231967 in stable/8) a little over a year ago. The exceptions are atime updates, mmaped files with dirty pages, and quotas. Under certain workloads I still notice periodic bursts of seek noise. After thinking about it for a bit, I suspect that it could be atime updates, but I haven't tried to confirm that. I never got a definition what a Lemming syncer term means. The (current) syncer model is to iterate over the list of the active vnodes, i.e. vnodes for which an open file exists, or a mapping is established, and initiate the neccessary writes. The iterations over the active list is performed several times during the same sync run over the filesystem, this is considered acceptable. (Mostly) independently, the syncer thread iterates over the list of the dirty buffers and writes them. The wdrain wait is independend from the syncer model used. It is entered by a thread which intends to write in some future, but the wait is performed before the entry into VFS is performed, in particular, before any VFS resources are acquired. The wait sleeps when the total amount of the buffer space for which the writes are active (runningbufspace counter) exceeds the hirunningbufspace threshold. This way buffer cache tries to avoid creating too long queue of the write requests. If there is some device which has high latency with the write completion, then it is easy to see that, for the load which creates intensive queue of writes to the said device, regardless of amount of writes to other devices, runningbufspace quickly gets populated with the buffers targeted to the slow device. Then, the wdrain wait mechanism kicks in, slowing all writers until the queue is processed. It could be argued that the current typical value of 16MB for the hirunningbufspace is too low, but experiments with increasing it did not provided any measureable change in the throughput or latency for some loads. And, just to wrestle with the misinformation, the unmapped buffer work has nothing to do with either syncer or runningbufspace. When using TCQ or NCQ, perhaps we should limit the number of outstanding writes per device to leave some slots open for reads. We should probably also prioritize reads over writes unless we are under memory pressure. Reads are allowed to start even when the runningbufspace is overflown. pgp3iUSyo6agv.pgp Description: PGP signature
Re: ale(4) cannot negotiate as GigE
On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote: Ok, here is final diff which combines two things you've tested. So revert any changes before applying it. Let me know how it goes on your box. Hmm, apparently something went wrong, as I'm back to 100baseTX after make kernel and reboot... ./danfe ___ 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: ale(4) cannot negotiate as GigE
On Mon, Mar 04, 2013 at 05:59:48AM +, Alexey Dokuchaev wrote:
On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote:
Ok, here is final diff which combines two things you've tested.
So revert any changes before applying it.
Let me know how it goes on your box.
Hmm, apparently something went wrong, as I'm back to 100baseTX after make
kernel and reboot...
Hmm, updated diff again.
./danfe
Index: sys/dev/ale/if_ale.c
===
--- sys/dev/ale/if_ale.c(revision 247382)
+++ sys/dev/ale/if_ale.c(working copy)
@@ -406,11 +406,13 @@ ale_phy_reset(struct ale_softc *sc)
CSR_WRITE_2(sc, ALE_GPHY_CTRL,
GPHY_CTRL_HIB_EN | GPHY_CTRL_HIB_PULSE | GPHY_CTRL_SEL_ANA_RESET |
GPHY_CTRL_PHY_PLL_ON);
- DELAY(1000);
+ CSR_READ_2(sc, ALE_GPHY_CTRL);
+ DELAY(2000);
CSR_WRITE_2(sc, ALE_GPHY_CTRL,
GPHY_CTRL_EXT_RESET | GPHY_CTRL_HIB_EN | GPHY_CTRL_HIB_PULSE |
GPHY_CTRL_SEL_ANA_RESET | GPHY_CTRL_PHY_PLL_ON);
- DELAY(1000);
+ CSR_READ_2(sc, ALE_GPHY_CTRL);
+ DELAY(2000);
#defineATPHY_DBG_ADDR 0x1D
#defineATPHY_DBG_DATA 0x1E
@@ -635,7 +637,7 @@ ale_attach(device_t dev)
/* Set up MII bus. */
error = mii_attach(dev, sc-ale_miibus, ifp, ale_mediachange,
ale_mediastatus, BMSR_DEFCAPMASK, sc-ale_phyaddr, MII_OFFSET_ANY,
- MIIF_DOPAUSE);
+ MIIF_DOPAUSE | MIIF_MACPRIV0);
if (error != 0) {
device_printf(dev, attaching PHYs failed\n);
goto fail;
@@ -1515,6 +1517,7 @@ ale_setwol(struct ale_softc *sc)
GPHY_CTRL_HIB_PULSE | GPHY_CTRL_PHY_PLL_ON |
GPHY_CTRL_SEL_ANA_RESET | GPHY_CTRL_PHY_IDDQ |
GPHY_CTRL_PCLK_SEL_DIS | GPHY_CTRL_PWDOWN_HW);
+ CSR_READ_2(sc, ALE_GPHY_CTRL);
return;
}
@@ -1547,6 +1550,7 @@ ale_setwol(struct ale_softc *sc)
GPHY_CTRL_HIB_PULSE | GPHY_CTRL_SEL_ANA_RESET |
GPHY_CTRL_PHY_IDDQ | GPHY_CTRL_PCLK_SEL_DIS |
GPHY_CTRL_PWDOWN_HW);
+ CSR_READ_2(sc, ALE_GPHY_CTRL);
}
/* Request PME. */
pmstat = pci_read_config(sc-ale_dev, pmc + PCIR_POWER_STATUS, 2);
Index: sys/dev/mii/atphy.c
===
--- sys/dev/mii/atphy.c (revision 247382)
+++ sys/dev/mii/atphy.c (working copy)
@@ -100,8 +100,14 @@ atphy_probe(device_t dev)
static int
atphy_attach(device_t dev)
{
+ struct mii_attach_args *ma;
+ u_int flags;
- mii_phy_dev_attach(dev, MIIF_NOMANPAUSE, atphy_funcs, 1);
+ ma = device_get_ivars(dev);
+ flags = MIIF_NOMANPAUSE;
+ if ((miibus_get_flags(dev) MIIF_MACPRIV0) != 0)
+ flags |= MIIF_PHYPRIV0;
+ mii_phy_dev_attach(dev, flags, atphy_funcs, 1);
return (0);
}
@@ -287,9 +293,11 @@ atphy_reset(struct mii_softc *sc)
uint32_t reg;
int i;
- /* Take PHY out of power down mode. */
- PHY_WRITE(sc, 29, 0x29);
- PHY_WRITE(sc, 30, 0);
+ if ((sc-mii_flags MIIF_PHYPRIV0) != 0) {
+ /* Take PHY out of power down mode. */
+ PHY_WRITE(sc, 29, 0x29);
+ PHY_WRITE(sc, 30, 0);
+ }
reg = PHY_READ(sc, ATPHY_SCR);
/* Enable automatic crossover. */
___
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: access to hard drives is blocked by writes to a flash drive
Content-Type: text/plain; charset=ISO-8859-1 In message 201303040301.r2431rjm008...@gw.catspoiler.org, Don Lewis writes: When using TCQ or NCQ, perhaps we should limit the number of outstanding writes per device to leave some slots open for reads. We should probably also prioritize reads over writes unless we are under memory pressure. Camera-grade flash seldom support either, they are strictly serial. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ 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: ale(4) cannot negotiate as GigE
On Mon, Mar 04, 2013 at 03:29:44PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 05:59:48AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote: Ok, here is final diff which combines two things you've tested. So revert any changes before applying it. Let me know how it goes on your box. Hmm, apparently something went wrong, as I'm back to 100baseTX after make kernel and reboot... Hmm, updated diff again. Better this time, I'm having 1000baseT again! :-) ./danfe ___ 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: access to hard drives is blocked by writes to a flash drive
On 4 Mar, Konstantin Belousov wrote: On Sun, Mar 03, 2013 at 07:01:27PM -0800, Don Lewis wrote: On 3 Mar, Poul-Henning Kamp wrote: For various reasons (see: Lemming-syncer) FreeBSD will block all I/O traffic to other disks too, when these pileups gets too bad. The Lemming-syncer problem should have mostly been fixed by 231160 in head (231952 in stable/9 and 231967 in stable/8) a little over a year ago. The exceptions are atime updates, mmaped files with dirty pages, and quotas. Under certain workloads I still notice periodic bursts of seek noise. After thinking about it for a bit, I suspect that it could be atime updates, but I haven't tried to confirm that. I never got a definition what a Lemming syncer term means. The (current) syncer model is to iterate over the list of the active vnodes, i.e. vnodes for which an open file exists, or a mapping is established, and initiate the neccessary writes. The iterations over the active list is performed several times during the same sync run over the filesystem, this is considered acceptable. Prior to 231160, the syncer thread would call sync_vnode() for the syncer vnode of each mountpoint every 30 seconds, depending on where the syncer vnode was in the worklist. sync_vnode() would in turn call VOP_FSYNC(-, MNT_LAZY, -) on the syncer vnode, which got mapped to sync_fsync(). sync_fsync() would then call vfs_msync() to perform an msync on all vnodes under the mount point, and then called VFS_SYNC(-, MNT_LAZY), which maps to a call to ffs_sync(). ffs_sync() would then ignore the MNT_LAZY flage and just blindly iterate over all the vnodes owned by the mountpoint, calling ffs_syncvnode() on any of them that had an IN_* flag set or had any dirty buffers. The result is that once every 30 seconds all of the dirty files under a mount point would be flushed to disk in one big blast. There have been a lot of improvements with 231160 and later changes, but I still notice periodic increases in seek noise under some workloads, but I haven't had a chance to investigate. (Mostly) independently, the syncer thread iterates over the list of the dirty buffers and writes them. It did that as well, prior to 231160. The wdrain wait is independend from the syncer model used. It is entered by a thread which intends to write in some future, but the wait is performed before the entry into VFS is performed, in particular, before any VFS resources are acquired. The wait sleeps when the total amount of the buffer space for which the writes are active (runningbufspace counter) exceeds the hirunningbufspace threshold. This way buffer cache tries to avoid creating too long queue of the write requests. If there is some device which has high latency with the write completion, then it is easy to see that, for the load which creates intensive queue of writes to the said device, regardless of amount of writes to other devices, runningbufspace quickly gets populated with the buffers targeted to the slow device. Then, the wdrain wait mechanism kicks in, slowing all writers until the queue is processed. Reserving at least sume space for each device might be beneficial to prevent one slow device from blocking writes to others, but in this case it sounds like reads are also getting blocked. It could be argued that the current typical value of 16MB for the hirunningbufspace is too low, but experiments with increasing it did not provided any measureable change in the throughput or latency for some loads. The correct value is probably proportional to the write bandwidth available. And, just to wrestle with the misinformation, the unmapped buffer work has nothing to do with either syncer or runningbufspace. When using TCQ or NCQ, perhaps we should limit the number of outstanding writes per device to leave some slots open for reads. We should probably also prioritize reads over writes unless we are under memory pressure. Reads are allowed to start even when the runningbufspace is overflown. I think reads are probably correctly self limiting in low memory situations because they'll be blocked when trying to allocate buffer space to read the data into. ___ 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: ale(4) cannot negotiate as GigE
On Mon, Mar 04, 2013 at 06:59:40AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 03:29:44PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 05:59:48AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote: Ok, here is final diff which combines two things you've tested. So revert any changes before applying it. Let me know how it goes on your box. Hmm, apparently something went wrong, as I'm back to 100baseTX after make kernel and reboot... Hmm, updated diff again. Better this time, I'm having 1000baseT again! :-) Thanks a lot for testing and patience! Could you reboot multiple times and check whether you reliably get a gigabit link? ./danfe ___ 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
[PATCH] kenv issue when there is no static environment
Planning to check the attached patch later this week, please let me know if there any objections. In case where there are no static kernel environment entries, the function init_dynamic_kenv() adds an incorrect entry at position 0 of the dynamic kernel environment. This entry is usually empty and confuses kenv(1). The entries added later by kenv(1) does not seem to be added, even though they are. The environment passed to the kernel can be empty when it is loaded from a bootloader other than loader(8). JC. kenv-fix.patch Description: Binary data ___ 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
