Re: squealing/whistling audio
On 9/18/2012 10:56 PM, matt wrote: On 09/18/12 18:01, Doug Barton wrote: Sometime in the last couple of months an old problem has resurfaced on HEAD, a sort of squealing/whistling sound in the audio, even without anything playing. The sound is similar to the wind whistling through something. Before I blindly go off on a bisecting spree, does anyone have a suggestion as to where I might look? Doug Electrically that's usually oscillation (too high gain or too much electrical feedback) or an unshielded input. Sorry, I should have been more clear. This problem doesn't occur in windows, or linux, and last time I checked, didn't occur in freebsd 8. I have everything irrlevant zeroed out in mixer. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: squealing/whistling audio
On Tue, Sep 18, 2012 at 10:56 PM, matt sendtom...@gmail.com wrote: On 09/18/12 18:01, Doug Barton wrote: Sometime in the last couple of months an old problem has resurfaced on HEAD, a sort of squealing/whistling sound in the audio, even without anything playing. The sound is similar to the wind whistling through something. Before I blindly go off on a bisecting spree, does anyone have a suggestion as to where I might look? Doug Electrically that's usually oscillation (too high gain or too much electrical feedback) or an unshielded input. My guess would be that there is an input that is defined and active in software, but is a loose, ungrounded pin in real life. Like a second microphone input on the chip, but not actually connected, would be my guess. Can you try purging out nids that you don't use with loader tunables (set their as to 0)? Or sysctls as reboots aren't as necessary anymore with snd_hda? Maybe something changed in software that is seeing inputs that were not present. Also just try muting all inputs with mixer... Just a guess, but when I hear squealing/whistling/howling I think analog before I think digital... Could also be a bitmasking/32-bit vs 64-bit bug like what was fixed last year in snd_emu10kx. HTH! -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: squealing/whistling audio
On 09/18/12 23:00, Doug Barton wrote: On 9/18/2012 10:56 PM, matt wrote: On 09/18/12 18:01, Doug Barton wrote: Sometime in the last couple of months an old problem has resurfaced on HEAD, a sort of squealing/whistling sound in the audio, even without anything playing. The sound is similar to the wind whistling through something. Before I blindly go off on a bisecting spree, does anyone have a suggestion as to where I might look? Doug Electrically that's usually oscillation (too high gain or too much electrical feedback) or an unshielded input. Sorry, I should have been more clear. This problem doesn't occur in windows, or linux, and last time I checked, didn't occur in freebsd 8. I have everything irrlevant zeroed out in mixer. Doug It was worth a shot. It is possible that each OS (and version) is setting the associations up properly though except HEAD on your machine. Is it a laptop or a desktop board? Any difference in the nid configuration between freebsd 8 and HEAD? Does changing any of the hw.snd sysctls (latency, exact rate, vpc_0db) have any effect on the sound? http://freshbsd.org/commit/freebsd/r230551 might be worth a look. I couldn't find anything newer that looked like it would have an effect. Their are some earlier commits around January that are dealing with signal gain that could also have an effect. Otherwise, I'm not sure where else to look. Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: MPSAFE VFS -- List of upcoming actions
On Wed, Sep 19, 2012 at 4:47 AM, Kevin Oberman kob6...@gmail.com wrote: On Tue, Sep 18, 2012 at 7:48 PM, Attilio Rao atti...@freebsd.org wrote: On Fri, Jul 13, 2012 at 12:18 AM, Attilio Rao atti...@freebsd.org wrote: 2012/7/4 Attilio Rao atti...@freebsd.org: 2012/6/29 Attilio Rao atti...@freebsd.org: As already published several times, according to the following plan: http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS I still haven't heard from Vivien or Edward, anyway as NTFS is basically only used RO these days (also the mount_ntfs code just permits RO mounting) I stripped all the uncomplete/bogus write support with the following patch: http://www.freebsd.org/~attilio/ntfs_remove_write.patch This is an attempt to make the code smaller and possibly just focus on the locking that really matter (as read-only filesystem). On some points of the patch I'm a bit less sure as we could easily take into account also write for things like vaccess() arguments, and make easier to re-add correct write support at some point in the future, but still force RO, even if the approach used in the patch is more correct IMHO. As an added bonus this patch cleans some dirty code in the mount operation and fixes a bug as vfs_mountedfrom() is called before real mounting is completed and can still fail. A quick update on this. It looks like NTFS won't be completed for this GSoC thus I seriously need to find an alternative to not loose the NTFS support entirely. I tried to look into the NTFS implementation right now and it is really a poor support. As Peter has also verified, it can deadlock in no-time, it compeltely violates VFS rules, etc. IMHO it deserves a complete rewrite if we would still support in-kernel NTFS. I also tried to look at the NetBSD implementation. Their code is someway similar to our, but they used very complicated (and very dirty) code to do the locking. Even if I don't know well enough NetBSD VFS, I have the impression not all the races are correctly handled. Definitively, not something I would like to port. Considering all that the only viable option would be meaning an userland filesystem implementation. My preferred choice would be to import PUFFS and librefuse on top of it but honestly it requires a lot of time to be completed, time which I don't currently have as in 2 months Giant must be gone by the VFS. I then decided to switch to gnn's rewamp of FUSE patches. You can find his initial e-mail here: http://lists.freebsd.org/pipermail/freebsd-fs/2012-March/013876.html I've precisely got the second version of George's patch and created this dolphin branch: svn://svn.freebsd.org/base/projects/fuse I'm fixing low hanging fruit for the moment (see r238411 for example) and I still have to make a throughful review. However my idea is to commit the support once: - ntfs-3g is well stress-tested and proves to be bug-free - there is no major/big technical issue pending after the reviews In the last weeks Peter, Florian, Gustau and I have been working in stabilizing fuse support. In the specific, Peter has worked hard on producing several utilities to nit stress-test fuse and in particular ntfs, Florian has improved fuse related ports (as explained later) and Gustau has done sparse testing. I feel moderately satisfied by the level of stability of fuse now to propose to wider usage, in particular given the huge amount of complaints I'm hearing around about occasional fuse users. The final target of the project is to completely import into base the content of fusefs-kmod starting from earlier posted patches by George. So far, we took care only of importing in the fuse branch the kernel part, so that fusefs-kmod userland part is still needed to be installed from ports, but I was studying the mount_fusefs licensing before to process with the import for the userland bits of it. The fixing has been happening here: svn://svn.freebsd.org/base/projects/fuse/ which is essentially an HEAD branch + fuse kernel components. In order to get fuse, please compile a kernel from this branch with FUSE option or simply build and load fuse module. Alternatively, a kernel patch that should work with HEAD@240684 is here: http://www.freebsd.org/~attilio/fuse_import/fuse_240684.patch I guess the patch can easilly apply to all FreeBSD branches, really, but it is not tested to anything else different then -CURRENT. As said you still need currently to build fusefs-kmod port. However you need these further patches, to be put in the fusefs-kmod/files/ directory:: http://www.freebsd.org/~attilio/fuse_import/patch-Makefile http://www.freebsd.org/~attilio/fuse_import/patch-mount_fusefs__mount_fusefs2.c They both disable the old kernel building/linking and import new functionality to let the new kernel support work well in presence of many consumers. In addition to fusefs-kmod, Bryan and Florian have also updated fusefs-lib and fusefs-ntfs ports. For
Re: Call for bge(4) testers
On Fri, 2012-09-14 at 14:27 -0700, YongHyeon PYUN wrote: All, There were lots of reports that stock bge(4) does not work on Dell Rx20/HP DL 360 G8. With the help of Broadcom and BCM5719/BCM5720 users I managed to address the issue but I had to touch very sensitive part of driver. Before committing the change to tree I'd like to know whether this change introduces regressions on old bge(4) controllers. If you're bge(4) user, please try latest WIP version at the following URL and let me know how it goes on your box. I'm especially interested in whether there is any ASF/IPMI regression on BCM570x/571x. http://people.freebsd.org/~yongari/bge/if_bge.c http://people.freebsd.org/~yongari/bge/if_bgereg.h http://people.freebsd.org/~yongari/bge/brgphy.c Build instructions 1. Copy both if_bge.c/if_bgereg.h to /usr/src/sys/dev/bge directory 2. Copy brgphy.c /usr/src/sys/dev/mii 3. Rebuild kernel and reboot to take the change effect. You can also use the files above for for 9.1/stable/9. For stable/8 it needs slight modification and I couldn't find time to regenerate the patch. Thanks. Still going through a battery of merging and regressions here at Y! I've got most of the Dell and HP gear that would be affected by these updates running at the moment via these updates. I have some different h/w IDs for brgphy and bge(4) that I need to capture and spam over this week. Sean ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: manual page | zpool-features
It should be part of the checkout. Try: man /usr/src/cddl/contrib/opensolaris/cmd/zpool/zpool-features.5 found it. :) Does this mean that I can not update from 9 to 10? No. So I ran mergemaster and upgraded zpool from '28' to 'zpool-features' and installed the new bootcode to ada0 and ada1. The next step needs to be right before I can reboot. pfctl and snmp_pf need to be recompiled. Does this mean 'make clean', 'make', and 'make install' in /usr/src/usr.sbin/bsnmpd/modules/snmp_pf and /usr/src/sbin/pfctl? Is either of the directories incorrect or some other combination of make calls required there? Thanks, Darrel ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: squealing/whistling audio
On Tue, 18 Sep 2012, Doug Barton wrote: Sometime in the last couple of months an old problem has resurfaced on HEAD, a sort of squealing/whistling sound in the audio, even without anything playing. The sound is similar to the wind whistling through something. Before I blindly go off on a bisecting spree, does anyone have a suggestion as to where I might look? It calls to mind this thread: http://lists.freebsd.org/pipermail/freebsd-current/2009-February/003608.html (with later followups http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009839.html and http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009850.html (and others?)) I had relief in my headphones with machdep.idle=spin, though that is only really useful when I am not paying my electricity bill... I agree with Matt that the noise is physically coming from analog leakage/crosstalk, and a software remedy will be something like disabling unused lines/pins. -Ben Kaduk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
g_dev_taste: make_dev_p() failed
GOHORNS:/usr/src/sys# uname -a FreeBSD GOHORNS.housenet.jrv 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r240529: Sat Sep 15 03:10:21 CDT 2012 r...@gohorns.housenet.jrv:/usr/obj/usr/src/sys/GENERIC amd64 I am getting an error when attaching some disks from Mac OSX. This is an enclose of 5 SATA disks used with OSX ZFS. Sep 19 02:56:28 GOHORNS kernel: g_dev_taste: make_dev_p() failed (gp-name=gpt/oformat%FF^PB9,, error=17) Sep 19 02:56:28 GOHORNS last message repeated 3 times When I look in /dev the device entries are there. Under FreeBSD it's using the siis driver for these disks. Each disk is GPT partitioned by OSX rather than whole disks ZFS. It looks like this in OSX: /dev/disk2 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk2 1:EFI 209.7 MB disk2s1 2:ZFS 3.0 TB disk2s2 /dev/disk3 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk3 1:EFI 209.7 MB disk3s1 2:ZFS 3.0 TB disk3s2 /dev/disk4 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk4 1:EFI 209.7 MB disk4s1 2:ZFS 3.0 TB disk4s2 /dev/disk5 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk5 1:EFI 209.7 MB disk5s1 2:ZFS 3.0 TB disk5s2 /dev/disk6 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk6 1:EFI 209.7 MB disk6s1 2:ZFS 3.0 TB disk6s2 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: MPSAFE VFS -- List of upcoming actions
On Wed, Sep 19, 2012 at 12:30 AM, Attilio Rao atti...@freebsd.org wrote: On Wed, Sep 19, 2012 at 4:47 AM, Kevin Oberman kob6...@gmail.com wrote: On Tue, Sep 18, 2012 at 7:48 PM, Attilio Rao atti...@freebsd.org wrote: On Fri, Jul 13, 2012 at 12:18 AM, Attilio Rao atti...@freebsd.org wrote: 2012/7/4 Attilio Rao atti...@freebsd.org: 2012/6/29 Attilio Rao atti...@freebsd.org: As already published several times, according to the following plan: http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS I still haven't heard from Vivien or Edward, anyway as NTFS is basically only used RO these days (also the mount_ntfs code just permits RO mounting) I stripped all the uncomplete/bogus write support with the following patch: http://www.freebsd.org/~attilio/ntfs_remove_write.patch This is an attempt to make the code smaller and possibly just focus on the locking that really matter (as read-only filesystem). On some points of the patch I'm a bit less sure as we could easily take into account also write for things like vaccess() arguments, and make easier to re-add correct write support at some point in the future, but still force RO, even if the approach used in the patch is more correct IMHO. As an added bonus this patch cleans some dirty code in the mount operation and fixes a bug as vfs_mountedfrom() is called before real mounting is completed and can still fail. A quick update on this. It looks like NTFS won't be completed for this GSoC thus I seriously need to find an alternative to not loose the NTFS support entirely. I tried to look into the NTFS implementation right now and it is really a poor support. As Peter has also verified, it can deadlock in no-time, it compeltely violates VFS rules, etc. IMHO it deserves a complete rewrite if we would still support in-kernel NTFS. I also tried to look at the NetBSD implementation. Their code is someway similar to our, but they used very complicated (and very dirty) code to do the locking. Even if I don't know well enough NetBSD VFS, I have the impression not all the races are correctly handled. Definitively, not something I would like to port. Considering all that the only viable option would be meaning an userland filesystem implementation. My preferred choice would be to import PUFFS and librefuse on top of it but honestly it requires a lot of time to be completed, time which I don't currently have as in 2 months Giant must be gone by the VFS. I then decided to switch to gnn's rewamp of FUSE patches. You can find his initial e-mail here: http://lists.freebsd.org/pipermail/freebsd-fs/2012-March/013876.html I've precisely got the second version of George's patch and created this dolphin branch: svn://svn.freebsd.org/base/projects/fuse I'm fixing low hanging fruit for the moment (see r238411 for example) and I still have to make a throughful review. However my idea is to commit the support once: - ntfs-3g is well stress-tested and proves to be bug-free - there is no major/big technical issue pending after the reviews In the last weeks Peter, Florian, Gustau and I have been working in stabilizing fuse support. In the specific, Peter has worked hard on producing several utilities to nit stress-test fuse and in particular ntfs, Florian has improved fuse related ports (as explained later) and Gustau has done sparse testing. I feel moderately satisfied by the level of stability of fuse now to propose to wider usage, in particular given the huge amount of complaints I'm hearing around about occasional fuse users. The final target of the project is to completely import into base the content of fusefs-kmod starting from earlier posted patches by George. So far, we took care only of importing in the fuse branch the kernel part, so that fusefs-kmod userland part is still needed to be installed from ports, but I was studying the mount_fusefs licensing before to process with the import for the userland bits of it. The fixing has been happening here: svn://svn.freebsd.org/base/projects/fuse/ which is essentially an HEAD branch + fuse kernel components. In order to get fuse, please compile a kernel from this branch with FUSE option or simply build and load fuse module. Alternatively, a kernel patch that should work with HEAD@240684 is here: http://www.freebsd.org/~attilio/fuse_import/fuse_240684.patch I guess the patch can easilly apply to all FreeBSD branches, really, but it is not tested to anything else different then -CURRENT. As said you still need currently to build fusefs-kmod port. However you need these further patches, to be put in the fusefs-kmod/files/ directory:: http://www.freebsd.org/~attilio/fuse_import/patch-Makefile http://www.freebsd.org/~attilio/fuse_import/patch-mount_fusefs__mount_fusefs2.c They both disable the old kernel building/linking and import new functionality to let the new kernel support work well in presence of many consumers. In addition to fusefs-kmod, Bryan
Re: MPSAFE VFS -- List of upcoming actions
On 9/19/12, Kevin Oberman kob6...@gmail.com wrote: On Wed, Sep 19, 2012 at 12:30 AM, Attilio Rao atti...@freebsd.org wrote: On Wed, Sep 19, 2012 at 4:47 AM, Kevin Oberman kob6...@gmail.com wrote: On Tue, Sep 18, 2012 at 7:48 PM, Attilio Rao atti...@freebsd.org wrote: On Fri, Jul 13, 2012 at 12:18 AM, Attilio Rao atti...@freebsd.org wrote: 2012/7/4 Attilio Rao atti...@freebsd.org: 2012/6/29 Attilio Rao atti...@freebsd.org: As already published several times, according to the following plan: http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS I still haven't heard from Vivien or Edward, anyway as NTFS is basically only used RO these days (also the mount_ntfs code just permits RO mounting) I stripped all the uncomplete/bogus write support with the following patch: http://www.freebsd.org/~attilio/ntfs_remove_write.patch This is an attempt to make the code smaller and possibly just focus on the locking that really matter (as read-only filesystem). On some points of the patch I'm a bit less sure as we could easily take into account also write for things like vaccess() arguments, and make easier to re-add correct write support at some point in the future, but still force RO, even if the approach used in the patch is more correct IMHO. As an added bonus this patch cleans some dirty code in the mount operation and fixes a bug as vfs_mountedfrom() is called before real mounting is completed and can still fail. A quick update on this. It looks like NTFS won't be completed for this GSoC thus I seriously need to find an alternative to not loose the NTFS support entirely. I tried to look into the NTFS implementation right now and it is really a poor support. As Peter has also verified, it can deadlock in no-time, it compeltely violates VFS rules, etc. IMHO it deserves a complete rewrite if we would still support in-kernel NTFS. I also tried to look at the NetBSD implementation. Their code is someway similar to our, but they used very complicated (and very dirty) code to do the locking. Even if I don't know well enough NetBSD VFS, I have the impression not all the races are correctly handled. Definitively, not something I would like to port. Considering all that the only viable option would be meaning an userland filesystem implementation. My preferred choice would be to import PUFFS and librefuse on top of it but honestly it requires a lot of time to be completed, time which I don't currently have as in 2 months Giant must be gone by the VFS. I then decided to switch to gnn's rewamp of FUSE patches. You can find his initial e-mail here: http://lists.freebsd.org/pipermail/freebsd-fs/2012-March/013876.html I've precisely got the second version of George's patch and created this dolphin branch: svn://svn.freebsd.org/base/projects/fuse I'm fixing low hanging fruit for the moment (see r238411 for example) and I still have to make a throughful review. However my idea is to commit the support once: - ntfs-3g is well stress-tested and proves to be bug-free - there is no major/big technical issue pending after the reviews In the last weeks Peter, Florian, Gustau and I have been working in stabilizing fuse support. In the specific, Peter has worked hard on producing several utilities to nit stress-test fuse and in particular ntfs, Florian has improved fuse related ports (as explained later) and Gustau has done sparse testing. I feel moderately satisfied by the level of stability of fuse now to propose to wider usage, in particular given the huge amount of complaints I'm hearing around about occasional fuse users. The final target of the project is to completely import into base the content of fusefs-kmod starting from earlier posted patches by George. So far, we took care only of importing in the fuse branch the kernel part, so that fusefs-kmod userland part is still needed to be installed from ports, but I was studying the mount_fusefs licensing before to process with the import for the userland bits of it. The fixing has been happening here: svn://svn.freebsd.org/base/projects/fuse/ which is essentially an HEAD branch + fuse kernel components. In order to get fuse, please compile a kernel from this branch with FUSE option or simply build and load fuse module. Alternatively, a kernel patch that should work with HEAD@240684 is here: http://www.freebsd.org/~attilio/fuse_import/fuse_240684.patch I guess the patch can easilly apply to all FreeBSD branches, really, but it is not tested to anything else different then -CURRENT. As said you still need currently to build fusefs-kmod port. However you need these further patches, to be put in the fusefs-kmod/files/ directory:: http://www.freebsd.org/~attilio/fuse_import/patch-Makefile http://www.freebsd.org/~attilio/fuse_import/patch-mount_fusefs__mount_fusefs2.c They both disable the old kernel building/linking and import new functionality to let the new kernel support work well in presence
Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
Hello, Freebsd-current. I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to build router's NanoBSD image, to today's morning (MSK time, GMT+4) revision. Unfortunately, I cannot provide exact version, as sources are in this unbootable VM too :) Kernel is GENERIC. VBox configuration is rather stander: 2 CPUs, ICH9, 2GB of RAM. Host is Windows 7/64bit. Booting hangs after (new?) line: atrtc0: AT realtime clock port 0x70-0x71 on acpi0 -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
Hello, Freebsd-current. You wrote 20 сентября 2012 г., 0:22:00: LS I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to LS build router's NanoBSD image, to today's morning (MSK time, GMT+4) LS revision. Unfortunately, I cannot provide exact version, as sources LS are in this unbootable VM too :) Revision is 240689 It looks like patch to RTC which is useful on Geode LX causes this hang. -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
240689 is a doc commit. Which commit is it really? :) Adrian On 19 September 2012 13:37, Lev Serebryakov l...@freebsd.org wrote: Hello, Freebsd-current. You wrote 20 сентября 2012 г., 0:22:00: LS I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to LS build router's NanoBSD image, to today's morning (MSK time, GMT+4) LS revision. Unfortunately, I cannot provide exact version, as sources LS are in this unbootable VM too :) Revision is 240689 It looks like patch to RTC which is useful on Geode LX causes this hang. -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
Hello, Adrian. You wrote 20 сентября 2012 г., 0:41:20: It looks like patch to RTC which is useful on Geode LX causes this hang. AC 240689 is a doc commit. Which commit is it really? :) I'm testing theory (build kernel from fresh sources), that it is caused by local RTC patch, which helps Geode. -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On Thu, 2012-09-20 at 00:37 +0400, Lev Serebryakov wrote: Hello, Freebsd-current. You wrote 20 сентября 2012 г., 0:22:00: LS I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to LS build router's NanoBSD image, to today's morning (MSK time, GMT+4) LS revision. Unfortunately, I cannot provide exact version, as sources LS are in this unbootable VM too :) Revision is 240689 It looks like patch to RTC which is useful on Geode LX causes this hang. Yes, exactly. I updated the PR to request that my patch not get committed because it locks up virtualbox. I hope to find time soon to learn enough about installing/configuring virtualbox to figure out what the problem is (offhand,I suspect it hangs in the loop that probes for the need to re-index, because vbox doesn't quite emulate the hardware behavior fully). -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
Ah, what's the patch? adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
Hello, Ian. You wrote 20 сентября 2012 г., 0:46:24: IL Yes, exactly. I updated the PR to request that my patch not get IL committed because it locks up virtualbox. I hope to find time soon to IL learn enough about installing/configuring virtualbox to figure out what IL the problem is (offhand,I suspect it hangs in the loop that probes for IL the need to re-index, because vbox doesn't quite emulate the hardware IL behavior fully). How could I help? Is it possible to debug kernel on such early stage? -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On 19 September 2012 13:54, Lev Serebryakov l...@freebsd.org wrote: Hello, Ian. You wrote 20 сентября 2012 г., 0:46:24: IL Yes, exactly. I updated the PR to request that my patch not get IL committed because it locks up virtualbox. I hope to find time soon to IL learn enough about installing/configuring virtualbox to figure out what IL the problem is (offhand,I suspect it hangs in the loop that probes for IL the need to re-index, because vbox doesn't quite emulate the hardware IL behavior fully). How could I help? Is it possible to debug kernel on such early stage? Add something to atrtc_start() to only loop over that loop say, 64k times before dropping out; and print an error if it hits that condition. Also, what's that RTCSA_8192 bit do? adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On Wed, 2012-09-19 at 14:00 -0700, Adrian Chadd wrote: On 19 September 2012 13:54, Lev Serebryakov l...@freebsd.org wrote: Hello, Ian. You wrote 20 сентября 2012 г., 0:46:24: IL Yes, exactly. I updated the PR to request that my patch not get IL committed because it locks up virtualbox. I hope to find time soon to IL learn enough about installing/configuring virtualbox to figure out what IL the problem is (offhand,I suspect it hangs in the loop that probes for IL the need to re-index, because vbox doesn't quite emulate the hardware IL behavior fully). How could I help? Is it possible to debug kernel on such early stage? Add something to atrtc_start() to only loop over that loop say, 64k times before dropping out; and print an error if it hits that condition. Also, what's that RTCSA_8192 bit do? That should set the interrupt rate really high, to minimize the time wasted waiting for the status bit to change in the register. Maybe that's the part that vbox isn't emulating well and so it never simulates an interrupt and leaves that loop. Or maybe because the loop is a tight busy-wait the emulator never gets control to simulate the occurance of the interrupt. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On 19 September 2012 14:05, Ian Lepore free...@damnhippie.dyndns.org wrote: Add something to atrtc_start() to only loop over that loop say, 64k times before dropping out; and print an error if it hits that condition. Also, what's that RTCSA_8192 bit do? That should set the interrupt rate really high, to minimize the time wasted waiting for the status bit to change in the register. Maybe that's the part that vbox isn't emulating well and so it never simulates an interrupt and leaves that loop. Or maybe because the loop is a tight busy-wait the emulator never gets control to simulate the occurance of the interrupt. Right. Being totally clueless, is atrc_start() called just at probe/attach, or during normal operation? adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On Wed, 2012-09-19 at 14:08 -0700, Adrian Chadd wrote: On 19 September 2012 14:05, Ian Lepore free...@damnhippie.dyndns.org wrote: Add something to atrtc_start() to only loop over that loop say, 64k times before dropping out; and print an error if it hits that condition. Also, what's that RTCSA_8192 bit do? That should set the interrupt rate really high, to minimize the time wasted waiting for the status bit to change in the register. Maybe that's the part that vbox isn't emulating well and so it never simulates an interrupt and leaves that loop. Or maybe because the loop is a tight busy-wait the emulator never gets control to simulate the occurance of the interrupt. Right. Being totally clueless, is atrc_start() called just at probe/attach, or during normal operation? It's called just once, from the attach() routine for the rtc device. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: g_dev_taste: make_dev_p() failed
on 19/09/2012 21:16 James R. Van Artsdalen said the following: GOHORNS:/usr/src/sys# uname -a FreeBSD GOHORNS.housenet.jrv 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r240529: Sat Sep 15 03:10:21 CDT 2012 r...@gohorns.housenet.jrv:/usr/obj/usr/src/sys/GENERIC amd64 I am getting an error when attaching some disks from Mac OSX. This is an enclose of 5 SATA disks used with OSX ZFS. Sep 19 02:56:28 GOHORNS kernel: g_dev_taste: make_dev_p() failed (gp-name=gpt/oformat%FF^PB9,, error=17) Sep 19 02:56:28 GOHORNS last message repeated 3 times error=17 is EEXIST /* File exists */ My guess that some partitions have the same GPT label. When I look in /dev the device entries are there. Under FreeBSD it's using the siis driver for these disks. Each disk is GPT partitioned by OSX rather than whole disks ZFS. It looks like this in OSX: /dev/disk2 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk2 1:EFI 209.7 MB disk2s1 2:ZFS 3.0 TB disk2s2 /dev/disk3 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk3 1:EFI 209.7 MB disk3s1 2:ZFS 3.0 TB disk3s2 /dev/disk4 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk4 1:EFI 209.7 MB disk4s1 2:ZFS 3.0 TB disk4s2 /dev/disk5 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk5 1:EFI 209.7 MB disk5s1 2:ZFS 3.0 TB disk5s2 /dev/disk6 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*3.0 TB disk6 1:EFI 209.7 MB disk6s1 2:ZFS 3.0 TB disk6s2 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[RFC] how to get real ifi_baudrate from network interface
hello,
for sometime now i've been repeatedly annoyed by the fact that 10G
interfaces lie about their ifi_baudrate. i would like to propose
simple (hopefuly) change to address this.
quick summary of the problem:
struct if_data {
...
u_char ifi_spare_char1;/* spare byte */
u_char ifi_spare_char2;/* spare byte */
...
u_long ifi_baudrate; /* linespeed */
...
};
as you can see ifi_baudrate is an u_long which is an arch specific
type. on 32-bit arch it does not have enough bits to hold 10G line
speed value (in bits per second)
proposal
we reuse one of the ifi_spare_char1 or ifi_spare_char2 bytes and
re-purpose it as power factor to be applied to ifi_baudrate, i.e.
real_ifi_baudrate = ifi_baudrate * 10 ** ifi_spare_char1
obviously, 10G nic drivers will have to set ifi_spare_char1 to
appropriate value, but it should not be a big deal. also, legacy tools
that do not know about ifi_spare_char1 would continue to report
wrong ifi_baudrate as they used to.
any objections?
thanks,
max
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On 19 September 2012 14:12, Ian Lepore free...@damnhippie.dyndns.org wrote: Right. Being totally clueless, is atrc_start() called just at probe/attach, or during normal operation? It's called just once, from the attach() routine for the rtc device. Right. Just have it loop over say 100 times, with a 10us sleep between each. Shouldn't that be enough? Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On Wed, 2012-09-19 at 14:30 -0700, Adrian Chadd wrote: On 19 September 2012 14:12, Ian Lepore free...@damnhippie.dyndns.org wrote: Right. Being totally clueless, is atrc_start() called just at probe/attach, or during normal operation? It's called just once, from the attach() routine for the rtc device. Right. Just have it loop over say 100 times, with a 10us sleep between each. Shouldn't that be enough? If by sleep you mean any form of pausing or sleeping that waits for a given amount of time... remember when this code is running we're still in the process of trying to figure out which clocks can be used for such purposes. That leaves DELAY(), which does pretty much the equivelent of what the loop in question is doing. Hmmm, but DELAY() does have the advantage of busy-looping for a known amount of time, making it easier to constrain the time spent in the loop regardless of the speed of the cpu. I'll have to look into how DELAY() is implemented for x86 and see if it's usable in this context. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for bge(4) testers
Hi, On Mon, Sep 17, 2012 at 09:37:21PM +0900, Wanpeng Qian wrote: Hi, here is the dmesg output. bge0: HP NC107i PCIe Gigabit Server Adapter, ASIC rev. 0x5784100 mem 0xfe9f-0xfe9f irq 18 at device 0.0 on pci4 bge0: CHIP ID 0x05784100; ASIC REV 0x5784; CHIP REV 0x57841; PCI-E miibus0: MII bus on bge0 brgphy0: BCM5784 10/100/1000baseT PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow It seems your controller is BCM5784 A1. The latest WIP have one change that may affect its DMA behavior. So it would be good to know how the WIP version works on your box. I update my system to 9-STABLE and using your WIP files. after I reboot the whole system. I cannot find bge anymore. here is the pciconf -lv output. none1@pci0:4:0:0: class=0x02 card=0x705d103c chip=0x165b14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'NetXtreme BCM5723 Gigabit Ethernet PCIe' class = network subclass = ethernet Regards. Qian FreeBSD 9.0 RELEASE. Regards. Qian watchdog timeouts can be triggered by various issues so it's hard to guess the root cause of the issue. Would you show me the dmesg output(bge(4)/brgphy(4) output only)? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore free...@damnhippie.dyndns.org wrote: ... Yes, exactly. I updated the PR to request that my patch not get committed because it locks up virtualbox. I hope to find time soon to learn enough about installing/configuring virtualbox to figure out what the problem is (offhand,I suspect it hangs in the loop that probes for the need to re-index, because vbox doesn't quite emulate the hardware behavior fully). Why not just detect VBox and disable that functionality? VMware at least has a sane way of determining whether or not you're running it based on the SMBios ident.. Thanks! -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On 19 September 2012 14:57, Garrett Cooper yaneg...@gmail.com wrote: On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore free...@damnhippie.dyndns.org wrote: ... Yes, exactly. I updated the PR to request that my patch not get committed because it locks up virtualbox. I hope to find time soon to learn enough about installing/configuring virtualbox to figure out what the problem is (offhand,I suspect it hangs in the loop that probes for the need to re-index, because vbox doesn't quite emulate the hardware behavior fully). Why not just detect VBox and disable that functionality? VMware at least has a sane way of determining whether or not you're running it based on the SMBios ident.. Sure, but that doens't answer the underlying reason(s) of why is it failing?. :-) Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On Wed, 2012-09-19 at 15:10 -0700, Adrian Chadd wrote: On 19 September 2012 14:57, Garrett Cooper yaneg...@gmail.com wrote: On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore free...@damnhippie.dyndns.org wrote: ... Yes, exactly. I updated the PR to request that my patch not get committed because it locks up virtualbox. I hope to find time soon to learn enough about installing/configuring virtualbox to figure out what the problem is (offhand,I suspect it hangs in the loop that probes for the need to re-index, because vbox doesn't quite emulate the hardware behavior fully). Why not just detect VBox and disable that functionality? VMware at least has a sane way of determining whether or not you're running it based on the SMBios ident.. Sure, but that doens't answer the underlying reason(s) of why is it failing?. :-) Yeah, I'd much rather understand a problem than tap dance around it, at least for starters. Figuring out what's really going on may lead to a discovery that it would fail in other circumstances as well, or it may lead to a bugfix in vbox if that's where the problem lies. I'm just a bit too busy with $work right now to dig into it. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On Wed, 19 Sep 2012 14:57:30 -0700, Garrett Cooper wrote: On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore free...@damnhippie.dyndns.org wrote: ... Yes, exactly. I updated the PR to request that my patch not get committed because it locks up virtualbox. I hope to find time soon to learn enough about installing/configuring virtualbox to figure out what the problem is (offhand,I suspect it hangs in the loop that probes for the need to re-index, because vbox doesn't quite emulate the hardware behavior fully). Why not just detect VBox and disable that functionality? VMware at least has a sane way of determining whether or not you're running it based on the SMBios ident.. VMware (as well as KVM and Xen) provides reliable way to detect its presence by checking hypervisor present CPUID's bit or accessing its I/O port, while VirtualBox doesn't do that, and matching SMBios ident doesn't seem to be really useful. Are there better and reliable ways of detecting VirtualBox? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: MPSAFE VFS -- List of upcoming actions
On 9/18/2012 9:48 PM, Attilio Rao wrote: In addition to fusefs-kmod, Bryan and Florian have also updated fusefs-lib and fusefs-ntfs ports. For instance, please refer to this e-mail: http://lists.freebsd.org/pipermail/freebsd-ports/2012-August/077950.html Even if this work is someway independent by the fusefs-kmod import, I warmly suggest to all of you to use their patches (and this what we have been testing so far too). I have committed my updates to sysutils/fusefs-ntfs now. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on arm/arm
TB --- 2012-09-20 00:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 00:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 00:30:00 - starting HEAD tinderbox run for arm/arm TB --- 2012-09-20 00:30:00 - cleaning the object tree TB --- 2012-09-20 00:30:00 - cvsupping the source tree TB --- 2012-09-20 00:30:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2012-09-20 00:31:06 - building world TB --- 2012-09-20 00:31:06 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 00:31:06 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 00:31:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 00:31:06 - SRCCONF=/dev/null TB --- 2012-09-20 00:31:06 - TARGET=arm TB --- 2012-09-20 00:31:06 - TARGET_ARCH=arm TB --- 2012-09-20 00:31:06 - TZ=UTC TB --- 2012-09-20 00:31:06 - __MAKE_CONF=/dev/null TB --- 2012-09-20 00:31:06 - cd /src TB --- 2012-09-20 00:31:06 - /usr/bin/make -B buildworld World build started on Thu Sep 20 00:31:07 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 [...] `chroot.o' is up to date. (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo tee.lo gzip.lo bzip2.lo ! xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/arm.arm/src/rescue/rescue/../librescue/exec.o /obj/arm.arm/src/rescue/rescue/../librescue/getusershell.o /obj/arm.arm/src/rescue/rescue/../librescue/login_class.o /obj/arm.arm/src/rescue/rescue/../librescue/popen.o /obj/arm.arm/src/rescue/rescue/../librescue/rcmdsh.o /obj/arm.arm/src/rescue/rescue/../librescue/sysctl.o /obj/arm.arm/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo: In function `_$$hide$$ nc.lo $a': _$$hide$$ nc.lo socks.c:(.text+0x18e0): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo: In function `_$$hide$$ zfs.lo $a': _$$hide$$ zfs.lo zfs_iter.c:(.text+0x1e80): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/arm.arm/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 01:23:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 01:23:32 - ERROR: failed to build world TB --- 2012-09-20 01:23:32 - 2026.35 user 493.66 system 3211.79 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [RFC] how to get real ifi_baudrate from network interface
On Wed, Sep 19, 2012 at 02:16:17PM -0700, Maksim Yevmenkin wrote:
M hello,
M
M for sometime now i've been repeatedly annoyed by the fact that 10G
M interfaces lie about their ifi_baudrate. i would like to propose
M simple (hopefuly) change to address this.
M
M quick summary of the problem:
M
M struct if_data {
M ...
M u_char ifi_spare_char1;/* spare byte */
M u_char ifi_spare_char2;/* spare byte */
M ...
M u_long ifi_baudrate; /* linespeed */
M ...
M };
M
M as you can see ifi_baudrate is an u_long which is an arch specific
M type. on 32-bit arch it does not have enough bits to hold 10G line
M speed value (in bits per second)
M
M proposal
M
M we reuse one of the ifi_spare_char1 or ifi_spare_char2 bytes and
M re-purpose it as power factor to be applied to ifi_baudrate, i.e.
M
M real_ifi_baudrate = ifi_baudrate * 10 ** ifi_spare_char1
M
M obviously, 10G nic drivers will have to set ifi_spare_char1 to
M appropriate value, but it should not be a big deal. also, legacy tools
M that do not know about ifi_spare_char1 would continue to report
M wrong ifi_baudrate as they used to.
M
M any objections?
IMO, this is way to go for stable branches. In head it'll be better just
have uint64_t without any crutches.
--
Totus tuus, Glebius.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on ia64/ia64
TB --- 2012-09-20 01:23:33 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 01:23:33 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 01:23:33 - starting HEAD tinderbox run for ia64/ia64 TB --- 2012-09-20 01:23:33 - cleaning the object tree TB --- 2012-09-20 01:23:33 - cvsupping the source tree TB --- 2012-09-20 01:23:33 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2012-09-20 01:23:58 - building world TB --- 2012-09-20 01:23:58 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 01:23:58 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 01:23:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 01:23:58 - SRCCONF=/dev/null TB --- 2012-09-20 01:23:58 - TARGET=ia64 TB --- 2012-09-20 01:23:58 - TARGET_ARCH=ia64 TB --- 2012-09-20 01:23:58 - TZ=UTC TB --- 2012-09-20 01:23:58 - __MAKE_CONF=/dev/null TB --- 2012-09-20 01:23:58 - cd /src TB --- 2012-09-20 01:23:58 - /usr/bin/make -B buildworld World build started on Thu Sep 20 01:23:59 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 [...] (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo mca.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo tee.lo gzip.lo bz! ip2.lo xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/ia64.ia64/src/rescue/rescue/../librescue/exec.o /obj/ia64.ia64/src/rescue/rescue/../librescue/getusershell.o /obj/ia64.ia64/src/rescue/rescue/../librescue/login_class.o /obj/ia64.ia64/src/rescue/rescue/../librescue/popen.o /obj/ia64.ia64/src/rescue/rescue/../librescue/rcmdsh.o /obj/ia64.ia64/src/rescue/rescue/../librescue/sysctl.o /obj/ia64.ia64/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo: In function `_$$hide$$ nc.lo main': (.text+0x4502): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo: In function `_$$hide$$ zfs.lo do_jail': _$$hide$$ zfs.lo zfs_main.c:(.text+0x4a42): undefined reference to `jail_getid' _$$hide$$ zfs.lo zfs_main.c:(.text+0x4b92): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/ia64.ia64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 02:33:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 02:33:12 - ERROR: failed to build world TB --- 2012-09-20 02:33:12 - 3249.67 user 521.70 system 4179.91 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on i386/pc98
TB --- 2012-09-20 00:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 00:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 00:30:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2012-09-20 00:30:00 - cleaning the object tree TB --- 2012-09-20 00:30:00 - cvsupping the source tree TB --- 2012-09-20 00:30:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2012-09-20 00:31:06 - building world TB --- 2012-09-20 00:31:06 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 00:31:06 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 00:31:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 00:31:06 - SRCCONF=/dev/null TB --- 2012-09-20 00:31:06 - TARGET=pc98 TB --- 2012-09-20 00:31:06 - TARGET_ARCH=i386 TB --- 2012-09-20 00:31:06 - TZ=UTC TB --- 2012-09-20 00:31:06 - __MAKE_CONF=/dev/null TB --- 2012-09-20 00:31:06 - cd /src TB --- 2012-09-20 00:31:06 - /usr/bin/make -B buildworld World build started on Thu Sep 20 00:31:07 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 [...] `chroot.o' is up to date. (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo bsdlabel.lo sconfig.lo fdisk.lo dhclient.lo head.lo mt.lo nc.lo sed.lo ! tail.lo tee.lo gzip.lo bzip2.lo xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/pc98.i386/src/rescue/rescue/../librescue/exec.o /obj/pc98.i386/src/rescue/rescue/../librescue/getusershell.o /obj/pc98.i386/src/rescue/rescue/../librescue/login_class.o /obj/pc98.i386/src/rescue/rescue/../librescue/popen.o /obj/pc98.i386/src/rescue/rescue/../librescue/rcmdsh.o /obj/pc98.i386/src/rescue/rescue/../librescue/sysctl.o /obj/pc98.i386/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo: In function `_$$hide$$ nc.lo main': (.text+0x2086): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo: In function `_$$hide$$ zfs.lo do_jail': _$$hide$$ zfs.lo zfs_main.c:(.text+0x1efb): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/pc98.i386/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 02:44:24 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 02:44:24 - ERROR: failed to build world TB --- 2012-09-20 02:44:24 - 6067.12 user 821.58 system 8064.09 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on amd64/amd64
TB --- 2012-09-20 00:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 00:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 00:30:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2012-09-20 00:30:00 - cleaning the object tree TB --- 2012-09-20 00:30:00 - cvsupping the source tree TB --- 2012-09-20 00:30:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile TB --- 2012-09-20 00:31:06 - building world TB --- 2012-09-20 00:31:06 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 00:31:06 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 00:31:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 00:31:06 - SRCCONF=/dev/null TB --- 2012-09-20 00:31:06 - TARGET=amd64 TB --- 2012-09-20 00:31:06 - TARGET_ARCH=amd64 TB --- 2012-09-20 00:31:06 - TZ=UTC TB --- 2012-09-20 00:31:06 - __MAKE_CONF=/dev/null TB --- 2012-09-20 00:31:06 - cd /src TB --- 2012-09-20 00:31:06 - /usr/bin/make -B buildworld World build started on Thu Sep 20 00:31:07 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 [...] `chroot.o' is up to date. (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo bsdlabel.lo fdisk.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo tee! .lo gzip.lo bzip2.lo xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/amd64.amd64/src/rescue/rescue/../librescue/exec.o /obj/amd64.amd64/src/rescue/rescue/../librescue/getusershell.o /obj/amd64.amd64/src/rescue/rescue/../librescue/login_class.o /obj/amd64.amd64/src/rescue/rescue/../librescue/popen.o /obj/amd64.amd64/src/rescue/rescue/../librescue/rcmdsh.o /obj/amd64.amd64/src/rescue/rescue/../librescue/sysctl.o /obj/amd64.amd64/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo: In function `main': socks.c:(.text+0x1d26): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo: In function `do_jail': zfs_main.c:(.text+0x1b55): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/amd64.amd64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 02:45:27 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 02:45:27 - ERROR: failed to build world TB --- 2012-09-20 02:45:27 - 6105.20 user 831.69 system 8126.12 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on i386/i386
TB --- 2012-09-20 00:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 00:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 00:30:00 - starting HEAD tinderbox run for i386/i386 TB --- 2012-09-20 00:30:00 - cleaning the object tree TB --- 2012-09-20 00:30:00 - cvsupping the source tree TB --- 2012-09-20 00:30:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2012-09-20 00:37:10 - building world TB --- 2012-09-20 00:37:10 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 00:37:10 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 00:37:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 00:37:10 - SRCCONF=/dev/null TB --- 2012-09-20 00:37:10 - TARGET=i386 TB --- 2012-09-20 00:37:10 - TARGET_ARCH=i386 TB --- 2012-09-20 00:37:10 - TZ=UTC TB --- 2012-09-20 00:37:10 - __MAKE_CONF=/dev/null TB --- 2012-09-20 00:37:10 - cd /src TB --- 2012-09-20 00:37:10 - /usr/bin/make -B buildworld World build started on Thu Sep 20 00:37:11 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 [...] `chroot.o' is up to date. (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo bsdlabel.lo sconfig.lo fdisk.lo dhclient.lo head.lo mt.lo nc.lo sed.lo ! tail.lo tee.lo gzip.lo bzip2.lo xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/i386.i386/src/rescue/rescue/../librescue/exec.o /obj/i386.i386/src/rescue/rescue/../librescue/getusershell.o /obj/i386.i386/src/rescue/rescue/../librescue/login_class.o /obj/i386.i386/src/rescue/rescue/../librescue/popen.o /obj/i386.i386/src/rescue/rescue/../librescue/rcmdsh.o /obj/i386.i386/src/rescue/rescue/../librescue/sysctl.o /obj/i386.i386/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo: In function `_$$hide$$ nc.lo main': (.text+0x2086): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo: In function `_$$hide$$ zfs.lo do_jail': _$$hide$$ zfs.lo zfs_main.c:(.text+0x1efb): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/i386.i386/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 02:49:20 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 02:49:20 - ERROR: failed to build world TB --- 2012-09-20 02:49:20 - 6073.02 user 814.87 system 8359.82 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on mips/mips
TB --- 2012-09-20 02:33:13 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 02:33:13 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 02:33:13 - starting HEAD tinderbox run for mips/mips TB --- 2012-09-20 02:33:13 - cleaning the object tree TB --- 2012-09-20 02:33:13 - cvsupping the source tree TB --- 2012-09-20 02:33:13 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2012-09-20 02:34:03 - building world TB --- 2012-09-20 02:34:03 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 02:34:03 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 02:34:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 02:34:03 - SRCCONF=/dev/null TB --- 2012-09-20 02:34:03 - TARGET=mips TB --- 2012-09-20 02:34:03 - TARGET_ARCH=mips TB --- 2012-09-20 02:34:03 - TZ=UTC TB --- 2012-09-20 02:34:03 - __MAKE_CONF=/dev/null TB --- 2012-09-20 02:34:03 - cd /src TB --- 2012-09-20 02:34:03 - /usr/bin/make -B buildworld World build started on Thu Sep 20 02:34:04 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 [...] `chroot.o' is up to date. (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo tee.lo gzip.lo bzip2.lo ! xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/mips.mips/src/rescue/rescue/../librescue/exec.o /obj/mips.mips/src/rescue/rescue/../librescue/getusershell.o /obj/mips.mips/src/rescue/rescue/../librescue/login_class.o /obj/mips.mips/src/rescue/rescue/../librescue/popen.o /obj/mips.mips/src/rescue/rescue/../librescue/rcmdsh.o /obj/mips.mips/src/rescue/rescue/../librescue/sysctl.o /obj/mips.mips/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo: In function `_$$hide$$ nc.lo main': (.text+0x228c): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo: In function `_$$hide$$ zfs.lo do_jail': _$$hide$$ zfs.lo zfs_main.c:(.text+0x2d94): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/mips.mips/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 03:26:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 03:26:30 - ERROR: failed to build world TB --- 2012-09-20 03:26:30 - 2142.23 user 477.09 system 3197.52 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on sparc64/sparc64
TB --- 2012-09-20 02:49:21 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 02:49:21 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 02:49:21 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2012-09-20 02:49:21 - cleaning the object tree TB --- 2012-09-20 02:49:21 - cvsupping the source tree TB --- 2012-09-20 02:49:21 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2012-09-20 02:50:13 - building world TB --- 2012-09-20 02:50:13 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 02:50:13 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 02:50:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 02:50:13 - SRCCONF=/dev/null TB --- 2012-09-20 02:50:13 - TARGET=sparc64 TB --- 2012-09-20 02:50:13 - TARGET_ARCH=sparc64 TB --- 2012-09-20 02:50:13 - TZ=UTC TB --- 2012-09-20 02:50:13 - __MAKE_CONF=/dev/null TB --- 2012-09-20 02:50:13 - cd /src TB --- 2012-09-20 02:50:13 - /usr/bin/make -B buildworld World build started on Thu Sep 20 02:50:14 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 [...] (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo bsdlabel.lo sunlabel.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo ! tee.lo gzip.lo bzip2.lo xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/sparc64.sparc64/src/rescue/rescue/../librescue/exec.o /obj/sparc64.sparc64/src/rescue/rescue/../librescue/getusershell.o /obj/sparc64.sparc64/src/rescue/rescue/../librescue/login_class.o /obj/sparc64.sparc64/src/rescue/rescue/../librescue/popen.o /obj/sparc64.sparc64/src/rescue/rescue/../librescue/rcmdsh.o /obj/sparc64.sparc64/src/rescue/rescue/../librescue/sysctl.o /obj/sparc64.sparc64/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo: In function `_$$hide$$ nc.lo main': (.text+0x218c): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo: In function `_$$hide$$ zfs.lo do_jail': _$$hide$$ zfs.lo zfs_main.c:(.text+0x2b98): undefined reference to `jail_getid' _$$hide$$ zfs.lo zfs_main.c:(.text+0x2c40): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/sparc64.sparc64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 03:45:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 03:45:18 - ERROR: failed to build world TB --- 2012-09-20 03:45:18 - 2446.84 user 470.77 system 3357.41 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on powerpc/powerpc
TB --- 2012-09-20 02:44:25 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 02:44:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 02:44:25 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-09-20 02:44:25 - cleaning the object tree TB --- 2012-09-20 02:44:25 - cvsupping the source tree TB --- 2012-09-20 02:44:25 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2012-09-20 02:45:24 - building world TB --- 2012-09-20 02:45:24 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 02:45:24 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 02:45:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 02:45:24 - SRCCONF=/dev/null TB --- 2012-09-20 02:45:24 - TARGET=powerpc TB --- 2012-09-20 02:45:24 - TARGET_ARCH=powerpc TB --- 2012-09-20 02:45:24 - TZ=UTC TB --- 2012-09-20 02:45:24 - __MAKE_CONF=/dev/null TB --- 2012-09-20 02:45:24 - cd /src TB --- 2012-09-20 02:45:24 - /usr/bin/make -B buildworld World build started on Thu Sep 20 02:45:26 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 [...] (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo tee.lo gzip.lo bzip2.lo ! xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/powerpc.powerpc/src/rescue/rescue/../librescue/exec.o /obj/powerpc.powerpc/src/rescue/rescue/../librescue/getusershell.o /obj/powerpc.powerpc/src/rescue/rescue/../librescue/login_class.o /obj/powerpc.powerpc/src/rescue/rescue/../librescue/popen.o /obj/powerpc.powerpc/src/rescue/rescue/../librescue/rcmdsh.o /obj/powerpc.powerpc/src/rescue/rescue/../librescue/sysctl.o /obj/powerpc.powerpc/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo: In function `_$$hide$$ nc.lo main': (.text+0x21d0): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo: In function `_$$hide$$ zfs.lo do_jail': _$$hide$$ zfs.lo zfs_main.c:(.text+0x239c): undefined reference to `jail_getid' _$$hide$$ zfs.lo zfs_main.c:(.text+0x2460): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/powerpc.powerpc/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 04:45:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 04:45:30 - ERROR: failed to build world TB --- 2012-09-20 04:45:30 - 6067.54 user 754.04 system 7265.67 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on powerpc64/powerpc
TB --- 2012-09-20 02:45:27 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 02:45:27 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 02:45:27 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2012-09-20 02:45:27 - cleaning the object tree TB --- 2012-09-20 02:45:27 - cvsupping the source tree TB --- 2012-09-20 02:45:27 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile TB --- 2012-09-20 02:46:28 - building world TB --- 2012-09-20 02:46:28 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 02:46:28 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 02:46:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 02:46:28 - SRCCONF=/dev/null TB --- 2012-09-20 02:46:28 - TARGET=powerpc TB --- 2012-09-20 02:46:28 - TARGET_ARCH=powerpc64 TB --- 2012-09-20 02:46:28 - TZ=UTC TB --- 2012-09-20 02:46:28 - __MAKE_CONF=/dev/null TB --- 2012-09-20 02:46:28 - cd /src TB --- 2012-09-20 02:46:28 - /usr/bin/make -B buildworld World build started on Thu Sep 20 02:46:28 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 [...] (cd /src/rescue/rescue/../../usr.sbin/chroot /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chroot/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chroot/ chroot.o) `chroot.o' is up to date. (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo tee.lo gzip.lo bzip2.lo ! xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/powerpc.powerpc64/src/rescue/rescue/../librescue/exec.o /obj/powerpc.powerpc64/src/rescue/rescue/../librescue/getusershell.o /obj/powerpc.powerpc64/src/rescue/rescue/../librescue/login_class.o /obj/powerpc.powerpc64/src/rescue/rescue/../librescue/popen.o /obj/powerpc.powerpc64/src/rescue/rescue/../librescue/rcmdsh.o /obj/powerpc.powerpc64/src/rescue/rescue/../librescue/sysctl.o /obj/powerpc.powerpc64/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo:(.text+0x22bc): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo:(.text+0x246c): undefined reference to `jail_getid' zfs.lo:(.text+0x254c): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/powerpc.powerpc64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 04:47:42 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 04:47:42 - ERROR: failed to build world TB --- 2012-09-20 04:47:42 - 6159.90 user 766.93 system 7334.80 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: MPSAFE VFS -- List of upcoming actions
On 19/09/2012 04:48, Attilio Rao wrote: On Fri, Jul 13, 2012 at 12:18 AM, Attilio Rao atti...@freebsd.org wrote: ... Alternatively, a kernel patch that should work with HEAD@240684 is here: http://www.freebsd.org/~attilio/fuse_import/fuse_240684.patch I guess the patch can easilly apply to all FreeBSD branches, really, but it is not tested to anything else different then -CURRENT. RELENG_9, fetched yesterday: === fuse (all) env CCACHE_PREFIX=/usr/local/bin/distcc /usr/local/bin/ccache cc -O2 -pipe -march=core2 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/HP6510b-9/amd64/usr/src/sys/HP6510b-9/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -I/usr/obj/HP6510b-9/amd64/usr/src/sys/HP6510b-9 -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -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 -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/src/sys/modules/fuse/../../fs/fuse/fuse_device.c env CCACHE_PREFIX=/usr/local/bin/distcc /usr/local/bin/ccache cc -O2 -pipe -march=core2 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/HP6510b-9/amd64/usr/src/sys/HP6510b-9/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -I/usr/obj/HP6510b-9/amd64/usr/src/sys/HP6510b-9 -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -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 -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/src/sys/modules/fuse/../../fs/fuse/fuse_node.c distcc[20814] ERROR: compile /root/.ccache/tmp/fuse_node.tmp.mobileKamikaze.norad.20806.i on localhost failed cc1: warnings being treated as errors /usr/src/sys/modules/fuse/../../fs/fuse/fuse_node.c: In function 'fuse_vnode_setsize': /usr/src/sys/modules/fuse/../../fs/fuse/fuse_node.c:378: warning: passing argument 3 of 'vtruncbuf' makes pointer from integer without a cast /usr/src/sys/modules/fuse/../../fs/fuse/fuse_node.c:378: error: too few arguments to function 'vtruncbuf' *** [fuse_node.o] Error code 1 1 error *** [all] Error code 2 1 error *** [modules-all] Error code 2 1 error *** [buildkernel] Error code 2 1 error *** [buildkernel] Error code 2 Stop in /usr/src. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on arm/arm
TB --- 2012-09-20 04:50:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-09-20 04:50:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-09-20 04:50:00 - starting HEAD tinderbox run for arm/arm TB --- 2012-09-20 04:50:00 - cleaning the object tree TB --- 2012-09-20 04:53:22 - cvsupping the source tree TB --- 2012-09-20 04:53:22 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2012-09-20 04:55:32 - building world TB --- 2012-09-20 04:55:32 - CROSS_BUILD_TESTING=YES TB --- 2012-09-20 04:55:32 - MAKEOBJDIRPREFIX=/obj TB --- 2012-09-20 04:55:32 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-09-20 04:55:32 - SRCCONF=/dev/null TB --- 2012-09-20 04:55:32 - TARGET=arm TB --- 2012-09-20 04:55:32 - TARGET_ARCH=arm TB --- 2012-09-20 04:55:32 - TZ=UTC TB --- 2012-09-20 04:55:32 - __MAKE_CONF=/dev/null TB --- 2012-09-20 04:55:32 - cd /src TB --- 2012-09-20 04:55:32 - /usr/bin/make -B buildworld World build started on Thu Sep 20 04:55:33 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 [...] `chroot.o' is up to date. (cd /src/rescue/rescue/../../usr.sbin/chown /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ depend /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chown/ chown.o) `chown.o' is up to date. cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo tee.lo gzip.lo bzip2.lo ! xz.lo tar.lo vi.lo id.lo chroot.lo chown.lo /obj/arm.arm/src/rescue/rescue/../librescue/exec.o /obj/arm.arm/src/rescue/rescue/../librescue/getusershell.o /obj/arm.arm/src/rescue/rescue/../librescue/login_class.o /obj/arm.arm/src/rescue/rescue/../librescue/popen.o /obj/arm.arm/src/rescue/rescue/../librescue/rcmdsh.o /obj/arm.arm/src/rescue/rescue/../librescue/sysctl.o /obj/arm.arm/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -ltermcap -lutil -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lavl -lzfs -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmd -lsbuf -lufs -lz -lbz2 -llzma -larchive -lcrypto -lm nc.lo: In function `_$$hide$$ nc.lo $a': _$$hide$$ nc.lo socks.c:(.text+0x18e0): warning: warning: mktemp() possibly used unsafely; consider using mkstemp() zfs.lo: In function `_$$hide$$ zfs.lo $a': _$$hide$$ zfs.lo zfs_iter.c:(.text+0x1e80): undefined reference to `jail_getid' *** Error code 1 Stop in /obj/arm.arm/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-09-20 05:48:42 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-09-20 05:48:42 - ERROR: failed to build world TB --- 2012-09-20 05:48:42 - 2031.13 user 491.52 system 3522.29 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
