Re: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 15:33:16 Mark Andrews wrote: In message 2490439.ec638ti...@x220.ovitrap.com, Erich writes: Hi, On 05 June 2012 12:48:20 Mark Andrews wrote: In message 3506767.fvm2kmt...@x220.ovitrap.com, Erich writes: On 05 June 2012 11:24:25 Mark Andrews wrote: It's already there. If you want the ports as of FreeBSD 4.x EOL then the tag is RELEASE_4_EOL. If you want ports as of FreeBSD 9.0 then the tag is RELEASE_9_9_0. I did not know this. Do you have a link for this? I never read about it. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. I understand this that I can use these tags on the FreeBSD sources but not on the ports. I never tried this on the ports. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On Tue, Jun 05, 2012 at 12:18:33PM +0700, Erich wrote: I did not know this. Do you have a link for this? I never read about it. The EOL announcements have them. I don't think the release announcements do, however. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
On 04.06.12 22:32, Dave Hayes wrote: Chris Nehrenapeiron+freebsd-sta...@isuckatdomains.net writes: The descriptions of the options assume the admin is familiar with the software they're installing. I do not think it is the FreeBSD Project's purview to document every option for every port. At the very least it'd take quite a lot of time and effort to document all of that. That's a fair position. Perhaps it would not be too much trouble to add this one idea to optionsng: a more info field on each option knob which may be filled in by a port maintainer. The pkg-descr file in the port already contains link to the software's origin. The various options the software has are or should be described there. We definitely don't want the ports cluttered with extraneous and sometimes out of date (and thus misleading) information. Beyond this, such explanations would duplicate each port's own documentation. Not necessarily. I don't have an example offhand, but I suspect there are a number of FreeBSD specific option knobs applied to ports. There are in a way, and all of them are pretty much generic. Like WITHOUT_X11, WITH_CUPS etc. The purpose of these options is to more or less define the environment in which the port is intended to be used. For example, on a head-less server you most definitely want to build (say) php5 with WITHOUT_X11 in order to not pull unnecessary X11 related pieces. The intent of such options is to go to make.conf. These options are for convenience however. You can set each port's options individually. In all case, compiling from source is not for those having no clue what they do. The ports infrastructure in FreeBSD is already doing the hard work to port the software to your OS, you need to make informed decisions on options yourself. If this is beyond you (and not you personally), then by all means use pre-packaged software in binary form. Since it is very likely that you interpret this as yet another elitist comment, let's make it clear: anyone is welcome to ask for help with FreeBSD and ports (in the proper mailing list as to not create much noise and get negative response). Nobody is obliged to provide any help on anything. Nevertheless, the FreeBSD users are great community and you are often getting help even for the most stupid questions. Except when you start with name calling, or insist if you don't help me, I will go elsewhere or apparently, you don't want the number of FreeBSD users to grow. Then you waste everyone's time -- that could be spent on answering other people's stupid questions. Daniel Daniel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. It's not particularly easy to see this on cvsweb. But let's take a look at a random Mk/bsd.*.mk file via 'cvs log': RCS file: /home/FreeBSD/pcvs/ports/Mk/bsd.apache.mk,v Working file: bsd.apache.mk head: 1.36 branch: locks: strict access list: symbolic names: RELEASE_8_3_0: 1.35 RELEASE_9_0_0: 1.33 RELEASE_7_4_0: 1.26 RELEASE_8_2_0: 1.26 RELEASE_6_EOL: 1.26 [...] RELEASE_6_1_0: 1.9 RELEASE_5_5_0: 1.9 keyword substitution: kv total revisions: 36;selected revisions: 36 description: revision 1.36 date: 2012/05/23 08:17:48; author: miwi; state: Exp; lines: +2 -2 - Remove emacs mode, -*- mode: ...; -*- [1] - Comments for BUILD_ and RUN_DEPENDS fail to mention alternate means to specify dependencie [2] - Fix make reinstall [3] - Trivial comment change for PORTDATA [4] [...] and so forth. The line RELEASE_8_3_0: 1.35 tells you the version of this file as of tag RELEASE_8_3_0 was r1.35. So that's what's on the 8.3R distribution media. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
On 05.06.12 07:33, Zane C. B-H. wrote: [on Exchange wiping devices] From a enterprise perspective, it makes sense. Lets say a device goes missing, it allows one to wipe it the next time it calls home. This is supposed to be handled by the device management software. Not by your e-mail server. Because it does not belong to the mail server, this is why you will not find this functionality implemented in any open mail server or calendaring or groupware software. As you involved enterprise and your previous statement on Apple, they surprisingly do have such device deployment and management solution. You can either use their own Apple Configurator, or any third party MDM as described in http://www.apple.com/ipad/business/integration/mdm/. I would not call this technique proprietary. Ok, it only works on iOS ;) The usefulness of such a feature is better disconnected from the debate of proprietary v. non-proprietary though, given the different nature of both issues. With this I fully agree. I hope you too agree, than when you disconnect the e-mail handling features of Exchange, from the lock-in technology Microsoft integrated there (ActiveSync), Exchange is no different than any other non-proprietary mail server. The point here is that in order to have more freedom, one has to set expectations and setups right, from the begining. Separate the MDM and e-mail functionality and you are no longer locked with Microsoft or anyone. You can easily replace each component of your system and use the best software for the task. Not make compromises. Daniel PS: Yes, I don't like Microsoft's offerings. I understand why they do this, but this doesn't mean I agree and since I have plenty of other choices... I prefer the best. My enterprise(s) have been running on BSD UNIX for good over 20 years now. No Microsoft stuff. Not needed, not missed. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cvsup{, d} woes after upgrading to RELENG_9 on amd64 this weekend
On Mon, Jun 4, 2012 at 4:34 AM, Henri Hennebert h...@restart.be wrote:
On 06/04/2012 10:53, Trond Endrestøl wrote:
Hi,
After upgrading to RELENG_9 as of yesterday on my amd64 system, cvsup
bombs out with Bus error: 10.
Example:
# /usr/local/bin/cvsup -g -L 2 /usr/src/stable-supfile
Parsing supfile /usr/src/stable-supfile
Connecting to localhost
Connected to localhost
Server software version: SNAP_16_1h
Negotiating file attribute support
Exchanging collection information
Establishing multiplexed-mode data connection
Running
Updating collection src-all/cvs
Bus error: 10
The only recent change I can think of is switching to clang for
building the kernel and base. Made I should rebuild world and kernel
using gcc.
This is the culprit, you must compile libc and libz with gcc.
See http://www.freebsd.org/cgi/query-pr.cgi?pr=162588
make.conf snipet from PR 162588:
.if defined(WITH_CLANG)
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
.if !defined(CPP) || ${CPP} == cpp
CPP=clang -E
.endif
NO_WERROR=
WERROR=
.endif # WITH_CLANG
acccording to http://wiki.freebsd.org/BuildingFreeBSDWithClang#Quickstart,
you should be using:
CPP=clang-cpp
If you change this , does it fix the issue?
Scot
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 1:01:37 Mark Linimon wrote: On Tue, Jun 05, 2012 at 12:18:33PM +0700, Erich wrote: I did not know this. Do you have a link for this? I never read about it. The EOL announcements have them. I don't think the release announcements do, however. this is the problem. I would like to be able to go back to the last release in case of a problem and restart from there. When it is possible to tag the EOL, it should be as easy to tag the SOL (start of life). This would save a lot of time for many people. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 1:09:50 Mark Linimon wrote: On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. It's not particularly easy to see this on cvsweb. But let's take a look at a random Mk/bsd.*.mk file via 'cvs log': here we are. I never found this. RCS file: /home/FreeBSD/pcvs/ports/Mk/bsd.apache.mk,v Working file: bsd.apache.mk head: 1.36 branch: locks: strict access list: symbolic names: RELEASE_8_3_0: 1.35 RELEASE_9_0_0: 1.33 RELEASE_7_4_0: 1.26 RELEASE_8_2_0: 1.26 RELEASE_6_EOL: 1.26 [...] RELEASE_6_1_0: 1.9 RELEASE_5_5_0: 1.9 If this list would make it into the documentation, all I asked would be already there. I could write this but my English will need some corrections. If you could give a link to how to do this properly, I would do it then. But is this true for apache only or for the whole ports tree? Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: cvsup{, d} woes after upgrading to RELENG_9 on amd64 this weekend
On 06/05/2012 10:17, Scot Hetzel wrote:
On Mon, Jun 4, 2012 at 4:34 AM, Henri Henneberth...@restart.be wrote:
On 06/04/2012 10:53, Trond Endrestøl wrote:
Hi,
After upgrading to RELENG_9 as of yesterday on my amd64 system, cvsup
bombs out with Bus error: 10.
Example:
# /usr/local/bin/cvsup -g -L 2 /usr/src/stable-supfile
Parsing supfile /usr/src/stable-supfile
Connecting to localhost
Connected to localhost
Server software version: SNAP_16_1h
Negotiating file attribute support
Exchanging collection information
Establishing multiplexed-mode data connection
Running
Updating collection src-all/cvs
Bus error: 10
The only recent change I can think of is switching to clang for
building the kernel and base. Made I should rebuild world and kernel
using gcc.
This is the culprit, you must compile libc and libz with gcc.
See http://www.freebsd.org/cgi/query-pr.cgi?pr=162588
make.conf snipet from PR 162588:
.if defined(WITH_CLANG)
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
.if !defined(CPP) || ${CPP} == cpp
CPP=clang -E
.endif
NO_WERROR=
WERROR=
.endif # WITH_CLANG
acccording to http://wiki.freebsd.org/BuildingFreeBSDWithClang#Quickstart,
you should be using:
CPP=clang-cpp
I change this a while ago and it don't change the problem at hand
Henri
If you change this , does it fix the issue?
Scot
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On Jun 5, 2012 3:07 AM, Erich erichfreebsdl...@ovitrap.com wrote: Hi, On 05 June 2012 11:24:25 Mark Andrews wrote: Version tagging is just a convient way to get a snapshot at a particular point in time unless you create branches that are them we do not ask for more. There should be only one difference to a snapshot. As snapshot has a date. No matter in what state the ports tree was, it is in that state in the ports tree. If user - especially the one not so fit in this aspect - want to use a snapshot, it will be difficult to impossible to figure out which one they need. If version numbers would be introduced, it would be ok to use the version number of the FreeBSD and have only version available which reflect the release version of the ports tree. People here want to make always a perfect system. People like me want to have some small things in there available with a click. As the ports trees are there anyway, only the direct link to the snapshot of that day or a version number in the ports tree would be needed to make this available for people who just want to use FreeBSD. Please note, I do not want any extra work spend here to make this perfect. I only want a simple way to fall back to a big net which is not that old from which the user can restart. I and most others will purposely refuse to document this in any official capacity, but I'll give you a hint. Look for the date tag in man csup. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Load when idl on stable
On Sun, Jun 3, 2012 at 11:55 PM, Oliver Pinter oliver.p...@gmail.comwrote: I think, this is the old thread: http://freebsd.1045724.n5.nabble.com/High-load-event-idl-td5671431.html The interrupt rerouting does not help? On 6/3/12, Matt Thyer matt.th...@gmail.com wrote: On Jun 1, 2012 11:27 PM, Albert Shih albert.s...@obspm.fr wrote: Hi I already post a message about my problem I've three PC, all are Dell. Two laptop and one desktop. All run FreeBSD 9-Stable amd64 Since 1 or 2 months I notice the load is never drop down 0.8-0.9 event when nothing running but only on those laptop. I update today my desktop to last csup src and everything is fine on the desktop. On both laptop the load is still at 0.8 - 0.9 And in same time the usb mouse on the laptop stop working meaning I can use the touchpad, but if I plug a usb mouse, the kernel see the device but the mouse not working on xorg. Is' not block my work so I can live with that. I just want report those problems. Regards. JAS Is this due to a high rate of interrupts ? i.e. can you see this with systat -vm 1 with a large number in the intr field. If yes, run vmstat -i to see what interrupt is being hit. Then tell us what hardware is on that irq (from grep irq /var/run/dmesg.boot). Matt did you enable device polling for your NIC? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ata_controlcmd undefined
I csupped my 9.0-STABLE kernel on Sunday and now get this message at the beginning of booting up: link-elf-obj: symbol ata_controlcmd undefined KLD file atapicat.ko - could not finalize loading Kernel configuration is GENERIC (except scheduler is SCHED_4BSD). -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ZFS autoexpand when there are 2 raidz2 vdevs
Hi, all, during the last couple of years I occasionally increased the capacity of raidz2 based zpools by replacing one disk at a time and resilvering, subsequently. After replacing the final disk and a reboot (I guess zpool export zpool import would have done the trick, too) the capacity of the FS on top of that pool was increased according to the size of the new disk. All of theses systems had a pool built on one single vdev. Last week I exchanged all disks of one vdev that is part of a 2 vdev zpool. According to the Solaris documentation I found that should be possible. I always assumed vdevs were sort of independent of each other. My observations: During resilvering the activity LEDs of all 12 disks were showing heavy load, not only the ones of the 6 disks being part of the vdev in question. After exchanging all 6 disks the capacity stayed the same. I tried zpool export, zpool import reboot zpool scrub to no avail. datatomb2# zpool status sx40 pool: sx40 state: ONLINE scan: scrub repaired 0 in 3h32m with 0 errors on Sat Jun 2 00:41:38 2012 config: NAME STATE READ WRITE CKSUM sx40 ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gpt/sx40-disk0 ONLINE 0 0 0 gpt/sx40-disk1 ONLINE 0 0 0 gpt/sx40-disk2 ONLINE 0 0 0 gpt/sx40-disk3 ONLINE 0 0 0 gpt/sx40-disk4 ONLINE 0 0 0 gpt/sx40-disk5 ONLINE 0 0 0 raidz2-1 ONLINE 0 0 0 gpt/sx40-disk6 ONLINE 0 0 0 gpt/sx40-disk7 ONLINE 0 0 0 gpt/sx40-disk8 ONLINE 0 0 0 gpt/sx40-disk9 ONLINE 0 0 0 gpt/sx40-disk10 ONLINE 0 0 0 gpt/sx40-disk11 ONLINE 0 0 0 errors: No known data errors datatomb2# zpool get all sx40 NAME PROPERTY VALUE SOURCE sx40 size 10.9T - sx40 capacity 78% - sx40 altroot- default sx40 health ONLINE - sx40 guid 1478259715706579670 default sx40 version28 default sx40 bootfs - default sx40 delegation on default sx40 autoreplaceoff default sx40 cachefile - default sx40 failmode waitdefault sx40 listsnapshots off default sx40 autoexpand on local sx40 dedupditto 0 default sx40 dedupratio 1.00x - sx40 free 2.31T - sx40 allocated 8.57T - sx40 readonly off - The first 6 disks building raidz2-0 are 2 TB ones, not 1 TB. The gpt partitions *are* about 2 TB in size. What am I missing? Any hints welcome. I do have the hardware to build another device with 6 drives 2 TB and 6 drives 1 TB, which I planned to hook up to another server. Of course I could connect it to this one first, build a second pool, copy over the data ... but I was trying to avoid that in the first place ;-) Thanks in advance, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote: But is this true for apache only or for the whole ports tree? Entire tree. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS autoexpand when there are 2 raidz2 vdevs
Dear Patrick Am 05.06.2012 um 13:29 schrieb Patrick M. Hausen hau...@punkt.de: Hi, all, during the last couple of years I occasionally increased the capacity of raidz2 based zpools by replacing one disk at a time and resilvering, subsequently. After replacing the final disk and a reboot (I guess zpool export zpool import would have done the trick, too) the capacity of the FS on top of that pool was increased according to the size of the new disk. All of theses systems had a pool built on one single vdev. Last week I exchanged all disks of one vdev that is part of a 2 vdev zpool. According to the Solaris documentation I found that should be possible. I always assumed vdevs were sort of independent of each other. My observations: During resilvering the activity LEDs of all 12 disks were showing heavy load, not only the ones of the 6 disks being part of the vdev in question. After exchanging all 6 disks the capacity stayed the same. I tried zpool export, zpool import reboot zpool scrub to no avail. I used zpool set autoextend=on tank zpool online -e tank da0 zpool online -e tank da1 ... zpool online -e tank da7 to increase the size of a raidz2 here from 5+ to 11+TB. Worked without problems. This was with v28. Please check manages etc. for further explanations. Best regards, Holger -- Holger Kipp Diplom-Mathematiker Senior Consultant Tel. : +49 30 436 58 114 Fax. : +49 30 436 58 214 Mobil: +49 178 36 58 114 Email: holger.k...@alogis.com alogis AG Alt-Moabit 90b D-10559 Berlin web : http://www.alogis.com -- alogis AG Sitz/Registergericht: Berlin/AG Charlottenburg, HRB 71484 Vorstand: Arne Friedrichs, Joern Samuelson Aufsichtsratsvorsitzender: Reinhard Mielke ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 1:09:50 Mark Linimon wrote: On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. I found now the location where this information is missing for beginners. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html I simply cannot believe that beginners would expect this information to find this in the section for updating the kernel. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS autoexpand when there are 2 raidz2 vdevs
Hi, Am 05.06.2012 um 14:28 schrieb Holger Kipp: I used zpool set autoextend=on tank zpool online -e tank da0 zpool online -e tank da1 ... zpool online -e tank da7 to increase the size of a raidz2 here from 5+ to 11+TB. Worked without problems. datatomb2# zpool online -e sx40 gpt/sx40-disk0 ... datatomb2# zpool online -e sx40 gpt/sx40-disk5 datatomb2# zpool get all sx40 NAME PROPERTY VALUE SOURCE sx40 size 16.3T - ... Thanks! This was with v28. Please check manages etc. for further explanations. Done :-) Still puzzled why this worked automagically before. I don't have the time right now to check the repository for a change that might disable the automatic expansion of all new devices, but I suspect something like this. I see how it is safer if you trigger expansion manually. E.g. if you need to use a bigger temporary disk untill your warranty replacement with the correct size arrives. Best regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
O. Hartmann ohart...@zedat.fu-berlin.de wrote: 2) Disk and network I/O issues under load. We realized that FreeBSD has some issues in multithreaded environments. Even on 6/12 or 12/24 core/thread systems, under heavy load (especially network and CPU load), disk I/O was (is?) poor. This is a no-go in a HPC environment. This got a lot better when I switched to native AHCI mode for SATA disks. You have to have a fairly recent mainboard; my workstation at the office (about 3 years old) doesn't support AHCI mode yet. 4) The lack of clustering capabilities. The lack of a clustered filesystem grows more and more important in the area of HPC, where storage systems get spread over a department. Yes, a clustered file system would be very useful to have, even outside the HPC area. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You Using FreeBSD?
On Sun, 03 Jun 2012 20:45:59 -0500, Stephen Montgomery-Smith step...@missouri.edu wrote: More recently I have had to start using Linux because FreeBSD doesn't have very good laptop support. (All I ask for is a way to configure the mouse pad so that I can switch off tap to click.) See, this isn't very obvious to most people. It took me forever to figure it out. On every other OS you use the Xorg synaptics driver, but on FreeBSD there is synaptics support built-in with the rest of the mouse driver. man 4 psm: Tap and drag gestures can be disabled by setting hw.psm.tap_enabled to 0 at boot-time. Currently, this is only supported on Synaptics touchpads with Extended support disabled. The behaviour may be changed after boot by setting the sysctl with the same name and by restarting moused(8) using /etc/rc.d/moused. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
In message 1541214.zfrdxxb...@x220.ovitrap.com, Erich writes: Hi, On 05 June 2012 1:09:50 Mark Linimon wrote: On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. I found now the location where this information is missing for beginners. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html I simply cannot believe that beginners would expect this information to find this in the section for updating the kernel. Erich Because, while you believe it is better to roll back to the release point it really isn't. The ports tree is rarely broken for long. When it is broken people will tell you to roll back to a good date and give you the date to use. I've had to roll back a couple of times in 11+ years of updating and never to a release point. What is there is good advice. Use a up-to-date ports tree. If it is broken wait a days or so and try again. If it is still broken report the problem using send-pr. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
Mark Linimon lini...@lonesome.com wrote: The current status is that we support 8.x and 9.x well. Ports support for 7.x is starting to fade over time as new upstream releases rely on newer APIs. 6.x went EOL 11/30/2010 and we no longer claim to support it in ports. FWIW ... In fact, I can confirm that the ports don't support 6.x anymore since last week. :-) # cd /usr/ports/dns/bind96 # make No closing parenthesis in archive specification /usr/ports/Mk/bsd.options.mk, line 177: Error in archive specification: WITH_ No closing parenthesis in archive specification /usr/ports/Mk/bsd.options.mk, line 177: Error in archive specification: WITH_ make: fatal errors encountered -- cannot continue Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd C++ is the only current language making COBOL look good. -- Bertrand Meyer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ata_controlcmd undefined
George Mitchell wrote: I csupped my 9.0-STABLE kernel on Sunday and now get this message at the beginning of booting up: link-elf-obj: symbol ata_controlcmd undefined KLD file atapicat.ko - could not finalize loading The same happened to me, except that I had device atapicam statically in my kernel config. When building the new kernel, linking failed because of missing symbols (ata_controlcmd and others). It seems that atapicam is now obsolet and has been replaced by options ATA_CAM which is already present in GENERIC. Have you tried removing atapicam_load from /boot/loader.conf (I guess that's where you're trying to load the module)? Kernel configuration is GENERIC (except scheduler is SCHED_4BSD). Just out of curiosity, why do you prefer SCHED_4BSD? Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd To this day, many C programmers believe that 'strong typing' just means pounding extra hard on the keyboard. -- Peter van der Linden ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
Look at the comment of the maintainer of LibreOffice ... btw I tested and libreoffice is still working as expected. Most of the time the libreoffice failures is from people tuning their system without knowing the impact/risk of doing such, for example building some c++ libraries with g++47 let's imagine cppunit or anyother library depended on by libreoffice, and building libreoffice with clang (which is default) and using the libstdc++ from base (which also is default) and the mix of libstdc++ is producing tons of problems. problem i can't fix. regards, Bapt pgp9XqKXJF7QQ.pgp Description: PGP signature
Netflix's New Peering Appliance Uses FreeBSD
I just saw this, and thought I'd share: Open Connect Appliance Software Netflix delivers streaming content using a combination of intelligent clients, a central control system, and a network of Open Connect appliances. When designing the Open Connect Appliance Software, we focused on these fundamental design goals: - Use of Open Source software - Ability to efficiently read from disk and write to network sockets - High-performance HTTP delivery - Ability to gather routing information via BGP Operating System For the operating system, we use FreeBSD http://www.freebsd.org/ version 9.0. This was selected for its balance of stability and features, a strong development community and staff expertise. We will contribute changes we make as part of our project to the community through the FreeBSD committers on our team. Web server We use the nginx http://www.nginx.org/ web server for its proven scalability and performance. Netflix audio and video is served via HTTP. Routing intelligence proxy We use the BIRD Internet routing daemon http://bird.network.cz/ to enable the transfer of network topology from ISP networks to the Netflix control system that directs clients to sources of content. Acknowledgements We would would like to express our thanks to the FreeBSD community, the nginx community, and Ondrej and the BIRD team for providing excellent open source software. We also work directly with Igor, Maxim, Andrew, Sergey, Ruslan and the rest of the team at nginx.com http://www.nginx.com/, who provide superb development support for our project. -- Benjamin Francom Information Technology Professional http://www.benfrancom.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
em interfaces supermicro X9SCM-F board
hello all. i have a new board the supermicro X9SCM-F with the latest firmware 508. I am having some trouble with the onboard intel nics. It only activate one nic. From dmesg em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0xf020-0xf03f mem 0xf780-0xf781,0xf7825000-0xf7825fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Setup of Shared code failed device_attach: em0 attach returned 6 ehci0: EHCI (generic) USB 2.0 controller mem 0xf7824000-0xf78243ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0: EHCI (generic) USB 2.0 controller on ehci0 pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci3: ACPI PCI bus on pcib3 em1: Intel(R) PRO/1000 Network Connection 7.2.3 port 0xd000-0xd01f mem 0xf770-0xf771,0xf772-0xf7723fff irq 16 at device 0.0 on pci3 em1: Using MSIX interrupts with 3 vectors em1: Ethernet address: 00:25:90:75:c8:08 pciconf -vl em0@pci0:0:25:0:class=0x02 card=0x8086 chip=0x15038086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = '82579V Gigabit Network Connection' class = network subclass = ethernet em1@pci0:3:0:0: class=0x02 card=0x15d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet I have anothe machine wich has 9.0 stable as of today, if i boot from that disk, then it shows the above dmesg message with one difference that it replaces em1 for em0 also. it then looks like so em0: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xf020-0xf03f mem 0xf780-0xf781,0xf7825000-0xf7825fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Setup of Shared code failed device_attach: em0 attach returned 6 ehci0: EHCI (generic) USB 2.0 controller mem 0xf7824000-0xf78243ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xd000-0xd01f mem 0xf770-0xf771,0xf772-0xf7723fff irq 16 at device 0.0 on pci3 em0: Using MSIX interrupts with 3 vectors em0: Ethernet address: 00:25:90:75:c8:08 So still one network card. Full dmesg from the 9.0-STABLE install. Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Tue Jun 5 13:55:38 CEST 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.05-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x1fbae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 33077051392 (31544 MB) Event timer LAPIC quality 600 ACPI APIC Table: SUPERM SMCI--MB FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ctl: CAM Target Layer loaded acpi0: SUPERM SMCI--MB on motherboard acpi0: Power Button (fixed) acpi0: reservation of 67, 1 (4) failed cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET frequency 14318180 Hz quality 550 Event timer HPET1 frequency 14318180 Hz quality 440 Event timer HPET2 frequency 14318180 Hz quality 440 Event timer HPET3 frequency 14318180 Hz quality 440 Event timer HPET4 frequency 14318180 Hz quality 440 atrtc0: AT realtime clock port 0x70-0x77 irq 8 on acpi0 atrtc0: Warning: Couldn't map I/O. Event timer RTC frequency 32768 Hz quality 0 attimer0: AT timer port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 19 at
Re: em interfaces supermicro X9SCM-F board
I have an X9SCA-F board and recently updated the BIOS to version 2.0 (the .508 BIOS file). Its not the same board as yours but maybe the you have the same problem. When i downloaded the BIOS from the Supermicro website on May 23 the included AMI.BAT only updated the BIOS and not the Intel ME BIOS extension. When i downloaded the file again 2 days ago the AMI.BAT was updated to also flash the Intel ME. Too bad the version number and the filename are still the same. I only got to know this after contacting their support. My problems were different though. Both of my nics were usable but were hanging after about 2 hours of heavy load but maybe your problem can be fixed with a new BIOS update. Sebastian Am 05.06.2012 um 18:46 schrieb Johan Hendriks: hello all. i have a new board the supermicro X9SCM-F with the latest firmware 508. I am having some trouble with the onboard intel nics. It only activate one nic. From dmesg em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0xf020-0xf03f mem 0xf780-0xf781,0xf7825000-0xf7825fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Setup of Shared code failed device_attach: em0 attach returned 6 ehci0: EHCI (generic) USB 2.0 controller mem 0xf7824000-0xf78243ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0: EHCI (generic) USB 2.0 controller on ehci0 pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci3: ACPI PCI bus on pcib3 em1: Intel(R) PRO/1000 Network Connection 7.2.3 port 0xd000-0xd01f mem 0xf770-0xf771,0xf772-0xf7723fff irq 16 at device 0.0 on pci3 em1: Using MSIX interrupts with 3 vectors em1: Ethernet address: 00:25:90:75:c8:08 pciconf -vl em0@pci0:0:25:0:class=0x02 card=0x8086 chip=0x15038086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = '82579V Gigabit Network Connection' class = network subclass = ethernet em1@pci0:3:0:0: class=0x02 card=0x15d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet I have anothe machine wich has 9.0 stable as of today, if i boot from that disk, then it shows the above dmesg message with one difference that it replaces em1 for em0 also. it then looks like so em0: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xf020-0xf03f mem 0xf780-0xf781,0xf7825000-0xf7825fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Setup of Shared code failed device_attach: em0 attach returned 6 ehci0: EHCI (generic) USB 2.0 controller mem 0xf7824000-0xf78243ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xd000-0xd01f mem 0xf770-0xf771,0xf772-0xf7723fff irq 16 at device 0.0 on pci3 em0: Using MSIX interrupts with 3 vectors em0: Ethernet address: 00:25:90:75:c8:08 So still one network card. Full dmesg from the 9.0-STABLE install. Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Tue Jun 5 13:55:38 CEST 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.05-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x1fbae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 33077051392 (31544 MB) Event timer LAPIC quality 600 ACPI APIC Table: SUPERM SMCI--MB FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ctl: CAM Target Layer loaded acpi0: SUPERM SMCI--MB on motherboard acpi0: Power Button (fixed) acpi0: reservation of 67, 1 (4) failed cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0
Re: Netflix's New Peering Appliance Uses FreeBSD
I didn't see a link to this information in the e-mail below. I found this info detailed here: https://signup.netflix.com/openconnect/software From: Benjamin Francom bfran...@gmail.com To: freebsd-stable@freebsd.org Sent: Tue, June 5, 2012 11:00:01 AM Subject: Netflix's New Peering Appliance Uses FreeBSD I just saw this, and thought I'd share: Open Connect Appliance Software Netflix delivers streaming content using a combination of intelligent clients, a central control system, and a network of Open Connect appliances. When designing the Open Connect Appliance Software, we focused on these fundamental design goals: - Use of Open Source software - Ability to efficiently read from disk and write to network sockets - High-performance HTTP delivery - Ability to gather routing information via BGP Operating System For the operating system, we use FreeBSD http://www.freebsd.org/ version 9.0. This was selected for its balance of stability and features, a strong development community and staff expertise. We will contribute changes we make as part of our project to the community through the FreeBSD committers on our team. Web server We use the nginx http://www.nginx.org/ web server for its proven scalability and performance. Netflix audio and video is served via HTTP. Routing intelligence proxy We use the BIRD Internet routing daemon http://bird.network.cz/ to enable the transfer of network topology from ISP networks to the Netflix control system that directs clients to sources of content. Acknowledgements We would would like to express our thanks to the FreeBSD community, the nginx community, and Ondrej and the BIRD team for providing excellent open source software. We also work directly with Igor, Maxim, Andrew, Sergey, Ruslan and the rest of the team at nginx.com http://www.nginx.com/, who provide superb development support for our project. -- Benjamin Francom Information Technology Professional http://www.benfrancom.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Netflix's New Peering Appliance Uses FreeBSD
Hi! I didn't see a link to this information in the e-mail below. I found this info detailed here: https://signup.netflix.com/openconnect/software If you come from an IP range outside of netflix' footprint, that page is not available. But have a look at that PDF, comes from their webpage: http://opsec.eu/backup/OpenConnectDeploymentGuide-v2.4a.pdf -- p...@opsec.eu+49 171 3101372 8 years to go ! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em interfaces supermicro X9SCM-F board
On 2012-06-05 (Tuesday) 19:31:44 Sebastian Stach wrote: I have an X9SCA-F board and recently updated the BIOS to version 2.0 (the .508 BIOS file). Its not the same board as yours but maybe the you have the same problem. When i downloaded the BIOS from the Supermicro website on May 23 the included AMI.BAT only updated the BIOS and not the Intel ME BIOS extension. When i downloaded the file again 2 days ago the AMI.BAT was updated to also flash the Intel ME. Too bad the version number and the filename are still the same. I only got to know this after contacting their support. My problems were different though. Both of my nics were usable but were hanging after about 2 hours of heavy load but maybe your problem can be fixed with a new BIOS update. Sebastian Hello I never have updated the BIOS on my X9SCM-F, yet the interfaces are also going down after some time of full load. Was the NIC issue fixed for you by updating the BIOS? Alonso ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em interfaces supermicro X9SCM-F board
Sebastian Stach schreef: I have an X9SCA-F board and recently updated the BIOS to version 2.0 (the .508 BIOS file). Its not the same board as yours but maybe the you have the same problem. When i downloaded the BIOS from the Supermicro website on May 23 the included AMI.BAT only updated the BIOS and not the Intel ME BIOS extension. When i downloaded the file again 2 days ago the AMI.BAT was updated to also flash the Intel ME. Too bad the version number and the filename are still the same. I only got to know this after contacting their support. My problems were different though. Both of my nics were usable but were hanging after about 2 hours of heavy load but maybe your problem can be fixed with a new BIOS update. Sebastian Am 05.06.2012 um 18:46 schrieb Johan Hendriks: hello all. i have a new board the supermicro X9SCM-F with the latest firmware 508. I am having some trouble with the onboard intel nics. It only activate one nic. From dmesg em0:Intel(R) PRO/1000 Network Connection 7.2.3 port 0xf020-0xf03f mem 0xf780-0xf781,0xf7825000-0xf7825fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Setup of Shared code failed device_attach: em0 attach returned 6 ehci0:EHCI (generic) USB 2.0 controller mem 0xf7824000-0xf78243ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0:EHCI (generic) USB 2.0 controller on ehci0 pcib2:ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2:ACPI PCI bus on pcib2 pcib3:ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci3:ACPI PCI bus on pcib3 em1:Intel(R) PRO/1000 Network Connection 7.2.3 port 0xd000-0xd01f mem 0xf770-0xf771,0xf772-0xf7723fff irq 16 at device 0.0 on pci3 em1: Using MSIX interrupts with 3 vectors em1: Ethernet address: 00:25:90:75:c8:08 pciconf -vl em0@pci0:0:25:0:class=0x02 card=0x8086 chip=0x15038086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = '82579V Gigabit Network Connection' class = network subclass = ethernet em1@pci0:3:0:0: class=0x02 card=0x15d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet I have anothe machine wich has 9.0 stable as of today, if i boot from that disk, then it shows the above dmesg message with one difference that it replaces em1 for em0 also. it then looks like so em0:Intel(R) PRO/1000 Network Connection 7.3.2 port 0xf020-0xf03f mem 0xf780-0xf781,0xf7825000-0xf7825fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Setup of Shared code failed device_attach: em0 attach returned 6 ehci0:EHCI (generic) USB 2.0 controller mem 0xf7824000-0xf78243ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 pcib2:ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2:ACPI PCI bus on pcib2 pcib3:ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci3:ACPI PCI bus on pcib3 em0:Intel(R) PRO/1000 Network Connection 7.3.2 port 0xd000-0xd01f mem 0xf770-0xf771,0xf772-0xf7723fff irq 16 at device 0.0 on pci3 em0: Using MSIX interrupts with 3 vectors em0: Ethernet address: 00:25:90:75:c8:08 So still one network card. Full dmesg from the 9.0-STABLE install. Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Tue Jun 5 13:55:38 CEST 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.05-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x1fbae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 33077051392 (31544 MB) Event timer LAPIC quality 600 ACPI APIC Table:SUPERM SMCI--MB FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ctl: CAM Target Layer loaded acpi0:SUPERM SMCI--MB on motherboard acpi0: Power Button (fixed) acpi0: reservation of 67, 1 (4) failed cpu0:ACPI CPU on acpi0 cpu1:ACPI CPU on acpi0 cpu2:ACPI CPU on acpi0 cpu3:ACPI CPU on acpi0 hpet0:High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET
Re: em interfaces supermicro X9SCM-F board
The AMI.BAT you have already updates the BIOS and the Intel ME. I'm still in contact with the support but they told me that this fixes the issue most people are having. On my board one of the two nics is still hanging under heavy load. I hope that they will come up with a solution to this. Sebastian Stach Am 05.06.2012 um 20:39 schrieb Johan Hendriks: Thanks for the pointer. But my ami.bat file from the just downloaded .508 (2.0) firmware is the same as the one i used. this is my ami.bat @echo off REN AFUDOSU.SMC AFUDOSU.EXE AFUDOSU.EXE %1 /P /B /N /K /R /FDT /MER /OPR REN AFUDOSU.EXE AFUDOSU.SMC I will also try to contact there support desk, maybe they need to adjust some things for the bios file for the X9SCM-F also. regards Johan Hendriks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problem with sub-path (or sub-url) in smbfs.
On Tue, 29 May 2012 23:00:31 +0200, Manuel Trujillo (TooManySecrets) toom...@toomany.net wrote: On Fri, May 25, 2012 at 12:38 PM, Manuel Trujillo (TooManySecrets) toom...@toomany.net wrote: I have also an /etc/nsmb.conf configured. All runs fine... except because I only can mount up to recursos (from the line teide/recursos/usuarios/myuser), and NOT the share myuser (the last part of the PATH). Anybody could tell me, please, where is the better site/list to make this question? Thank you very much. Maybe freebsd-fs. Do you have error messages? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Load when idl on stable
Le 03/06/2012 ? 23:55:06+0200, Oliver Pinter a écrit I think, this is the old thread: http://freebsd.1045724.n5.nabble.com/High-load-event-idl-td5671431.html Yes. But because I didn't find any solution, I resent the problem. The interrupt rerouting does not help? Well I've no idea what you talking but I try every solution describe in the thread you mentioned. I didn't find any solution. Regards. NB: I forget to say I'm not a developer, just sysadmin. I use Stable just for report here any problem I got. -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@jabber.obspm.fr Heure local/Local time: mar 5 jui 2012 21:34:35 CEST ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Load when idl on stable
Le 04/06/2012 ? 06:22:34+0930, Matt Thyer a écrit Hi, Is this due to a high rate of interrupts ? No idea ;-) i.e. can you see this with systat -vm 1 with a large number in the intr field. Well I don't known what you mean by «high rate», so I make a compraison between my desktop and my laptop. On the laptop (where the load is always high) I got ~500- 650 total Interrupts with ~490-500 from hpet0 uhci On my desktop (load is ~0) I got ~340- 360 total Interrupts with 320-350 from hpet0 20 If yes, run vmstat -i to see what interrupt is being hit. On my laptop (uptime ~ 1h): vmstat -i interrupt total rate irq1: atkbd07240 1 irq9: acpi07 0 irq12: psm044037 10 irq14: ata0 6590 1 irq17: wpi0 683770155 irq18: atapci1 15447 3 irq19: fwohci0 2 0 irq20: hpet0 uhci0* 2888037656 irq22: ehci0 uhci4 2 0 irq256: hdac0 270090 61 Total3915222890 On my destkop (uptime 5 days) interrupt total rate irq1: atkbd0 239742 0 irq12: psm0 999224 2 irq16: uhci0 4062873 9 irq17: fwohci0++ 1 0 irq20: hpet0 222779529500 irq22: uhci2 ehci0222967 0 irq24: vgapci0972589 2 irq256: hdac09881473 22 irq257: bge0 8422313 18 irq258: ahci05744209 12 Total 253324920568 Then tell us what hardware is on that irq (from grep irq /var/run/dmesg.boot). Here on the laptop: grep irq /var/run/dmesg.boot ioapic0 Version 2.0 irqs 0-23 on motherboard atrtc0: AT realtime clock port 0x70-0x71,0x72-0x77 irq 8 on acpi0 attimer0: AT timer port 0x40-0x43,0x50-0x53 irq 2 on acpi0 vgapci0: VGA-compatible display port 0xdf00-0xdf7f mem 0xf500-0xf5ff,0xe000-0xefff,0xf200-0xf3ff irq 16 at device 0.0 on pci1 uhci0: Intel 82801H (ICH8) USB controller USB-D port 0x6f20-0x6f3f irq 20 at device 26.0 on pci0 uhci1: Intel 82801H (ICH8) USB controller USB-E port 0x6f00-0x6f1f irq 21 at device 26.1 on pci0 ehci0: Intel 82801H (ICH8) USB 2.0 controller USB2-B mem 0xfed1c400-0xfed1c7ff irq 22 at device 26.7 on pci0 hdac0: Intel 82801H HDA Controller mem 0xf6ffc000-0xf6ff irq 21 at device 27.0 on pci0 wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xf1fff000-0xf1ff irq 17 at device 0.0 on pci12 bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x00a200 mem 0xf1bf-0xf1bf irq 17 at device 0.0 on pci9 uhci2: Intel 82801H (ICH8) USB controller USB-A port 0x6f80-0x6f9f irq 20 at device 29.0 on pci0 uhci3: Intel 82801H (ICH8) USB controller USB-B port 0x6f60-0x6f7f irq 21 at device 29.1 on pci0 uhci4: Intel 82801H (ICH8) USB controller USB-C port 0x6f40-0x6f5f irq 22 at device 29.2 on pci0 ehci1: Intel 82801H (ICH8) USB 2.0 controller USB2-A mem 0xfed1c000-0xfed1c3ff irq 20 at device 29.7 on pci0 fwohci0: 1394 Open Host Controller Interface mem 0xf1aff800-0xf1af irq 19 at device 1.0 on pci3 atapci0: Intel ICH8M UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x6fa0-0x6faf irq 16 at device 31.1 on pci0 atapci1: Intel ICH8M SATA300 controller port 0x6eb0-0x6eb7,0x6eb8-0x6ebb,0x6ec0-0x6ec7,0x6ec8-0x6ecb,0x6ee0-0x6eef,0xeff0-0xefff irq 18 at device 31.2 on pci0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64,0x62,0x66 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@jabber.obspm.fr Heure local/Local time: mar 5 jui 2012 21:38:47 CEST ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Load when idl on stable
Le 05/06/2012 ? 12:40:19+0200, Matthias Gamsjager a écrit I've three PC, all are Dell. Two laptop and one desktop. All run FreeBSD 9-Stable amd64 Since 1 or 2 months I notice the load is never drop down 0.8-0.9 event when nothing running but only on those laptop. I update today my desktop to last csup src and everything is fine on the desktop. On both laptop the load is still at 0.8 - 0.9 And in same time the usb mouse on the laptop stop working meaning I can use the touchpad, but if I plug a usb mouse, the kernel see the device but the mouse not working on xorg. Is' not block my work so I can live with that. I just want report those problems. did you enable device polling for your NIC? No it's standard configuration about NIC. I don't need to enable anything to got high load, I boot the laptop, log with root login that's enough (without X11) to got 0.6-0.7 load. Basicaly I use a wifi NIC, and most important I change nothing on the configuration since ... long time ago (maybe FreeBSD 6.x). First time I got a problem so strange with Stable. (Maybe third time I got a problem with stable ;-) ). Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@jabber.obspm.fr Heure local/Local time: mar 5 jui 2012 21:51:58 CEST ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
On Fri, 01 Jun 2012 20:57:52 +0200, Thomas David Rivers riv...@dignus.com wrote: We used to have FreeBSD exclusively on desktops... Now, we have migrated to other desktops (mac) with FreeBSD running the build and file server... Why? Because - the mac updates itself! No pain, no installation, no keeping-up with mailing lists/announcements, just click and its done. Mac OS has a nice X11 server, the Mac UI is good enough, you don't have to install/update anything, the app store is perfect for downloading/installing whatever a desktop user might need. It was just too alluring... So, FreeBSD runs our NFS file server, and we log into a larger FreeBSD machine to do builds, etc... but, the desktop has moved. One developer here uses Linux Debian for about the same reason, it's trivial to update (via the network) to new versions, etc... Our web site used to be FreeBSD-based, but it was just too cost-effective to get a virtual Linux box on the backbone and move everything to that. Our requirements aren't too big, so that works beautifully. There _are_ people doing virtual FreeBSD boxes in a similar fashion, but they were quote a lot more for the annual fee.. so, Linux it was... I suppose, in some sense, you could argue that MacOS is FreeBSD... - Dave Rivers - Have you already tried pc-bsd? http://www.pcbsd.org/ FreeBSD with easy install and auto-update. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Load when idl on stable
On 06/05/12 15:37, Albert Shih wrote: Le 03/06/2012 ? 23:55:06+0200, Oliver Pinter a écrit I think, this is the old thread: http://freebsd.1045724.n5.nabble.com/High-load-event-idl-td5671431.html Yes. But because I didn't find any solution, I resent the problem. The interrupt rerouting does not help? Well I've no idea what you talking but I try every solution describe in the thread you mentioned. I didn't find any solution. Regards. NB: I forget to say I'm not a developer, just sysadmin. I use Stable just for report here any problem I got. Try changing kern.eventtimer.timer: % sysctl kern.eventtimer.timer=LAPIC How to display your choices ordered by quality: % sysctl kern.eventtimer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em interfaces supermicro X9SCM-F board
Sebastian Stach wrote: I have an X9SCA-F board and recently updated the BIOS to version 2.0 (the .508 BIOS file). Its not the same board as yours but maybe the you have the same problem. When i downloaded the BIOS from the Supermicro website on May 23 the included AMI.BAT only updated the BIOS and not the Intel ME BIOS extension. [...] There is a differenc between X9SCM-F and X9SCA-F. The SCM version has 82579V and 82574L NIC, but X9SCA-F has both NICs 82574L. And as I read about some problems with 82579V on the net, I bought X9SCA-F few weeks ago. I didn't notice any problem. Can you describe the conditions when you have some network problems so I can do some tests? I am running FreeBSD 8.3-RELEASE for testing, not heavily loaded. Miroslav Lachman Am 05.06.2012 um 18:46 schrieb Johan Hendriks: hello all. i have a new board the supermicro X9SCM-F with the latest firmware 508. I am having some trouble with the onboard intel nics. It only activate one nic. From dmesg em0:Intel(R) PRO/1000 Network Connection 7.2.3 port 0xf020-0xf03f mem 0xf780-0xf781,0xf7825000-0xf7825fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Setup of Shared code failed device_attach: em0 attach returned 6 ehci0:EHCI (generic) USB 2.0 controller mem 0xf7824000-0xf78243ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0:EHCI (generic) USB 2.0 controller on ehci0 pcib2:ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2:ACPI PCI bus on pcib2 pcib3:ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci3:ACPI PCI bus on pcib3 em1:Intel(R) PRO/1000 Network Connection 7.2.3 port 0xd000-0xd01f mem 0xf770-0xf771,0xf772-0xf7723fff irq 16 at device 0.0 on pci3 em1: Using MSIX interrupts with 3 vectors em1: Ethernet address: 00:25:90:75:c8:08 pciconf -vl em0@pci0:0:25:0:class=0x02 card=0x8086 chip=0x15038086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = '82579V Gigabit Network Connection' class = network subclass = ethernet em1@pci0:3:0:0: class=0x02 card=0x15d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em interfaces supermicro X9SCM-F board
I just need to run a tool like iperf and let it run. After about 1-2 hours my nic will just hang without any messages. I can't even ping the machine anymore. I also installed Solaris to check if it's maybe a FreeBSD problem but it's the same there. The support told me that they know about problems with the nics and the BIOS version 2.0 but that the new update should fix it. Which BIOS version do you have? Sebastian Stach Am 05.06.2012 um 22:16 schrieb Miroslav Lachman: There is a differenc between X9SCM-F and X9SCA-F. The SCM version has 82579V and 82574L NIC, but X9SCA-F has both NICs 82574L. And as I read about some problems with 82579V on the net, I bought X9SCA-F few weeks ago. I didn't notice any problem. Can you describe the conditions when you have some network problems so I can do some tests? I am running FreeBSD 8.3-RELEASE for testing, not heavily loaded. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Load when idl on stable
Le 05/06/2012 ? 16:14:56-0400, Adam McDougall a écrit On 06/05/12 15:37, Albert Shih wrote: Le 03/06/2012 ? 23:55:06+0200, Oliver Pinter a écrit I think, this is the old thread: http://freebsd.1045724.n5.nabble.com/High-load-event-idl-td5671431.html Yes. But because I didn't find any solution, I resent the problem. The interrupt rerouting does not help? Well I've no idea what you talking but I try every solution describe in the thread you mentioned. I didn't find any solution. Regards. NB: I forget to say I'm not a developer, just sysadmin. I use Stable just for report here any problem I got. Try changing kern.eventtimer.timer: % sysctl kern.eventtimer.timer=LAPIC I have no idea what's that mean, but yes it's much better. After 10 minutes the load drop to 0.08 (from 0.60-0.70) last pid: 2876; load averages: 0.05, 0.06, 0.17 up 0+02:14:49 22:45:45 81 processes: 1 running, 80 sleeping but still more than my desktop: last pid: 10150; load averages: 0.00, 0.00, 0.00 up 5+04:42:21 22:46:18 166 processes: 1 running, 165 sleeping Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@jabber.obspm.fr Heure local/Local time: mar 5 jui 2012 22:44:55 CEST ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em interfaces supermicro X9SCM-F board
Sebastian Stach wrote: I just need to run a tool like iperf and let it run. After about 1-2 hours my nic will just hang without any messages. I can't even ping the machine anymore. I also installed Solaris to check if it's maybe a FreeBSD problem but it's the same there. The support told me that they know about problems with the nics and the BIOS version 2.0 but that the new update should fix it. Which BIOS version do you have? The board had BIOS 1.1a with build date 2011-09-28 so I updated it to version 2.0 with build date 2012-05-08. I am preparing iperf test so I will let you know tomorrow about results. One question - are you using dedicated management port or shared with Intel NIC? Miroslav Lachman Am 05.06.2012 um 22:16 schrieb Miroslav Lachman: There is a differenc between X9SCM-F and X9SCA-F. The SCM version has 82579V and 82574L NIC, but X9SCA-F has both NICs 82574L. And as I read about some problems with 82579V on the net, I bought X9SCA-F few weeks ago. I didn't notice any problem. Can you describe the conditions when you have some network problems so I can do some tests? I am running FreeBSD 8.3-RELEASE for testing, not heavily loaded. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: em interfaces supermicro X9SCM-F board
The default was that IPMI is shared with the Intel NIC but i configured it to use the dedicated interface. Sebastian Stach Am 05.06.2012 um 23:21 schrieb Miroslav Lachman: The board had BIOS 1.1a with build date 2011-09-28 so I updated it to version 2.0 with build date 2012-05-08. I am preparing iperf test so I will let you know tomorrow about results. One question - are you using dedicated management port or shared with Intel NIC? Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Netflix's New Peering Appliance Uses FreeBSD
On Jun 5, 2012, at 9:56 AM, Benjamin Francom wrote: I just saw this, and thought I'd share: Open Connect Appliance Software Netflix delivers streaming content using a combination of intelligent clients, a central control system, and a network of Open Connect appliances. When designing the Open Connect Appliance Software, we focused on these fundamental design goals: - Use of Open Source software - Ability to efficiently read from disk and write to network sockets - High-performance HTTP delivery - Ability to gather routing information via BGP Operating System For the operating system, we use FreeBSD http://www.freebsd.org/ version 9.0. This was selected for its balance of stability and features, a strong development community and staff expertise. We will contribute changes we make as part of our project to the community through the FreeBSD committers on our team. Web server Yes, we are indeed using FreeBSD at Netflix! For those who are interested, I recently moved from Yahoo to Netflix to help support FreeBSD for them, and I'm definitely impressed with what is going on there. Other than a few small changes, we're using stock FreeBSD 9, tracking the 9-stable branch on a regular basis. Our chassis is a semi-custom 4U 19 form factor with thirty six 3TB SATA disks and 2 SSDs. Each disk has its own UFS+J filesystem, except for the SSDs that are mirrored together with gmirror. The SSDs hold the OS image and cache some of the busiest content. The other disks hold nothing but the audio and video files for our content streams. We connect to the outside world via a twin-port Intel 10GBe optical NIC (only one port is active at the moment), and we use LSI MPT2 controllers for 32 of the 36 disks. The other 4 disks connect to the onboard AHCI SATA controller. All of the disks are direct-attach with no SAS backplanes or expanders. Out-of-band management happens via IPMI on an on-board 1Gb NIC. The entire system consumes around 500W of power, making it a very efficient appliance for its functionality. Netflix is also at the front of the internet pack with IPv6 roll-out, and FreeBSD plays an essential part of that. We've been working hard on stabilizing the FreeBSD IPv6 stack for production-level traffic, and I recommend that all users of IPv6 update to the latest patches in 9-stable and 8-stable. Contact me directly if you have questions about this. That said, we're excited about World IPv6 Day, and we're ready with DNS records and content service from both Amazon and the traditional CDNs as well as our OpenConnect network. From an advocacy standpoint, Netflix represents 30% of all North American internet traffic during peak hours, and FreeBSD is becoming an integral part of that metric as we shift traffic off of the traditional CDNs. We're expanding quickly, which means that FreeBSD is once again a core part of the internet infrastructure. As we find and fix stability and performance issues, we're aggressively pushing those changes into FreeBSD so that everyone can benefit from them, just as we benefit from the contributions of the rest of the FreeBSD ecosystem. We're proud to be a part of the community, and look forward to a long-term relationship with FreeBSD. If you have any questions, let me know or follow the information links on the OpenConnect web site. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ata_controlcmd undefined
On 06/05/12 11:20, Oliver Fromme wrote: George Mitchell wrote: I csupped my 9.0-STABLE kernel on Sunday and now get this message at the beginning of booting up: link-elf-obj: symbol ata_controlcmd undefined KLD file atapicat.ko - could not finalize loading The same happened to me, except that I had device atapicam statically in my kernel config. When building the new kernel, linking failed because of missing symbols (ata_controlcmd and others). It seems that atapicam is now obsolet and has been replaced by options ATA_CAM which is already present in GENERIC. Okay, thanks for the explanation. Have you tried removing atapicam_load from /boot/loader.conf (I guess that's where you're trying to load the module)? Yes. Kernel configuration is GENERIC (except scheduler is SCHED_4BSD). Just out of curiosity, why do you prefer SCHED_4BSD? Don't get me started! -- George Best regards Oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Netflix's New Peering Appliance Uses FreeBSD
On Jun 5, 2012, at 20:16, Scott Long wrote: If you have any questions, let me know or follow the information links on the OpenConnect web site. Out of curiosity, given that Linux seems popular in so many other places (Google, Facebook), is there any particular reason why FreeBSD was chosen for this? I'm sure Linux is used in many other places (much of Netflix's IT infrastructure is on Amazon IIRC), so I'm kind of surprised that they went with FreeBSD when they probably already have so much knowledge with Linux. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on amd64/amd64
TB --- 2012-06-05 23:22:03 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-05 23:22:03 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-05 23:22:03 - starting RELENG_8 tinderbox run for amd64/amd64 TB --- 2012-06-05 23:22:03 - cleaning the object tree TB --- 2012-06-05 23:22:03 - cvsupping the source tree TB --- 2012-06-05 23:22:03 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/amd64/amd64/supfile TB --- 2012-06-05 23:22:14 - building world TB --- 2012-06-05 23:22:14 - CROSS_BUILD_TESTING=YES TB --- 2012-06-05 23:22:14 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-05 23:22:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-05 23:22:14 - SRCCONF=/dev/null TB --- 2012-06-05 23:22:14 - TARGET=amd64 TB --- 2012-06-05 23:22:14 - TARGET_ARCH=amd64 TB --- 2012-06-05 23:22:14 - TZ=UTC TB --- 2012-06-05 23:22:14 - __MAKE_CONF=/dev/null TB --- 2012-06-05 23:22:14 - cd /src TB --- 2012-06-05 23:22:14 - /usr/bin/make -B buildworld World build started on Tue Jun 5 23:22:15 UTC 2012 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 stage 5.1: building 32 bit shim libraries World build completed on Wed Jun 6 00:30:14 UTC 2012 TB --- 2012-06-06 00:30:14 - generating LINT kernel config TB --- 2012-06-06 00:30:14 - cd /src/sys/amd64/conf TB --- 2012-06-06 00:30:14 - /usr/bin/make -B LINT TB --- 2012-06-06 00:30:14 - cd /src/sys/amd64/conf TB --- 2012-06-06 00:30:14 - /usr/sbin/config -m LINT TB --- 2012-06-06 00:30:14 - building LINT kernel TB --- 2012-06-06 00:30:14 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 00:30:14 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 00:30:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 00:30:14 - SRCCONF=/dev/null TB --- 2012-06-06 00:30:14 - TARGET=amd64 TB --- 2012-06-06 00:30:14 - TARGET_ARCH=amd64 TB --- 2012-06-06 00:30:14 - TZ=UTC TB --- 2012-06-06 00:30:14 - __MAKE_CONF=/dev/null TB --- 2012-06-06 00:30:14 - cd /src TB --- 2012-06-06 00:30:14 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Jun 6 00:30:14 UTC 2012 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 [...] : export_syms awk -f /src/sys/conf/kmod_syms.awk if_rum.ko export_syms | xargs -J% objcopy % if_rum.ko objcopy --strip-debug if_rum.ko === usb/run (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/amd64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -I/obj/amd64/src/sys/LINT -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:77:1: error: nitems redefined In file included from /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:27: @/sys/param.h:274:1: error: this is the location of the previous definition *** Error code 1 Stop in /src/sys/modules/usb/run. *** Error code 1 Stop in /src/sys/modules/usb. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-06 00:48:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-06 00:48:26 - ERROR: failed to build LINT kernel TB --- 2012-06-06 00:48:26 - 4069.31 user 737.18 system 5183.05 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on i386/i386
TB --- 2012-06-06 00:04:34 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-06 00:04:34 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-06 00:04:34 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2012-06-06 00:04:34 - cleaning the object tree TB --- 2012-06-06 00:04:34 - cvsupping the source tree TB --- 2012-06-06 00:04:34 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/i386/supfile TB --- 2012-06-06 00:04:45 - building world TB --- 2012-06-06 00:04:45 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 00:04:45 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 00:04:45 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 00:04:45 - SRCCONF=/dev/null TB --- 2012-06-06 00:04:45 - TARGET=i386 TB --- 2012-06-06 00:04:45 - TARGET_ARCH=i386 TB --- 2012-06-06 00:04:45 - TZ=UTC TB --- 2012-06-06 00:04:45 - __MAKE_CONF=/dev/null TB --- 2012-06-06 00:04:45 - cd /src TB --- 2012-06-06 00:04:45 - /usr/bin/make -B buildworld World build started on Wed Jun 6 00:04:46 UTC 2012 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 Wed Jun 6 00:51:29 UTC 2012 TB --- 2012-06-06 00:51:29 - generating LINT kernel config TB --- 2012-06-06 00:51:29 - cd /src/sys/i386/conf TB --- 2012-06-06 00:51:29 - /usr/bin/make -B LINT TB --- 2012-06-06 00:51:29 - cd /src/sys/i386/conf TB --- 2012-06-06 00:51:29 - /usr/sbin/config -m LINT TB --- 2012-06-06 00:51:29 - building LINT kernel TB --- 2012-06-06 00:51:29 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 00:51:29 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 00:51:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 00:51:29 - SRCCONF=/dev/null TB --- 2012-06-06 00:51:29 - TARGET=i386 TB --- 2012-06-06 00:51:29 - TARGET_ARCH=i386 TB --- 2012-06-06 00:51:29 - TZ=UTC TB --- 2012-06-06 00:51:29 - __MAKE_CONF=/dev/null TB --- 2012-06-06 00:51:29 - cd /src TB --- 2012-06-06 00:51:29 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Jun 6 00:51:29 UTC 2012 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 [...] awk -f /src/sys/conf/kmod_syms.awk if_rum.kld export_syms | xargs -J% objcopy % if_rum.kld ld -Bshareable -d -warn-common -o if_rum.ko if_rum.kld objcopy --strip-debug if_rum.ko === usb/run (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/i386/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/i386/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:77:1: error: nitems redefined In file included from /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:27: @/sys/param.h:274:1: error: this is the location of the previous definition *** Error code 1 Stop in /src/sys/modules/usb/run. *** Error code 1 Stop in /src/sys/modules/usb. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-06 01:11:13 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-06 01:11:13 - ERROR: failed to build LINT kernel TB --- 2012-06-06 01:11:13 - 3185.40 user 542.33 system 3999.20 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on i386/pc98
TB --- 2012-06-06 00:08:22 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-06 00:08:22 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-06 00:08:22 - starting RELENG_8 tinderbox run for i386/pc98 TB --- 2012-06-06 00:08:22 - cleaning the object tree TB --- 2012-06-06 00:08:22 - cvsupping the source tree TB --- 2012-06-06 00:08:22 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/pc98/supfile TB --- 2012-06-06 00:08:33 - building world TB --- 2012-06-06 00:08:33 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 00:08:33 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 00:08:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 00:08:33 - SRCCONF=/dev/null TB --- 2012-06-06 00:08:33 - TARGET=pc98 TB --- 2012-06-06 00:08:33 - TARGET_ARCH=i386 TB --- 2012-06-06 00:08:33 - TZ=UTC TB --- 2012-06-06 00:08:33 - __MAKE_CONF=/dev/null TB --- 2012-06-06 00:08:33 - cd /src TB --- 2012-06-06 00:08:33 - /usr/bin/make -B buildworld World build started on Wed Jun 6 00:08:34 UTC 2012 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 Wed Jun 6 00:54:49 UTC 2012 TB --- 2012-06-06 00:54:49 - generating LINT kernel config TB --- 2012-06-06 00:54:49 - cd /src/sys/pc98/conf TB --- 2012-06-06 00:54:49 - /usr/bin/make -B LINT TB --- 2012-06-06 00:54:49 - cd /src/sys/pc98/conf TB --- 2012-06-06 00:54:49 - /usr/sbin/config -m LINT TB --- 2012-06-06 00:54:49 - building LINT kernel TB --- 2012-06-06 00:54:49 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 00:54:49 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 00:54:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 00:54:49 - SRCCONF=/dev/null TB --- 2012-06-06 00:54:49 - TARGET=pc98 TB --- 2012-06-06 00:54:49 - TARGET_ARCH=i386 TB --- 2012-06-06 00:54:49 - TZ=UTC TB --- 2012-06-06 00:54:49 - __MAKE_CONF=/dev/null TB --- 2012-06-06 00:54:49 - cd /src TB --- 2012-06-06 00:54:49 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Jun 6 00:54:49 UTC 2012 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 [...] awk -f /src/sys/conf/kmod_syms.awk if_rum.kld export_syms | xargs -J% objcopy % if_rum.kld ld -Bshareable -d -warn-common -o if_rum.ko if_rum.kld objcopy --strip-debug if_rum.ko === usb/run (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/pc98/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/pc98/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:77:1: error: nitems redefined In file included from /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:27: @/sys/param.h:274:1: error: this is the location of the previous definition *** Error code 1 Stop in /src/sys/modules/usb/run. *** Error code 1 Stop in /src/sys/modules/usb. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-06 01:11:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-06 01:11:22 - ERROR: failed to build LINT kernel TB --- 2012-06-06 01:11:22 - 3004.39 user 522.87 system 3780.00 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on mips/mips
TB --- 2012-06-06 00:26:55 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-06 00:26:55 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-06 00:26:55 - starting RELENG_8 tinderbox run for mips/mips TB --- 2012-06-06 00:26:55 - cleaning the object tree TB --- 2012-06-06 00:26:55 - cvsupping the source tree TB --- 2012-06-06 00:26:55 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/mips/mips/supfile TB --- 2012-06-06 00:27:09 - building world TB --- 2012-06-06 00:27:09 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 00:27:09 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 00:27:09 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 00:27:09 - SRCCONF=/dev/null TB --- 2012-06-06 00:27:09 - TARGET=mips TB --- 2012-06-06 00:27:09 - TARGET_ARCH=mips TB --- 2012-06-06 00:27:09 - TZ=UTC TB --- 2012-06-06 00:27:09 - __MAKE_CONF=/dev/null TB --- 2012-06-06 00:27:09 - cd /src TB --- 2012-06-06 00:27:09 - /usr/bin/make -B buildworld World build started on Wed Jun 6 00:27:09 UTC 2012 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 Wed Jun 6 01:03:48 UTC 2012 TB --- 2012-06-06 01:03:48 - cd /src/sys/mips/conf TB --- 2012-06-06 01:03:48 - /usr/sbin/config -m ADM5120 TB --- 2012-06-06 01:03:48 - building ADM5120 kernel TB --- 2012-06-06 01:03:48 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 01:03:48 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 01:03:48 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 01:03:48 - SRCCONF=/dev/null TB --- 2012-06-06 01:03:48 - TARGET=mips TB --- 2012-06-06 01:03:48 - TARGET_ARCH=mips TB --- 2012-06-06 01:03:48 - TZ=UTC TB --- 2012-06-06 01:03:48 - __MAKE_CONF=/dev/null TB --- 2012-06-06 01:03:48 - cd /src TB --- 2012-06-06 01:03:48 - /usr/bin/make -B buildkernel KERNCONF=ADM5120 Kernel build for ADM5120 started on Wed Jun 6 01:03:48 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for ADM5120 completed on Wed Jun 6 01:05:02 UTC 2012 TB --- 2012-06-06 01:05:02 - cd /src/sys/mips/conf TB --- 2012-06-06 01:05:02 - /usr/sbin/config -m ALCHEMY TB --- 2012-06-06 01:05:02 - building ALCHEMY kernel TB --- 2012-06-06 01:05:02 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 01:05:02 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 01:05:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 01:05:02 - SRCCONF=/dev/null TB --- 2012-06-06 01:05:02 - TARGET=mips TB --- 2012-06-06 01:05:02 - TARGET_ARCH=mips TB --- 2012-06-06 01:05:02 - TZ=UTC TB --- 2012-06-06 01:05:02 - __MAKE_CONF=/dev/null TB --- 2012-06-06 01:05:02 - cd /src TB --- 2012-06-06 01:05:02 - /usr/bin/make -B buildkernel KERNCONF=ALCHEMY Kernel build for ALCHEMY started on Wed Jun 6 01:05:02 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for ALCHEMY completed on Wed Jun 6 01:06:14 UTC 2012 TB --- 2012-06-06 01:06:14 - cd /src/sys/mips/conf TB --- 2012-06-06 01:06:14 - /usr/sbin/config -m AR71XX TB --- 2012-06-06 01:06:14 - building AR71XX kernel TB --- 2012-06-06 01:06:14 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 01:06:14 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 01:06:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 01:06:14 - SRCCONF=/dev/null TB --- 2012-06-06 01:06:14 - TARGET=mips TB --- 2012-06-06 01:06:14 - TARGET_ARCH=mips TB --- 2012-06-06 01:06:14 - TZ=UTC TB --- 2012-06-06 01:06:14 - __MAKE_CONF=/dev/null TB --- 2012-06-06 01:06:14 - cd /src TB --- 2012-06-06 01:06:14 - /usr/bin/make -B buildkernel KERNCONF=AR71XX Kernel build for AR71XX started on Wed Jun 6 01:06:14 UTC 2012 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 [...] awk -f /src/sys/conf/kmod_syms.awk if_rum.ko.debug export_syms | xargs -J% objcopy % if_rum.ko.debug objcopy --only-keep-debug if_rum.ko.debug if_rum.ko.symbols objcopy --strip-debug --add-gnu-debuglink=if_rum.ko.symbols if_rum.ko.debug if_rum.ko === usb/run (all) cc -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/mips/src/sys/AR71XX/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param
[releng_8 tinderbox] failure on ia64/ia64
TB --- 2012-06-06 00:20:20 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-06 00:20:20 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-06 00:20:20 - starting RELENG_8 tinderbox run for ia64/ia64 TB --- 2012-06-06 00:20:20 - cleaning the object tree TB --- 2012-06-06 00:20:20 - cvsupping the source tree TB --- 2012-06-06 00:20:20 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/ia64/ia64/supfile TB --- 2012-06-06 00:20:31 - building world TB --- 2012-06-06 00:20:31 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 00:20:31 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 00:20:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 00:20:31 - SRCCONF=/dev/null TB --- 2012-06-06 00:20:31 - TARGET=ia64 TB --- 2012-06-06 00:20:31 - TARGET_ARCH=ia64 TB --- 2012-06-06 00:20:31 - TZ=UTC TB --- 2012-06-06 00:20:31 - __MAKE_CONF=/dev/null TB --- 2012-06-06 00:20:31 - cd /src TB --- 2012-06-06 00:20:31 - /usr/bin/make -B buildworld World build started on Wed Jun 6 00:20:32 UTC 2012 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 Wed Jun 6 01:18:57 UTC 2012 TB --- 2012-06-06 01:18:57 - generating LINT kernel config TB --- 2012-06-06 01:18:57 - cd /src/sys/ia64/conf TB --- 2012-06-06 01:18:57 - /usr/bin/make -B LINT TB --- 2012-06-06 01:18:57 - cd /src/sys/ia64/conf TB --- 2012-06-06 01:18:57 - /usr/sbin/config -m LINT TB --- 2012-06-06 01:18:57 - building LINT kernel TB --- 2012-06-06 01:18:57 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 01:18:57 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 01:18:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 01:18:57 - SRCCONF=/dev/null TB --- 2012-06-06 01:18:57 - TARGET=ia64 TB --- 2012-06-06 01:18:57 - TARGET_ARCH=ia64 TB --- 2012-06-06 01:18:57 - TZ=UTC TB --- 2012-06-06 01:18:57 - __MAKE_CONF=/dev/null TB --- 2012-06-06 01:18:57 - cd /src TB --- 2012-06-06 01:18:57 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Jun 6 01:18:57 UTC 2012 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 [...] awk -f /src/sys/conf/kmod_syms.awk if_rum.kld export_syms | xargs -J% objcopy % if_rum.kld ld -Bshareable -d -warn-common -o if_rum.ko if_rum.kld objcopy --strip-debug if_rum.ko === usb/run (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/ia64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/ia64/src/sys/LINT -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -std=iso9899:1999 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:77:1: error: nitems redefined In file included from /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:27: @/sys/param.h:274:1: error: this is the location of the previous definition *** Error code 1 Stop in /src/sys/modules/usb/run. *** Error code 1 Stop in /src/sys/modules/usb. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-06 01:37:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-06 01:37:31 - ERROR: failed to build LINT kernel TB --- 2012-06-06 01:37:31 - 3959.70 user 527.77 system 4631.04 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-ia64-ia64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on powerpc/powerpc
TB --- 2012-06-06 00:48:27 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-06 00:48:27 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-06 00:48:27 - starting RELENG_8 tinderbox run for powerpc/powerpc TB --- 2012-06-06 00:48:27 - cleaning the object tree TB --- 2012-06-06 00:48:27 - cvsupping the source tree TB --- 2012-06-06 00:48:27 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/powerpc/powerpc/supfile TB --- 2012-06-06 00:48:38 - building world TB --- 2012-06-06 00:48:38 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 00:48:38 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 00:48:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 00:48:38 - SRCCONF=/dev/null TB --- 2012-06-06 00:48:38 - TARGET=powerpc TB --- 2012-06-06 00:48:38 - TARGET_ARCH=powerpc TB --- 2012-06-06 00:48:38 - TZ=UTC TB --- 2012-06-06 00:48:38 - __MAKE_CONF=/dev/null TB --- 2012-06-06 00:48:38 - cd /src TB --- 2012-06-06 00:48:38 - /usr/bin/make -B buildworld World build started on Wed Jun 6 00:48:38 UTC 2012 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 Wed Jun 6 01:31:15 UTC 2012 TB --- 2012-06-06 01:31:15 - generating LINT kernel config TB --- 2012-06-06 01:31:15 - cd /src/sys/powerpc/conf TB --- 2012-06-06 01:31:15 - /usr/bin/make -B LINT TB --- 2012-06-06 01:31:15 - cd /src/sys/powerpc/conf TB --- 2012-06-06 01:31:15 - /usr/sbin/config -m LINT TB --- 2012-06-06 01:31:15 - building LINT kernel TB --- 2012-06-06 01:31:15 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 01:31:15 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 01:31:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 01:31:15 - SRCCONF=/dev/null TB --- 2012-06-06 01:31:15 - TARGET=powerpc TB --- 2012-06-06 01:31:15 - TARGET_ARCH=powerpc TB --- 2012-06-06 01:31:15 - TZ=UTC TB --- 2012-06-06 01:31:15 - __MAKE_CONF=/dev/null TB --- 2012-06-06 01:31:15 - cd /src TB --- 2012-06-06 01:31:15 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Jun 6 01:31:15 UTC 2012 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 [...] awk -f /src/sys/conf/kmod_syms.awk if_rum.kld export_syms | xargs -J% objcopy % if_rum.kld ld -Bshareable -d -warn-common -o if_rum.ko if_rum.kld objcopy --strip-debug if_rum.ko === usb/run (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/powerpc/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mlongcall -fno-omit-frame-pointer -I/obj/powerpc/src/sys/LINT -msoft-float -mno-altivec -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:77:1: error: nitems redefined In file included from /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:27: @/sys/param.h:274:1: error: this is the location of the previous definition *** Error code 1 Stop in /src/sys/modules/usb/run. *** Error code 1 Stop in /src/sys/modules/usb. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-06 01:43:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-06 01:43:53 - ERROR: failed to build LINT kernel TB --- 2012-06-06 01:43:53 - 2796.39 user 441.25 system 3326.69 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-powerpc-powerpc.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on sparc64/sparc64
TB --- 2012-06-06 00:51:08 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-06 00:51:08 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-06 00:51:08 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2012-06-06 00:51:08 - cleaning the object tree TB --- 2012-06-06 00:51:08 - cvsupping the source tree TB --- 2012-06-06 00:51:08 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/sparc64/sparc64/supfile TB --- 2012-06-06 00:51:19 - building world TB --- 2012-06-06 00:51:19 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 00:51:19 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 00:51:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 00:51:19 - SRCCONF=/dev/null TB --- 2012-06-06 00:51:19 - TARGET=sparc64 TB --- 2012-06-06 00:51:19 - TARGET_ARCH=sparc64 TB --- 2012-06-06 00:51:19 - TZ=UTC TB --- 2012-06-06 00:51:19 - __MAKE_CONF=/dev/null TB --- 2012-06-06 00:51:19 - cd /src TB --- 2012-06-06 00:51:19 - /usr/bin/make -B buildworld World build started on Wed Jun 6 00:51:19 UTC 2012 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 Wed Jun 6 01:31:24 UTC 2012 TB --- 2012-06-06 01:31:24 - generating LINT kernel config TB --- 2012-06-06 01:31:24 - cd /src/sys/sparc64/conf TB --- 2012-06-06 01:31:24 - /usr/bin/make -B LINT TB --- 2012-06-06 01:31:24 - cd /src/sys/sparc64/conf TB --- 2012-06-06 01:31:24 - /usr/sbin/config -m LINT TB --- 2012-06-06 01:31:24 - building LINT kernel TB --- 2012-06-06 01:31:24 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 01:31:24 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 01:31:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 01:31:24 - SRCCONF=/dev/null TB --- 2012-06-06 01:31:24 - TARGET=sparc64 TB --- 2012-06-06 01:31:24 - TARGET_ARCH=sparc64 TB --- 2012-06-06 01:31:24 - TZ=UTC TB --- 2012-06-06 01:31:24 - __MAKE_CONF=/dev/null TB --- 2012-06-06 01:31:24 - cd /src TB --- 2012-06-06 01:31:24 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Jun 6 01:31:24 UTC 2012 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 [...] awk -f /src/sys/conf/kmod_syms.awk if_rum.kld export_syms | xargs -J% objcopy % if_rum.kld ld -Bshareable -d -warn-common -o if_rum.ko if_rum.kld objcopy --strip-debug if_rum.ko === usb/run (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sparc64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/sparc64/src/sys/LINT -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:77:1: error: nitems redefined In file included from /src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:27: @/sys/param.h:274:1: error: this is the location of the previous definition *** Error code 1 Stop in /src/sys/modules/usb/run. *** Error code 1 Stop in /src/sys/modules/usb. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-06 01:44:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-06 01:44:40 - ERROR: failed to build LINT kernel TB --- 2012-06-06 01:44:40 - 2699.03 user 426.41 system 3212.26 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Netflix's New Peering Appliance Uses FreeBSD
Maybe their knowledge of Linux drove them to use FreeBSD. Sorry, couldn't resist ;) On 06/05/2012 19:42, David Magda wrote: On Jun 5, 2012, at 20:16, Scott Long wrote: If you have any questions, let me know or follow the information links on the OpenConnect web site. Out of curiosity, given that Linux seems popular in so many other places (Google, Facebook), is there any particular reason why FreeBSD was chosen for this? I'm sure Linux is used in many other places (much of Netflix's IT infrastructure is on Amazon IIRC), so I'm kind of surprised that they went with FreeBSD when they probably already have so much knowledge with Linux. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 1:09:50 Mark Linimon wrote: On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. I found now the point in which all normal users will give up: The handbook states this: Which version(s) of them do you want? 'With CVSup, you can receive virtually any version of the sources that ever existed. That is possible because the cvsupd server works directly from the CVS repository, which contains all of the versions. You specify which one of them you want using the tag= and date= value fields. Warning: Be very careful to specify any tag= fields correctly. Some tags are valid only for certain collections of files. If you specify an incorrect or misspelled tag, CVSup will delete files which you probably do not want deleted. In particular, use only tag=. for the ports-* collections.' Why should a normal user continue to search for a tag when the handbook is so clear on this? Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 7:13:47 Mark Linimon wrote: On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote: But is this true for apache only or for the whole ports tree? Entire tree. my problem with this is that the documentation states something very different: From the handbook at the location where beginners will look for it: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html 'Which version(s) of them do you want? With CVSup, you can receive virtually any version of the sources that ever existed. That is possible because the cvsupd server works directly from the CVS repository, which contains all of the versions. You specify which one of them you want using the tag= and date= value fields. Warning: Be very careful to specify any tag= fields correctly. Some tags are valid only for certain collections of files. If you specify an incorrect or misspelled tag, CVSup will delete files which you probably do not want deleted. In particular, use only tag=. for the ports-* collections.' I think that this states very clearly that there are no tags. So, after we learned that every thing I am asking is there anyway in an official and supported way, only the documentation has to be changed. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
Hi, On 06 June 2012 0:42:47 Mark Andrews wrote: In message 1541214.zfrdxxb...@x220.ovitrap.com, Erich writes: Hi, On 05 June 2012 1:09:50 Mark Linimon wrote: On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. I found now the location where this information is missing for beginners. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html I simply cannot believe that beginners would expect this information to find this in the section for updating the kernel. Erich Because, while you believe it is better to roll back to the release point it really isn't. The ports tree is rarely broken for long. When it is broken people will tell you to roll back to a good date and give you the date to use. I've had to roll back a couple of times in 11+ years of updating and never to a release point. What is there is good advice. Use a up-to-date ports tree. If it is broken wait a days or so and try again. If it is still broken report the problem using send-pr. you will find thousands of notes that people should not run bleeding edge when it comes to the kernel. But people are forced to run bleeding edge on the ports. The documentation than even states that there is no fall back. You state it as being just normal to wait for a week or more until the problem is solved. I cannot imagine that people who come to FreeBSD and get trapped somehow will stick to it then. They might will ask on this list just to learn that there is no help available. Just wait. People who have to make decisions what operating system should be used on their workplaces will not like this and stick with whatever they have. I believe that this is a very good user repellent. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Netflix's New Peering Appliance Uses FreeBSD
On Jun 5, 2012, at 6:42 PM, David Magda wrote: On Jun 5, 2012, at 20:16, Scott Long wrote: If you have any questions, let me know or follow the information links on the OpenConnect web site. Out of curiosity, given that Linux seems popular in so many other places (Google, Facebook), is there any particular reason why FreeBSD was chosen for this? I'm sure Linux is used in many other places (much of Netflix's IT infrastructure is on Amazon IIRC), so I'm kind of surprised that they went with FreeBSD when they probably already have so much knowledge with Linux. Linux works wonderfully on EC2 for our CC and computational tasks, FreeBSD is proving to work well on deployed hardware for serving bits. It highly maintainable, and there's an excellent community supporting it. From the website: For the operating system, we use FreeBSD http://www.freebsd.org/ version 9.0. This was selected for its balance of stability and features, a strong development community and staff expertise. We will contribute changes we make as part of our project to the community through the FreeBSD committers on our team. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on arm/arm
TB --- 2012-06-06 05:11:14 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-06 05:11:14 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-06 05:11:14 - starting RELENG_8 tinderbox run for arm/arm TB --- 2012-06-06 05:11:14 - cleaning the object tree TB --- 2012-06-06 05:11:14 - cvsupping the source tree TB --- 2012-06-06 05:11:14 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/arm/arm/supfile TB --- 2012-06-06 05:11:41 - building world TB --- 2012-06-06 05:11:41 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 05:11:41 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 05:11:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 05:11:41 - SRCCONF=/dev/null TB --- 2012-06-06 05:11:41 - TARGET=arm TB --- 2012-06-06 05:11:41 - TARGET_ARCH=arm TB --- 2012-06-06 05:11:41 - TZ=UTC TB --- 2012-06-06 05:11:41 - __MAKE_CONF=/dev/null TB --- 2012-06-06 05:11:41 - cd /src TB --- 2012-06-06 05:11:41 - /usr/bin/make -B buildworld World build started on Wed Jun 6 05:11:41 UTC 2012 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 Wed Jun 6 05:48:17 UTC 2012 TB --- 2012-06-06 05:48:17 - cd /src/sys/arm/conf TB --- 2012-06-06 05:48:17 - /usr/sbin/config -m AVILA TB --- 2012-06-06 05:48:17 - building AVILA kernel TB --- 2012-06-06 05:48:17 - CROSS_BUILD_TESTING=YES TB --- 2012-06-06 05:48:17 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-06 05:48:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-06 05:48:17 - SRCCONF=/dev/null TB --- 2012-06-06 05:48:17 - TARGET=arm TB --- 2012-06-06 05:48:17 - TARGET_ARCH=arm TB --- 2012-06-06 05:48:17 - TZ=UTC TB --- 2012-06-06 05:48:17 - __MAKE_CONF=/dev/null TB --- 2012-06-06 05:48:17 - cd /src TB --- 2012-06-06 05:48:17 - /usr/bin/make -B buildkernel KERNCONF=AVILA Kernel build for AVILA started on Wed Jun 6 05:48:17 UTC 2012 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 [...] cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/cam/cam_queue.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/cam/cam_sim.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/cam/cam_xpt.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/cam/ata/ata_all.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/cam/ata/ata_xpt.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls
Re: Netflix's New Peering Appliance Uses FreeBSD
On Tue, 5 Jun 2012, Kurt Jaeger wrote: I didn't see a link to this information in the e-mail below. I found this info detailed here: https://signup.netflix.com/openconnect/software If you come from an IP range outside of netflix' footprint, that page is not available. Indeed, I found it a tad strange that URL redirecting to https://signup.netflix.com/global which sayeth: Sorry, Netflix is not available in your country... yet Enter your name and email address below and we'll email you when Netflix is available. But have a look at that PDF, comes from their webpage: http://opsec.eu/backup/OpenConnectDeploymentGuide-v2.4a.pdf Interesting box alright. Hope it wasn't Top Secret in my country, and that I can ask my (Debian based) ISP when they'll be getting some? :) Good to see Scott's found something to keep him off the streets too .. cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
