Re: md2 on current and 10.
Am 09.01.2014 02:59, schrieb Mikhail T.: On 08.01.2014 20:05, Peter Wemm wrote: The path of least resistance is to make a libmd2 port. It's the only way I can see you getting to use it on 10.0. *I* don't really care. *I* don't use md2 myself. I became aware of the problem by accident -- because one of my ports was affected (tcl-trf). But I can fix the port, no huhu. It just seems to me, FreeBSD as a project goofed by abruptly removing the functions, that have been in the base for many years. But if the src-committers don't care to ungoof it -- despite my raising awareness as much (and, perhaps, even above) as permissible by politeness -- then so be it... Mikhail, There have been license concerns raised about the MD2 algorithm, and apparently it is FreeBSD policy to not burden our users with known/surprising license restrictions. It would also appear that this license policy would overrule compatibility with an old algorithm (MD2). You have _not_ responded to these license concerns, but _only_ argued with compatibility, and along the lines of user/maintainer convenience. The MD2 functionality can be offered through a port, where it is much easier to handle legal concerns. It may be inconvenient to a maintainer, and you may be disappointed or frustrated about a lack of a proper discontinual phase, but I see a port as the _only_ viable option. Making a port use libmd2, or OpenSSL-from-ports-built-with-MD2 should (1) satisfy compatibility and (2) base system licensing requirements, all at the same time. What is the reason why you don't find it acceptable to offer an option to build your affected tcl-trf port against a ports OpenSSL? Is there a technical concern beyond adding proper _DEPENDS lines? Is there a social concern beyond the maintainer's one-time work? Do we have a release note entry for MD2 removal? (I haven't checked.) If not, can we add it before 10.0-RELEASE given there is a -RC5 now? Cheers, Matthias ___ 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: interesting routing bug...
On 09.01.2014 05:18, John-Mark Gurney wrote: Well, I was trying to manually add a route for a host on the local network (I can explain why, but it doesn't matter) and I got this: Hello! There are several different kernel userland bugs :) # netstat -rnfinet Routing tables Internet: DestinationGatewayFlagsNetif Expire default192.168.0.14 UGS re0 127.0.0.1 link#3 UHlo0 192.168.0.0/24 link#1 U re0 192.168.0.21 link#1 UHS lo0 # route add -host 192.168.0.254 -interface re0 -link 04:4a:31:d3:95:dc add net 192.168.0.254: gateway re0 -link specifier assumes no parameter, so the next argument is treated as netmask (since dst/gw are already supplied). It is successfully parsed by getaddr() as AF_LINK sockaddr. I've added additional check which requires dst/mask address families to be equal (r260472). Historically, our kernel is a bit relaxed on checking validness for network masks: it does not check family does not perform usual (addrmask == addr) check. masked copy is performed instead. This is a bit tricky to fix since most in-kernel consumers are supplying non-masked address. I'm going to fix this soon. # netstat -rnfinet Routing tables Internet: DestinationGatewayFlagsNetif Expire 0.0.0.00x2050090:2b:34:ab:bb:85 USre0 Basically kernel treats sockaddr_dl as non-contiguos mask. default192.168.0.14 UGS re0 10.0.0.0/8 link#2 Umsk0 10.42.42.21link#2 UHS lo0 127.0.0.1 link#3 UHlo0 192.168.0.0/24 link#1 U re0 192.168.0.21 link#1 UHS lo0 # route delete 0.0.0.0 delete net 0.0.0.0 # route flush Our rtsock protocol does not provide rtable flush, so internally route(8) does route dump for given table and issues RTF_DELETE messages for every route. It seems that non-contiguous masks are handled incorrectly here.. :: localhost-fib 0 done :::0.0.0.0 localhost-fib 0 done fe80:: localhost-fib 0 done ff02:: localhost-fib 0 done # netstat -rnfinet Routing tables Internet: DestinationGatewayFlagsNetif Expire 0.0.0.00x2050090:2b:34:ab:bb:85 USre0 127.0.0.1 link#3 UHlo0 192.168.0.0/24 link#1 U re0 192.168.0.21 link#1 UHS lo0 So, as you can see, I have managed to add a bogus route w/o a way to remove it short of rebooting the box... And because of this route, You should be able to delete this using exactly the same command (s/add/del/). some hosts like svn0.us-west.freebsd.org will match causing the machine to try to find the ip on the local network. This route I assume should be rejected by the kernel and not added, or there is a mismatch between the route program and how the kernel understands it. I can provide more information upon request. Thanks. ___ 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
Intel graphics driver broken on 10-RC5
Hi I just tried a few variants on my 64 bit laptop with Intel HD4000 graphics. Ivy bridge I think (not haswell for sure).. 10.0-RC5 compiled from source [GENERIC kernel config on amd64 and i386] works with vesa but with Intel I can't even start X (this was possible a while ago on 10 alpha I think) CURRENT [amd64] seem to work fine with Intel driver so far. I have X + openbox + glxgears running. Attached with this mail is Xorg.log, dmesg and pkg info from 10.0-RC5 on amd64. All packages are installed with pkg install xxx Is it to expect that the Intel driver won't be usable in the final 10.0 release? Keep up the good work!! Best regards -- Johannes Lundberg -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. FreeBSD PC 10.0-RC5 FreeBSD 10.0-RC5 #0 r260461M: Thu Jan 9 15:29:40 JST 2014 root@PC:/usr/obj/usr/src-releng10/sys/GENERIC amd64 # pkg info appres-1.0.4 Program to list application's resources aspell-0.60.6.1_3 Spelling checker with better suggestion logic than ispell bitmap-1.0.7 Bitmap editor and converter utilities for X ca_root_nss-3.15.3.1 The root certificate bundle from the Mozilla Project cairo-1.10.2_7,2 Vector graphics library with cross-device output support compositeproto-0.4.2 Composite extension headers consolekit-0.4.3 Framework for defining and tracking users cups-client-1.5.4_1Common UNIX Printing System: Library cups damageproto-1.2.1 Damage extension headers dbus-1.6.12A message bus system for inter-application communication dbus-glib-0.100.2 GLib bindings for the D-BUS messaging system dejavu-2.34Bitstream Vera Fonts clone with a wider range of characters dmidecode-2.12 Tool for dumping DMI (SMBIOS) contents in human-readable format dmxproto-2.3.1 DMX extension headers dri-7.6.1_3,2 OpenGL hardware acceleration drivers for the DRI dri2proto-2.8 DRI2 prototype headers encodings-1.0.4_1,1X.Org Encoding fonts expat-2.1.0XML 1.0 parser written in C fixesproto-5.0 Fixes extension headers flac-1.3.0_1 Free lossless audio codec flite-1.4 A small run-time speech synthesis engine font-adobe-100dpi-1.0.3_1 X.Org Adobe 100dpi font font-adobe-75dpi-1.0.3_1 X.Org Adobe 75dpi font font-adobe-utopia-100dpi-1.0.4_1 X.Org Adobe Utopia 100dpi font font-adobe-utopia-75dpi-1.0.4_1 X.Org Adobe Utopia 75dpi font font-adobe-utopia-type1-1.0.4_1 X.Org Adobe Utopia Type1 font font-alias-1.0.3_1 X.Org Font aliases font-arabic-misc-1.0.3_1 X.Org miscellaneous Arabic fonts font-bh-100dpi-1.0.3_1 X.Org Bigelow Holmes 100dpi font font-bh-75dpi-1.0.3_1 X.Org Bigelow Holmes 75dpi font font-bh-lucidatypewriter-100dpi-1.0.3_1 X.Org Bigelow Holmes Lucida TypeWriter 100dpi font font-bh-lucidatypewriter-75dpi-1.0.3_1 X.Org Bigelow Holmes Lucida TypeWriter 75dpi font font-bh-ttf-1.0.3_1X.Org Bigelow Holmes TTF font font-bh-type1-1.0.3_1 X.Org Bigelow Holmes Type1 font font-bitstream-100dpi-1.0.3_1 X.Org Bitstream Vera 100dpi font font-bitstream-75dpi-1.0.3_1 X.Org Bitstream Vera 75dpi font font-bitstream-type1-1.0.3_1 X.Org Bitstream Vera Type1 font font-cronyx-cyrillic-1.0.3_1 X.Org Cronyx Cyrillic font font-cursor-misc-1.0.3_1 X.Org miscellaneous Cursor fonts font-daewoo-misc-1.0.3_1 X.Org miscellaneous Daewoo fonts font-dec-misc-1.0.3_1 X.Org miscellaneous Dec fonts font-ibm-type1-1.0.3_1 X.Org IBM Type1 font font-isas-misc-1.0.3_1 X.Org miscellaneous ISAS fonts font-jis-misc-1.0.3_1 X.Org miscellaneous JIS fonts font-micro-misc-1.0.3_1X.Org miscellaneous Micro fonts font-misc-cyrillic-1.0.3_1 X.Org miscellaneous Cyrillic font font-misc-ethiopic-1.0.3_1 X.Org miscellaneous Ethiopic font font-misc-meltho-1.0.3_1 X.Org miscellaneous Meltho font font-misc-misc-1.1.2_1 X.Org miscellaneous Misc fonts font-mutt-misc-1.0.3_1 X.Org miscellaneous Mutt fonts font-schumacher-misc-1.1.2_1 X.Org miscellaneous Schumacher fonts font-screen-cyrillic-1.0.4_1 X.Org Screen Cyrillic font font-sony-misc-1.0.3_1 X.Org miscellaneous Sony fonts font-sun-misc-1.0.3_1 X.Org miscellaneous Sun fonts font-util-1.3.0_1
Re: Install 10.0-RC3 on MacBookPro Late 2013
Huang's MBP: xhci0@pci0:0:20:0:class=0x0c0330 card=0x72708086 chip=0x8c318086 rev=0x05 hdr=0x00 seems to be different from my MBA. Is there any more information I can provide that can help us come closer to finding a solution? -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Wed, Jan 8, 2014 at 9:37 AM, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: Hi Hans Yeah I made sure I got the latest source that contained your latest commit. Sorry no patch at this moment. I've been busy with other things lately so I haven't worked on this for some time now but felt the urge to give it a try when it seemed to be OK on MBP.. Output from pciconf -lv xhci0@pci0:0:20:0: class=0x0c0330 card=0x72708086 chip=0x9c318086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point-LP USB xHCI HC' class = serial bus sublass = USB -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Tue, Jan 7, 2014 at 10:29 PM, Hans Petter Selasky h...@bitfrost.nowrote: On 01/07/14 14:22, Lundberg, Johannes wrote: Lucky you! I tried the latest src just now, made memstick on amd64 and ran on MBA2013 but no luck. Reverting xhci* to 243780 as I've done before made it pass the boot sequence and to the installer. Was hoping the same fix applied to Air as well:( Hi Johannes, Do you have a patch which fixes the problem instead of reverting? You are sure you tested the latest and greatest? Can you show pciconf -lv (only USB controllers) ? --HPS -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. ___ 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: Intel graphics driver broken on 10-RC5
Hi Johannes, Are you using the packaged Xorg in both cases? Currently, the default for 10 is the old (pre-KMS) X.org and the default for 11 (HEAD) is the newer (post-KMS) one. If you're using the default one, would you mind trying the new one? You can build it from ports by putting this in your make.conf: WITH_NEW_XORG=yes WITH_GALLIUM=yes I'm currently running it with AMD graphics on 10-RC4 and finding it works a lot better than the older version, and we're considering enabling it for the 10.0-RELEASE. The down side is that, without newcons, you lose working VTs after X has started. David On 9 Jan 2014, at 11:14, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: Hi I just tried a few variants on my 64 bit laptop with Intel HD4000 graphics. Ivy bridge I think (not haswell for sure).. 10.0-RC5 compiled from source [GENERIC kernel config on amd64 and i386] works with vesa but with Intel I can't even start X (this was possible a while ago on 10 alpha I think) CURRENT [amd64] seem to work fine with Intel driver so far. I have X + openbox + glxgears running. Attached with this mail is Xorg.log, dmesg and pkg info from 10.0-RC5 on amd64. All packages are installed with pkg install xxx Is it to expect that the Intel driver won't be usable in the final 10.0 release? Keep up the good work!! Best regards -- Johannes Lundberg -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. pkginfo.txtxorg.txtdmesg.txt___ 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: Intel graphics driver broken on 10-RC5
On Thu, 9 Jan 2014, David Chisnall wrote: Hi Johannes, Are you using the packaged Xorg in both cases? Currently, the default for 10 is the old (pre-KMS) X.org and the default for 11 (HEAD) is the newer (post-KMS) one. If you're using the default one, would you mind trying the new one? You can build it from ports by putting this in your make.conf: WITH_NEW_XORG=yes WITH_GALLIUM=yes I'm currently running it with AMD graphics on 10-RC4 and finding it works a lot better than the older version, and we're considering enabling it for the 10.0-RELEASE. The down side is that, without newcons, you lose working VTs after X has started. The wiki now has the update procedure: https://wiki.freebsd.org/Graphics#Installing_KMS_Ports This will work either to update an already-installed X, or to install it from scratch (just install x11/xorg afterwards). It has been tested on 9.2 and 10-STABLE. ___ 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 10-RC4: Got crash in igb driver
Dear, I experience some troubles with the igb device driver on FreeBSD 10-RC4. The kernel make a pagefault in the igb_tx_ctx_setup function when accessing to a IPv6 header. The network configuration is the following: - box acting as an IPv6 router - one interface with an IPv6 (igb0) - another interface with a vlan, and IPv6 on it (vlan0 on igb1) Vlan Hardware tagging is set on both interfaces. The packet that cause the crash come from igb0 and go to vlan0. After investigation, i see that the mbuf is split in two. The first one carry the ethernet header, the second, the IPv6 header and data payload. The split is due to the m_copy done in ip6_forward, that make the mbuf not writable and the M_PREPEND in ether_output that insert the new mbuf before the original one. The kernel crashes only if the newly allocated mbuf is at the end of a memory page, and no page is available after this one. So, it's extremly rare. I inserted a KASSERT into the function (see attached patch) to check this behavior, and it raises on every IPv6 forwarded packet to the vlan. The problem disapear if i remove hardware tagging. In the commit 256200, i see that pullups has been removed. May it be related ? Can you confirm the problem ? Best regards -- Alexandre Martins NETASQ -- We secure IT --- sys/dev/e1000/if_igb.c.orig 2014-01-09 16:33:39.0 +0100 +++ sys/dev/e1000/if_igb.c 2014-01-09 16:36:31.0 +0100 @@ -3883,6 +3883,7 @@ type_tucmd_mlhl |= E1000_ADVTXD_TUCMD_IPV4; break; case ETHERTYPE_IPV6: + KASSERT(ehdrlen + sizeof(struct ip6_hdr) = mp-m_len, (Ethernet and IPv6 header not contiguous)); ip6 = (struct ip6_hdr *)(mp-m_data + ehdrlen); ip_hlen = sizeof(struct ip6_hdr); /* XXX-BZ this will go badly in case of ext hdrs. */ smime.p7s Description: S/MIME cryptographic signature
FreeBSD 10.0-RC5 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The fifth RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. This is expected to be the final RC build of the 10.0-RELEASE cycle. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here (or any of the FreeBSD mirror sites): ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.0/ If you notice problems you can report them through the normal GNATS PR system or here on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the releng/10.0 branch. Important note to freebsd-update(8) users: Please be sure to follow the instructions in the following FreeBSD Errata Notices before upgrading the system to 10.0-RC5: . EN-13:04.freebsd-update: http://www.freebsd.org/security/advisories/FreeBSD-EN-13:04.freebsd-update.asc . EN-13:05.freebsd-update: http://www.freebsd.org/security/advisories/FreeBSD-EN-13:05.freebsd-update.asc Pre-installed virtual machine images for 10.0-RC5 are also available for amd64 and i386 architectures. The images are located under the 'snapshots' directory on FTP, here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-RC5/ The disk images are available in both QCOW2, VHD, and VMDK format. The image download size is approximately 135 MB, which decompress to a 20GB sparse image. The partition layout is: . 512k - freebsd-boot GPT partition type (bootfs GPT label) . 1GB - freebsd-swap GPT partition type (swapfs GPT label) . ~17GB - freebsd-ufs GPT partition type (rootfs GPT label) Changes between -RC4 and -RC5 include: o Fix an IPv4 multicast regression. o Fixes OpenSSL for CVE-2013-4353, CVE-2013-6449, CVE-2013-6450. o Revert a change to the kinfo_file structure to preserve ABI. o Fix a race condition which could prevent the file descriptor table from being properly updated. The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 10.0-RC5 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 9.x. Alternatively, the user can install misc/compat9x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 10.0-RC5 amd64: SHA256 (FreeBSD-10.0-RC5-amd64-bootonly.iso) = 82b3f486f921480ba8ffb14af2dc52e744fafd9cf319c569ec7e8d9e39617b70 SHA256 (FreeBSD-10.0-RC5-amd64-disc1.iso) = 9b9f00af75fcbdd3ffae8f8a29943a3c24223989d5088e36cd21b9fcaec06280 SHA256 (FreeBSD-10.0-RC5-amd64-dvd1.iso) = cc412b77d2449a75a11151a257537f30cc8acd2b53258815692532ef5640c25a SHA256 (FreeBSD-10.0-RC5-amd64-memstick.img) = 9a09c2b8abc2a6968f06a9e6624155dbd5b1ce0d38a8d687041fc6dd1222127d MD5 (FreeBSD-10.0-RC5-amd64-bootonly.iso) = 76031b20b5d8c433c3a9b4d36a0e27b2 MD5 (FreeBSD-10.0-RC5-amd64-disc1.iso) = 48ee98fe1fd97f93ec7b0ec6c091f3aa MD5 (FreeBSD-10.0-RC5-amd64-dvd1.iso) = b998bb2907462c79798eda737c4f669a MD5 (FreeBSD-10.0-RC5-amd64-memstick.img) = 2348590592b314205e39a2d289e38f2e o 10.0-RC5 i386: SHA256 (FreeBSD-10.0-RC5-i386-bootonly.iso) = a54645f14e23d0ee59b40bf9f74dbb57066e04c623505be2037bfac176297dd2 SHA256 (FreeBSD-10.0-RC5-i386-disc1.iso) = 387e77a8cc355d4c2d321b3b1a681d0a5fc926f8fc6c21c248ff6070a137c122 SHA256 (FreeBSD-10.0-RC5-i386-dvd1.iso) = 7236d2060f0067c8b2088f564069820e2e085e2654a8310cf4ac409075c24794 SHA256 (FreeBSD-10.0-RC5-i386-memstick.img) = 90358cd91572f40ac901f1cbd2281f2498124bf54e11bde1cf6e81f88825efd9 MD5 (FreeBSD-10.0-RC5-i386-bootonly.iso) = 341620be9e759acdfc31eafc76710055 MD5 (FreeBSD-10.0-RC5-i386-disc1.iso) = 634d4b075318639bd99bb104ae7074ee MD5 (FreeBSD-10.0-RC5-i386-dvd1.iso) = b3a4978405fda0eb9d04c4e73d50ec10 MD5 (FreeBSD-10.0-RC5-i386-memstick.img) = ab5a3f64ac068d8544d96d9afb872a91 o 10.0-RC5 ia64: SHA256 (FreeBSD-10.0-RC5-ia64-bootonly.iso) = d665d88b4c8127125843717847f0e34d6a990e618d33327969b7e2b421a80c68
Re: [Xen-devel] [PATCH v9 15/19] xen: create a Xen nexus to use in PV/PVH
On 07/01/14 15:27, Julien Grall wrote: On 01/07/2014 08:29 AM, Roger Pau Monné wrote: On 06/01/14 12:33, Julien Grall wrote: On 01/06/2014 09:35 AM, Roger Pau Monné wrote: On 05/01/14 22:55, Julien Grall wrote: On 01/02/2014 03:43 PM, Roger Pau Monne wrote: Introduce a Xen specific nexus that is going to be in charge for attaching Xen specific devices. Now that we have a xenpv bus, do we really need a specific nexus for Xen? We should be able to use the identify callback of xenpv to create the bus. The other part of this patch can be merged in the patch #14 Introduce xenpv bus and a dummy pvcpu device. On x86 at least we need the Xen specific nexus, or we will fall back to use the legacy nexus which is not what we really want. Oh right, in any case can we use the identify callback of xenpv to add the bus? AFAICT this kind of bus devices don't have a identify routine, and they are usually added manually from the specific nexus, see acpi or legacy. Could you add the device on ARM when you detect that you are running as a Xen guest, or in the generic ARM nexus if Xen is detected? Is there any reason to not add identify callback? If it's possible, I would like to avoid as much as possible #ifdef XENHVM in ARM code. Maybe the x86 world is really different from the ARM world in how nexus works, but I rather prefer to have a #ifdef XENHVM and a BUS_ADD_CHILD that attaches the xenpv bus in the generic ARM nexus rather than having something that completely diverges from what buses usually do in FreeBSD. It's going to be much more difficult to track in case of bugs, and it's not what people expects, but that's just my opinion. I can certainly add the identify routine if there's an agreement that it's the best way to deal with it. Roger. ___ 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: FreeBSD 10.0-RC5 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Glen Barber ha scritto: The fifth RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. I've upgraded one of my machine from 9.2 to 10.0-RC5 via freebsd-update, but it didn'seem to have worked (yes, I updated 9.2 to latest patch release before upgrading). After the first 'freebsd-update install' and rebooting: # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching metadata signature for 10.0-RC5 from update2.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 10.0-RC5-p0. # uname -a FreeBSD ripple.andxor.it 10.0-RC5 FreeBSD 10.0-RC5 #0 r260430: Wed Jan 8 05:10:04 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # cc -v Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070831 patched [FreeBSD] - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlLO1ZAACgkQgRXp2M5fVU1GiACfQZbNc3DUg4BZD55r3ljoqyLa JrYAoO3gmOtAkkf1l4NQRmcwfXI/OfLw =nRva -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC5 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Dupre ha scritto: # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. Ok, please ignore my message. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlLO1eIACgkQgRXp2M5fVU3hIgCfWuYq3ZgTiXP8IXnM2idTQZSk XBgAoJY8TKTlijXyWpz117YZu5metAju =8SvU -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Mouse Not Working
Hey All, Stupid bug report. I just updated my source tree today. Last update was 03 Jan 2014. Sometime between then and now was a commit that killed my mouse in Xorg. My Xorg was configured to use hald/dbus (and I'll be testing switching over to devd soon). I'm not sure which commit broke the mouse. I've tested on two different systems with three different mice. Relevant lines from Xorg.0.log: [33.824] (**) Option Device /dev/ums0 [33.824] (==) USB Optical Mouse: Protocol: Auto [33.824] (**) USB Optical Mouse: always reports core events [33.824] (EE) xf86OpenSerial: Cannot open device /dev/ums0 Device busy. [33.824] (EE) USB Optical Mouse: cannot open input device [33.824] (EE) PreInit returned 2 for USB Optical Mouse [33.824] (II) UnloadModule: mouse [33.824] (EE) config/hal: NewInputDeviceRequest failed (2) Thanks, Shawn ___ 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: Mouse Not Working
On Thu, Jan 9, 2014 at 12:09 PM, Shawn Webb latt...@gmail.com wrote: Hey All, Stupid bug report. I just updated my source tree today. Last update was 03 Jan 2014. Sometime between then and now was a commit that killed my mouse in Xorg. My Xorg was configured to use hald/dbus (and I'll be testing switching over to devd soon). I'm not sure which commit broke the mouse. I've tested on two different systems with three different mice. Relevant lines from Xorg.0.log: [33.824] (**) Option Device /dev/ums0 [33.824] (==) USB Optical Mouse: Protocol: Auto [33.824] (**) USB Optical Mouse: always reports core events [33.824] (EE) xf86OpenSerial: Cannot open device /dev/ums0 Device busy. [33.824] (EE) USB Optical Mouse: cannot open input device [33.824] (EE) PreInit returned 2 for USB Optical Mouse [33.824] (II) UnloadModule: mouse [33.824] (EE) config/hal: NewInputDeviceRequest failed (2) Thanks, Shawn Solved off-list. I had to rebuild hald. ___ 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: interesting routing bug...
Alexander V. Chernikov wrote this message on Thu, Jan 09, 2014 at 15:04 +0400: On 09.01.2014 05:18, John-Mark Gurney wrote: Well, I was trying to manually add a route for a host on the local network (I can explain why, but it doesn't matter) and I got this: Hello! There are several different kernel userland bugs :) # netstat -rnfinet Routing tables Internet: DestinationGatewayFlagsNetif Expire default192.168.0.14 UGS re0 127.0.0.1 link#3 UHlo0 192.168.0.0/24 link#1 U re0 192.168.0.21 link#1 UHS lo0 # route add -host 192.168.0.254 -interface re0 -link 04:4a:31:d3:95:dc add net 192.168.0.254: gateway re0 -link specifier assumes no parameter, so the next argument is treated as netmask (since dst/gw are already supplied). Ahh, now I understand the following: The optional modifiers -xns, -osi, -atalk, and -link specify that all subsequent addresses are in the XNS, OSI, or AppleTalk address families, or are specified as link-level addresses, and the names must be numeric specifications rather than symbolic names. From what you state above, it appears you're saying that -interface re0 becomes the gateway, but the man page isn't clear about that... In the above command, I assume that the -interface is being interpeted as the gateway. If the destination is directly reachable via an interface requiring no intermediary system to act as a gateway, the -interface modifier should be specified; the gateway given is the address of this host on the common network, indicating the interface to be used for transmission. Alter- nately, if the interface is point to point the name of the interface itself may be given, in which case the route remains valid even if the local or remote addresses change. Because I didn't give it a common address (I assume IP) and I didn't give it a PTP interface. Maybe something like: ... the -interface modifier should be specified. If the specified gateway is an address on this host, use the interface that the address is on. If the gateway is the name of the interface then the route remains valid even if the local address changes. This way it will be more clear that -interface is a modifier for the gateway argument instead of still requiring you to specify a gateway in addition to the -interface. Part of my confusion was that the gateway returned was a mac address... I assumed it was bogus junk, but it turns out that it's the mac address of my local interface instead of link#1 or the mac address of the destination system like it was on 9.x and before. It is successfully parsed by getaddr() as AF_LINK sockaddr. I've added additional check which requires dst/mask address families to be equal (r260472). Thanks. Historically, our kernel is a bit relaxed on checking validness for network masks: it does not check family does not perform usual (addrmask == addr) check. masked copy is performed instead. This is a bit tricky to fix since most in-kernel consumers are supplying non-masked address. I'm going to fix this soon. # netstat -rnfinet Routing tables Internet: DestinationGatewayFlagsNetif Expire 0.0.0.00x2050090:2b:34:ab:bb:85 USre0 Basically kernel treats sockaddr_dl as non-contiguos mask. default192.168.0.14 UGS re0 10.0.0.0/8 link#2 Umsk0 10.42.42.21link#2 UHS lo0 127.0.0.1 link#3 UHlo0 192.168.0.0/24 link#1 U re0 192.168.0.21 link#1 UHS lo0 # route delete 0.0.0.0 delete net 0.0.0.0 # route flush Our rtsock protocol does not provide rtable flush, so internally route(8) does route dump for given table and issues RTF_DELETE messages for every route. It seems that non-contiguous masks are handled incorrectly here.. Ok, thanks for pointers on where to look. The above did solve my problem in that I just needed to leave off the -link xxx arg, and I was able to do what I wanted to... -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ 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: [Xen-devel] [PATCH v9 15/19] xen: create a Xen nexus to use in PV/PVH
On 01/09/14 11:30, Roger Pau Monné wrote: On 07/01/14 15:27, Julien Grall wrote: On 01/07/2014 08:29 AM, Roger Pau Monné wrote: On 06/01/14 12:33, Julien Grall wrote: On 01/06/2014 09:35 AM, Roger Pau Monné wrote: On 05/01/14 22:55, Julien Grall wrote: On 01/02/2014 03:43 PM, Roger Pau Monne wrote: Introduce a Xen specific nexus that is going to be in charge for attaching Xen specific devices. Now that we have a xenpv bus, do we really need a specific nexus for Xen? We should be able to use the identify callback of xenpv to create the bus. The other part of this patch can be merged in the patch #14 Introduce xenpv bus and a dummy pvcpu device. On x86 at least we need the Xen specific nexus, or we will fall back to use the legacy nexus which is not what we really want. Oh right, in any case can we use the identify callback of xenpv to add the bus? AFAICT this kind of bus devices don't have a identify routine, and they are usually added manually from the specific nexus, see acpi or legacy. Could you add the device on ARM when you detect that you are running as a Xen guest, or in the generic ARM nexus if Xen is detected? Is there any reason to not add identify callback? If it's possible, I would like to avoid as much as possible #ifdef XENHVM in ARM code. Maybe the x86 world is really different from the ARM world in how nexus works, but I rather prefer to have a #ifdef XENHVM and a BUS_ADD_CHILD that attaches the xenpv bus in the generic ARM nexus rather than having something that completely diverges from what buses usually do in FreeBSD. It's going to be much more difficult to track in case of bugs, and it's not what people expects, but that's just my opinion. I can certainly add the identify routine if there's an agreement that it's the best way to deal with it. Roger. ___ 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 Attaching sub-devices to nexus using device_identify() is the usual way to do this kind of thing. Note that if you do this, your device_probe() routine should return BUS_PROBE_NOWILDCARD to deal with platforms (ARM, MIPS, PowerPC, sparc64) with real autoconfigured devices hanging directly from nexus. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
unused in_cksum_update() ?
a lot of arch-specific headers (sys/${ARCH}/include/in_cksum.h)
have a lengthy definition for
in_cksum_update(struct ip *ip)
which seems completely unused in our source tree.
Time to remove it perhaps ?
grep cannot find any use at least since stable/8
cheers
luigi
___
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 --- 2014-01-09 17:30:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 17:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-01-09 17:30:19 - starting HEAD tinderbox run for arm/arm TB --- 2014-01-09 17:30:19 - cleaning the object tree TB --- 2014-01-09 17:30:19 - /usr/local/bin/svn stat /src TB --- 2014-01-09 17:30:24 - At svn revision 260487 TB --- 2014-01-09 17:30:25 - building world TB --- 2014-01-09 17:30:25 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 17:30:25 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 17:30:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 17:30:25 - SRCCONF=/dev/null TB --- 2014-01-09 17:30:25 - TARGET=arm TB --- 2014-01-09 17:30:25 - TARGET_ARCH=arm TB --- 2014-01-09 17:30:25 - TZ=UTC TB --- 2014-01-09 17:30:25 - __MAKE_CONF=/dev/null TB --- 2014-01-09 17:30:25 - cd /src TB --- 2014-01-09 17:30:25 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 17:30:34 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:234:4: error: use of undeclared identifier 'mfcp'; did you mean 'mfc'? mfcp = mfc.mf6c_next; ^~~~ mfc /src/usr.bin/netstat/mroute6.c:121:14: note: 'mfc' declared here struct mf6c mfc; ^ 16 errors generated. *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 20:22:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 20:22:53 - ERROR: failed to build world TB --- 2014-01-09 20:22:53 - 8324.73 user 1506.38 system 10353.82 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-arm-arm.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on armv6/arm
TB --- 2014-01-09 17:30:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 17:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-01-09 17:30:19 - starting HEAD tinderbox run for armv6/arm TB --- 2014-01-09 17:30:19 - cleaning the object tree TB --- 2014-01-09 17:30:19 - /usr/local/bin/svn stat /src TB --- 2014-01-09 17:30:24 - At svn revision 260487 TB --- 2014-01-09 17:30:25 - building world TB --- 2014-01-09 17:30:25 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 17:30:25 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 17:30:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 17:30:25 - SRCCONF=/dev/null TB --- 2014-01-09 17:30:25 - TARGET=arm TB --- 2014-01-09 17:30:25 - TARGET_ARCH=armv6 TB --- 2014-01-09 17:30:25 - TZ=UTC TB --- 2014-01-09 17:30:25 - __MAKE_CONF=/dev/null TB --- 2014-01-09 17:30:25 - cd /src TB --- 2014-01-09 17:30:25 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 17:30:34 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:234:4: error: use of undeclared identifier 'mfcp'; did you mean 'mfc'? mfcp = mfc.mf6c_next; ^~~~ mfc /src/usr.bin/netstat/mroute6.c:121:14: note: 'mfc' declared here struct mf6c mfc; ^ 16 errors generated. *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 20:22:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 20:22:53 - ERROR: failed to build world TB --- 2014-01-09 20:22:53 - 8328.09 user 1505.75 system 10353.83 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-armv6-arm.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on i386/i386
TB --- 2014-01-09 17:30:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 17:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-01-09 17:30:19 - starting HEAD tinderbox run for i386/i386 TB --- 2014-01-09 17:30:19 - cleaning the object tree TB --- 2014-01-09 17:30:19 - /usr/local/bin/svn stat /src TB --- 2014-01-09 17:30:24 - At svn revision 260487 TB --- 2014-01-09 17:30:25 - building world TB --- 2014-01-09 17:30:25 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 17:30:25 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 17:30:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 17:30:25 - SRCCONF=/dev/null TB --- 2014-01-09 17:30:25 - TARGET=i386 TB --- 2014-01-09 17:30:25 - TARGET_ARCH=i386 TB --- 2014-01-09 17:30:25 - TZ=UTC TB --- 2014-01-09 17:30:25 - __MAKE_CONF=/dev/null TB --- 2014-01-09 17:30:25 - cd /src TB --- 2014-01-09 17:30:25 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 17:30:34 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:234:4: error: use of undeclared identifier 'mfcp'; did you mean 'mfc'? mfcp = mfc.mf6c_next; ^~~~ mfc /src/usr.bin/netstat/mroute6.c:121:14: note: 'mfc' declared here struct mf6c mfc; ^ 16 errors generated. *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 20:31:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 20:31:18 - ERROR: failed to build world TB --- 2014-01-09 20:31:18 - 8917.85 user 1473.61 system 10858.22 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-i386.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on amd64/amd64
TB --- 2014-01-09 17:30:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 17:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-01-09 17:30:19 - starting HEAD tinderbox run for amd64/amd64 TB --- 2014-01-09 17:30:19 - cleaning the object tree TB --- 2014-01-09 17:30:19 - /usr/local/bin/svn stat /src TB --- 2014-01-09 17:30:24 - At svn revision 260487 TB --- 2014-01-09 17:30:25 - building world TB --- 2014-01-09 17:30:25 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 17:30:25 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 17:30:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 17:30:25 - SRCCONF=/dev/null TB --- 2014-01-09 17:30:25 - TARGET=amd64 TB --- 2014-01-09 17:30:25 - TARGET_ARCH=amd64 TB --- 2014-01-09 17:30:25 - TZ=UTC TB --- 2014-01-09 17:30:25 - __MAKE_CONF=/dev/null TB --- 2014-01-09 17:30:25 - cd /src TB --- 2014-01-09 17:30:25 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 17:30:34 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:234:4: error: use of undeclared identifier 'mfcp'; did you mean 'mfc'? mfcp = mfc.mf6c_next; ^~~~ mfc /src/usr.bin/netstat/mroute6.c:121:14: note: 'mfc' declared here struct mf6c mfc; ^ 16 errors generated. *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 20:31:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 20:31:30 - ERROR: failed to build world TB --- 2014-01-09 20:31:30 - 8924.77 user 1475.62 system 10870.43 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-amd64-amd64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on mips/mips
TB --- 2014-01-09 20:31:18 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 20:31:18 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-01-09 20:31:18 - starting HEAD tinderbox run for mips/mips TB --- 2014-01-09 20:31:18 - cleaning the object tree TB --- 2014-01-09 20:31:18 - /usr/local/bin/svn stat /src TB --- 2014-01-09 20:31:22 - At svn revision 260487 TB --- 2014-01-09 20:31:23 - building world TB --- 2014-01-09 20:31:23 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 20:31:23 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 20:31:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 20:31:23 - SRCCONF=/dev/null TB --- 2014-01-09 20:31:23 - TARGET=mips TB --- 2014-01-09 20:31:23 - TARGET_ARCH=mips TB --- 2014-01-09 20:31:23 - TZ=UTC TB --- 2014-01-09 20:31:23 - __MAKE_CONF=/dev/null TB --- 2014-01-09 20:31:23 - cd /src TB --- 2014-01-09 20:31:23 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 20:31:30 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:179: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:180: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:224: error: 'MF6C_INCOMPLETE_PARENT' undeclared (first use in this function) cc1: warnings being treated as errors /src/usr.bin/netstat/mroute6.c:122: warning: unused variable 'rte' /src/usr.bin/netstat/mroute6.c:121: warning: unused variable 'mfc' /src/usr.bin/netstat/mroute6.c:120: warning: unused variable 'mif6table' /src/usr.bin/netstat/mroute6.c:119: warning: unused variable 'mf6ctable' *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 21:25:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 21:25:39 - ERROR: failed to build world TB --- 2014-01-09 21:25:39 - 2370.88 user 541.47 system 3261.27 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-mips-mips.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on mips64/mips
TB --- 2014-01-09 20:31:30 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 20:31:30 - 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 --- 2014-01-09 20:31:30 - starting HEAD tinderbox run for mips64/mips TB --- 2014-01-09 20:31:30 - cleaning the object tree TB --- 2014-01-09 20:31:30 - /usr/local/bin/svn stat /src TB --- 2014-01-09 20:31:33 - At svn revision 260487 TB --- 2014-01-09 20:31:34 - building world TB --- 2014-01-09 20:31:34 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 20:31:34 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 20:31:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 20:31:34 - SRCCONF=/dev/null TB --- 2014-01-09 20:31:34 - TARGET=mips TB --- 2014-01-09 20:31:34 - TARGET_ARCH=mips64 TB --- 2014-01-09 20:31:34 - TZ=UTC TB --- 2014-01-09 20:31:34 - __MAKE_CONF=/dev/null TB --- 2014-01-09 20:31:34 - cd /src TB --- 2014-01-09 20:31:34 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 20:31:41 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:179: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:180: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:224: error: 'MF6C_INCOMPLETE_PARENT' undeclared (first use in this function) cc1: warnings being treated as errors /src/usr.bin/netstat/mroute6.c:122: warning: unused variable 'rte' /src/usr.bin/netstat/mroute6.c:121: warning: unused variable 'mfc' /src/usr.bin/netstat/mroute6.c:120: warning: unused variable 'mif6table' /src/usr.bin/netstat/mroute6.c:119: warning: unused variable 'mf6ctable' *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 21:25:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 21:25:39 - ERROR: failed to build world TB --- 2014-01-09 21:25:39 - 2375.84 user 543.84 system 3249.05 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-mips64-mips.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: unused in_cksum_update() ?
It's likely used elsewhere; it's the kind of thing you abuse when
doing header rewriting and reinjection. So, what's the NAT and such
code using?
-a
On 9 January 2014 11:21, Luigi Rizzo ri...@iet.unipi.it wrote:
a lot of arch-specific headers (sys/${ARCH}/include/in_cksum.h)
have a lengthy definition for
in_cksum_update(struct ip *ip)
which seems completely unused in our source tree.
Time to remove it perhaps ?
grep cannot find any use at least since stable/8
cheers
luigi
___
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
lldb build failure: undefined reference to `vtable for lldb_private::TypeFormatImpl_Format'
Ed and -current: I followed the instructions on the wiki for building lldb (r198872) on 9.1-RELEASE amd64. I'm using clang in the base system (3.1). I get this failure: [1/2] Linking CXX executable bin/lldb-3.5 [...snip...] lib/liblldb.so.3.5: undefined reference to `vtable for lldb_private::TypeFormatImpl_Format' lib/liblldb.so.3.5: undefined reference to `vtable for lldb_private::TypeFormatImpl_EnumType' The complete output is below. Any ideas? What other info can I provide? Thanks, Eric On 12/17/2013 16:15, Ed Maste wrote: The in-tree snapshot of LLDB is at a point where it's usable and suitable for wider testing on amd64, and so I intend to enable it by default in the near future. Further information on the FreeBSD port of LLDB is on the wiki, at https://wiki.freebsd.org/lldb On my desktop LLDB added about 5 minutes to a buildworld and 80MB to objdir (over a baseline of about an hour and 1.8GB). If you wish to avoid building it, you can add 'WITHOUT_LLDB=' to src.conf. -Ed ___ 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 $ ninja lldb [1/2] Linking CXX executable bin/lldb-3.5 FAILED: : /usr/bin/clang++ -std=c++11 -stdlib=libc++ -I/usr/local/include/python2.7 -g -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -fcolor-diagnostics -fno-rtti tools/lldb/tools/driver/CMakeFiles/lldb.dir/Driver.cpp.o tools/lldb/tools/driver/CMakeFiles/lldb.dir/IOChannel.cpp.o tools/lldb/tools/driver/CMakeFiles/lldb.dir/ELWrapper.cpp.o tools/lldb/tools/driver/CMakeFiles/lldb.dir/Platform.cpp.o tools/lldb/tools/driver/CMakeFiles/lldb.dir/GetOptWrapper.cpp.o -o bin/lldb-3.5 -L/usr/local/lib lib/liblldb.so.3.5 -Wl,--start-group lib/liblldbAPI.a lib/liblldbBreakpoint.a lib/liblldbCommands.a lib/liblldbDataFormatters.a lib/liblldbHostCommon.a lib/liblldbCore.a lib/liblldbExpression.a lib/liblldbInterpreter.a lib/liblldbSymbol.a lib/liblldbTarget.a lib/liblldbUtility.a lib/liblldbPluginDisassemblerLLVM.a lib/liblldbPluginSymbolFileDWARF.a lib/liblldbPluginSymbolFileSymtab.a lib/liblldbPluginDynamicLoaderStatic.a lib/liblldbPluginDynamicLoaderPosixDYLD.a lib/liblldbPluginObjectFileMachO.a lib/liblldbPluginObjectFileELF.a lib/liblldbPluginSymbolVendorELF.a lib/liblldbPluginObjectContainerBSDArchive.a lib/liblldbPluginObjectContainerMachOArchive.a lib/liblldbPluginProcessGDBRemote.a lib/liblldbPluginProcessMachCore.a lib/liblldbPluginProcessUtility.a lib/liblldbPluginPlatformGDB.a lib/liblldbPluginPlatformFreeBSD.a lib/liblldbPluginPlatformLinux.a lib/liblldbPluginPlatformPOSIX.a lib/liblldbPluginPlatformWindows.a lib/liblldbPluginPlatformMacOSX.a lib/liblldbPluginDynamicLoaderMacOSXDYLD.a lib/liblldbPluginUnwindAssemblyInstEmulation.a lib/liblldbPluginUnwindAssemblyX86.a lib/liblldbPluginAppleObjCRuntime.a lib/liblldbPluginCXXItaniumABI.a lib/liblldbPluginABIMacOSX_arm.a lib/liblldbPluginABIMacOSX_i386.a lib/liblldbPluginABISysV_x86_64.a lib/liblldbPluginInstructionARM.a lib/liblldbPluginObjectFilePECOFF.a lib/liblldbPluginOSPython.a lib/liblldbHostFreeBSD.a lib/liblldbPluginProcessFreeBSD.a lib/liblldbPluginProcessPOSIX.a lib/liblldbPluginProcessElfCore.a -Wl,--end-group lib/libclangCodeGen.a lib/libLLVMIRReader.a lib/libLLVMInstrumentation.a lib/libLLVMLinker.a lib/libLLVMObjCARCOpts.a lib/libclangRewriteFrontend.a lib/libclangFrontend.a lib/libclangDriver.a lib/libclangParse.a lib/libclangRewriteCore.a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangEdit.a lib/libclangAST.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMAArch64CodeGen.a lib/libLLVMAArch64AsmParser.a lib/libLLVMAArch64Disassembler.a lib/libLLVMARMCodeGen.a lib/libLLVMARMAsmParser.a lib/libLLVMARMDisassembler.a lib/libLLVMCppBackendCodeGen.a lib/libLLVMHexagonCodeGen.a lib/libLLVMMipsCodeGen.a lib/libLLVMMipsAsmParser.a lib/libLLVMMipsDisassembler.a lib/libLLVMMSP430CodeGen.a lib/libLLVMNVPTXCodeGen.a lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMR600CodeGen.a lib/libLLVMSparcCodeGen.a lib/libLLVMSparcAsmParser.a lib/libLLVMSparcDisassembler.a lib/libLLVMSystemZCodeGen.a lib/libLLVMSystemZAsmParser.a lib/libLLVMSystemZDisassembler.a lib/libLLVMX86AsmParser.a lib/libLLVMX86Disassembler.a lib/libLLVMXCoreCodeGen.a lib/libLLVMXCoreDisassembler.a lib/libLLVMJIT.a lib/libLLVMInterpreter.a lib/libLLVMX86CodeGen.a lib/libLLVMAsmParser.a lib/libLLVMBitWriter.a lib/libLLVMipo.a lib/libLLVMBitReader.a lib/libLLVMMCJIT.a lib/libLLVMMCDisassembler.a lib/libLLVMOption.a lib/libLLVMAArch64Desc.a lib/libLLVMARMDesc.a lib/libLLVMCppBackendInfo.a lib/libLLVMHexagonAsmPrinter.a lib/libLLVMMipsDesc.a lib/libLLVMMSP430Desc.a lib/libLLVMNVPTXDesc.a
Re: unused in_cksum_update() ?
On Thu, Jan 09, 2014 at 01:27:52PM -0800, Adrian Chadd wrote: It's likely used elsewhere; it's the kind of thing you abuse when doing header rewriting and reinjection. So, what's the NAT and such code using? natd/libalias has its own code with a DifferentialChecksum() function in sys/netinet/libalias/alias_util.c which adds and subtracts the chunks in the old and new packet. ip_fastfwd.c does it inline: /* * Decrement the TTL and incrementally change the IP header checksum. * Don't bother doing this with hw checksum offloading, it's faster * doing it right here. */ ip-ip_ttl -= IPTTLDEC; if (ip-ip_sum = (u_int16_t) ~htons(IPTTLDEC 8)) ip-ip_sum -= ~htons(IPTTLDEC 8); else ip-ip_sum += htons(IPTTLDEC 8); ip_forward() relies on the recomputation done in ip_output(). And there is no trace of in_cksum_update() in the entire source tree apart from its definition. cheers luigi ___ 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 --- 2014-01-09 20:22:54 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 20:22:54 - 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 --- 2014-01-09 20:22:54 - starting HEAD tinderbox run for ia64/ia64 TB --- 2014-01-09 20:22:54 - cleaning the object tree TB --- 2014-01-09 20:22:54 - /usr/local/bin/svn stat /src TB --- 2014-01-09 20:23:03 - At svn revision 260487 TB --- 2014-01-09 20:23:04 - building world TB --- 2014-01-09 20:23:04 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 20:23:04 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 20:23:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 20:23:04 - SRCCONF=/dev/null TB --- 2014-01-09 20:23:04 - TARGET=ia64 TB --- 2014-01-09 20:23:04 - TARGET_ARCH=ia64 TB --- 2014-01-09 20:23:04 - TZ=UTC TB --- 2014-01-09 20:23:04 - __MAKE_CONF=/dev/null TB --- 2014-01-09 20:23:04 - cd /src TB --- 2014-01-09 20:23:04 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 20:23:12 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:179: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:180: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:224: error: 'MF6C_INCOMPLETE_PARENT' undeclared (first use in this function) cc1: warnings being treated as errors /src/usr.bin/netstat/mroute6.c:122: warning: unused variable 'rte' /src/usr.bin/netstat/mroute6.c:121: warning: unused variable 'mfc' /src/usr.bin/netstat/mroute6.c:120: warning: unused variable 'mif6table' /src/usr.bin/netstat/mroute6.c:119: warning: unused variable 'mf6ctable' *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 21:41:50 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 21:41:50 - ERROR: failed to build world TB --- 2014-01-09 21:41:50 - 3753.49 user 642.99 system 4736.45 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-ia64-ia64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on sparc64/sparc64
TB --- 2014-01-09 21:41:50 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 21:41:50 - 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 --- 2014-01-09 21:41:50 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2014-01-09 21:41:50 - cleaning the object tree TB --- 2014-01-09 21:41:50 - /usr/local/bin/svn stat /src TB --- 2014-01-09 21:41:54 - At svn revision 260487 TB --- 2014-01-09 21:41:55 - building world TB --- 2014-01-09 21:41:55 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 21:41:55 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 21:41:55 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 21:41:55 - SRCCONF=/dev/null TB --- 2014-01-09 21:41:55 - TARGET=sparc64 TB --- 2014-01-09 21:41:55 - TARGET_ARCH=sparc64 TB --- 2014-01-09 21:41:55 - TZ=UTC TB --- 2014-01-09 21:41:55 - __MAKE_CONF=/dev/null TB --- 2014-01-09 21:41:55 - cd /src TB --- 2014-01-09 21:41:55 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 21:42:02 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:179: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:180: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:224: error: 'MF6C_INCOMPLETE_PARENT' undeclared (first use in this function) cc1: warnings being treated as errors /src/usr.bin/netstat/mroute6.c:122: warning: unused variable 'rte' /src/usr.bin/netstat/mroute6.c:121: warning: unused variable 'mfc' /src/usr.bin/netstat/mroute6.c:120: warning: unused variable 'mif6table' /src/usr.bin/netstat/mroute6.c:119: warning: unused variable 'mf6ctable' *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 22:41:36 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 22:41:36 - ERROR: failed to build world TB --- 2014-01-09 22:41:36 - 2731.84 user 534.55 system 3585.67 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-sparc64-sparc64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on i386/pc98
TB --- 2014-01-09 20:22:54 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 20:22:54 - 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 --- 2014-01-09 20:22:54 - starting HEAD tinderbox run for i386/pc98 TB --- 2014-01-09 20:22:54 - cleaning the object tree TB --- 2014-01-09 20:22:54 - /usr/local/bin/svn stat /src TB --- 2014-01-09 20:23:03 - At svn revision 260487 TB --- 2014-01-09 20:23:04 - building world TB --- 2014-01-09 20:23:04 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 20:23:04 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 20:23:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 20:23:04 - SRCCONF=/dev/null TB --- 2014-01-09 20:23:04 - TARGET=pc98 TB --- 2014-01-09 20:23:04 - TARGET_ARCH=i386 TB --- 2014-01-09 20:23:04 - TZ=UTC TB --- 2014-01-09 20:23:04 - __MAKE_CONF=/dev/null TB --- 2014-01-09 20:23:04 - cd /src TB --- 2014-01-09 20:23:04 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 20:23:12 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:234:4: error: use of undeclared identifier 'mfcp'; did you mean 'mfc'? mfcp = mfc.mf6c_next; ^~~~ mfc /src/usr.bin/netstat/mroute6.c:121:14: note: 'mfc' declared here struct mf6c mfc; ^ 16 errors generated. *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 23:28:36 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 23:28:36 - ERROR: failed to build world TB --- 2014-01-09 23:28:36 - 9407.55 user 1164.82 system 11142.53 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-pc98.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on powerpc/powerpc
TB --- 2014-01-09 21:25:40 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 21:25:40 - 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 --- 2014-01-09 21:25:40 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2014-01-09 21:25:40 - cleaning the object tree TB --- 2014-01-09 21:25:40 - /usr/local/bin/svn stat /src TB --- 2014-01-09 21:25:44 - At svn revision 260487 TB --- 2014-01-09 21:25:45 - building world TB --- 2014-01-09 21:25:45 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 21:25:45 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 21:25:45 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 21:25:45 - SRCCONF=/dev/null TB --- 2014-01-09 21:25:45 - TARGET=powerpc TB --- 2014-01-09 21:25:45 - TARGET_ARCH=powerpc TB --- 2014-01-09 21:25:45 - TZ=UTC TB --- 2014-01-09 21:25:45 - __MAKE_CONF=/dev/null TB --- 2014-01-09 21:25:45 - cd /src TB --- 2014-01-09 21:25:45 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 21:25:52 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:179: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:180: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:224: error: 'MF6C_INCOMPLETE_PARENT' undeclared (first use in this function) cc1: warnings being treated as errors /src/usr.bin/netstat/mroute6.c:122: warning: unused variable 'rte' /src/usr.bin/netstat/mroute6.c:121: warning: unused variable 'mfc' /src/usr.bin/netstat/mroute6.c:120: warning: unused variable 'mif6table' /src/usr.bin/netstat/mroute6.c:119: warning: unused variable 'mf6ctable' *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 23:51:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 23:51:37 - ERROR: failed to build world TB --- 2014-01-09 23:51:37 - 7512.41 user 1038.59 system 8757.50 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-powerpc-powerpc.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on powerpc64/powerpc
TB --- 2014-01-09 21:25:40 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-09 21:25:40 - 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 --- 2014-01-09 21:25:40 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2014-01-09 21:25:40 - cleaning the object tree TB --- 2014-01-09 21:25:40 - /usr/local/bin/svn stat /src TB --- 2014-01-09 21:25:44 - At svn revision 260487 TB --- 2014-01-09 21:25:45 - building world TB --- 2014-01-09 21:25:45 - CROSS_BUILD_TESTING=YES TB --- 2014-01-09 21:25:45 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-09 21:25:45 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-09 21:25:45 - SRCCONF=/dev/null TB --- 2014-01-09 21:25:45 - TARGET=powerpc TB --- 2014-01-09 21:25:45 - TARGET_ARCH=powerpc64 TB --- 2014-01-09 21:25:45 - TZ=UTC TB --- 2014-01-09 21:25:45 - __MAKE_CONF=/dev/null TB --- 2014-01-09 21:25:45 - cd /src TB --- 2014-01-09 21:25:45 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Jan 9 21:25:52 UTC 2014 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 [...] /src/usr.bin/netstat/mroute6.c:179: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:180: error: dereferencing pointer to incomplete type /src/usr.bin/netstat/mroute6.c:224: error: 'MF6C_INCOMPLETE_PARENT' undeclared (first use in this function) cc1: warnings being treated as errors /src/usr.bin/netstat/mroute6.c:122: warning: unused variable 'rte' /src/usr.bin/netstat/mroute6.c:121: warning: unused variable 'mfc' /src/usr.bin/netstat/mroute6.c:120: warning: unused variable 'mif6table' /src/usr.bin/netstat/mroute6.c:119: warning: unused variable 'mf6ctable' *** Error code 1 Stop. bmake[3]: stopped in /src/usr.bin/netstat *** Error code 1 Stop. bmake[2]: stopped in /src/usr.bin *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-09 23:52:21 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-09 23:52:21 - ERROR: failed to build world TB --- 2014-01-09 23:52:21 - 7581.95 user 1052.02 system 8801.38 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-powerpc64-powerpc.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Error when adding user with multiple groups with bsdconfig
Hi I'm on 11-CURRENT amd64. I wanted to add a user using bsdconfig but got an error when adding to several groups. Error message: ERROR!: pw pw: group `wheel daemon operator dialer network` does not exist. Creating a user who is only added to one group (for example wheel) works fine. I have submitted a PR. -- Johannes Lundberg -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. ___ 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: FreeBSD 10-RC4: Got crash in igb driver
On Thu, Jan 09, 2014 at 04:06:09PM +0100, Alexandre Martins wrote: Dear, I experience some troubles with the igb device driver on FreeBSD 10-RC4. The kernel make a pagefault in the igb_tx_ctx_setup function when accessing to a IPv6 header. The network configuration is the following: - box acting as an IPv6 router - one interface with an IPv6 (igb0) - another interface with a vlan, and IPv6 on it (vlan0 on igb1) Vlan Hardware tagging is set on both interfaces. The packet that cause the crash come from igb0 and go to vlan0. After investigation, i see that the mbuf is split in two. The first one carry the ethernet header, the second, the IPv6 header and data payload. The split is due to the m_copy done in ip6_forward, that make the mbuf not writable and the M_PREPEND in ether_output that insert the new mbuf before the original one. The kernel crashes only if the newly allocated mbuf is at the end of a memory page, and no page is available after this one. So, it's extremly rare. I inserted a KASSERT into the function (see attached patch) to check this behavior, and it raises on every IPv6 forwarded packet to the vlan. The problem disapear if i remove hardware tagging. In the commit 256200, i see that pullups has been removed. May it be related ? I think I introduced the header parsing code to meet controller requirement in em(4) and Jack borrowed that code in the past but it seems it was removed in r256200. It seems igb_tx_ctx_setup() assumes it can access ethernet/IP/TCP/UDP headers in the first mbuf of the chain. This looks wrong to me. Can you confirm the problem ? Probably Jack can tell more about change made in r256200. It's not easy for me to verify correctness of igb(4) at this moment. Best regards -- Alexandre Martins NETASQ -- We secure IT ___ 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: FreeBSD 10.0-RC5 Now Available
Hi, I upgraded this morning to FreeBSD X220.alogt.com 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #7 r260489: Fri Jan 10 08:25:55 WITA 2014 er...@x220.alogt.com:/usr/obj/usr/src/sys/X220 amd64 just to find out that the mouse is not working under X anymore. The ports are from revision 336079. I have an X220. Neither the internal stick nor the external USB connected Logitech Trackman work. Both work outside X. X logs these mouse related messages: [ 315.926] (==) intel(0): Silken mouse enabled [ 316.960] (II) config/hal: Adding input device Trackball [ 316.960] (II) LoadModule: mouse [ 316.961] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so [ 316.977] (II) Module mouse: vendor=X.Org Foundation [ 316.977]compiled for 1.12.4, module version = 1.9.0 [ 316.977]Module class: X.Org XInput Driver [ 316.977]ABI class: X.Org XInput driver, version 16.0 [ 316.977] (II) Using input driver 'mouse' for 'Trackball' [ 316.977] (**) Trackball: always reports core events [ 316.977] (**) Option Device /dev/ums0 [ 316.977] (==) Trackball: Protocol: Auto [ 316.977] (**) Trackball: always reports core events [ 316.977] (EE) xf86OpenSerial: Cannot open device /dev/ums0 Device busy. [ 316.977] (EE) Trackball: cannot open input device [ 316.977] (EE) PreInit returned 2 for Trackball [ 316.977] (II) UnloadModule: mouse [ 316.991] (II) config/hal: Adding input device PS/2 Mouse [ 316.991] (II) Using input driver 'mouse' for 'PS/2 Mouse' [ 316.991] (**) PS/2 Mouse: always reports core events [ 316.991] (**) Option Device /dev/psm0 [ 316.991] (==) PS/2 Mouse: Protocol: Auto [ 316.991] (**) PS/2 Mouse: always reports core events [ 316.991] (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. [ 316.991] (EE) PS/2 Mouse: cannot open input device [ 316.991] (EE) PreInit returned 2 for PS/2 Mouse [ 316.991] (II) UnloadModule: mouse This are the X message I get when running X on an older release candidate: [ 111.171] (II) config/hal: Adding input device PS/2 Mouse [ 111.171] (II) LoadModule: mouse [ 111.171] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so [ 111.181] (II) Module mouse: vendor=X.Org Foundation [ 111.181]compiled for 1.12.4, module version = 1.9.0 [ 111.181]Module class: X.Org XInput Driver [ 111.181]ABI class: X.Org XInput driver, version 16.0 [ 111.181] (II) Using input driver 'mouse' for 'PS/2 Mouse' [ 111.181] (**) PS/2 Mouse: always reports core events [ 111.181] (**) Option Device /dev/sysmouse [ 111.181] (==) PS/2 Mouse: Protocol: Auto [ 111.181] (**) PS/2 Mouse: always reports core events [ 111.181] (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50 [ 111.181] (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5 [ 111.181] (**) PS/2 Mouse: Buttons: 5 [ 111.181] (**) Option config_info hal:/org/freedesktop/Hal/devices/psm_0 [ 111.181] (II) XINPUT: Adding extended input device PS/2 Mouse (type: MOUSE, id 7) [ 111.181] (**) PS/2 Mouse: (accel) keeping acceleration scheme 1 [ 111.181] (**) PS/2 Mouse: (accel) acceleration profile 0 [ 111.181] (**) PS/2 Mouse: (accel) acceleration factor: 2.000 [ 111.181] (**) PS/2 Mouse: (accel) acceleration threshold: 4 [ 111.181] (II) PS/2 Mouse: SetupAuto: hw.iftype is 4, hw.model is 0 [ 111.182] (II) PS/2 Mouse: SetupAuto: protocol is SysMouse The same X worked perfectly with any FreeBSD 10 since BETA1. When I change xorg.conf and disable moused, I am able to get the internal mouse (stick) working but not the external one. The external mouse is recognised by the system when disconnected and reconnected but not by X. It also works outside X. I will update the ports tree tonight or tomorrow morning to see what will happen then. Erich On Thu, 9 Jan 2014 11:18:18 -0500 Glen Barber g...@freebsd.org wrote: Changes between -RC4 and -RC5 include: o Fix an IPv4 multicast regression. o Fixes OpenSSL for CVE-2013-4353, CVE-2013-6449, CVE-2013-6450. o Revert a change to the kinfo_file structure to preserve ABI. o Fix a race condition which could prevent the file descriptor table from being properly updated. ___ 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: FreeBSD 10.0-RC5 Now Available
On 1/9/14 10:52 PM, Allan Jude wrote: Another user had this problem this morning, try reinstalling or recompiling hald I had this too today. There's an easier, lamer workaround: Put moused_nondefault_enable=NO in your /etc/rc.conf, and unplug/plug your USB mouse (or kill moused), and restart your X server or login manager. This costs you 1 mouse pointer in text mode. --jh ___ 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
Move 3G modem from u3g to uhso?
Hi
I have been using Globetrotter HSUPA Modem Option N.V. usb modem for a
while with the uhso driver and now I installed 11-CURRENT and see that it
has been added to devd and u3g is loaded automatically. Since this device
has support for it wouldn't it be better to use uhso driver so we get the
uhso0 network interface?
The device in question is
nomatch 32 {
match bus uhub[0-9]+;
match mode host;
match vendor 0x0af0;
match product 0x9000;
action kldload -n u3g;
};
which I changed to
nomatch 32 {
match bus uhub[0-9]+;
match mode host;
match vendor 0x0af0;
match product 0x9000;
action kldload -n uhso;
};
But this also requires adding the device in sys/dev/usb/net/uhso.c
/* Option GTM661W */
UHSO_DEV(OPTION, GTM661W, UHSO_AUTO_IFACE),
Best regards
--
Johannes Lundberg
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
___
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: FreeBSD 10.0-RC5 Now Available
On Fri, Jan 10, 2014 at 11:41:02AM +0800, Erich Dollansky wrote: On Thu, 9 Jan 2014 11:18:18 -0500 Glen Barber g...@freebsd.org wrote: Changes between -RC4 and -RC5 include: o Revert a change to the kinfo_file structure to preserve ABI. I upgraded this morning to FreeBSD X220.alogt.com 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #7 r260489: Fri Jan 10 08:25:55 WITA 2014 er...@x220.alogt.com:/usr/obj/usr/src/sys/X220 amd64 just to find out that the mouse is not working under X anymore. You should rebuild your ports after upgrading from the previous -RCs, since there was an ABI change. Glen pgpUJn5GKbpDw.pgp Description: PGP signature
Re: Move 3G modem from u3g to uhso?
On 01/10/14 06:06, Lundberg, Johannes wrote:
Hi
I have been using Globetrotter HSUPA Modem Option N.V. usb modem for a
while with the uhso driver and now I installed 11-CURRENT and see that it
has been added to devd and u3g is loaded automatically. Since this device
has support for it wouldn't it be better to use uhso driver so we get the
uhso0 network interface?
The device in question is
nomatch 32 {
match bus uhub[0-9]+;
match mode host;
match vendor 0x0af0;
match product 0x9000;
action kldload -n u3g;
};
which I changed to
nomatch 32 {
match bus uhub[0-9]+;
match mode host;
match vendor 0x0af0;
match product 0x9000;
action kldload -n uhso;
};
But this also requires adding the device in sys/dev/usb/net/uhso.c
/* Option GTM661W */
UHSO_DEV(OPTION, GTM661W, UHSO_AUTO_IFACE),
Hi,
When you remove the device entry from the u3g.c driver, the usb.conf
file will be updated later. Can you submit a complete patch for this?
--HPS
___
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: Error when adding user with multiple groups with bsdconfig
On 10 Jan 2014, at 00:37, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: Creating a user who is only added to one group (for example wheel) works fine. I created a user with bsdconfig for the first time yesterday and found that their new home directory was owned by root. Did you experience this, or is it just me? David ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Error when adding user with multiple groups with bsdconfig
At least all dot files were owned by root if I remember correctly. I think there is a PR for this. -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Fri, Jan 10, 2014 at 4:33 PM, David Chisnall thera...@freebsd.orgwrote: On 10 Jan 2014, at 00:37, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: Creating a user who is only added to one group (for example wheel) works fine. I created a user with bsdconfig for the first time yesterday and found that their new home directory was owned by root. Did you experience this, or is it just me? David -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. ___ 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
