From owner-freebsd-stable@FreeBSD.ORG Sun Sep 28 15:51:24 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 22DE1150; Sun, 28 Sep 2014 15:51:24 +0000 (UTC) Date: Sun, 28 Sep 2014 11:51:18 -0400 From: Glen Barber To: freebsd-stable@FreeBSD.org Subject: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140928155118.GA75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 15:51:25 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The third BETA build of the 10.1-RELEASE release cycle is now available on the FTP servers for the amd64, armv6, i386, ia64, powerpc, powerpc64 and sparc64 architectures. This is expected to be the final BETA release of the 10.1-RELEASE cycle. The image checksums follow at the end of this email. Installer images and memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/ If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the "stable/10" branch. A list of changes since 10.0-RELEASE are available on the stable/10 release notes page here: http://www.freebsd.org/relnotes/10-STABLE/relnotes/article.html Changes between 10.1-BETA2 and 10.1-BETA3 include: o Support for serial and null console has been added to the UEFI boot loader. o A potential panic triggered by referencing a device that has been renamed has been fixed in the cam(4) subsystem. o OpenPAM has been updated to the Ourouparia (20140912) release. o New sysctls have been added to vt(4) to enable or disable potentially dangerous key combinations (such as reboot, halt, and break to debugger). o The mkimg(1) utility has been updated to allow creating empty partition entries. o The GEOM_ELI class will now cache passphrases for disk decryption, which allows the system to boot after the first passphrase entry if the remaining disks on the system use the same passphrase. o Support for controlling mfi(4) controller properties has been added to mfiutil(8). o The /usr/lib32/compat shared library directory has been added to the default ld-elf32.so.1 path. o Use of "no" for a Norwegian keymap file is now permitted in rc.conf(5). o Several bug fixes to autofs(5) have been implemented. Pre-installed virtual machine images for 10.1-BETA3 are also available for amd64 and i386 architectures. The images are located here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/10.1-BETA3/ The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. 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) Note to consumers of the dvd1.iso image: The packages included on the dvd will not be recognized by bsdconfig(8), and the cause is being investigated. The packages, however, can be installed manually. To install packages from the dvd1.iso installer, create and mount the /dist directory: # mkdir -p /dist # mount -t cd9660 /dev/cd0 /dist Next, install pkg(8) from the DVD: # env REPOS_DIR=/dist/packages/repos \ pkg bootstrap At this point, pkg-install(8) can be used to install additional packages from the DVD. Please note, the REPOS_DIR environment variable should be used each time using the DVD as the package repository, otherwise conflicts with packages from the upstream mirrors may occur when they are fetched. For example, to install Gnome and Xorg, run: # env REPOS_DIR=/dist/packages/repos \ pkg install xorg-server xorg gnome2 [...] 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.1-BETA3 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 8.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.1-BETA3 amd64 GENERIC: SHA256 (FreeBSD-10.1-BETA3-amd64-bootonly.iso) = 0ef4d0e42e87c6603a05562e1b831f596f619dbfee2e60fb14c504baa481357b SHA256 (FreeBSD-10.1-BETA3-amd64-bootonly.iso.xz) = b59f075977a75c23eedb94384221e618875d521ba730efac208b4ec8d3da2817 SHA256 (FreeBSD-10.1-BETA3-amd64-disc1.iso) = 0f4da9d3d2e7212d11dceccc69578a9758ca0e80d5ae418d2269f2668b27e8d5 SHA256 (FreeBSD-10.1-BETA3-amd64-disc1.iso.xz) = 7412e17c1a33e01e3f147a49fdbd3caa11840db0a59fb993b25a09712651214a SHA256 (FreeBSD-10.1-BETA3-amd64-dvd1.iso) = c7af6b1c9c83899390fb268e9f822da62b129dd360c6a13b3f2551c8577be486 SHA256 (FreeBSD-10.1-BETA3-amd64-dvd1.iso.xz) = f06b8a9040775621d4247b42b6ebe195ba9881bd485b8072e9760c06dbc8870a SHA256 (FreeBSD-10.1-BETA3-amd64-memstick.img) = e1b6661c17028fcbce77136604b915f77ead465726e494c51cc26a540eb2c43e SHA256 (FreeBSD-10.1-BETA3-amd64-memstick.img.xz) = a2dff8f69c58f7781743ec31aa3114a1dc9657ce21710d1cba7b78d8096f4a9f SHA256 (FreeBSD-10.1-BETA3-amd64-mini-memstick.img) = c5a79d921743aa008a16e151dc07843d1ecdda4f2d3081019ba6eec9c361eb08 SHA256 (FreeBSD-10.1-BETA3-amd64-mini-memstick.img.xz) = e5a5f0503a68a1449a9bfe2d7009b6c794a9eea07ad67c9c7bccadd52c7f7c3e SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-bootonly.iso) = f9423b9757e3b94f2b9e45f69248f3bd9a4d05804cec3292d5f2f3d12d52fce4 SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-bootonly.iso.xz) = 354d213f231c16cadd413b3c9bd96ae76d38a3cae6cd5d0491d4ae9f3bb9b8d5 SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-disc1.iso) = 36d80cf425ae31107ee4df313003690d99d648b3b8a78bb65ab7ba671454268c SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-disc1.iso.xz) = 4f1103976d6d09f277f8fe8e889aab0c598bdddf5437cf67caeb7fc314420ba8 SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-dvd1.iso) = 765d87408dd20665f4295b8522fbdc880d4b5d4bffff096c81b2b5ea77c5972a SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-dvd1.iso.xz) = 0ca60f82374724fd2c11db0f06684c6de2ec9dd8dbee3e838182577c4cf3fb96 SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-memstick.img) = bed88bf6c84c4a2114cbad07a492fba870d36c8ed01079982a329698fe451697 SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-memstick.img.xz) = ac83ef2ec4d3e384d3336f49b5649cb9bbdbf593aeecc14033ba1c058da183b2 SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-mini-memstick.img) = aca2da3b6bec3158d7a3d6a362e95b056883452a7c002546983338b7fb2ce429 SHA256 (FreeBSD-10.1-BETA3-amd64-uefi-mini-memstick.img.xz) = 94d08cacf63c8aba7c611537bec48404c5be539148b60ddd99f6918c6ade23f0 MD5 (FreeBSD-10.1-BETA3-amd64-bootonly.iso) = 607a9e372e556fd5e0c9f120ed84e1f1 MD5 (FreeBSD-10.1-BETA3-amd64-bootonly.iso.xz) = 874bc083a6f07052d21c9b89fcbc4e28 MD5 (FreeBSD-10.1-BETA3-amd64-disc1.iso) = e09a87d2cfab617a182d0c3ca7e1dafa MD5 (FreeBSD-10.1-BETA3-amd64-disc1.iso.xz) = bb12fe731a8e0bf5443564f85a7e8b48 MD5 (FreeBSD-10.1-BETA3-amd64-dvd1.iso) = 17f12347faca55089790b56f0cdaf202 MD5 (FreeBSD-10.1-BETA3-amd64-dvd1.iso.xz) = 86e4544374ff3052eb2cbae3c0bafcc0 MD5 (FreeBSD-10.1-BETA3-amd64-memstick.img) = e1bc8e402e84e62f90c9abecabf4d7cc MD5 (FreeBSD-10.1-BETA3-amd64-memstick.img.xz) = efdcd2bafe9071be0592c542ea4ef6b5 MD5 (FreeBSD-10.1-BETA3-amd64-mini-memstick.img) = 2e20ab092fce3d325a3ac0a932f893d0 MD5 (FreeBSD-10.1-BETA3-amd64-mini-memstick.img.xz) = b15b1121f0f78e312171529bfe890735 MD5 (FreeBSD-10.1-BETA3-amd64-uefi-bootonly.iso) = ea606460bb60eda97bf1049810fb9aea MD5 (FreeBSD-10.1-BETA3-amd64-uefi-bootonly.iso.xz) = 256dc6711d32a1fb558d86255a2297ec MD5 (FreeBSD-10.1-BETA3-amd64-uefi-disc1.iso) = 6ac832e07364c19b796c8ef944547614 MD5 (FreeBSD-10.1-BETA3-amd64-uefi-disc1.iso.xz) = 65d275fbf137f57e37a4bd60602e4106 MD5 (FreeBSD-10.1-BETA3-amd64-uefi-dvd1.iso) = a3d8aa77b08aa992d748f7571db90508 MD5 (FreeBSD-10.1-BETA3-amd64-uefi-dvd1.iso.xz) = 7d094ff187d1e29bb2a7ad9d372fc478 MD5 (FreeBSD-10.1-BETA3-amd64-uefi-memstick.img) = 18ce8eb12c3340f51949e1c4d005f6d6 MD5 (FreeBSD-10.1-BETA3-amd64-uefi-memstick.img.xz) = a977bb3bcbd84ac69fc73a9a3125510d MD5 (FreeBSD-10.1-BETA3-amd64-uefi-mini-memstick.img) = ea77ebcd4d0a9b0d186433d2f23ec76f MD5 (FreeBSD-10.1-BETA3-amd64-uefi-mini-memstick.img.xz) = 9782ffb75fb1f2b11563cb64806f8eed o 10.1-BETA3 i386 GENERIC: SHA256 (FreeBSD-10.1-BETA3-i386-bootonly.iso) = 73a42f58090fc28cccc908bd2f29a99d81013cf1b15fb0b79bba499f962784c7 SHA256 (FreeBSD-10.1-BETA3-i386-bootonly.iso.xz) = fec8bc3e0ca05f71be28df3da5b92656b5a5de01ad8a379c53c2f6ce1f796be0 SHA256 (FreeBSD-10.1-BETA3-i386-disc1.iso) = 73e831ef3afd268a7ee7689a34c7385b880b5f32e21ea1b179afd558d4d443c2 SHA256 (FreeBSD-10.1-BETA3-i386-disc1.iso.xz) = 430ac11e95e4b2dc5bb396e7e9fdecba627d10afb793b6e9a9c6541446d444fa SHA256 (FreeBSD-10.1-BETA3-i386-dvd1.iso) = 0d43dd224a08f18f5fc4c1bbd369e1b9b5d115b25e980a439341dd91d68328ef SHA256 (FreeBSD-10.1-BETA3-i386-dvd1.iso.xz) = 271d95100c9bc2eb4fb52dc6987e0d467d676e36d3b9452b018eccdf25858251 SHA256 (FreeBSD-10.1-BETA3-i386-memstick.img) = 34ea7a75ab7b610220547829922b6348e6f793175c0ad13e89fa6795788d4056 SHA256 (FreeBSD-10.1-BETA3-i386-memstick.img.xz) = aeb63aadd5c65435528401093568a10d60306d6564a6c04c212ed52d2bdf084e SHA256 (FreeBSD-10.1-BETA3-i386-mini-memstick.img) = 6e7393df3643532aa206c9beea11b22df19f05b2ef49fc4fbf32f46eab2f7ef2 SHA256 (FreeBSD-10.1-BETA3-i386-mini-memstick.img.xz) = 01d3cc0bc39a50e130f7303f80991c0a7effefe0cac8c47803214f0aade8e455 MD5 (FreeBSD-10.1-BETA3-i386-bootonly.iso) = 083ce634cac98f2a081311ed08ab6e26 MD5 (FreeBSD-10.1-BETA3-i386-bootonly.iso.xz) = c7c0843656e58d34d94847c88ae4fd81 MD5 (FreeBSD-10.1-BETA3-i386-disc1.iso) = 48905000ad8c64dd47f2fe06551a4433 MD5 (FreeBSD-10.1-BETA3-i386-disc1.iso.xz) = 09119f49a619d1cc666d169676ef6023 MD5 (FreeBSD-10.1-BETA3-i386-dvd1.iso) = e60ef6369b53b09ac4a0cefd0e2e7fe5 MD5 (FreeBSD-10.1-BETA3-i386-dvd1.iso.xz) = 3fbf33b92963cb4b32f075aed1fe06a0 MD5 (FreeBSD-10.1-BETA3-i386-memstick.img) = 452f3fe737add9d831190e11fe5eba8b MD5 (FreeBSD-10.1-BETA3-i386-memstick.img.xz) = 1cef03a5b0494490aab7bc9858501210 MD5 (FreeBSD-10.1-BETA3-i386-mini-memstick.img) = 3761a7de1797d57ad512fd3b798239be MD5 (FreeBSD-10.1-BETA3-i386-mini-memstick.img.xz) = 029930518ad99de1576b72064da1d135 o 10.1-BETA3 ia64 GENERIC: SHA256 (FreeBSD-10.1-BETA3-ia64-bootonly.iso) = a2c07b9f49962eb3508fd871a603d2a50ff635eb441264f071ff9b06b1bfa171 SHA256 (FreeBSD-10.1-BETA3-ia64-bootonly.iso.xz) = d940b5d3f278c37d86e4725c40d6b82afbb7a0c71c461ced5b6a2c9f230358c5 SHA256 (FreeBSD-10.1-BETA3-ia64-disc1.iso) = a2a01a82533f5e57921c46a5206c758c55eda73450c687f54b239ab3a1090d04 SHA256 (FreeBSD-10.1-BETA3-ia64-disc1.iso.xz) = dda2b3cd2e976b5254a5f2e3b3fb471e734fc0502abd8c38bce37b219ee9e72b SHA256 (FreeBSD-10.1-BETA3-ia64-memstick.img) = ee3cbfdf70ccc5802fbc4dc5c2a07b5f3e1c3a305d5435cef83cae146018a58d SHA256 (FreeBSD-10.1-BETA3-ia64-memstick.img.xz) = c5a054ec71a9bb5c56551196c672d670c95ee94c99cb59992cf6852f2975577f SHA256 (FreeBSD-10.1-BETA3-ia64-mini-memstick.img) = e80d2e7543756f9a8189adf6787d15171d7c5c5d2156a14af5515e38d2a770d4 SHA256 (FreeBSD-10.1-BETA3-ia64-mini-memstick.img.xz) = 606fc51f28f14e271abe53f830acf7ab7267dd27d562f228cb8274ef3901b8cd MD5 (FreeBSD-10.1-BETA3-ia64-bootonly.iso) = 4a3590cb11489985677db4f03f10d05e MD5 (FreeBSD-10.1-BETA3-ia64-bootonly.iso.xz) = 5b464bcba08748cc71030ba6f084a663 MD5 (FreeBSD-10.1-BETA3-ia64-disc1.iso) = 2117d7a8e1e0afe9fb778ca07575c291 MD5 (FreeBSD-10.1-BETA3-ia64-disc1.iso.xz) = c117ed46e2b22ccfa8268d8fdad53cbc MD5 (FreeBSD-10.1-BETA3-ia64-memstick.img) = 014ced0846819d741ad4bf8bcf1cddf1 MD5 (FreeBSD-10.1-BETA3-ia64-memstick.img.xz) = 34747fa129d4a6077f23f87496fbb462 MD5 (FreeBSD-10.1-BETA3-ia64-mini-memstick.img) = e3b5ab5aa6de9476fefb1f68c76f8bd9 MD5 (FreeBSD-10.1-BETA3-ia64-mini-memstick.img.xz) = a4c4f4732ec27c04b795181d845c75a0 o 10.1-BETA3 powerpc GENERIC: SHA256 (FreeBSD-10.1-BETA3-powerpc-bootonly.iso) = e286501660d69bac89b1c2512d8a60579b4ac112213f5d75459d0d3965b8654c SHA256 (FreeBSD-10.1-BETA3-powerpc-bootonly.iso.xz) = 3339fe8ccd1559e8307cf21e002edf9b8b757c13a75dfe852a4301e3618aadaf SHA256 (FreeBSD-10.1-BETA3-powerpc-disc1.iso) = 8e70ed332235bd1973da8e3edd0a4265a878ec5b6dd216affcd5e73f7b3ff6bb SHA256 (FreeBSD-10.1-BETA3-powerpc-disc1.iso.xz) = 10a38b42355f3444cbdebf3deb5a32897db24fe9d8ac48477f7e5b2f9cf92bb0 SHA256 (FreeBSD-10.1-BETA3-powerpc-memstick.img) = c419c3becc2edc343633e88ca2445f021036a553b382c6cd90435666e6f7e173 SHA256 (FreeBSD-10.1-BETA3-powerpc-memstick.img.xz) = 73e9e74ca190df15c0d669b1a69511456f24e6e0026dd52c406f39f58f527a9b SHA256 (FreeBSD-10.1-BETA3-powerpc-mini-memstick.img) = 983fcbe78ccc52e37f7bf89836fcd593247287dc598172c8e488eaa94502d955 SHA256 (FreeBSD-10.1-BETA3-powerpc-mini-memstick.img.xz) = 3c3f317966e684993c42e72eaa13c7dd142a334e85872b857ff830b0254c5338 MD5 (FreeBSD-10.1-BETA3-powerpc-bootonly.iso) = d2f1b40d459a893d222502f5da84cec3 MD5 (FreeBSD-10.1-BETA3-powerpc-bootonly.iso.xz) = 9fbb87555c08d466e11c05ee54ac1ee6 MD5 (FreeBSD-10.1-BETA3-powerpc-disc1.iso) = 89c82bac1416c1ce86ccd472bef4a050 MD5 (FreeBSD-10.1-BETA3-powerpc-disc1.iso.xz) = bd4b924612d0853685fb6ec7fdf01c8e MD5 (FreeBSD-10.1-BETA3-powerpc-memstick.img) = a14c97cbb7bc51fef5b6fda5800be40b MD5 (FreeBSD-10.1-BETA3-powerpc-memstick.img.xz) = 375238cabc2d4f585e4f3b13e935335e MD5 (FreeBSD-10.1-BETA3-powerpc-mini-memstick.img) = aeb5834cb5286ab9236741411a0947e5 MD5 (FreeBSD-10.1-BETA3-powerpc-mini-memstick.img.xz) = 48b7d0415e5ac00de50543f498c873c0 o 10.1-BETA3 powerpc64 GENERIC64: SHA256 (FreeBSD-10.1-BETA3-powerpc-powerpc64-bootonly.iso) = 5fdb83ad175fc536be2c3ae4d37386ccb00999ef21215bd141216cb5e58edffc SHA256 (FreeBSD-10.1-BETA3-powerpc-powerpc64-bootonly.iso.xz) = ca0e652b577e5e7824b3a1dd231ed91f3df84294c6031e2d1236bd6cc3882733 SHA256 (FreeBSD-10.1-BETA3-powerpc-powerpc64-disc1.iso) = aceb54cf0b584bf3dfd61e768f5bb43aa8e3cf1189878226999eff5389958298 SHA256 (FreeBSD-10.1-BETA3-powerpc-powerpc64-disc1.iso.xz) = 1fddbe5569b245d748665e655426c44b42ddffc0bd5e0a1b0479d6660f8e0e00 SHA256 (FreeBSD-10.1-BETA3-powerpc-powerpc64-memstick.img) = 8a346eb43172c574f66bd4e982016b0495b4bfa68e272ca3e59570dcdc190545 SHA256 (FreeBSD-10.1-BETA3-powerpc-powerpc64-memstick.img.xz) = 45aa7ce2d24579f3a2aafafc951693bf0d1a58a69da76b84157b11281b9e93a0 SHA256 (FreeBSD-10.1-BETA3-powerpc-powerpc64-mini-memstick.img) = 74cc8fe53679bccbc59a74bc3e7a1d4d6277f5ceb1f9214037c64a62c1b1d256 SHA256 (FreeBSD-10.1-BETA3-powerpc-powerpc64-mini-memstick.img.xz) = 6261b4b474416d023200fbc3b7c5d57a31a8499d528b1c5742197b3ae2e9db3c MD5 (FreeBSD-10.1-BETA3-powerpc-powerpc64-bootonly.iso) = ea963fadd14c56397e7ce525ca9c57fc MD5 (FreeBSD-10.1-BETA3-powerpc-powerpc64-bootonly.iso.xz) = 27aa82d1174180f9395e4d34bc662372 MD5 (FreeBSD-10.1-BETA3-powerpc-powerpc64-disc1.iso) = c62474b25a04ded00fd998ca6b274ce6 MD5 (FreeBSD-10.1-BETA3-powerpc-powerpc64-disc1.iso.xz) = 3020ceb66b5184f590f8db9f189b4a7a MD5 (FreeBSD-10.1-BETA3-powerpc-powerpc64-memstick.img) = ac406d29554cd3001b91cf178b01eff3 MD5 (FreeBSD-10.1-BETA3-powerpc-powerpc64-memstick.img.xz) = ed6cbf39ca883e08c5fba376d324cad8 MD5 (FreeBSD-10.1-BETA3-powerpc-powerpc64-mini-memstick.img) = 95a03a43404728eb929c683f1b39b982 MD5 (FreeBSD-10.1-BETA3-powerpc-powerpc64-mini-memstick.img.xz) = 513104d4880ceb3d575820dcd82ddae1 o 10.1-BETA3 sparc64 GENERIC: SHA256 (FreeBSD-10.1-BETA3-sparc64-bootonly.iso) = 70b621d4b5c60bda9a16cf5368835bad7c7d20bad0a1bfee339e12fe56b47c24 SHA256 (FreeBSD-10.1-BETA3-sparc64-bootonly.iso.xz) = 38494348980dcc23a2767b638be9584858549662f549bf89e993527952caf6d8 SHA256 (FreeBSD-10.1-BETA3-sparc64-disc1.iso) = 3efb130923d65430143eb2ef5aa6acd3d3bf1450d3cb1b4fdd4f16f995b7c9c2 SHA256 (FreeBSD-10.1-BETA3-sparc64-disc1.iso.xz) = 72223e0fe3fb5ebbde712e953f8d3a2c1b885eaa49edef5ef8a87ffc048eccaa MD5 (FreeBSD-10.1-BETA3-sparc64-bootonly.iso) = e48d6d67d8d1b4ec474c15e804c38f99 MD5 (FreeBSD-10.1-BETA3-sparc64-bootonly.iso.xz) = a926f8f65ea473b209437225ba17b722 MD5 (FreeBSD-10.1-BETA3-sparc64-disc1.iso) = 254505363ff9eeefa8e8240f7b9a8bc1 MD5 (FreeBSD-10.1-BETA3-sparc64-disc1.iso.xz) = aa7698f07bbf80edfd4d513af90bd013 o 10.1-BETA3 armv6 BEAGLEBONE: SHA256 (FreeBSD-10.1-BETA3-arm-armv6-BEAGLEBONE.img.bz2) = 05d7193ea5e0d2d157b40a78ceeca70a270db7588e114a0ce2b6b06e3d5daaa8 MD5 (FreeBSD-10.1-BETA3-arm-armv6-BEAGLEBONE.img.bz2) = ec513269ef6bf7248a1bde9d46005083 o 10.1-BETA3 armv6 RPI-B: SHA256 (FreeBSD-10.1-BETA3-arm-armv6-RPI-B.img.bz2) = 2e7d26212d144720ef4a95212972863cd125f31bb7514866523e91e215b54c7c MD5 (FreeBSD-10.1-BETA3-arm-armv6-RPI-B.img.bz2) = c095186d862207c72b390a8a3e5d4f34 o 10.1-BETA3 armv6 PANDABOARD: SHA256 (FreeBSD-10.1-BETA3-arm-armv6-PANDABOARD.img.bz2) = ee549dacc22dde5bf864c5076ff56962dd5a507447938a37b4d9505bd0e32ca1 MD5 (FreeBSD-10.1-BETA3-arm-armv6-PANDABOARD.img.bz2) = 3864fe19b2ab8d043752d5aa4fc3f1c3 o 10.1-BETA3 armv6 WANDBOARD-QUAD: SHA256 (FreeBSD-10.1-BETA3-arm-armv6-WANDBOARD-QUAD.img.bz2) = 98479b993be01aa9a6e1fce6465f7ddc83c60dadd086b695a460a5fb7d3477be MD5 (FreeBSD-10.1-BETA3-arm-armv6-WANDBOARD-QUAD.img.bz2) = 881b4731a8c27825520713df4beeb2de o 10.1-BETA3 armv6 ZEDBOARD: SHA256 (FreeBSD-10.1-BETA3-arm-armv6-ZEDBOARD.img.bz2) = 7f6edb0ed4c5b20e041c92afa1f516c1e1e0f400d39f719afbaf60f9b8a9df9f MD5 (FreeBSD-10.1-BETA3-arm-armv6-ZEDBOARD.img.bz2) = 249bb5ff491a43f05f6757c7dc0eeb63 == VM IMAGE CHECKSUMS == o 10.1-BETA3 amd64: SHA256 (FreeBSD-10.1-BETA3-amd64.qcow2.xz) = d6a21ab4f6fb525b0c5c26ae882ae715fdbcedb25475ce50c76c8156aad2bdf3 SHA256 (FreeBSD-10.1-BETA3-amd64.raw.xz) = 82e11f3d33d07017b9fcf4849af0e8a9a4ab36543036f5ca191643c8425c18be SHA256 (FreeBSD-10.1-BETA3-amd64.vhd.xz) = 05777975c9da2b22417b89d4fed8de253a3d7e9f4bd16e99ab8181d5f6e0c9e3 SHA256 (FreeBSD-10.1-BETA3-amd64.vmdk.xz) = 2eb32d0a090d18ba4daa2c83d782ed32ff31828359902806b02197083225c8ae MD5 (FreeBSD-10.1-BETA3-amd64.qcow2.xz) = 4f47e7707cd54f0c580e18579891a2a7 MD5 (FreeBSD-10.1-BETA3-amd64.raw.xz) = b9980672b805702e2b3602174b637632 MD5 (FreeBSD-10.1-BETA3-amd64.vhd.xz) = 4cbac3c9373479cbfa4259bc41d61c62 MD5 (FreeBSD-10.1-BETA3-amd64.vmdk.xz) = fe03e9c0ca1a2a52da47e6cf30c38c73 o 10.1-BETA3 i386: SHA256 (FreeBSD-10.1-BETA3-i386.qcow2.xz) = c10ef4d27f24560ead89bc62f744edf46a5020c90ca45bd415661e05640d4189 SHA256 (FreeBSD-10.1-BETA3-i386.raw.xz) = 569cbb6c5dbed55bf5af851f3b6b898b57c3c12947a04a3c5bdc19a6dc3e3510 SHA256 (FreeBSD-10.1-BETA3-i386.vhd.xz) = 3f305c10bcbdcd2236b5d4fc0a6093cbb7c10a33e9a47f6f233b215f73fc0e04 SHA256 (FreeBSD-10.1-BETA3-i386.vmdk.xz) = 22d9542f8ced2587aa16273fdb5aafb6d7bcd41399fda4c862e1c76a9bb879a7 MD5 (FreeBSD-10.1-BETA3-i386.qcow2.xz) = 7b774432cfdab6dcc2d04e70c1c0499b MD5 (FreeBSD-10.1-BETA3-i386.raw.xz) = dca0e6becd18cb947074ce947df86ed0 MD5 (FreeBSD-10.1-BETA3-i386.vhd.xz) = cb4c1bda0a66da428015c2d70184b599 MD5 (FreeBSD-10.1-BETA3-i386.vmdk.xz) = 3da8c5c6b161ea13ce01b94d8673409a Glen Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKC52AAoJEAMUWKVHj+KT628P/2UtWmU8XdmPc9qTKQ3/TzFk N8R+BeUvUI/mEwsCLapOT5QNGihnp4ax+BBfA/UIZCrxRkIYs5o5KeZbWjtDPwWI 0EHkSIOTQY6x5Ro0gM12JqNk00rzKA6DoC783m+qZPoG3xUxzV3Ex+s+s7zAvNh1 8xE/a1fAE94uGqQzb1WWxoPmTCMihXkbAM0s/oZfefHaK28LhVVdQpmyluhHRMO+ b0x33i6+utyBFjEJ8tACPOLDcke5kN85h4bf3TpygqKLS+xO7FaLuiLfNx30Vge+ L9U4EpRD9JJt5kUhSRVNU5M+b7cFsQC5C1LdKlaVjJFUahREBVJM6sEHtzVQ1u7j 09kM+C2f3nilqPzvHksOz397YQ6ji5fIXhyE5tC877CHAohDnA6hcXikwqhsdXaY QYdyv6Lvkjj2oJYob61fzp7XsdKxxs/FyicbmLs8P3ifD2okXjQy834g8Ew6jSe4 HVa5GHWCChTDk9dShknN8EmBxmZoEemKwpKzQ4DAxi+x99kjgPR93Qw8LNJ9OF37 JOt1Osi2qhY53SdRE11bRGF3tFTWdaBb1/rCqixsStnwCjPNN1vGZMG7ItNjWpnQ gA2ny1WQqXpHmQ3iz/yfZ0Ckdj053lVE5yj3aRgUKH1Dg6t/DYD8AOgC37Yq1FLB DS2aasunymVVOBt+d6ib =DZK0 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 28 21:37:50 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 62756A27; Sun, 28 Sep 2014 21:37:50 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 306B8B88; Sun, 28 Sep 2014 21:37:50 +0000 (UTC) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.5/8.14.5) with ESMTP id s8SLc3Uo068251; Sun, 28 Sep 2014 14:38:09 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: (from www@localhost) by udns.ultimatedns.net (8.14.5/8.14.5/Submit) id s8SLbwbK068250; Sun, 28 Sep 2014 14:37:58 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net ([2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Sun, 28 Sep 2014 14:37:58 -0700 (PDT) Message-ID: <7b0a119ebc4d8d7813f92c0f94aba8d8.authenticated@ultimatedns.net> Date: Sun, 28 Sep 2014 14:37:58 -0700 (PDT) Subject: Mesa-9: configure: error: C compiler cannot create executables From: "Chris H" To: "freebsd current" , "freebsd stable" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 21:37:50 -0000 Greetings, A recent install of RELENG_9, followed by a build|install world|kernel. Returns the following error when attempting an make install of x11/xorg-minimal ===> Configuring for dri-9.1.7_5,2 configure: loading site script /usr/ports/Templates/config.site checking build system type... amd64-portbld-freebsd9.3 checking host system type... amd64-portbld-freebsd9.3 checking target system type... amd64-portbld-freebsd9.3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether gmake sets $(MAKE)... yes checking whether gmake supports nested variables... yes checking for style of include used by gmake... GNU checking for gcc... clang checking whether the C compiler works... no configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': configure: error: C compiler cannot create executables See `config.log' for more details ===> Script "configure" failed unexpectedly. Please report the problem to x11@FreeBSD.org [maintainer] and attach the "/usr/ports/graphics/dri/work/Mesa-9.1.7/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** [do-configure] Error code 1 Any thoughts on how to overcome this issue? Relevant info: # svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Relative URL: ^/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 272203 Node Kind: directory Schedule: normal Last Changed Author: thomas Last Changed Rev: 272184 Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 369380 Node Kind: directory Schedule: normal Last Changed Author: mva Last Changed Rev: 369380 Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 root@demon:/usr/obj/usr/src/sys/DEMON amd64 Thank you for all your time, and consideration. --Chris From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 01:02:06 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A319A20E; Mon, 29 Sep 2014 01:02:06 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 78BD6F2D; Mon, 29 Sep 2014 01:02:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=2oMPz8rSmbkFN3/zoLWp+peM8ThKyxt067ZAdkgEO94=; b=YiMdsx6qlSVe5Sbgb/mWZlHaok/XYyrkss8Tvem+Iun01B4JYbXJd3m0jygd9hM8diUgiUl4BBrgb67lvLtYsXDahR7Kb2goWFk+jn2tSGa8OPSMMvf+2uvIiBB3qA6M5FlpXNuQSOgYkmLKiCk9GGg5vzGyQROkTWwtaUa+7Mk=; Received: from [182.5.36.225] (port=25705 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1XYPLo-000p3b-O8; Sun, 28 Sep 2014 19:02:05 -0600 Date: Mon, 29 Sep 2014 09:01:49 +0800 From: Erich Dollansky To: Glen Barber Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929090149.34aa1927@X220.alogt.com> In-Reply-To: <20140928155118.GA75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: FreeBSD Release Engineering Team , freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 01:02:06 -0000 Hi, On Sun, 28 Sep 2014 11:51:18 -0400 Glen Barber wrote: > The third BETA build of the 10.1-RELEASE release cycle is now > available on the FTP servers for the amd64, armv6, i386, ia64, > powerpc, powerpc64 and sparc64 architectures. > is the Raspberry B+ supported or just the Raspberry B? > This is expected to be the final BETA release of the 10.1-RELEASE > cycle. > If you would like to use SVN to do a source based update of an > existing system, use the "stable/10" branch. > I just did. Of course, it will take now some time before I have binaries for the amd64 to test. Erich From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 01:12:49 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64D93493; Mon, 29 Sep 2014 01:12:48 +0000 (UTC) Date: Sun, 28 Sep 2014 21:12:43 -0400 From: Glen Barber To: Erich Dollansky Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929011243.GF75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929090149.34aa1927@X220.alogt.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ShzNbizneSsKYyOp" Content-Disposition: inline In-Reply-To: <20140929090149.34aa1927@X220.alogt.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-arm@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 01:12:49 -0000 --ShzNbizneSsKYyOp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Added freebsd-arm@ and BCC'd re@] On Mon, Sep 29, 2014 at 09:01:49AM +0800, Erich Dollansky wrote: > On Sun, 28 Sep 2014 11:51:18 -0400 > Glen Barber wrote: > > The third BETA build of the 10.1-RELEASE release cycle is now > > available on the FTP servers for the amd64, armv6, i386, ia64, > > powerpc, powerpc64 and sparc64 architectures. > >=20 > is the Raspberry B+ supported or just the Raspberry B? >=20 I am unsure, and do not have access to a RaspberryPi B+ to test. The freebsd-arm@ list is the best place to find the answer to this question. Glen --ShzNbizneSsKYyOp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKLILAAoJEAMUWKVHj+KTz8YQAIxhCaPp0X0HGjD+RyVp6V+J tmv/RPGMGwZrfOA+o+FYf91/DWHypV8z/V7Jtbx9xJqcRf4dm8zw1SIii1x4bBKT mhMtxjGNoD+29uPWF2u4b2l46271Mm7uSIIPXQucAt+Pfxg1p20WBbZdhits6NIv iIoLiHtj8qipfsYUpnuiLe0lXCo9Ts+zwibVyKt1HzBDwZb+/N0JkY8ny02rJUga C9w+wL4KfWrZnYPV/fNbym5xp3Ngx2Jzy+1NgKq78mQyD00/qGvZ/0CpRa21oLxm UGxraKywxGsnsz5Uvrr7XlvzVCqJ/wHIaUbR3/EcFDzvxNDesBX1wUU+ZsnqSraQ yBDIfHmu8qgzIzVZqEev9barVIy7MiBW/eIawdHrhSSgIBJWU7VIDw1ENS50bqxW R8ke/00y2wqyt4sZw74ljScSmG1z8Wie8jvZmnY7DW6EHZdMH0hhUNB8nipO7iwm r8lLhm61di0NI5BYWP6iyoGxhV93f17q3pcYhTYv+YejBKPnUUCmYL2S73JeK9XQ 1C0Wit11PTv+Mxy6ZhQ/JfuKknJQBP7ruyq/NIR9p7quXTcHqwErVf+YoQszylr9 kAasduFf18nAUMuIMhnCE0o/5slTFLkCxORUlE2sxnT0OrpJkYivWuLagPnUTPRe U8OcD6baTyFIdVuwdJrW =lRT+ -----END PGP SIGNATURE----- --ShzNbizneSsKYyOp-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 01:28:48 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 196D67EF; Mon, 29 Sep 2014 01:28:48 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E11AF19C; Mon, 29 Sep 2014 01:28:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=Jv3uWBRJOm4FtQAfXPG0agr3GI6ifffAzd/eGZMMxYY=; b=ZSoHEDdbZSAvOWx4zBPr4rmkXAiCNYv/7nPMDJtvteUf71+OBgetok8V1RD7GWjuYdq9Fak0iYUh+mpncrsvGM+E+NsEPM7SKXO/bNSvAdWDTc9QNJbWmSZznUBXDXh7+cYofAeAdWHq4i6b2ypzD0IZzklKVEhrbNE7ebZ/msA=; Received: from [182.5.36.225] (port=56286 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1XYPld-0011sM-V9; Sun, 28 Sep 2014 19:28:46 -0600 Date: Mon, 29 Sep 2014 09:28:35 +0800 From: Erich Dollansky To: Glen Barber Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929092835.6313304a@X220.alogt.com> In-Reply-To: <20140929011243.GF75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929090149.34aa1927@X220.alogt.com> <20140929011243.GF75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-arm@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 01:28:48 -0000 Hi, On Sun, 28 Sep 2014 21:12:43 -0400 Glen Barber wrote: > [Added freebsd-arm@ and BCC'd re@] > > On Mon, Sep 29, 2014 at 09:01:49AM +0800, Erich Dollansky wrote: > > On Sun, 28 Sep 2014 11:51:18 -0400 > > Glen Barber wrote: > > > The third BETA build of the 10.1-RELEASE release cycle is now > > > available on the FTP servers for the amd64, armv6, i386, ia64, > > > powerpc, powerpc64 and sparc64 architectures. > > > > > is the Raspberry B+ supported or just the Raspberry B? > > > > I am unsure, and do not have access to a RaspberryPi B+ to test. The > freebsd-arm@ list is the best place to find the answer to this > question. > I have one. I will give the build a try after the machine has finished its current task. This can take days. Erich From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 01:29:01 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3539B90F; Mon, 29 Sep 2014 01:29:01 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B7C761A0; Mon, 29 Sep 2014 01:29:00 +0000 (UTC) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.5/8.14.5) with ESMTP id s8T1TB8c010767; Sun, 28 Sep 2014 18:29:17 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: (from www@localhost) by udns.ultimatedns.net (8.14.5/8.14.5/Submit) id s8T1T6TQ010764; Sun, 28 Sep 2014 18:29:06 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net ([2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Sun, 28 Sep 2014 18:29:06 -0700 (PDT) Message-ID: <26670d7976dc83f6afaf63577f6c114d.authenticated@ultimatedns.net> In-Reply-To: <55ea1654e68d865f7becfa4bf57474c3.authenticated@ultimatedns.net> References: <7b0a119ebc4d8d7813f92c0f94aba8d8.authenticated@ultimatedns.net> <542882B7.4060407@freebsd.org> <82259777bbe474bb5581c2b4a0b79f25.authenticated@ultimatedns.net> <54288C32.3080201@freebsd.org> <55ea1654e68d865f7becfa4bf57474c3.authenticated@ultimatedns.net> Date: Sun, 28 Sep 2014 18:29:06 -0700 (PDT) Subject: Re: Mesa-9: configure: error: C compiler cannot create executables From: "Chris H" To: freebsd-stable@freebsd.org User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-current@freebsd.org, Allan Jude X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 01:29:01 -0000 >> On 09/28/2014 18:11, Chris H wrote: >>>> On 09/28/2014 17:37, Chris H wrote: >>>>> Greetings, >>>>> A recent install of RELENG_9, followed by a build|install world|kernel. >>>>> Returns the following error when attempting an make install of >>>>> x11/xorg-minimal >>>>> >>>>> ===> Configuring for dri-9.1.7_5,2 >>>>> configure: loading site script /usr/ports/Templates/config.site >>>>> checking build system type... amd64-portbld-freebsd9.3 >>>>> checking host system type... amd64-portbld-freebsd9.3 >>>>> checking target system type... amd64-portbld-freebsd9.3 >>>>> checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel >>>>> checking whether build environment is sane... yes >>>>> checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p >>>>> checking for gawk... (cached) /usr/bin/awk >>>>> checking whether gmake sets $(MAKE)... yes >>>>> checking whether gmake supports nested variables... yes >>>>> checking for style of include used by gmake... GNU >>>>> checking for gcc... clang >>>>> checking whether the C compiler works... no >>>>> configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': >>>>> configure: error: C compiler cannot create executables >>>>> See `config.log' for more details >>>>> ===> Script "configure" failed unexpectedly. >>>>> Please report the problem to x11@FreeBSD.org [maintainer] and attach the >>>>> "/usr/ports/graphics/dri/work/Mesa-9.1.7/config.log" including the output of >>>>> the failure of your make command. Also, it might be a good idea to provide >>>>> an overview of all packages installed on your system (e.g. a >>>>> /usr/local/sbin/pkg-static info -g -Ea). >>>>> *** [do-configure] Error code 1 >>>>> >>>>> Any thoughts on how to overcome this issue? >>>>> >>>>> Relevant info: >>>>> >>>>> # svn info /usr/src >>>>> >>>>> Path: /usr/src >>>>> Working Copy Root Path: /usr/src >>>>> URL: svn://svn.freebsd.org/base/stable/9 >>>>> Relative URL: ^/stable/9 >>>>> Repository Root: svn://svn.freebsd.org/base >>>>> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >>>>> Revision: 272203 >>>>> Node Kind: directory >>>>> Schedule: normal >>>>> Last Changed Author: thomas >>>>> Last Changed Rev: 272184 >>>>> Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) >>>>> >>>>> svn info /usr/ports >>>>> Path: /usr/ports >>>>> Working Copy Root Path: /usr/ports >>>>> URL: svn://svn.freebsd.org/ports/head >>>>> Relative URL: ^/head >>>>> Repository Root: svn://svn.freebsd.org/ports >>>>> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 >>>>> Revision: 369380 >>>>> Node Kind: directory >>>>> Schedule: normal >>>>> Last Changed Author: mva >>>>> Last Changed Rev: 369380 >>>>> Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) >>>>> >>>>> FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 >>>>> root@demon:/usr/obj/usr/src/sys/DEMON amd64 >>>>> >>>>> Thank you for all your time, and consideration. >>>>> >>>>> --Chris >>>>> >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>>>> >>>> >>>> What does config.log say? >>> Please see attached (config.log.txt) -- it's big. :) >>> >>>> >>>> also 'clang -v' >>> nadda -- don't think it's installed -- WITHOUT_CLANG=true (/etc/make.conf) >>> >>> Thank you for your thoughtful reply, Allan. >>> >>> --Chris >>> >>>> >>>> >>>> -- >>>> Allan Jude >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>>> >>>> >>>> >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> >> echo $CC > # echo $CC > CC: Undefined variable >> >> It seems it is trying to use clang, and you have disabled clang >> >> check your /etc/make.conf > I'm carrying over defines from a 9.2-STABLE box: > WITHOUT_CLANG=true > FAVORITE_COMPILER=gcc > > These worked famously on the 9.2. So I thought them safe here (9.3). >> >> you might need to add CC=gcc to /etc/make.conf to make it work >> >> Warning: I have no idea what I am talking about, it is 2am at a BSD >> conference hacking lounge > LOL I wish you the best! :) > > Thank you for taking the time to reply, Allan. Especially under the > circumstances! > > --Chris A trip to lang/gcc; make install clean. Also failed to help. I guess there isn't a compiler capable of creating executables available with RELENG_9? Is this some fascist move to eliminate (g)cc from FreeBSD. So that only clang/llvm work? ugh. :-| --Chris >> >> >> -- >> Allan Jude >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 02:36:21 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 161CB569; Mon, 29 Sep 2014 02:36:20 +0000 (UTC) Date: Sun, 28 Sep 2014 22:36:16 -0400 From: Glen Barber To: Erich Dollansky Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929023616.GG75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929090149.34aa1927@X220.alogt.com> <20140929011243.GF75063@hub.FreeBSD.org> <20140929092835.6313304a@X220.alogt.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jb2K77FXt9dSeH4m" Content-Disposition: inline In-Reply-To: <20140929092835.6313304a@X220.alogt.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-arm@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 02:36:21 -0000 --jb2K77FXt9dSeH4m Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 29, 2014 at 09:28:35AM +0800, Erich Dollansky wrote: > On Sun, 28 Sep 2014 21:12:43 -0400 > Glen Barber wrote: > > > is the Raspberry B+ supported or just the Raspberry B? > >=20 > > I am unsure, and do not have access to a RaspberryPi B+ to test. The > > freebsd-arm@ list is the best place to find the answer to this > > question. > >=20 > I have one. I will give the build a try after the machine has finished > its current task. This can take days. >=20 Why not try the images already available here? http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/ Glen --jb2K77FXt9dSeH4m Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKMWgAAoJEAMUWKVHj+KTURUP/jNRO/pi8K/RFofR3BYD3K4D O2yzo43Sgb6U0MuqZfhe/vb96EmeFDKtpEXtcz99PmPzOCDOoyA8MTcnR2yYc3r7 P6Sk1FfBWVws/HeLQrt3gm168y1Uevm7QZYzaOGr3u+5eT78nA42kKPRvXN6ksuh ieOsiIJOYaKFGqd4vUA3o52t8EPA4XCUzHVw8diTWAb/4Iv3EGLGFpRe7ihnJL+1 GjwoOfQ4VcC6uVWI/AD3jttmohAxDWjMuVP22x4cWghVYpQmysTocA+7EAE1bYTj FHdRqBvlLbVSKCqQOBPKg2EEaM37ieH/wSZzL7RV1LE8RPvan3fKfPvMyoSsD51L bNJAiLRuPlRT71dlunX6/hf6fpF5nfg/p9txzAdYBUoYTDyZjiBL9ZYD9uIkl8oE HHRJ1WSCvdI8RV08DqgooQY32CAuhNNMhNRGK62D+w14bidCp9TRIn8E+25ez4Ni GBR64YmNydeGaoQ5zXkyjGxS7jRKZfWNXWJFKhRwpdGijSX6qH2Qn2w9L3OjWQUx yY2yHc84EsSNsa9GJ9JZtBKpAjWKKb+zERSISipn/vhPvHnQaZyLTvX0/bYP3XtQ WVHL/DOfao2DZ22KaEB1SPRtU9f7Ag5vHCVli552wOp61xSwMhdQ+2TaoO3N3coo ieddglEiAhk3Xg1R0Q+I =iu20 -----END PGP SIGNATURE----- --jb2K77FXt9dSeH4m-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 02:47:17 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 120716CC; Mon, 29 Sep 2014 02:47:17 +0000 (UTC) Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C32FBA93; Mon, 29 Sep 2014 02:47:16 +0000 (UTC) Message-ID: In-Reply-To: <20140928155118.GA75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> Date: Mon, 29 Sep 2014 04:45:21 +0200 Subject: Re: FreeBSD 10.1-BETA3 Now Available From: beeessdee@ruggedinbox.com To: "Glen Barber" Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 02:47:17 -0000 On Sun, 28 Sep 2014 11:51:18 -0400, "Glen Barber" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 Why 10.1-BETA3 announcement signed with not usual PGP key? gpgv: Signature made Sun Sep 28 11:51:18 2014 EDT using RSA key ID 478FE293 gpgv: Can't check signature: No public key Compare 10.1-BETA2 announce: gpgv: Signature made Sun Sep 21 13:06:56 2014 EDT using RSA key ID AF8B5ED0 gpgv: using subkey AF8B5ED0 instead of primary key A0B946A3 gpgv: Good signature from "Glen Barber " gpgv: aka "Glen Barber " gpgv: aka "Glen Barber " gpgv: textmode signature, digest algorithm SHA256 This key new last year/expire 2018, so very unexpected. Shocking it is: some people actually check this, not like http://xkcd.com/1181/ , you know. ;-) Seriously, SHA256 checksum on ftp mirror not so useful. PGP signed mail with checksum, who could guess, we actually use this and its not wasted efforts! Thanks. From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 02:51:07 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C42C07D9; Mon, 29 Sep 2014 02:51:06 +0000 (UTC) Date: Sun, 28 Sep 2014 22:51:02 -0400 From: Glen Barber To: beeessdee@ruggedinbox.com Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929025102.GH75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1dkYmjfcc/LECdOT" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 02:51:07 -0000 --1dkYmjfcc/LECdOT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 29, 2014 at 04:45:21AM +0200, beeessdee@ruggedinbox.com wrote: > Why 10.1-BETA3 announcement signed with not usual PGP key? >=20 Because it is a BETA build, and not a release. Glen --1dkYmjfcc/LECdOT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKMkWAAoJEAMUWKVHj+KTY1QQAKPWQu7XIilmt1sBiqscjRW0 9jvluUGEGObPgOb7gyWr2iFAV5QnuP16S6c/AWxe3SaTrZwEBowX1nN6nYrh4Vqp Q75tYNEA0zRVd8l8Z1GgoanTP3Vh28C4Exv/a1iesGqWD+liyWjTHvQeRpYQ/Yp1 mNNgSAmb8xBgyfB0/h6HDdLwDWk7IoWlKVq/6U7xGa9bWV5BaBodUYCztIMjk/8h HOjPZzPWgBxXYEFhJgJF6/Cp6fuFqkISO8KaHGF3GmdacNtZKUPhdolikCtNqMGU 55zw0h7tAMdn/xAwZ43p3v09+luuC91hKFwHRS66Ud8xIbuOJrk/0lK5AgEX6+cz MqAzHOa++ZqG7Q59Rf97b1rDKpHYs3kFwWmUfJsdMgAVpwabmnT0grPKYMkg6TBD prWfNCf5HirL54UidwHucPlsUtqNPE73woROqT5zS5Bqtk8oMN9oIvh8xMykZFDd w5iM7R9u2FRuKxohJDSPktLw9To11vA9pudZIJI+LnfuaZ9lIO/2andHQJejlfBG czgr7elwU8r88DQmzqfXacT/2QlELqlHqJdezrvWRUhGxj57YB8oF5ButoIQDlwI 9HPqUu+PdDeqWKDYyXyGI4RqZZKb/bDwZ01wbXmX3mw2ZqmkfH64Q3zvTzv5d/lz DUTWSi8YSVVbQdRULqo2 =rLaZ -----END PGP SIGNATURE----- --1dkYmjfcc/LECdOT-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 03:00:56 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 35D7293C; Mon, 29 Sep 2014 03:00:56 +0000 (UTC) Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E8066B86; Mon, 29 Sep 2014 03:00:55 +0000 (UTC) Message-ID: In-Reply-To: <20140929025102.GH75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929025102.GH75063@hub.FreeBSD.org> Date: Mon, 29 Sep 2014 04:58:38 +0200 Subject: Re: FreeBSD 10.1-BETA3 Now Available From: beeessdee@ruggedinbox.com To: "Glen Barber" Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: beeessdee@ruggedinbox.com, FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 03:00:56 -0000 On Mon, September 29, 2014 4:51 am, "Glen Barber" wrote: > On Mon, Sep 29, 2014 at 04:45:21AM +0200, beeessdee@ruggedinbox.com wrote: >> Why 10.1-BETA3 announcement signed with not usual PGP key? >> > > Because it is a BETA build, and not a release. > > Glen As my first mail said: BETA2 announce signed with keyid 0xAF8B5ED0 (subkey of primary 0xA0B946A3, Key fingerprint = 78B3 42BA 26C7 B2AC 681E A7BE 524F 0C37 A0B9 46A3). So as BETA1, and many other prerelease announce by you IIRC... So, why BETA2 and BETA3 different keys? Is there official policy? Thanks for reply. From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 03:11:24 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 76166C36; Mon, 29 Sep 2014 03:11:23 +0000 (UTC) Date: Sun, 28 Sep 2014 23:11:20 -0400 From: Glen Barber To: beeessdee@ruggedinbox.com Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929031120.GI75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929025102.GH75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vMIwsFy2iMQolwSC" Content-Disposition: inline In-Reply-To: <20140929025102.GH75063@hub.FreeBSD.org> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 03:11:24 -0000 --vMIwsFy2iMQolwSC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 28, 2014 at 10:51:02PM -0400, Glen Barber wrote: > On Mon, Sep 29, 2014 at 04:45:21AM +0200, beeessdee@ruggedinbox.com wrote: > > Why 10.1-BETA3 announcement signed with not usual PGP key? > >=20 >=20 > Because it is a BETA build, and not a release. >=20 After re-reading your reply, I realize I haven't sent my last set of PGP subkeys. Anyway, this is not RE-related. Glen --vMIwsFy2iMQolwSC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKM3YAAoJEAMUWKVHj+KTgTkP/2Qcz4xH0aEju7FEeultpr48 gUjX6PNKUAJXt+5RgmfEoJwfoA6ttwF6yQJQMn3MKwybmG24qSaOnCPWNCQCzvLb s2OtyS3eKtOGLyJE8a8Yu90UmtsDjalJOPJYZU+XhfHwMoHSdoaJ6X0x2vs+7L62 Rr6zzo0L9C4vNcpXlW6DImvNmeQSD6uL8Gc0UlnTZn+jFP6NPkAc97uduj19qdJT XBArifm0584s66CKEhNP8Oi4tmAJryTpAcqdbKPBAOnIBIil/YV1ComzyQQdYje1 U9IqmuMHOV0x2ku1T3aqAjOyC8PCoIDSvkq4vdwqH3UsKYt3IMmimpVxtFMca0Ir hwmRwyFOQsPNF2qQxnHrtKIkiyPt7i/ufke6G6l9JhDpsYybfY0mRHIqt4AhVGjN u8up4VmKKGLtH2KtpNfI3GEfENf7V6yrnjH+nwiB0/q/RwaLVEFRhKnX8ZVfPnpM eLSDyKZFGj5jHpDzlF8be8OCdczk2AWkcFo5RcGn2TVTBLd07KwdIXvPnur9DTGR tIsPrGmA3zwuhvXMOOHSa7wtdl5udYogTNWtIjXgSu+RFEJJss46gpP57tGCSFjL ioD/MtSxL6sUATg2LzVsLQT2A8zbLANcUtCKbvbF139hMwG0nLDQxQKu/pDMhnbH XJnIxTCt6HVrCyKh40sS =UQ+c -----END PGP SIGNATURE----- --vMIwsFy2iMQolwSC-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 03:12:53 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F038D34; Mon, 29 Sep 2014 03:12:52 +0000 (UTC) Date: Sun, 28 Sep 2014 23:12:49 -0400 From: Glen Barber To: beeessdee@ruggedinbox.com Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929031249.GJ75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929025102.GH75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="XsNr6wQGW5mnDcoi" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 03:12:53 -0000 --XsNr6wQGW5mnDcoi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 29, 2014 at 04:58:38AM +0200, beeessdee@ruggedinbox.com wrote: > On Mon, September 29, 2014 4:51 am, "Glen Barber" wrote: > > On Mon, Sep 29, 2014 at 04:45:21AM +0200, beeessdee@ruggedinbox.com wro= te: > >> Why 10.1-BETA3 announcement signed with not usual PGP key? > >> > > > > Because it is a BETA build, and not a release. > > >=20 > As my first mail said: BETA2 announce signed with keyid 0xAF8B5ED0 > (subkey of primary 0xA0B946A3, Key fingerprint =3D 78B3 42BA 26C7 B2AC 68= 1E=20 > A7BE 524F 0C37 A0B9 46A3). So as BETA1, and many other prerelease > announce by you IIRC... >=20 > So, why BETA2 and BETA3 different keys? Is there official policy? >=20 No. See subsequent reply. Glen --XsNr6wQGW5mnDcoi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKM4xAAoJEAMUWKVHj+KT3eQP/3MZ3d6rFsEzxzAHobNnrHGq GVm6KV9ssWvpvrRgTyrXN1ADj5ABkYc+/SID1F2dMzvhXiLFrv479MjdoiS8K8Fi P+pp0RDcqvsCcpuM1RuwqGbrT1g2TCTA4eX4lsWt36lqY3UakAU8s/mwItDLAncF J24YIk9VypXjk9lO7e+HYFmcVzByMtc6l4gHkTOKQ/y2syx46MIXeptyTCn11Qr7 eN4t7PDiZavScoMVNEnN4yt0dHOsDxOVb9BuLruPG2SsXmn4arJTGpQXQHXh80+N aAZ8iNDmlfJpqOV9+ClAofjXv0ZrpS5PEnLCgunjeBWodEdFJRJoUyLMsITHr+aq bIBv4YObI31UcsT0jFcjNuXZRR96qA3UtNKry8HTjVG1PprGYpdOAvLQHkvGDmXX QEHpuue9DYKAZVdNGzFu/QeYIdAWqy9eTvga0o1j/QdZLjkXPXThd4uyuTSGPCtm BHzSvqZR0cNeqrG72J5CPxLmVf8nZepXPPKCIx5UeRFYOZ/nz05GCruTf+HoH+E5 5dSZe+mgkugZmkB5wzmF5DLhYNkxgLBk2pOM8qyeF1LoelmP0bYJtFySrTAJjlD3 to/YAA9Qwz6riiYgunTQiKt9JQlQZG084kruKR1MkemgltzBWsXbM3/vq0J6V6wp P7Zck608DDRuTNyPzhQk =/NOi -----END PGP SIGNATURE----- --XsNr6wQGW5mnDcoi-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 03:15:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6672E37; Mon, 29 Sep 2014 03:15:13 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 79C7FDDD; Mon, 29 Sep 2014 03:15:13 +0000 (UTC) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.5/8.14.5) with ESMTP id s8T3FSI4036735; Sun, 28 Sep 2014 20:15:33 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: (from www@localhost) by udns.ultimatedns.net (8.14.5/8.14.5/Submit) id s8T3FMqf036729; Sun, 28 Sep 2014 20:15:22 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net ([2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Sun, 28 Sep 2014 20:15:23 -0700 (PDT) Message-ID: <411fc42685f5deb5ca9cf02374fc531a.authenticated@ultimatedns.net> In-Reply-To: <26670d7976dc83f6afaf63577f6c114d.authenticated@ultimatedns.net> References: <7b0a119ebc4d8d7813f92c0f94aba8d8.authenticated@ultimatedns.net> <542882B7.4060407@freebsd.org> <82259777bbe474bb5581c2b4a0b79f25.authenticated@ultimatedns.net> <54288C32.3080201@freebsd.org> <55ea1654e68d865f7becfa4bf57474c3.authenticated@ultimatedns.net> <26670d7976dc83f6afaf63577f6c114d.authenticated@ultimatedns.net> Date: Sun, 28 Sep 2014 20:15:23 -0700 (PDT) Subject: Re: Mesa-9: configure: error: C compiler cannot create executables From: "Chris H" To: "Allan Jude" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 03:15:14 -0000 >>> On 09/28/2014 18:11, Chris H wrote: >>>>> On 09/28/2014 17:37, Chris H wrote: >>>>>> Greetings, >>>>>> A recent install of RELENG_9, followed by a build|install world|kernel. >>>>>> Returns the following error when attempting an make install of >>>>>> x11/xorg-minimal >>>>>> >>>>>> ===> Configuring for dri-9.1.7_5,2 >>>>>> configure: loading site script /usr/ports/Templates/config.site >>>>>> checking build system type... amd64-portbld-freebsd9.3 >>>>>> checking host system type... amd64-portbld-freebsd9.3 >>>>>> checking target system type... amd64-portbld-freebsd9.3 >>>>>> checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel >>>>>> checking whether build environment is sane... yes >>>>>> checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p >>>>>> checking for gawk... (cached) /usr/bin/awk >>>>>> checking whether gmake sets $(MAKE)... yes >>>>>> checking whether gmake supports nested variables... yes >>>>>> checking for style of include used by gmake... GNU >>>>>> checking for gcc... clang >>>>>> checking whether the C compiler works... no >>>>>> configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': >>>>>> configure: error: C compiler cannot create executables >>>>>> See `config.log' for more details >>>>>> ===> Script "configure" failed unexpectedly. >>>>>> Please report the problem to x11@FreeBSD.org [maintainer] and attach the >>>>>> "/usr/ports/graphics/dri/work/Mesa-9.1.7/config.log" including the output of >>>>>> the failure of your make command. Also, it might be a good idea to provide >>>>>> an overview of all packages installed on your system (e.g. a >>>>>> /usr/local/sbin/pkg-static info -g -Ea). >>>>>> *** [do-configure] Error code 1 >>>>>> >>>>>> Any thoughts on how to overcome this issue? >>>>>> >>>>>> Relevant info: >>>>>> >>>>>> # svn info /usr/src >>>>>> >>>>>> Path: /usr/src >>>>>> Working Copy Root Path: /usr/src >>>>>> URL: svn://svn.freebsd.org/base/stable/9 >>>>>> Relative URL: ^/stable/9 >>>>>> Repository Root: svn://svn.freebsd.org/base >>>>>> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >>>>>> Revision: 272203 >>>>>> Node Kind: directory >>>>>> Schedule: normal >>>>>> Last Changed Author: thomas >>>>>> Last Changed Rev: 272184 >>>>>> Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) >>>>>> >>>>>> svn info /usr/ports >>>>>> Path: /usr/ports >>>>>> Working Copy Root Path: /usr/ports >>>>>> URL: svn://svn.freebsd.org/ports/head >>>>>> Relative URL: ^/head >>>>>> Repository Root: svn://svn.freebsd.org/ports >>>>>> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 >>>>>> Revision: 369380 >>>>>> Node Kind: directory >>>>>> Schedule: normal >>>>>> Last Changed Author: mva >>>>>> Last Changed Rev: 369380 >>>>>> Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) >>>>>> >>>>>> FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 >>>>>> root@demon:/usr/obj/usr/src/sys/DEMON amd64 >>>>>> >>>>>> Thank you for all your time, and consideration. >>>>>> >>>>>> --Chris >>>>>> >>>>>> _______________________________________________ >>>>>> freebsd-current@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>>>>> >>>>> >>>>> What does config.log say? >>>> Please see attached (config.log.txt) -- it's big. :) >>>> >>>>> >>>>> also 'clang -v' >>>> nadda -- don't think it's installed -- WITHOUT_CLANG=true (/etc/make.conf) >>>> >>>> Thank you for your thoughtful reply, Allan. >>>> >>>> --Chris >>>> >>>>> >>>>> >>>>> -- >>>>> Allan Jude >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>> >>> echo $CC >> # echo $CC >> CC: Undefined variable >>> >>> It seems it is trying to use clang, and you have disabled clang >>> >>> check your /etc/make.conf >> I'm carrying over defines from a 9.2-STABLE box: >> WITHOUT_CLANG=true >> FAVORITE_COMPILER=gcc >> >> These worked famously on the 9.2. So I thought them safe here (9.3). >>> >>> you might need to add CC=gcc to /etc/make.conf to make it work >>> >>> Warning: I have no idea what I am talking about, it is 2am at a BSD >>> conference hacking lounge >> LOL I wish you the best! :) >> >> Thank you for taking the time to reply, Allan. Especially under the >> circumstances! >> >> --Chris > > A trip to lang/gcc; make install clean. Also failed to help. > I guess there isn't a compiler capable of creating executables > available with RELENG_9? Is this some fascist move to eliminate > (g)cc from FreeBSD. So that only clang/llvm work? > > ugh. :-| Well. A quick look at graphics/dri/Makefile, reveals it is a diabolical plot to insist gcc goes away. :( I simply commented the conditional, and added GCC to suit my needs. :) # gcc from base can't handle some code in mesa 9.1+ # We only care for 9.x and 8.x, not for old pre-clang default current. # This is for 0b0000 binary which gcc 4.3+ understands and is in the i965 driver. .if defined(WITH_NEW_XORG) . if (${OSVERSION} >= 901500 && ${OSVERSION} < 1000000) \ && ${ARCH} == amd64 USE_GCC=yes #CC=clang #CXX=clang++ #CPP=clang-cpp . elif ${OSVERSION} < 901500 USE_GCC=yes . endif .endif Die clang, die! --Chris > > > --Chris > >>> >>> >>> -- >>> Allan Jude >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>> >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 03:33:08 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D7A7A1F0; Mon, 29 Sep 2014 03:33:08 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9EB27F90; Mon, 29 Sep 2014 03:33:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=jCroS9HO9ZZwOvleBBQNz+R88MQAvh9MzMb86/+uhyM=; b=wSZnF7QTWYxGiDnor+TnXkFibXuRoZWgF/ochvUnQH7YAb2yinFwyNv4NLXjH27wkdM25mZy6VtdVx5D6Ev/XsJpKSVTO80CznQ8DF13VqgB0Quz6wC6PqQN5fMRN1LpPghqVgInoKTvjv6hS5m3yGkVFxYzUqRni9L56i6Kq7c=; Received: from [182.5.36.225] (port=41535 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1XYRhu-0021U9-Kd; Sun, 28 Sep 2014 21:33:03 -0600 Date: Mon, 29 Sep 2014 11:32:30 +0800 From: Erich Dollansky To: Glen Barber Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929113230.144be5da@X220.alogt.com> In-Reply-To: <20140929023616.GG75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929090149.34aa1927@X220.alogt.com> <20140929011243.GF75063@hub.FreeBSD.org> <20140929092835.6313304a@X220.alogt.com> <20140929023616.GG75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-arm@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 03:33:09 -0000 Hi, On Sun, 28 Sep 2014 22:36:16 -0400 Glen Barber wrote: > On Mon, Sep 29, 2014 at 09:28:35AM +0800, Erich Dollansky wrote: > > On Sun, 28 Sep 2014 21:12:43 -0400 > > Glen Barber wrote: > > > > is the Raspberry B+ supported or just the Raspberry B? > > > > > > I am unsure, and do not have access to a RaspberryPi B+ to test. > > > The freebsd-arm@ list is the best place to find the answer to this > > > question. > > > > > I have one. I will give the build a try after the machine has > > finished its current task. This can take days. > > > > Why not try the images already available here? > > http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/ yes, why not. I downloaded it already and still start to test it later. Is there somewhere a documentation of how this image was build? Erich From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 03:44:19 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16801403; Mon, 29 Sep 2014 03:44:19 +0000 (UTC) Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C8344F7; Mon, 29 Sep 2014 03:44:18 +0000 (UTC) Message-ID: In-Reply-To: <20140929031120.GI75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929025102.GH75063@hub.FreeBSD.org> <20140929031120.GI75063@hub.FreeBSD.org> Date: Mon, 29 Sep 2014 05:42:30 +0200 Subject: Re: FreeBSD 10.1-BETA3 Now Available From: beeessdee@ruggedinbox.com To: "Glen Barber" Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 03:44:19 -0000 On Mon, September 29, 2014 5:11 am, "Glen Barber" wrote: > On Sun, Sep 28, 2014 at 10:51:02PM -0400, Glen Barber wrote: >> On Mon, Sep 29, 2014 at 04:45:21AM +0200, beeessdee@ruggedinbox.com >> wrote: >> > Why 10.1-BETA3 announcement signed with not usual PGP key? >> > >> >> Because it is a BETA build, and not a release. >> > > After re-reading your reply, I realize I haven't sent my last set of PGP > subkeys. Thanks gjb@! I will watch for those, so I can verify BETA3 and later before testing/using. (But sad nobody before noticed and asked you. I thought I am very slow.) > Anyway, this is not RE-related. Jah, 'RE-related' would be public verify method for whole svn repo tied to audit trail of release process. :-( Anyway... thanks again for clarify the mysterious keyid 0x478FE293. (fyi I checked keyservers too before I mail the list.) From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 04:22:31 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75C11A51 for ; Mon, 29 Sep 2014 04:22:31 +0000 (UTC) Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 370A274F for ; Mon, 29 Sep 2014 04:22:31 +0000 (UTC) Message-ID: <2ac3ccbb9ede61a99b0306107ad3846b.squirrel@s4bysmmsnraf7eut.onion> In-Reply-To: <3d80542ccc73686094ddde4e18465e4a.squirrel@s4bysmmsnraf7eut.onion> References: <4490c8c4d489370c7617c0ace9e773be.squirrel@s4bysmmsnraf7eut.onion> <3d80542ccc73686094ddde4e18465e4a.squirrel@s4bysmmsnraf7eut.onion> Date: Mon, 29 Sep 2014 06:20:09 +0200 Subject: Re: vt(4) "newcons" and 80x25 vty? (tested: 10.1-BETA2) From: beeessdee@ruggedinbox.com To: "Ronald Klop" Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 04:22:31 -0000 On Fri, September 26, 2014 12:51 am, beeessdee@ruggedinbox.com wrote: > On Thu, 25 Sep 2014 18:13:56 +0200, "Ronald Klop" > wrote: > >> On Thu, 25 Sep 2014 17:31:49 +0200, wrote: >> >>> I daily use FreeBSD with base system virtual terminals (no X). I am >>> excited of vt(4) with Unicodes support. But screen has arbitrary >>> number >>> of lines and columns, whatever will fit with selected font. How to get >>> standard 80x25? >> >> Hello, >> >> Can you try hw.vga.textmode=1 in loader.conf? It will a similar screen >> as >> syscons did. >> See man vt(4). > > Thanks for the response. > > That sounds as good workaround, if works when kms/drm loaded; I will try > it as soon as I can be by my test machine. Original problem is still a problem, workaround not work. *Either* I have 80x25 mode (mildly improvement with some vt(4) font mapping?), *or* I have graphics mode with wide range of characters but WAY tiny, tiny, and too many lines/columns on screen. Also some bugs/hangs with font loading. Any suggest how to tweak/debug further, I will appreciate. Key points: * hw.vga.textmode=1 not affect situation with kms driver loaded: Tiny characters, much too many lines/cols. Maybe this seem obvious, but important for next reason. * VT in VGA textmode fonts loading broken (tested 10.1-BETA2). Tried vidfont(1) and also vidcontrol -f [size] [filename]. For loading "VGA" fonts, screen weird/unusable (see below). For loading Gallant (12x22), the virtual terminal freeze (both other vty still ok). * So, I can see some nice accented Latin characters (mapped from BIOS provided font?). Not like sc(4), with vt(4) I can echo raw utf-8 of these! But not any Cyrillic, CJK, Middle Eastern, etc. With kern.vty=vt and hw.vga.textmode=1 (set at loader prompt), when use vidfont(1) to select fonts called "VGA" in it's menu, it's very weird. Cursor gets stuck in small area at top corner of screen. Rest of screen retains its contents, cannot be cleared. reset(1) and clear(1) does nothing. Not find way to fix this, except reboot. Obvious the 12x22 font (as gallant) will not expect working in "textmode". And does not work (hangs vty). As stated in previous mail, with kms driver vidfont(1) has bug prevent gallant load (but vidcontrol -f works). Test platform: 10.1-BETA2 amd64 live usb. I use loader prompt to select vty subsystem, set options, load kms drivers sometimes (also sometimes kldload later). I try all combinations I can think of. Cannot try 10.1-BETA3 until I get gjb@ PGP keyid 0x478FE293, per other thread today on -stable. I hope this will be fixed, and maybe I try hacking on it sometime (where to start?). I will be sad to see this broken still by 10.1-RELEASE. It is encouraged for more people try Old Fashioned Unix at the terminal... especially people using non English language. From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 04:33:34 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1DD02CB8; Mon, 29 Sep 2014 04:33:34 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E92C28A1; Mon, 29 Sep 2014 04:33:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=K6IFUiXlsH2QnzSUBqtIcMm2tZyMGN0zOj8J0pmZS18=; b=D8Bjg2GMe0x11Z2qQ2hJ2/LA4UFWE/5eTG6ztxEzu4WhbIvxn2JWd4J7U3ZqDvaPBINGBrESiBra4dZMk7UWx2tkK/gdzSvFLJsxfB9B5uDRZg8WirL83fGcwK5WxXUhyFdckawSHYP/FJZXkmO6/rhQHREiHdDLVzZcLl5Eyzw=; Received: from [182.5.36.225] (port=61812 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1XYSeR-002RcD-Uy; Sun, 28 Sep 2014 22:33:32 -0600 Date: Mon, 29 Sep 2014 12:33:27 +0800 From: Erich Dollansky To: Glen Barber Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929123327.6ab0207c@X220.alogt.com> In-Reply-To: <20140929023616.GG75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929090149.34aa1927@X220.alogt.com> <20140929011243.GF75063@hub.FreeBSD.org> <20140929092835.6313304a@X220.alogt.com> <20140929023616.GG75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-arm@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 04:33:34 -0000 Hi, On Sun, 28 Sep 2014 22:36:16 -0400 Glen Barber wrote: > On Mon, Sep 29, 2014 at 09:28:35AM +0800, Erich Dollansky wrote: > > On Sun, 28 Sep 2014 21:12:43 -0400 > > Glen Barber wrote: > > > > is the Raspberry B+ supported or just the Raspberry B? > > > > > > I am unsure, and do not have access to a RaspberryPi B+ to test. > > > The freebsd-arm@ list is the best place to find the answer to this > > > question. > > > > > I have one. I will give the build a try after the machine has > > finished its current task. This can take days. > > > > Why not try the images already available here? > > http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/ > I have tried it now several times. All with the same result. The machine seems to start as the partition is fully expanded. The USB interface does not seem to be recognised. As I do not have monitor cable here, I am not able to do further testing. I will try now to compile the CURRENT sources and see what will happen there. Erich From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 05:46:02 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE32D553; Mon, 29 Sep 2014 05:46:02 +0000 (UTC) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id 9E3B4F0B; Mon, 29 Sep 2014 05:46:02 +0000 (UTC) Received: from localhost (w142149.ppp.asahi-net.or.jp [121.1.142.149]) by mailssl.asahi-net.or.jp (Postfix) with ESMTP id A023411F01; Mon, 29 Sep 2014 14:27:16 +0900 (JST) Date: Mon, 29 Sep 2014 14:27:12 +0900 (JST) Message-Id: <20140929.142712.117419748410715004.shigeru@os-hackers.jp> To: erichsfreebsdlist@alogt.com Subject: Re: FreeBSD 10.1-BETA3 Now Available From: YAMAMOTO Shigeru In-Reply-To: <20140929123327.6ab0207c@X220.alogt.com> References: <20140929092835.6313304a@X220.alogt.com> <20140929023616.GG75063@hub.FreeBSD.org> <20140929123327.6ab0207c@X220.alogt.com> X-Mailer: Mew version 6.6 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: gjb@FreeBSD.org, freebsd-arm@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 05:46:02 -0000 Hi, >>>>> "Erich" == Erich Dollansky writes: > On Sun, 28 Sep 2014 22:36:16 -0400 > Glen Barber wrote: > > Why not try the images already available here? > > > > http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/ > > > I have tried it now several times. All with the same result. > > The machine seems to start as the partition is fully expanded. The USB > interface does not seem to be recognised. It seems me it is same problem, http://lists.freebsd.org/pipermail/freebsd-arm/2014-July/008872.html Please try to use newer firmware image in your SD image. Thanks, --- YAMAMOTO Shigeru From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 05:52:49 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D2EF3875; Mon, 29 Sep 2014 05:52:49 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 529D9FD; Mon, 29 Sep 2014 05:52:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=iwrhMRgdRiiybrRgx3ECsdeZv4+DPHyaUIKGWg6N28k=; b=cQ16HR8GhlMQnASSLqpzLRGuEKEDFWYvhRZf8gAVTxb/ny+PnNJge9UjlMCPH7aAd49PdqypERGE3CSIKfF6S9qL2OhPwDrMgqTClJPPVqbcKYDw2R6LBibM8vJSNMHDedVhAdqB9JOx7/2R3RNDjmLez3VprAFMixq0UC8t0n4=; Received: from [182.5.36.225] (port=12285 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1XYTt9-003ct6-Gu; Sun, 28 Sep 2014 23:52:48 -0600 Date: Mon, 29 Sep 2014 13:52:32 +0800 From: Erich Dollansky To: YAMAMOTO Shigeru Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929135232.07844765@X220.alogt.com> In-Reply-To: <20140929.142712.117419748410715004.shigeru@os-hackers.jp> References: <20140929092835.6313304a@X220.alogt.com> <20140929023616.GG75063@hub.FreeBSD.org> <20140929123327.6ab0207c@X220.alogt.com> <20140929.142712.117419748410715004.shigeru@os-hackers.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: gjb@FreeBSD.org, freebsd-arm@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 05:52:49 -0000 Hi, On Mon, 29 Sep 2014 14:27:12 +0900 (JST) YAMAMOTO Shigeru wrote: > >>>>> "Erich" == Erich Dollansky writes: > > On Sun, 28 Sep 2014 22:36:16 -0400 > > Glen Barber wrote: > > > Why not try the images already available here? > > > > > > http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/ > > > > > I have tried it now several times. All with the same result. > > > > The machine seems to start as the partition is fully expanded. The > > USB interface does not seem to be recognised. > > It seems me it is same problem, > http://lists.freebsd.org/pipermail/freebsd-arm/2014-July/008872.html > > Please try to use newer firmware image in your SD image. > it seems that this does not solve the problem. I have copied the firmware from a media with a running system to the new image but it did not boot properly either. I am currently compiling 11 on the Raspberry itself. Let me see how far I will come with it. Erich From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 05:54:26 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A0127AB9; Mon, 29 Sep 2014 05:54:26 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 77B4113D; Mon, 29 Sep 2014 05:54:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=dbdghB+28OW5cyGosVkIpJ3xuADZeVSQOW+AY7tF0/Y=; b=FO3QiuPn8hO8s0GC79QuwlnrJ40Ti730jnpo9oWIDEPc5OkfyBv/gWLS/TSPRrbBBZNBnpdY6RZJ06Sv+F8loO1wplE3q82zL5CVk8GwiDjA3cPPpb3egWJ//jq3pV2CU0vDZBLLTEf4R6ib1zq81C5TTouK7NMuHQH+xECIRHg=; Received: from [182.5.36.225] (port=21010 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1XYTui-003enK-SM; Sun, 28 Sep 2014 23:54:25 -0600 Date: Mon, 29 Sep 2014 13:54:19 +0800 From: Erich Dollansky To: YAMAMOTO Shigeru Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929135419.0eb10c46@X220.alogt.com> In-Reply-To: <20140929.142712.117419748410715004.shigeru@os-hackers.jp> References: <20140929092835.6313304a@X220.alogt.com> <20140929023616.GG75063@hub.FreeBSD.org> <20140929123327.6ab0207c@X220.alogt.com> <20140929.142712.117419748410715004.shigeru@os-hackers.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: gjb@FreeBSD.org, freebsd-arm@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 05:54:26 -0000 Hi, On Mon, 29 Sep 2014 14:27:12 +0900 (JST) YAMAMOTO Shigeru wrote: > > It seems me it is same problem, > http://lists.freebsd.org/pipermail/freebsd-arm/2014-July/008872.html > > Please try to use newer firmware image in your SD image. > I forgot to mention that the running Raspberry is using you image. Erich From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 09:04:33 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CC26A35F for ; Mon, 29 Sep 2014 09:04:33 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id A6AEE991 for ; Mon, 29 Sep 2014 09:04:33 +0000 (UTC) Received: from [172.16.0.139] (unknown [92.247.20.226]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 1067B54E5D for ; Mon, 29 Sep 2014 09:04:30 +0000 (UTC) Message-ID: <5429209C.6020402@freebsd.org> Date: Mon, 29 Sep 2014 05:04:28 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Mesa-9: configure: error: C compiler cannot create executables References: <7b0a119ebc4d8d7813f92c0f94aba8d8.authenticated@ultimatedns.net> <542882B7.4060407@freebsd.org> <82259777bbe474bb5581c2b4a0b79f25.authenticated@ultimatedns.net> <54288C32.3080201@freebsd.org> <55ea1654e68d865f7becfa4bf57474c3.authenticated@ultimatedns.net> <26670d7976dc83f6afaf63577f6c114d.authenticated@ultimatedns.net> <411fc42685f5deb5ca9cf02374fc531a.authenticated@ultimatedns.net> In-Reply-To: <411fc42685f5deb5ca9cf02374fc531a.authenticated@ultimatedns.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 09:04:33 -0000 On 2014-09-28 23:15, Chris H wrote: > > Die clang, die! > > --Chris So yes, that port requires newer GCC than is in base (die GPLv3, die) I am not sure why the conditional was not causing the dependency on ports gcc to fire correctly, or why that makefile was explicitly setting cc=clang As long as your issue is solved, best of luck, but really, embrace the clang, the clang is your friend. Long live clang. -- Allan Jude From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 12:16:52 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DB806AA0; Mon, 29 Sep 2014 12:16:51 +0000 (UTC) Date: Mon, 29 Sep 2014 08:16:48 -0400 From: Glen Barber To: beeessdee@ruggedinbox.com Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929121648.GL75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929025102.GH75063@hub.FreeBSD.org> <20140929031120.GI75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="s0AIMtcnAlS2OWxa" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 12:16:52 -0000 --s0AIMtcnAlS2OWxa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 29, 2014 at 05:42:30AM +0200, beeessdee@ruggedinbox.com wrote: > Thanks gjb@! I will watch for those, so I can verify BETA3 and later > before testing/using. >=20 The new subkeys are signed with my old keys, so verification shouldn't be an issue. > > Anyway, this is not RE-related. >=20 > Jah, 'RE-related' would be public verify method for whole svn repo tied to > audit trail of release process. :-( >=20 I don't understand what you mean. We have a verifiable audit trail - it is all in svn revision history. Glen --s0AIMtcnAlS2OWxa Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKU2wAAoJEAMUWKVHj+KTPkUP/26CZHdvhssBJurK5HYJOZeJ rUd5xyv/LZjzc5LRGOKRRfxRooXlS2fUoZT2tCDLxlZGlfkgLJ7kR2RU+AU2ysqr ME62mPlyIzButXiTqbdGpU1s7I9JnSPzObVLN4qSzXasehXGrI7FcLFdzf/YGJbR DuFVcnvSNVLiG/iRx+XMlsWyUEz+mL5q1enwlfMGzUgCvFNnKz85m3cmaUkKwPp0 TQZxxpkUgVf+rf9d2FYEhrNOfrWDVuFbEN9KTe8drxWCjJgHQa623pWV8GX5rGgv 3OP3mGVmBzqHq55lIcptWLC3JcT7hr3hMP4hrOUDoNi9ysafRa20yGKPT4QJpi3y KnmudS4P5xp6VDNwN4Jx4vHv0v3n3eRJDvK2m4Qe2jVOKf1OQ7J2zKeggJV6he4w qfsf8GhCZtgbjXKD7Og2IRViV655tDJH8qF2U13p2cqfkXjZvIbtXXAZAlA9LTeq tG4oVvBZ7kIC0eTf5YzXCaVVufUx0/cL/j3oBdxJW7jIKRfcz5VGM+6qaBFD1mz+ fQMw6fQ7Zbcn19PCefhcmcQRAWCOm+eNuZQwE1zbVH+nLXH3TmnsbARDoTdM2myO 8i9JPRdHbh87bJg7pxc6wTf4lyMucbybxTsVXNHexQPY+ger4P/pAqdGYV5fRBCI DZHxdckKHPvKk7VYa471 =7/N2 -----END PGP SIGNATURE----- --s0AIMtcnAlS2OWxa-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 13:32:50 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CADEDF12 for ; Mon, 29 Sep 2014 13:32:50 +0000 (UTC) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ozzie.tundraware.com", Issuer "ozzie.tundraware.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 95012B0E for ; Mon, 29 Sep 2014 13:32:49 +0000 (UTC) Received: from [10.219.168.191] ([66.175.245.1]) (authenticated bits=0) by ozzie.tundraware.com (8.14.9/8.14.9) with ESMTP id s8TDWRwl079761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 29 Sep 2014 08:32:32 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <54295F65.3090600@tundraware.com> Date: Mon, 29 Sep 2014 08:32:21 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: FreeBSD Stable Subject: Still Seeing Parallel Build Breakage In 10.1-BETA3 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [75.145.138.73]); Mon, 29 Sep 2014 08:32:33 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s8TDWRwl079761 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:32:50 -0000 FYI - Code Branch: /usr/src>svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/10 Relative URL: ^/stable/10 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 272279 Node Kind: directory Schedule: normal Last Changed Author: wblock Last Changed Rev: 272275 Last Changed Date: 2014-09-28 18:15:18 -0500 (Sun, 28 Sep 2014) Buildworld is fine with -j4, but buildkernel blows out: ===> ata/atapci/chipsets/atacenatek (cleandir) --- cleandir_subdir_bwi --- --- cleanobj --- --- cleandir_subdir_ata --- --- cleanobj --- --- cleanobj --- rm: fts_read: No such file or directory *** [cleanobj] Error code 1 make[5]: stopped in /usr/src/sys/modules/ata/atapci --- _sub.cleandir --- A failure has been detected in another branch of the parallel make make[7]: stopped in /usr/src/sys/modules/ata/atapci/chipsets/atacenatek --- cleandir_subdir_bktr --- A failure has been detected in another branch of the parallel make --- cleandir_subdir_ata --- *** [_sub.cleandir] Error code 2 make[6]: stopped in /usr/src/sys/modules/ata/atapci/chipsets --- cleandir_subdir_bktr --- make[4]: stopped in /usr/src/sys/modules/bktr --- cleandir_subdir_ata --- 1 error -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 13:47:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B5B464DA for ; Mon, 29 Sep 2014 13:47:02 +0000 (UTC) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 71E3AC7C for ; Mon, 29 Sep 2014 13:47:01 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.9/8.14.9) with ESMTP id s8TDl0BC008625; Mon, 29 Sep 2014 06:47:00 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.9/8.14.9/Submit) id s8TDkxXa008624; Mon, 29 Sep 2014 06:46:59 -0700 (PDT) (envelope-from david) Date: Mon, 29 Sep 2014 06:46:59 -0700 From: David Wolfskill To: Tim Daneliuk Subject: Re: Still Seeing Parallel Build Breakage In 10.1-BETA3 Message-ID: <20140929134659.GQ1304@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Tim Daneliuk , FreeBSD Stable References: <54295F65.3090600@tundraware.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="OxDG9cJJSSQMUzGF" Content-Disposition: inline In-Reply-To: <54295F65.3090600@tundraware.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:47:02 -0000 --OxDG9cJJSSQMUzGF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 29, 2014 at 08:32:21AM -0500, Tim Daneliuk wrote: > FYI - >=20 > Code Branch: >=20 > /usr/src>svn info > Path: . > Working Copy Root Path: /usr/src > URL: svn://svn.freebsd.org/base/stable/10 > Relative URL: ^/stable/10 > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 272279 > Node Kind: directory > Schedule: normal > Last Changed Author: wblock > Last Changed Rev: 272275 > Last Changed Date: 2014-09-28 18:15:18 -0500 (Sun, 28 Sep 2014) >=20 >=20 > Buildworld is fine with -j4, but buildkernel blows out: > ... I use $(( 2 * $( sysctl -n hw.ncpu ) )) for the -j value; in each of the following cases, that works out to 4: FreeBSD g1-235.catwhisker.org 10.1-BETA3 FreeBSD 10.1-BETA3 #1346 r272275M= /272280:1000717: Mon Sep 29 05:41:54 PDT 2014 root@g1-235.catwhisker.or= g:/common/S3/obj/usr/src/sys/CANARY i386 FreeBSD freebeast.catwhisker.org 10.1-BETA3 FreeBSD 10.1-BETA3 #1594 r2722= 75M/272280:1000717: Mon Sep 29 06:14:44 PDT 2014 root@freebeast.catwhis= ker.org:/common/S3/obj/usr/src/sys/GENERIC i386 My laptop is the one with a kernel config of CANARY; the build machine uses GENERIC. So: it works for me.... Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --OxDG9cJJSSQMUzGF Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ7BAEBCgBmBQJUKWLRXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4 QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk7mwcP912z18kEdmSCG/CwYmUNxWa7 N3cQSUvSg39IILK+A8789lnlCxXHGh1xNH74QsVVDxdOFG17d5qw/yZUhCyubDVR ndgJrLnkDQi8TB2sxj3eYJUCCW3Rk6ebMDpRBzmkSgAs3qrJKFOnX3v8RJlctHHP s+5PpA0EgcHv3AK/4AukTW7od1jdnShkOmpwtTeKCcxVyY65eYn4T/OwrD0/FOCP EaW2O5nPjhIW12nzFeLyiNH5ggo7w7AOt+dWYEauSAprwXkxDktpg1NZebpVOL3W AEMrc4xG+KF987RSXRFek1J/xQvNaVpnnhWpemyIUQSWolV5dY7o/e3aKagH0ETy FvoQyLGmZC+buDAuXB4YPBD2rxMdsFO4lWMijKZI6NEvIYg9aKsoKZoMFEbgShXN Wdny7hTax5nbxzbvuR1RpM4QBwi6wW7oTQspIRQtz7Amahj8Ypz+fQfYElsThNPb lamkmIo0YrA7/JNeGAC0AFIsZhZ7z8BF4Aq6xltiwTQbhzelcyygHk2Ah2iQBm8a aVFjaDf3W4BgG4DjBzB+p5XfTbS8IbXcnx6/9/WfH1GImNTKW65IFUwmpJQNj0nm 3gprDTJswc+71qZ2A/hiWMpMmwc8hjOLgsPk4HNfvjarMZWFktPcGi7IFfjItFH3 iVZ8K3dFy61sI1D/rPQ= =bSZP -----END PGP SIGNATURE----- --OxDG9cJJSSQMUzGF-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 13:49:35 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 870CE632 for ; Mon, 29 Sep 2014 13:49:35 +0000 (UTC) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 384C5CA0 for ; Mon, 29 Sep 2014 13:49:35 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.9/8.14.9) with ESMTP id s8TDnXGJ081135; Mon, 29 Sep 2014 09:49:33 -0400 (EDT) (envelope-from lidl@pix.net) Message-ID: <5429636D.2000305@pix.net> Date: Mon, 29 Sep 2014 09:49:33 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: FreeBSD 10.1-BETA3 Now Available References: <20140928155118.GA75063@hub.FreeBSD.org> In-Reply-To: <20140928155118.GA75063@hub.FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:49:35 -0000 The sparc64 images are not retrievable from the ftp server. Both the: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/FreeBSD-10.1-BETA3-sparc64-disc1.iso And the .xz file: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/FreeBSD-10.1-BETA3-sparc64-disc1.iso.xz Cannot be accessed. Thanks for your attention. -Kurt From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 13:52:54 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5CC6F84F for ; Mon, 29 Sep 2014 13:52:54 +0000 (UTC) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 38A21D6E for ; Mon, 29 Sep 2014 13:52:54 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.9/8.14.9) with ESMTP id s8TDqr9Z081162; Mon, 29 Sep 2014 09:52:53 -0400 (EDT) (envelope-from lidl@pix.net) Message-ID: <54296435.40006@pix.net> Date: Mon, 29 Sep 2014 09:52:53 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: FreeBSD 10.1-BETA3 Now Available References: <20140928155118.GA75063@hub.FreeBSD.org> <5429636D.2000305@pix.net> In-Reply-To: <5429636D.2000305@pix.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:52:54 -0000 On 9/29/14 9:49 AM, Kurt Lidl wrote: > The sparc64 images are not retrievable from the ftp server. > > Both the: > ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/FreeBSD-10.1-BETA3-sparc64-disc1.iso > > > And the .xz file: > ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/FreeBSD-10.1-BETA3-sparc64-disc1.iso.xz > > > Cannot be accessed. > > Thanks for your attention. > > -Kurt Experimenting a bit, I was able to fetch the .xz file by manually changing the hostname to be ftp5.us.freebsd.org. So, whatever the problem, it can be worked around by changing to a different ftp mirror. -Kurt From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 13:55:08 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DDEE3984; Mon, 29 Sep 2014 13:55:07 +0000 (UTC) Date: Mon, 29 Sep 2014 09:55:03 -0400 From: Glen Barber To: Tim Daneliuk Subject: Re: Still Seeing Parallel Build Breakage In 10.1-BETA3 Message-ID: <20140929135503.GM75063@hub.FreeBSD.org> References: <54295F65.3090600@tundraware.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GEl8M6OaEs83Y7Jz" Content-Disposition: inline In-Reply-To: <54295F65.3090600@tundraware.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Warner Losh , FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:55:08 -0000 --GEl8M6OaEs83Y7Jz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [CC imp@] On Mon, Sep 29, 2014 at 08:32:21AM -0500, Tim Daneliuk wrote: > FYI - >=20 > Code Branch: >=20 > /usr/src>svn info > Path: . > Working Copy Root Path: /usr/src > URL: svn://svn.freebsd.org/base/stable/10 > Relative URL: ^/stable/10 > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 272279 > Node Kind: directory > Schedule: normal > Last Changed Author: wblock > Last Changed Rev: 272275 > Last Changed Date: 2014-09-28 18:15:18 -0500 (Sun, 28 Sep 2014) >=20 >=20 > Buildworld is fine with -j4, but buildkernel blows out: >=20 This is fixed in head in revision r268376, and planned to be merged to stable/10 soon (so it will be included in 10.1-RELEASE). A random, but interesting datapoint: the fts_read() failure seems to be correlated to the processing speed (CPU and RAM) versus the speed of the disks. On one of the RE build machines, prior to r268376 in head/, I could consistently reproduce this particular build failure when building with '-j' values of 24+. On one of the newer RE machines, both world and kernel are build with '-j48', and I have yet to see this particular build failure in the stable/10 branch. The main difference between the two machines is that the second machine mentioned is configured with proper partition alignment and ashift=3D12 versus ashift=3D9. Glen --GEl8M6OaEs83Y7Jz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKWS3AAoJEAMUWKVHj+KTcp4P/jlFEDJ/beKnc174o6ZK5UNV 4ofvUqfUvuyAmo5z5gkfR4bVRZlIPszhoW3MSF9MA7aVGb26E9NfcH9EI6XjHvA0 ohc7upRsMmzluJz+2nQ71sY31MgdOkhyG3GoDeRsLc6Bp133kPNmg6PC/W0z7OyD 8Muq2oBfcvyWQ5Ev/eyyzPRMQN0v1/v4ogl9ODdCQe2nra9y6yCicVIG2M60MhJF kkcAqfi5Sgq1dm7ihqRHx75NxS3f/Ag1H85Yrk/uRwU03L7SSc9PUm39RVKIzRz4 024aRSQLvwGLm5kMw2rkxEpHyevUrZ4730hwxCOKMYRgQNRxaFXbylDAkJzAa/Q1 pty4YAsPYs4ZbEP6VhRogoLOC8IhAAU3O5FvHvqwaZ2sPVpD2MTvT+knQWjYgEaw NpSdjuMkY6nShimllWg4bhhX86zv2fGXrG++s1aYDjvZEHOwiwvdo5zhHEn0HG1Y kORUM54BLe4F4vfDu2zk+28NVwy93fQ45hP0Of374dLqngFP1vvDUccXVe5dLw0H CkIlQScIsefcNbIpB/quTXOy7jNDUQkVr+O5KmE3npmseMh/QBPzs1+QER0FDRSQ BsHuI3sDL70T02Grs29+Y61YeEMVy8RyoPZCFTXj3ccbTtiLnlae6TOM9cLSO+3b yScrR+ZR0Kexjx9zxK+p =Taqi -----END PGP SIGNATURE----- --GEl8M6OaEs83Y7Jz-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 13:56:26 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 909D8A7B; Mon, 29 Sep 2014 13:56:25 +0000 (UTC) Date: Mon, 29 Sep 2014 09:56:22 -0400 From: Glen Barber To: Kurt Lidl Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929135622.GN75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <5429636D.2000305@pix.net> <54296435.40006@pix.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pYU1PAVEPli1Yt9/" Content-Disposition: inline In-Reply-To: <54296435.40006@pix.net> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:56:26 -0000 --pYU1PAVEPli1Yt9/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 29, 2014 at 09:52:53AM -0400, Kurt Lidl wrote: > On 9/29/14 9:49 AM, Kurt Lidl wrote: > >The sparc64 images are not retrievable from the ftp server. > > > >Both the: > >ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/FreeBSD-10.1-= BETA3-sparc64-disc1.iso > > > > > >And the .xz file: > >ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/FreeBSD-10.1-= BETA3-sparc64-disc1.iso.xz > > > > > >Cannot be accessed. > > > >Thanks for your attention. > > > >-Kurt >=20 > Experimenting a bit, I was able to fetch the .xz file by manually > changing the hostname to be ftp5.us.freebsd.org. So, whatever the > problem, it can be worked around by changing to a different ftp mirror. >=20 Hmm.. I'll take a look. Thank you for the report. Glen --pYU1PAVEPli1Yt9/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKWUGAAoJEAMUWKVHj+KT0YUP/2rR507u5VXbtfaDGKJJT2xF 1twt1Zva+WVo8HvUMdJi5L0UGzc69OnNwPxTvtNdah4+r2vKOXmsxw4w1p2Ya9Gi 2Z1wzdsw+rjiLYgmKNrkDu+fRbYJpWrH4iSCMLaxBN4kJw8a7DW7DUAjjJyI9Byc uzQLL7hx9A/vYHkSkUpnLkI/mg/HXc0l6zAnThUDUC/blX5b2VlYqK2hfpdHcdJw +48oRWNkR7sHt2Vj/kteFm/yeo5HVixGagGT+mmvDCTCiRs+AUjxoGbkR3K1IsVD 7kuvxL8psg+xBdGU8ALGfqkm1EjS9NtGSb0AaKyWTuYAr4kt3ZMCVV55G/GD0bSv KCFGiwBt+KCiSXr5rck4ef6Z1OaiMOD987KaKiCJ6jpmfEyH+w2S/J1vhSjftyda XHgweOA6P31hAUnGzsV6ql1vizWKpOLxeF+Ro1/vS6zzR7vhnOwIJIFFRCwX8UWT +NhnDAEb55Ny6RllBsVgtTl0xGzuGQMxWH7G5awCK8GwE0A/xqSSd+5mJuZhQXEV 5bhax7U7u0ZSq/GJdVyR7dITkq+b6zLynhhvuSwidWjMB970jNh2JMccd3qv3amz 7nkLtUU8tCrfR24ur+5EidQMkTOZt7SstbPIYBWSDRehj510ZYjIn5Dak56sqojd y7foqPrXenL+/kKgcnbX =bPqW -----END PGP SIGNATURE----- --pYU1PAVEPli1Yt9/-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 14:14:05 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 81A8B69 for ; Mon, 29 Sep 2014 14:14:05 +0000 (UTC) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 53EA3FB5 for ; Mon, 29 Sep 2014 14:14:04 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by gateway2.nyi.internal (Postfix) with ESMTP id 631BB19FD for ; Mon, 29 Sep 2014 10:14:03 -0400 (EDT) Received: from web6 ([10.202.2.216]) by compute2.internal (MEProxy); Mon, 29 Sep 2014 10:14:03 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=b33U5th8c/NIktwW1nSK5X2o LjU=; b=E06MuGPWUQ9WlSltNlOTh4M9llQXflcfqjw2HhcFx2/bdjUdFKjHM5CN lyvKjKE/GWKp+gqg5otm1SRaZUWYthnx6GuIcXyOB/yM/e3Yuat2UNnwoX3jaRN+ sNAFePKCrcITuSk5626sXvdAeL55aukn44KuNsiHidRiHcCcfGw= Received: by web6.nyi.internal (Postfix, from userid 99) id 3660E5A31A; Mon, 29 Sep 2014 10:14:03 -0400 (EDT) Message-Id: <1412000043.1250852.172976197.0B46058D@webmail.messagingengine.com> X-Sasl-Enc: gXgLJwd0klZanC17pWD1OVj7ysiuQ7SbbmZtobZ+y0hp 1412000043 From: Mark Felder To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-cad53418 In-Reply-To: <541DE9FC.2090003@gmx.net> References: <541DE9FC.2090003@gmx.net> Subject: Re: xzgrep: incomplete results on larger files Date: Mon, 29 Sep 2014 09:14:03 -0500 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 14:14:05 -0000 On Sat, Sep 20, 2014, at 15:56, Stefan Ehmann wrote: > I observed the following behavior on 10.1-BETA1 r271683M (amd64): > > xzgrep doesn't search the complete file: > $ seq 10000 | xz > seq.xz > $ xzgrep -c . seq.xz > 6775 > > Using regular grep works as expected: > $ xzcat seq.xz | grep -c . > 10000 > > Processing seems to stop after 32KB (uncompressed). > Wow, this is bizarre... Compression with xz is getting more and more popular. This may have bit me a few times and I didn't even know it! I'll see what I can to do bring this to someone's attention. From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 14:24:50 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 837AC653; Mon, 29 Sep 2014 14:24:49 +0000 (UTC) Date: Mon, 29 Sep 2014 10:24:45 -0400 From: Glen Barber To: Erich Dollansky Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <20140929142445.GQ75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929090149.34aa1927@X220.alogt.com> <20140929011243.GF75063@hub.FreeBSD.org> <20140929092835.6313304a@X220.alogt.com> <20140929023616.GG75063@hub.FreeBSD.org> <20140929113230.144be5da@X220.alogt.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nDoN7yiCo0/V4Duf" Content-Disposition: inline In-Reply-To: <20140929113230.144be5da@X220.alogt.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-arm@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 14:24:50 -0000 --nDoN7yiCo0/V4Duf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 29, 2014 at 11:32:30AM +0800, Erich Dollansky wrote: > On Sun, 28 Sep 2014 22:36:16 -0400 > Glen Barber wrote: > > On Mon, Sep 29, 2014 at 09:28:35AM +0800, Erich Dollansky wrote: > > Why not try the images already available here? > >=20 > > http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/ >=20 > yes, why not. I downloaded it already and still start to test it later. >=20 > Is there somewhere a documentation of how this image was build? >=20 The arm images are currently built using Crochet. The documentation is in the README.md file here: https://github.com/kientzle/crochet-freebsd Glen --nDoN7yiCo0/V4Duf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUKWutAAoJEAMUWKVHj+KTX0gP/RsiT7fNRO7VH+jillRFw32v lMCcZ/BSM+IKTHTA2VhhYcw2dhiv0eJlFIW6cLafbU3GVdjWFlPXh3l5MvT2UtHI gTd/UnWrG82PQJXkn8f2K8h5k7ARLUBDxiIUsR77KnMLvtCet4LMoB0+9YhpD5hG hXF1gyZ8QNFJxotb218i1SmfRE7Y0shk3K+wBfiHsIUGElxxh6+jByypSPGbU75I piNGEwDnKrs3ItIaqLVtpZSIi5wT1JyECFT07sboSWnY8IHQHbcmrObfdvpyhhxr G8t31gnUKUhUY8V/Lkmt2ScXq0qL1NrYKMQm97laYBvTpvxoIhCQ0CKh+hzZ7ODJ DrnonDTOhy5RA8Sy26cRVmVljRNotunjISzDhKSeyJ5+0UD43oaRvmp4ch1AutzG /SsZniRUU/rG6S3yDkCFPYnIDqRCKkoluoq6ZN4vbOyczbfk5JFAwce+pJ57EUvm In6mAr7vfmvuUgSwKQbeQptxnGtPKMCc88+Xuk7Ue1hxpz+MG9QCajfDy+5dq0EB +zmau8+CvXutQt6ufoweCfE6E8bjkkOx6POQbW8uDtkkBCPrIwTDGi9OAcC/3ROb TaDdbnsmPW0e7iQD+UGpZKqlV+sGsC+fLnVY4Pt/RKdcYUQAOunO5djXC78It1LN Jwqe2E1yVnQOe6FKQ6AO =Ak+q -----END PGP SIGNATURE----- --nDoN7yiCo0/V4Duf-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 14:31:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CFAB9955; Mon, 29 Sep 2014 14:31:13 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CA971A6; Mon, 29 Sep 2014 14:31:13 +0000 (UTC) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.5/8.14.5) with ESMTP id s8TEVTVc010237; Mon, 29 Sep 2014 07:31:35 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: (from www@localhost) by udns.ultimatedns.net (8.14.5/8.14.5/Submit) id s8TEVMgr010213; Mon, 29 Sep 2014 07:31:22 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net ([2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Mon, 29 Sep 2014 07:31:24 -0700 (PDT) Message-ID: In-Reply-To: References: Date: Mon, 29 Sep 2014 07:31:24 -0700 (PDT) Subject: Re: dmesg seems broken From: "Chris H" To: "Brandon Allbery" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd current , freebsd stable , freebsd amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 14:31:13 -0000 > On Sat, Sep 27, 2014 at 7:22 PM, Chris H wrote: > >> Where can I get that information? Where was it sent? Why am I >> not allowed to view it? >> > > Sounds to me like the kernel ring buffer is now too small for all the early > boot messages? OK more investigation indicates that bumping kern.msgbufsize will return the missing bits. Maybe this is what you were trying to tell me. ;) Anyway. Anyone know why was this tunable reduced? I don't experience this on RELENG_8, or 11-CURRENT. FWIW I have loader.conf(5) set to boot verbose. But still didn't get the info expected. :( Thanks for the reply, Brandon. --Chris > > -- > brandon s allbery kf8nh sine nomine associates > allbery.b@gmail.com ballbery@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 17:06:31 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 444CDBEB for ; Mon, 29 Sep 2014 17:06:31 +0000 (UTC) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1F9B77D1 for ; Mon, 29 Sep 2014 17:06:31 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.9/8.14.9) with ESMTP id s8TH6TLP082472; Mon, 29 Sep 2014 13:06:29 -0400 (EDT) (envelope-from lidl@pix.net) Message-ID: <54299195.2010900@pix.net> Date: Mon, 29 Sep 2014 13:06:29 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-stable Subject: FreeBSD 10.1-BETA3 - zfs bootblocks broken Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 17:06:31 -0000 I got the FreeBSD 10.1-BETA3 distribution ISO and tried two things this morning. 1) Following the system prompts, it will successfully create and install into UFS filesystems. 2) Following a procedure that I've used many times in the past to install the sparc64 onto ZFS-only media, it fails to boot. The "zfsloader" program is failing: Executing last command: boot disk0 Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0 File and args: >> FreeBSD/sparc64 ZFS boot block Boot path: /pci@1f,0/pci@1/scsi@8/disk@0,0:a Consoles: Open Firmware console Memory Address not Aligned I reported this problem with the 10.1-BETA2 iso as well. I spent some time this last weekend tracking down the cause of this failure, using the 10.1-BETA2 code. I've narrowed the failure down to this call, in .../sys/boot/zfsimpl.c (line 1155): error = zio_decompress_data(cpfunc, pbuf, BP_GET_PSIZE(bp), buf, BP_GET_LSIZE(bp)); I don't know when this was broken. I have an ISO image I created from r264194 that works fine. (Built back on 06-Apr-2014.) Thanks for any help. -Kurt From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 18:58:24 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D1FB44E7 for ; Mon, 29 Sep 2014 18:58:24 +0000 (UTC) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 188F86B6 for ; Mon, 29 Sep 2014 18:58:23 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id z12so42386lbi.16 for ; Mon, 29 Sep 2014 11:58:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=T8/BsSYd0Vwnr8SuGEj5VVm/00idpu/xOiK7tkoE2As=; b=Ct+6LGzzjc+QFg/a7ltunwpM8piuCjkuDeTEORGQ2Qf5u14jC9pIwIX7qXEeBN2ZbD /6uNz2DLpWl+COkRahpqdDlP8yWPUcUnxqvt3IMAGB6UCpsVJ98YLXThjuASgJWuoM4h wvnCqxq1pgpXs5hm7p2YgDDxy5+np9zBFBa6NM+H03I8MtRx6PrbZTkydrB29Jd0R4D6 G0bZsxLZr3upFjGdWVFCh8q6echp47/C3aod3Y5o3Y1qU91gO9B0Hc3EaIPCNi43BZmv r+Mdc7v1zNUThlO3pW0UwftFP4UIv6d0hQXbPGwHmfa7OLBZDb1A+YXwb0kvi/8A2DNe hwFA== MIME-Version: 1.0 X-Received: by 10.152.5.40 with SMTP id p8mr42179973lap.32.1412017101414; Mon, 29 Sep 2014 11:58:21 -0700 (PDT) Received: by 10.114.216.37 with HTTP; Mon, 29 Sep 2014 11:58:20 -0700 (PDT) Date: Mon, 29 Sep 2014 11:58:20 -0700 Message-ID: Subject: 10.1-BETA2 possible kernel memory leak in routing table From: Rumen Telbizov To: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 18:58:24 -0000 Hello everyone, I have recently upgraded one of our main firewalls from FreeBSD 9.2 to10.1-BETA2 (r271983). It has been running in production since last Thursday and overall I am pretty happy with it and seeing significant improvements in performance. However I do notice this morning that the *wired* portion of the memory has been steadily growing over the weekend and is now over a few gigabytes. Here's a graph: [image: Inline image 2] The switchover was done on late 25th when production traffic started flowing through it. I checked vmstat -m and noticed that the *routetbl* is pretty large - 2.8GB and keeps on growing. Here's a few minutes worth of monitoring it: # while true; do date; vmstat -m | grep routetbl; sleep 60; done Type InUse MemUse HighUse Requests Size(s) Mon Sep 29 18:27:55 UTC 2014 routetbl 5988792 2888491K - 14285826 32,64,128,256,512,2048 Mon Sep 29 18:28:55 UTC 2014 routetbl 5990120 2889131K - 14288972 32,64,128,256,512,2048 Mon Sep 29 18:29:55 UTC 2014 routetbl 5991448 2889771K - 14292352 32,64,128,256,512,2048 Mon Sep 29 18:30:55 UTC 2014 routetbl 5992776 2890411K - 14295464 32,64,128,256,512,2048 Mon Sep 29 18:31:55 UTC 2014 routetbl 5994104 2891051K - 14298576 32,64,128,256,512,2048 Mon Sep 29 18:32:55 UTC 2014 routetbl 5995432 2891691K - 14301904 32,64,128,256,512,2048 Mon Sep 29 18:33:55 UTC 2014 routetbl 5996096 2892011K - 14303624 32,64,128,256,512,2048 Mon Sep 29 18:34:55 UTC 2014 routetbl 5997422 2892650K - 14306980 32,64,128,256,512,2048 Mon Sep 29 18:35:55 UTC 2014 routetbl 5998750 2893290K - 14310092 32,64,128,256,512,2048 Mon Sep 29 18:36:55 UTC 2014 routetbl 6000078 2893930K - 14313204 32,64,128,256,512,2048 Mon Sep 29 18:37:55 UTC 2014 routetbl 6001406 2894570K - 14316532 32,64,128,256,512,2048 Mon Sep 29 18:38:55 UTC 2014 routetbl 6002734 2895210K - 14319644 32,64,128,256,512,2048 Mon Sep 29 18:39:55 UTC 2014 routetbl 6004062 2895850K - 14323024 32,64,128,256,512,2048 Mon Sep 29 18:40:56 UTC 2014 routetbl 6004726 2896170K - 14324745 32,64,128,256,512,2048 Mon Sep 29 18:41:56 UTC 2014 routetbl 6006054 2896810K - 14327857 32,64,128,256,512,2048 Mon Sep 29 18:42:56 UTC 2014 routetbl 6007382 2897450K - 14331185 32,64,128,256,512,2048 Mon Sep 29 18:43:56 UTC 2014 routetbl 6008710 2898090K - 14334297 32,64,128,256,512,2048 As you can see for this interval it grew 9599K (2898090-2888491). The routing table does not change at all on this machine. netstat -rn | wc -l reports 145 entries all the time. As a comparison on the old, inactive FreeBSD 9.2 firewall I have: # vmstat -m | grep routetbl routetbl 451 98K - 7336488 32,64,128,256,512,1024 Here are some configuration details of the system. loader.conf: autoboot_delay="3" zfs_load="YES" vfs.root.mountfrom="zfs:zroot/freebsd10" vfs.zfs.arc_max="500M" kern.geom.label.gptid.enable="0" hw.ix.num_queues="12" hw.ix.txd="4096" hw.ix.rxd="4096" sysctl.conf: # CARP related net.inet.carp.allow=1 net.inet.carp.preempt=1 net.inet.carp.log=2 # Stop sending ICMP redirects net.inet.ip.redirect=0 # Fast Forwarding net.inet.ip.fastforwarding=1 # Enable better lacp/lagg transmit distribution net.link.lagg.default_use_flowid=0 I could provide additional debug information upon request. Your help is appreciated. Regards, -- Rumen Telbizov Unix Systems Administrator From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 20:05:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6459697A for ; Mon, 29 Sep 2014 20:05:13 +0000 (UTC) Received: from fs.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "NewFS.denninger.net", Issuer "NewFS.denninger.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D49FEEB for ; Mon, 29 Sep 2014 20:05:12 +0000 (UTC) Received: from [192.168.1.40] (localhost [127.0.0.1]) by fs.denninger.net (8.14.9/8.14.8) with ESMTP id s8TK4osF045209 for ; Mon, 29 Sep 2014 15:04:50 -0500 (CDT) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (TLS/SSL) [192.168.1.40] by Spamblock-sys (LOCAL/AUTH); Mon Sep 29 15:04:50 2014 Message-ID: <5429BB41.8080609@denninger.net> Date: Mon, 29 Sep 2014 15:04:17 -0500 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: MPS Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080300030308020709080300" X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 20:05:13 -0000 This is a cryptographically signed message in MIME format. --------------ms080300030308020709080300 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Has anyone found a set of configuration settings for the mps driver (LSI SAS series cards) that gets the following situation under control? I have a machine here with one of these cards and a SAS expander. The expander has 16 ports, the card has 8 -- one connector attached to the expander. So I have 20 potential drives associated with this adapter. The issue is that the driver makes utterly no sense when it comes to assigning drive designations. In theory it should enumerate in series; that is, target 0 on the card should be da0, target 1 da1, etc. This assumes there are no gaps in the attached drives; if there are then things may move around, which is why some people wire drives. Ok so far, but it doesn't behave that way! This is the excerpt of what it returns: root@Dbms-10:/boot # dmesg|grep mps mps0: port 0xc000-0xc0ff mem 0xfbb3c000-0xfbb3ffff,0xfbb40000-0xfbb7ffff irq 30 at device 0.0 on pci3 mps0: Firmware: 19.00.00.00, Driver: 19.00.00.00-fbsd mps0: IOCCapabilities: 1285c ses0 at mps0 bus 0 scbus0 target 8 lun 0 da0 at mps0 bus 0 scbus0 target 0 lun 0 da1 at mps0 bus 0 scbus0 target 1 lun 0 da2 at mps0 bus 0 scbus0 target 2 lun 0 da3 at mps0 bus 0 scbus0 target 3 lun 0 *da4 at mps0 bus 0 scbus0 target 6 lun 0** **da5 at mps0 bus 0 scbus0 target 7 lun 0* Those last two are the drives the card identifies as being on targets 0 and 1 when looked at in the BIOS. The other four drives (0-3) are on the SAS expander -- and there's a two drive "gap" in the targets identified as well which has zippo for logic associated with it. Even more-oddly if I swap the plugs -- that is, plug the two boot disks into the OTHER connector (putatively targets 4-7) and put the SAS expander on the 0-3 port connector the BIOS *does* show the target shift but the machine, when it boots, still places those two drives on targets 6 and 7! There is nothing in /boot/loader.conf or /boot/device.hints that relates to these devices at all. I would like to wire down the various ports so Drive Bay #x corresponds to da[x] but how can you when you don't know what order they will come up in predicated on either the physical port they're occupying or, for that matter, what the card's BIOS shows them as? I looked in the driver's man page and saw nothing related to this; I get around it by labeling the drives and then using "glabel list" to see what da[x] number it grabbed if I need to pull a disk while the machine is up, but this is a rather-unfriendly way to handle that. --=20 Karl Denninger karl@denninger.net /The Market Ticker/ --------------ms080300030308020709080300 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFTzCC BUswggQzoAMCAQICAQgwDQYJKoZIhvcNAQEFBQAwgZ0xCzAJBgNVBAYTAlVTMRAwDgYDVQQI EwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExLzAtBgkqhkiG9w0BCQEWIGN1c3Rv bWVyLXNlcnZpY2VAY3VkYXN5c3RlbXMubmV0MB4XDTEzMDgyNDE5MDM0NFoXDTE4MDgyMzE5 MDM0NFowWzELMAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExFzAVBgNVBAMTDkthcmwg RGVubmluZ2VyMSEwHwYJKoZIhvcNAQkBFhJrYXJsQGRlbm5pbmdlci5uZXQwggIiMA0GCSqG SIb3DQEBAQUAA4ICDwAwggIKAoICAQC5n2KBrBmG22nVntVdvgKCB9UcnapNThrW1L+dq6th d9l4mj+qYMUpJ+8I0rTbY1dn21IXQBoBQmy8t1doKwmTdQ59F0FwZEPt/fGbRgBKVt3Quf6W 6n7kRk9MG6gdD7V9vPpFV41e+5MWYtqGWY3ScDP8SyYLjL/Xgr+5KFKkDfuubK8DeNqdLniV jHo/vqmIgO+6NgzPGPgmbutzFQXlxUqjiNAAKzF2+Tkddi+WKABrcc/EqnBb0X8GdqcIamO5 SyVmuM+7Zdns7D9pcV16zMMQ8LfNFQCDvbCuuQKMDg2F22x5ekYXpwjqTyfjcHBkWC8vFNoY 5aFMdyiN/Kkz0/kduP2ekYOgkRqcShfLEcG9SQ4LQZgqjMpTjSOGzBr3tOvVn5LkSJSHW2Z8 Q0dxSkvFG2/lsOWFbwQeeZSaBi5vRZCYCOf5tRd1+E93FyQfpt4vsrXshIAk7IK7f0qXvxP4 GDli5PKIEubD2Bn+gp3vB/DkfKySh5NBHVB+OPCoXRUWBkQxme65wBO02OZZt0k8Iq0i4Rci WV6z+lQHqDKtaVGgMsHn6PoeYhjf5Al5SP+U3imTjF2aCca1iDB5JOccX04MNljvifXgcbJN nkMgrzmm1ZgJ1PLur/ADWPlnz45quOhHg1TfUCLfI/DzgG7Z6u+oy4siQuFr9QT0MQIDAQAB o4HWMIHTMAkGA1UdEwQCMAAwEQYJYIZIAYb4QgEBBAQDAgWgMAsGA1UdDwQEAwIF4DAsBglg hkgBhvhCAQ0EHxYdT3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFHw4 +LnuALyLA5Cgy7T5ZAX1WzKPMB8GA1UdIwQYMBaAFF3U3hpBZq40HB5VM7B44/gmXiI0MDgG CWCGSAGG+EIBAwQrFilodHRwczovL2N1ZGFzeXN0ZW1zLm5ldDoxMTQ0My9yZXZva2VkLmNy bDANBgkqhkiG9w0BAQUFAAOCAQEAZ0L4tQbBd0hd4wuw/YVqEBDDXJ54q2AoqQAmsOlnoxLO 31ehM/LvrTIP4yK2u1VmXtUumQ4Ao15JFM+xmwqtEGsh70RRrfVBAGd7KOZ3GB39FP2TgN/c L5fJKVxOqvEnW6cL9QtvUlcM3hXg8kDv60OB+LIcSE/P3/s+0tEpWPjxm3LHVE7JmPbZIcJ1 YMoZvHh0NSjY5D0HZlwtbDO7pDz9sZf1QEOgjH828fhtborkaHaUI46pmrMjiBnY6ujXMcWD pxtikki0zY22nrxfTs5xDWGxyrc/cmucjxClJF6+OYVUSaZhiiHfa9Pr+41okLgsRB0AmNwE f6ItY3TI8DGCBQowggUGAgEBMIGjMIGdMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHRmxvcmlk YTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExDMRwwGgYD VQQDExNDdWRhIFN5c3RlbXMgTExDIENBMS8wLQYJKoZIhvcNAQkBFiBjdXN0b21lci1zZXJ2 aWNlQGN1ZGFzeXN0ZW1zLm5ldAIBCDAJBgUrDgMCGgUAoIICOzAYBgkqhkiG9w0BCQMxCwYJ KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDA5MjkyMDA0MTdaMCMGCSqGSIb3DQEJBDEW BBQyWXW/LkZOt02jdSsBTWryqTJvUjBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjAL BglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFA MAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIG0BgkrBgEEAYI3EAQxgaYwgaMwgZ0xCzAJBgNV BAYTAlVTMRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoT EEN1ZGEgU3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExLzAtBgkq hkiG9w0BCQEWIGN1c3RvbWVyLXNlcnZpY2VAY3VkYXN5c3RlbXMubmV0AgEIMIG2BgsqhkiG 9w0BCRACCzGBpqCBozCBnTELMAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExEjAQBgNV BAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1zIExMQzEcMBoGA1UEAxMTQ3Vk YSBTeXN0ZW1zIExMQyBDQTEvMC0GCSqGSIb3DQEJARYgY3VzdG9tZXItc2VydmljZUBjdWRh c3lzdGVtcy5uZXQCAQgwDQYJKoZIhvcNAQEBBQAEggIAGQrzw4H0gcAQk0sMXwwqCe+93+Yo z34Sa+VLJBE9CogyopDlL2MDFjzMGLzxCPcoTRLruceyBgDxoa9TwlDq/ZOirqiWSZUQSVbm m5uUUm3sjth4Nvh9fZcQCf5XJO9YWqfr6LZSYZIexC+jSnvy/UJzUG3edYsTv82DhphlPpEF GL+l+JFdczcjoLVH6pzdCjLoieiM+lj2iECAwuQLPlCmzyafdW7jb5Tr8SKQer0saYW4dQHq 669ypLNrIT20a9FPhHOapXbYhbxQxzbhZVXr4WRG9Y+m+8bXMGJ7LrFgLzxbmYl8zQPIboXt fXanIE4fO0FD0vsqu3Utcu2DHiaC5hqlfMXPC2PJnThaOtwN/ES2Ery+vvC/OT1xPBj+YSCq rhBqtvb/NUZ9mVETQH/wr+loigAk3X9ywjTxmsbRLgpxEiRm4o/bk+aDq5MNcT76PPmXntJF Tf8nOIVNPancXzonm6pQ46tCOfVfTqbPIJ+MULfatAQq96Fpx2aXuzTc722KEaYrm84kNUQV pAz14zKubto+1J8vMgVgkAyRvn58T6QFEZiMpG0fA9XO9+JLePpvdFrYMLVaASfZqMrKimZE LO8GW8J7+PkmnbQY5JjjYdiBI6ogm1AG2+WnXs2ORG0oI7u4qRIsb73ZzVKmGSWK1XeQXTAU GB1seX8AAAAAAAA= --------------ms080300030308020709080300-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 20:20:16 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DEE98CE2 for ; Mon, 29 Sep 2014 20:20:16 +0000 (UTC) Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69A7EB2 for ; Mon, 29 Sep 2014 20:20:16 +0000 (UTC) Received: by mail-lb0-f173.google.com with SMTP id 10so16758505lbg.4 for ; Mon, 29 Sep 2014 13:20:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type; bh=R+qk2biGWzp1XrZADYlzHStAU3MEHVQguCo8CzQeCiU=; b=TLx45kB36ZQ4awR9OcYdSVj1kA5OE9q2tcXywig67zmGGHT+TXJNtDBNy1APGwEzRh vEGLyNehRAQLgav3R9MyiLEJ3qlqfXoHSYIBDKZgSmpxfAEJUrTMGL2qLfbA17ob6IS/ XLfNen7irOHV87lbQ1ttwLNKf8NLaCUjoOO0CgZ61RwXTDv61Ahqlei+IdlWHjsUbNvu 85R3ych+hxftsgBhca0lNZPqChvuGUEF/jvSuSS9W8YgmCf1K7q3Sx0qh70v7c+Ff4/u J0HBbq7o8/Ic5xPKTo5rceNLAxSvzBw+cKEfXwr1WCJh451swHlwqECYVvDeixwe79Ya eBVA== X-Received: by 10.112.16.129 with SMTP id g1mr39352393lbd.19.1412022014361; Mon, 29 Sep 2014 13:20:14 -0700 (PDT) Received: from localhost (exit2.tor-proxy.net.ua. [46.28.68.158]) by mx.google.com with ESMTPSA id rl6sm5234055lac.17.2014.09.29.13.20.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Sep 2014 13:20:12 -0700 (PDT) From: marekrud@gmail.com To: freebsd-stable@freebsd.org Subject: vt does not resume properly after zzz Date: Mon, 29 Sep 2014 22:20:06 +0200 Message-ID: <864mvqfabt.fsf@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 20:20:17 -0000 --=-=-= Content-Type: text/plain Hi all, I have configured vt by adding `kern.vty=vt' to /boot/loader.conf. After suspending the system using zzz and resuming, I can only see black screen. The system seem to be running, but the display is off. I was able to reproduce it on two different computers running 10.1-BETA2 and 10.1-BETA3. Is there a simple way to fix it? Should I report it to Bugzilla? Thank you for help! Marek --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJUKb79AAoJEJCuhmH9YEALX4MP/3iZMpfqUKdDNL59Z7i9HgXR 7hIFYypowVTcKzTaSlceRdDY9LaduuUBbM9Kk0I0aJpTYsPpWAF4CoFkobSxHY2j J0GcPwdmy4qWb814RtGuPnDRenzLUUZxxz24dA73C1q+aAoXgYmA2aDUm6wvPBwt QjiqqP6VuHxQCTcNKQaWS+z/qBTkWdWCOMbVZMeARa7ybqqL2J4a4lF9h+fb0Wv2 qsMSkTZkeRRgm75c8Zs80PWHt4UIcag7uJ8uMwXBeLtgWqgyA4c8USZdorIdS6fi PQl1Bo9ctxf32oIimckytEqh0RxE/jQMKOX7HDwE91G8vagsR8erk2cds7bvfVOY SdkyNyLVRxtzlbZfzaX8RzoljG9Crl7/fZFJNPfFhJh9Kqs7eEZBmRwtm4weRw2d 8xW9aDRYR7KLnmzjY/f32nA1SkZCQHALYI6SX6a0CqSkqDqmxYOI9gvzg7q3Uj8P vbb7+lOsh9HY15S9woxuRZA1ThYxaF0eA0WHijRAYNbedpV0MldgmnaRQRqMU0oB OfMkrimrUzjaNDtzPQ2CPrSS18HD2BCMh+pnaSm4tMN4aDotV1Vg1fQQdcUInsDs J8ekut1Po/T/CAqF1kgOKtIT99a0RDNEILTL08qghA+8IKyzGARgSAgts3Q4qEt6 ZIQHT1vKGKql893mZNhm =MrfY -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 20:25:21 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 52B32E6A for ; Mon, 29 Sep 2014 20:25:21 +0000 (UTC) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id E0589170 for ; Mon, 29 Sep 2014 20:25:20 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id 12FD520E7088B; Mon, 29 Sep 2014 20:25:13 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.multiplay.co.uk X-Spam-Level: ** X-Spam-Status: No, score=2.2 required=8.0 tests=AWL,BAYES_00,DOS_OE_TO_MX, FSL_HELO_NON_FQDN_1,RDNS_DYNAMIC,STOX_REPLY_TYPE autolearn=no version=3.3.1 Received: from r2d2 (82-69-141-170.dsl.in-addr.zen.co.uk [82.69.141.170]) by smtp1.multiplay.co.uk (Postfix) with ESMTPS id 46A2A20E70885; Mon, 29 Sep 2014 20:25:06 +0000 (UTC) Message-ID: <018BC41041EE4DF589EF5D834AD45BAD@multiplay.co.uk> From: "Steven Hartland" To: "Karl Denninger" , References: <5429BB41.8080609@denninger.net> Subject: Re: MPS Date: Mon, 29 Sep 2014 21:25:02 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 20:25:21 -0000 I seem to remember detection being made parallel for speed, as there can be lots of drives. The Avago guys may be able to shed more light. Regards Steve ----- Original Message ----- From: "Karl Denninger" To: Sent: Monday, September 29, 2014 9:04 PM Subject: MPS Has anyone found a set of configuration settings for the mps driver (LSI SAS series cards) that gets the following situation under control? I have a machine here with one of these cards and a SAS expander. The expander has 16 ports, the card has 8 -- one connector attached to the expander. So I have 20 potential drives associated with this adapter. The issue is that the driver makes utterly no sense when it comes to assigning drive designations. In theory it should enumerate in series; that is, target 0 on the card should be da0, target 1 da1, etc. This assumes there are no gaps in the attached drives; if there are then things may move around, which is why some people wire drives. Ok so far, but it doesn't behave that way! This is the excerpt of what it returns: root@Dbms-10:/boot # dmesg|grep mps mps0: port 0xc000-0xc0ff mem 0xfbb3c000-0xfbb3ffff,0xfbb40000-0xfbb7ffff irq 30 at device 0.0 on pci3 mps0: Firmware: 19.00.00.00, Driver: 19.00.00.00-fbsd mps0: IOCCapabilities: 1285c ses0 at mps0 bus 0 scbus0 target 8 lun 0 da0 at mps0 bus 0 scbus0 target 0 lun 0 da1 at mps0 bus 0 scbus0 target 1 lun 0 da2 at mps0 bus 0 scbus0 target 2 lun 0 da3 at mps0 bus 0 scbus0 target 3 lun 0 *da4 at mps0 bus 0 scbus0 target 6 lun 0** **da5 at mps0 bus 0 scbus0 target 7 lun 0* Those last two are the drives the card identifies as being on targets 0 and 1 when looked at in the BIOS. The other four drives (0-3) are on the SAS expander -- and there's a two drive "gap" in the targets identified as well which has zippo for logic associated with it. Even more-oddly if I swap the plugs -- that is, plug the two boot disks into the OTHER connector (putatively targets 4-7) and put the SAS expander on the 0-3 port connector the BIOS *does* show the target shift but the machine, when it boots, still places those two drives on targets 6 and 7! There is nothing in /boot/loader.conf or /boot/device.hints that relates to these devices at all. I would like to wire down the various ports so Drive Bay #x corresponds to da[x] but how can you when you don't know what order they will come up in predicated on either the physical port they're occupying or, for that matter, what the card's BIOS shows them as? I looked in the driver's man page and saw nothing related to this; I get around it by labeling the drives and then using "glabel list" to see what da[x] number it grabbed if I need to pull a disk while the machine is up, but this is a rather-unfriendly way to handle that. -- Karl Denninger karl@denninger.net /The Market Ticker/ From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 21:05:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7A04CE93 for ; Mon, 29 Sep 2014 21:05:13 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1181381C for ; Mon, 29 Sep 2014 21:05:12 +0000 (UTC) Received: from walrus.pepperland ([81.217.76.60]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MVJze-1XlLD60GTu-00YgDL; Mon, 29 Sep 2014 23:05:10 +0200 Message-ID: <5429C985.4090806@gmx.net> Date: Mon, 29 Sep 2014 23:05:09 +0200 From: Stefan Ehmann User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Mark Felder Subject: Re: xzgrep: incomplete results on larger files References: <541DE9FC.2090003@gmx.net> <1412000043.1250852.172976197.0B46058D@webmail.messagingengine.com> In-Reply-To: <1412000043.1250852.172976197.0B46058D@webmail.messagingengine.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:N5ck9Jf7JoON5HZispTppUb3oqHbDS0esRn+59nkfnxW7KdOouX dnti3KRPqVJv3G/Ivf0ugGIYH3v/V4/HqWC2VPRGqgREjNvAHeyRGgRIIJr7ieV/WZ7CvR7 NKZnBHDPJpXtiUrZRYtlk2sumddVfeK8d3Eq/r0lCuBcLz4OfZRpchLwmtoiTLuadDkspdq PkZRnE9utjVnxuYa1DskQ== X-UI-Out-Filterresults: notjunk:1; Cc: freebsd-stable@freebsd.org, gabor@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 21:05:13 -0000 On 29.09.2014 16:14, Mark Felder wrote: > > > On Sat, Sep 20, 2014, at 15:56, Stefan Ehmann wrote: >> I observed the following behavior on 10.1-BETA1 r271683M (amd64): >> >> xzgrep doesn't search the complete file: >> $ seq 10000 | xz > seq.xz >> $ xzgrep -c . seq.xz >> 6775 >> >> Using regular grep works as expected: >> $ xzcat seq.xz | grep -c . >> 10000 >> >> Processing seems to stop after 32KB (uncompressed). >> > > Wow, this is bizarre... Compression with xz is getting more and more > popular. This may have bit me a few times and I didn't even know it! > > I'll see what I can to do bring this to someone's attention. I've looked further into this issue. The original approach could never have worked since the xz library was used incorrectly. I came up with this patch today: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186861 It's getting late. So it's not tested very much and might contain bugs. -- Stefan From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 23:14:22 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 381152BE for ; Mon, 29 Sep 2014 23:14:22 +0000 (UTC) Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C4D68786 for ; Mon, 29 Sep 2014 23:14:21 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id u57so2467601wes.12 for ; Mon, 29 Sep 2014 16:14:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zQ4mZRHJL80wMkQhipPzDOkqBs4IPnQN2xGRT/QiH6w=; b=L9paBwhjbb3nnYhGvRkGgXeK50L5BX4itBjsBVpu7Ln+6tvSTm/fGEifB6VJ39kQV7 DKVLX4WpzEP4SaMfQYA9tkzNj7jp5kgacPQkJgTRCWe2XCN2vuzLeGNblYpBdnxm7WH4 CvPDTL2FnIrDnRKdCcHbzrSG4HRXJjcxdpl8dtVsg6PgDch+5XWY4m1dzJYOmTq+vSBp CgoeL7DhXCqdohI+GdENHbUrW2hjh/a7Zx7zAbpBdW3J1tBgPNNwuTlxCqvye7MLtGsF 4h3ewq9pbecuRMllBfwkVnJgIAsA6aWfXbX+vnTTWVgTyaABFPh/l0V9VGuHvlBFmRUg ryaw== MIME-Version: 1.0 X-Received: by 10.180.108.176 with SMTP id hl16mr1307173wib.4.1412032460019; Mon, 29 Sep 2014 16:14:20 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.27.86.81 with HTTP; Mon, 29 Sep 2014 16:14:19 -0700 (PDT) In-Reply-To: <864mvqfabt.fsf@gmail.com> References: <864mvqfabt.fsf@gmail.com> Date: Mon, 29 Sep 2014 16:14:19 -0700 X-Google-Sender-Auth: 8O3awhfD6yDcTo7CQQSuidonSjI Message-ID: Subject: Re: vt does not resume properly after zzz From: Kevin Oberman To: marekrud@gmail.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 23:14:22 -0000 On Mon, Sep 29, 2014 at 1:20 PM, wrote: > Hi all, > > I have configured vt by adding `kern.vty=vt' to /boot/loader.conf. > > After suspending the system using zzz and resuming, I can only see black > screen. The system seem to be running, but the display is off. I was > able to reproduce it on two different computers running 10.1-BETA2 and > 10.1-BETA3. > > Is there a simple way to fix it? Should I report it to Bugzilla? > > Thank you for help! > > Marek > Since it works fine for me and, I presume, for many others, a bit more information would help. 1. Does syscons work after resume? 2. Does the system run a graphics interface or is it text only? If so, does the problem show up in both modes? 3. WITH_NEW_XORG? (I am pretty sure it is, but confirmation would be good.) 4. What driver? 5. What graphics system? 6. What type of system? (This stuff is tied closely to BIOS, so exact hardware is significant.) 7. Contents of /etc/make.conf, /etc/src.conf, /boot/loader.conf, and /etc/sysctl.conf 8. Contents of messages log at the time of the suspend and resume 9. If not using GENERIC, your configuration file. 10. After the resume, is the system accessible over the network? 11. Is the display working but the backlight not on? Try looking at the screen in bright light and see if you can see anything on the screen I'm probably missing a few things, but those will at least help narrow it down. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 23:42:52 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5C5548AD for ; Mon, 29 Sep 2014 23:42:52 +0000 (UTC) Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 208DDA7C for ; Mon, 29 Sep 2014 23:42:51 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id rl12so5542664iec.9 for ; Mon, 29 Sep 2014 16:42:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=6Zxrs0eeofsgXFtv194+gG2m3Y+SgTRiJ3l/eJ1DL6k=; b=AYr1ERik+TStEZC/a5rBr1wsDRwyGG7kflbb2sBWG73GzucO8C/8oAkRRaA5R28dIn D1T9atUabDeeGnM+E+KIsYS1i/UwpoVYpdz0iLw+g00dNveXZPCFist0SzehgER1qHW1 l/T+/DuYUUmUNwo608vslwCwLm88KOhJ6roVxdKr6xM/QjWUQlB7nOLXtYT7x4CJDK6Y Awfr412d3c676+JkhDxvT3LbD3gNKhvFo9VbZj+w/WaNJlSVTtIGjrcc4jQUUkZCFLKR etXpmOVGvBLYluM1uIIYPRV/4d1oGjIJmQsuRq/2Ti2x4U7LB8U8kgUpyRW8/43jx1fw LOQQ== X-Gm-Message-State: ALoCoQmFsXrghTX+0beHwRjIjHUZCVuYMxDE+t7icv0EObZATRiELcdurQA9sItgYIxzKPi/YxIr X-Received: by 10.50.115.73 with SMTP id jm9mr1604404igb.3.1412034170890; Mon, 29 Sep 2014 16:42:50 -0700 (PDT) Received: from [10.1.10.201] ([50.253.99.174]) by mx.google.com with ESMTPSA id qd4sm11679677igb.19.2014.09.29.16.42.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 29 Sep 2014 16:42:49 -0700 (PDT) Sender: Warner Losh Content-Type: multipart/signed; boundary="Apple-Mail=_71A8E637-B4F9-4292-A55F-06B04418347C"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Still Seeing Parallel Build Breakage In 10.1-BETA3 From: Warner Losh In-Reply-To: <20140929135503.GM75063@hub.FreeBSD.org> Date: Mon, 29 Sep 2014 17:42:47 -0600 Message-Id: <197722BF-8687-4129-A965-6C68C1CEDCB8@bsdimp.com> References: <54295F65.3090600@tundraware.com> <20140929135503.GM75063@hub.FreeBSD.org> To: Glen Barber X-Mailer: Apple Mail (2.1878.6) Cc: Warner Losh , Tim Daneliuk , FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 23:42:52 -0000 --Apple-Mail=_71A8E637-B4F9-4292-A55F-06B04418347C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 I=92m putting together my MFC packet for this tomorrow.. I just today = finished setting up my new office after the move=85 Warner On Sep 29, 2014, at 7:55 AM, Glen Barber wrote: > [CC imp@] >=20 > On Mon, Sep 29, 2014 at 08:32:21AM -0500, Tim Daneliuk wrote: >> FYI - >>=20 >> Code Branch: >>=20 >> /usr/src>svn info >> Path: . >> Working Copy Root Path: /usr/src >> URL: svn://svn.freebsd.org/base/stable/10 >> Relative URL: ^/stable/10 >> Repository Root: svn://svn.freebsd.org/base >> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >> Revision: 272279 >> Node Kind: directory >> Schedule: normal >> Last Changed Author: wblock >> Last Changed Rev: 272275 >> Last Changed Date: 2014-09-28 18:15:18 -0500 (Sun, 28 Sep 2014) >>=20 >>=20 >> Buildworld is fine with -j4, but buildkernel blows out: >>=20 >=20 > This is fixed in head in revision r268376, and planned to be merged to > stable/10 soon (so it will be included in 10.1-RELEASE). >=20 > A random, but interesting datapoint: the fts_read() failure seems to = be > correlated to the processing speed (CPU and RAM) versus the speed of = the > disks. >=20 > On one of the RE build machines, prior to r268376 in head/, I could > consistently reproduce this particular build failure when building = with > '-j' values of 24+. On one of the newer RE machines, both world and > kernel are build with '-j48', and I have yet to see this particular > build failure in the stable/10 branch. The main difference between = the > two machines is that the second machine mentioned is configured with > proper partition alignment and ashift=3D12 versus ashift=3D9. >=20 > Glen --Apple-Mail=_71A8E637-B4F9-4292-A55F-06B04418347C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUKe54AAoJEGwc0Sh9sBEAVxAP/2dm2tbUTJdj0HyzjDa7YFTI RO7GRjoxUTz+KDrjgxQp/gJxEsNnNR0XGn/CBOmGpWZWPCncLEDNNEi6ivsloHYC gSU16iP2ep/3M/JR0SvOCN1+T97vIw3rJvWN5MhX6l0BbO6q/0oZpUV/2g1h2VC2 Xd2XslNseP4jo4/t78BXC2mjxTzSigRbbDIDcGDkRIY/rPjI2b+r9gDaNSTBDxE5 PxGhqY9yBRssJ4dGdkMFklhte0usu4KKzGEm0XrPTtCxsUkpRDMFsnMBnUoaNvdv LMV4Dvdb55vqpmElN2jOIGpzOfZ8uzgjYYkGCebAalpxKGABxBQZZGx8soClJbyV vGz7E0DZMoWjeqxOLfACLk9DXbZZf3RG/OeEmamHNhF2wIgc9ZsKkjQzHQSKYJ0K GndUFDUM+74/NmqQst5abu8ozL8rj2JnIj4fkNgEbB5C5PYAkm5mzJ8aHyUGDVqx T+75tj+hihLYVm14WrFQS6XOy/IN346tDmH2GZFEEx8Y4Ug7uAzDSB/SiuwhIoFr q4uGXqUIyvongC9g095JdpHciqbjsOFS8Z+aRLqibXAJXwpYrMH/gXxPWvUi7/Qq r2VzMADgh/twBRcZCw7OWbPgPaD9LPERswNAoSUmc/BJs8wkWFrNZpj9qL7pI4EL a/M11E7u9wEGjQeneAeG =zfqG -----END PGP SIGNATURE----- --Apple-Mail=_71A8E637-B4F9-4292-A55F-06B04418347C-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 30 00:17:12 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D649116 for ; Tue, 30 Sep 2014 00:17:12 +0000 (UTC) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 18E32DD5 for ; Tue, 30 Sep 2014 00:17:11 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id b13so5234845wgh.10 for ; Mon, 29 Sep 2014 17:17:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ZYMQH0zWEdPKPuaUEjsG0hAC3CNTrq8hsPFYx8F9NYM=; b=SZQq/ARN9Bgxbb9ypiz5Sn362dyJ9l5tOIYXZqp5xwdEQGxZyHbiSU9xv+Jr8Abv7t JxZjiuAEwOKbd/NJDHYvCYOtbspDichWMC+kGmXmSFbro3EjBPj7fpggTq8ez7GcIjNw oXcS6azma+KfhbiaWCAiHjuiEb5bNhUzXuPiclM//V2wNdFEQq47e8mc/k/7naJTQGd8 nOaZ1r1f1y5PdrX67mega5PcB9zPrpnvWrjHZJJepyjdqF7/xD+pr4hBogbAuaQRCHix YKdOWd+uRiS6RbqEJCt5YmqeA8cU9uCzfZuIGMCKj+lNmp5nbuwVCzEYeYv0FkEp3231 +ELA== MIME-Version: 1.0 X-Received: by 10.180.107.194 with SMTP id he2mr1483629wib.72.1412036230363; Mon, 29 Sep 2014 17:17:10 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.27.86.81 with HTTP; Mon, 29 Sep 2014 17:17:10 -0700 (PDT) In-Reply-To: <018BC41041EE4DF589EF5D834AD45BAD@multiplay.co.uk> References: <5429BB41.8080609@denninger.net> <018BC41041EE4DF589EF5D834AD45BAD@multiplay.co.uk> Date: Mon, 29 Sep 2014 17:17:10 -0700 X-Google-Sender-Auth: NFIbLB4zenvgcT8f-HaGrXvTOAM Message-ID: Subject: Re: MPS From: Kevin Oberman To: Steven Hartland Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD-STABLE Mailing List , Karl Denninger X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 00:17:12 -0000 On Mon, Sep 29, 2014 at 1:25 PM, Steven Hartland wrote: > I seem to remember detection being made parallel for speed, as there > can be lots of drives. The Avago guys may be able to shed more light. > > Regards > Steve > > ----- Original Message ----- From: "Karl Denninger" > To: > Sent: Monday, September 29, 2014 9:04 PM > Subject: MPS > > > > Has anyone found a set of configuration settings for the mps driver (LSI > SAS series cards) that gets the following situation under control? > > I have a machine here with one of these cards and a SAS expander. The > expander has 16 ports, the card has 8 -- one connector attached to the > expander. So I have 20 potential drives associated with this adapter. > > The issue is that the driver makes utterly no sense when it comes to > assigning drive designations. In theory it should enumerate in series; > that is, target 0 on the card should be da0, target 1 da1, etc. This > assumes there are no gaps in the attached drives; if there are then > things may move around, which is why some people wire drives. > > Ok so far, but it doesn't behave that way! > > This is the excerpt of what it returns: > > root@Dbms-10:/boot # dmesg|grep mps > mps0: port 0xc000-0xc0ff mem > 0xfbb3c000-0xfbb3ffff,0xfbb40000-0xfbb7ffff irq 30 at device 0.0 on pci3 > mps0: Firmware: 19.00.00.00, Driver: 19.00.00.00-fbsd > mps0: IOCCapabilities: > 1285c > ses0 at mps0 bus 0 scbus0 target 8 lun 0 > da0 at mps0 bus 0 scbus0 target 0 lun 0 > da1 at mps0 bus 0 scbus0 target 1 lun 0 > da2 at mps0 bus 0 scbus0 target 2 lun 0 > da3 at mps0 bus 0 scbus0 target 3 lun 0 > *da4 at mps0 bus 0 scbus0 target 6 lun 0** > **da5 at mps0 bus 0 scbus0 target 7 lun 0* > > Those last two are the drives the card identifies as being on targets 0 > and 1 when looked at in the BIOS. The other four drives (0-3) are on > the SAS expander -- and there's a two drive "gap" in the targets > identified as well which has zippo for logic associated with it. > > Even more-oddly if I swap the plugs -- that is, plug the two boot disks > into the OTHER connector (putatively targets 4-7) and put the SAS > expander on the 0-3 port connector the BIOS *does* show the target shift > but the machine, when it boots, still places those two drives on targets > 6 and 7! > > There is nothing in /boot/loader.conf or /boot/device.hints that relates > to these devices at all. > > I would like to wire down the various ports so Drive Bay #x corresponds > to da[x] but how can you when you don't know what order they will come > up in predicated on either the physical port they're occupying or, for > that matter, what the card's BIOS shows them as? > > I looked in the driver's man page and saw nothing related to this; I get > around it by labeling the drives and then using "glabel list" to see > what da[x] number it grabbed if I need to pull a disk while the machine > is up, but this is a rather-unfriendly way to handle that. > > -- > Karl Denninger > karl@denninger.net > /The Market Ticker/ > Karl, This problem seems to crop up with some controllers, especially when port expanders are used. If at all possible, I really recommend labeling them and using the labels in lieu of device names. I stopped using device names some time ago just because of this. I do recommend using the labeling for the file system involved as opposed to glabel, if it has one. Certainly UFS does and I thought ZFS did, as well, but I am less sure of that as ZFS started to stabilize about the time I stopped dealing with big systems. I still find UFS quite adequate for my baby server and laptop. I do use glabel for swap. In any case, using labeling will give you stable names to put into things like your fstab and not make you worry about the actual device number. And, of course, talking to the manufacturer is also a good idea, espacially when they don't say "FreeBSD? We don't support that.". -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Tue Sep 30 00:24:46 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A0EA526A for ; Tue, 30 Sep 2014 00:24:46 +0000 (UTC) Received: from fs.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "NewFS.denninger.net", Issuer "NewFS.denninger.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 66203EAD for ; Tue, 30 Sep 2014 00:24:45 +0000 (UTC) Received: from [192.168.1.40] (localhost [127.0.0.1]) by fs.denninger.net (8.14.9/8.14.8) with ESMTP id s8U0OXQG099405 for ; Mon, 29 Sep 2014 19:24:33 -0500 (CDT) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (TLS/SSL) [192.168.1.40] by Spamblock-sys (LOCAL/AUTH); Mon Sep 29 19:24:33 2014 Message-ID: <5429F820.6040305@denninger.net> Date: Mon, 29 Sep 2014 19:24:00 -0500 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: MPS References: <5429BB41.8080609@denninger.net> <018BC41041EE4DF589EF5D834AD45BAD@multiplay.co.uk> In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040804000906030202030207" X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 00:24:46 -0000 This is a cryptographically signed message in MIME format. --------------ms040804000906030202030207 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 9/29/2014 7:17 PM, Kevin Oberman wrote: > On Mon, Sep 29, 2014 at 1:25 PM, Steven Hartland > wrote: > >> I seem to remember detection being made parallel for speed, as there >> can be lots of drives. The Avago guys may be able to shed more light. >> >> Regards >> Steve >> >> ----- Original Message ----- From: "Karl Denninger" >> To: >> Sent: Monday, September 29, 2014 9:04 PM >> Subject: MPS >> >> >> >> Has anyone found a set of configuration settings for the mps driver (L= SI >> SAS series cards) that gets the following situation under control? >> >> I have a machine here with one of these cards and a SAS expander. The= >> expander has 16 ports, the card has 8 -- one connector attached to the= >> expander. So I have 20 potential drives associated with this adapter.= >> >> The issue is that the driver makes utterly no sense when it comes to >> assigning drive designations. In theory it should enumerate in series= ; >> that is, target 0 on the card should be da0, target 1 da1, etc. This >> assumes there are no gaps in the attached drives; if there are then >> things may move around, which is why some people wire drives. >> >> Ok so far, but it doesn't behave that way! >> >> This is the excerpt of what it returns: >> >> root@Dbms-10:/boot # dmesg|grep mps >> mps0: port 0xc000-0xc0ff mem >> 0xfbb3c000-0xfbb3ffff,0xfbb40000-0xfbb7ffff irq 30 at device 0.0 on pc= i3 >> mps0: Firmware: 19.00.00.00, Driver: 19.00.00.00-fbsd >> mps0: IOCCapabilities: >> 1285c >> ses0 at mps0 bus 0 scbus0 target 8 lun 0 >> da0 at mps0 bus 0 scbus0 target 0 lun 0 >> da1 at mps0 bus 0 scbus0 target 1 lun 0 >> da2 at mps0 bus 0 scbus0 target 2 lun 0 >> da3 at mps0 bus 0 scbus0 target 3 lun 0 >> *da4 at mps0 bus 0 scbus0 target 6 lun 0** >> **da5 at mps0 bus 0 scbus0 target 7 lun 0* >> >> Those last two are the drives the card identifies as being on targets = 0 >> and 1 when looked at in the BIOS. The other four drives (0-3) are on >> the SAS expander -- and there's a two drive "gap" in the targets >> identified as well which has zippo for logic associated with it. >> >> Even more-oddly if I swap the plugs -- that is, plug the two boot disk= s >> into the OTHER connector (putatively targets 4-7) and put the SAS >> expander on the 0-3 port connector the BIOS *does* show the target shi= ft >> but the machine, when it boots, still places those two drives on targe= ts >> 6 and 7! >> >> There is nothing in /boot/loader.conf or /boot/device.hints that relat= es >> to these devices at all. >> >> I would like to wire down the various ports so Drive Bay #x correspond= s >> to da[x] but how can you when you don't know what order they will come= >> up in predicated on either the physical port they're occupying or, for= >> that matter, what the card's BIOS shows them as? >> >> I looked in the driver's man page and saw nothing related to this; I g= et >> around it by labeling the drives and then using "glabel list" to see >> what da[x] number it grabbed if I need to pull a disk while the machin= e >> is up, but this is a rather-unfriendly way to handle that. >> >> -- >> Karl Denninger >> karl@denninger.net >> /The Market Ticker/ >> > Karl, > > This problem seems to crop up with some controllers, especially when p= ort > expanders are used. > > If at all possible, I really recommend labeling them and using the labe= ls > in lieu of device names. I stopped using device names some time ago jus= t > because of this. I do recommend using the labeling for the file system > involved as opposed to glabel, if it has one. Certainly UFS does and I > thought ZFS did, as well, but I am less sure of that as ZFS started to > stabilize about the time I stopped dealing with big systems. I still fi= nd > UFS quite adequate for my baby server and laptop. I do use glabel for s= wap. > > In any case, using labeling will give you stable names to put into thin= gs > like your fstab and not make you worry about the actual device number. = And, > of course, talking to the manufacturer is also a good idea, espacially = when > they don't say "FreeBSD? We don't support that.". > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > Yeah, that's been my answer along with lettering the drive carriers but it pisses me off. Ah well if that's how it is then that's how it is. :-)= Glabel works fine across the board provided you put it on a slice rather than a disk, which I do anyway so as to maintain "nice-nice" with AF (4k) disks along with leaving a small amount of space at the end unallocated, so if by some chance a different brand replacement drive isn't quite the same number of sectors it can be dropped into the pool as a replacement. --=20 Karl Denninger karl@denninger.net /The Market Ticker/ --------------ms040804000906030202030207 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFTzCC BUswggQzoAMCAQICAQgwDQYJKoZIhvcNAQEFBQAwgZ0xCzAJBgNVBAYTAlVTMRAwDgYDVQQI EwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExLzAtBgkqhkiG9w0BCQEWIGN1c3Rv bWVyLXNlcnZpY2VAY3VkYXN5c3RlbXMubmV0MB4XDTEzMDgyNDE5MDM0NFoXDTE4MDgyMzE5 MDM0NFowWzELMAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExFzAVBgNVBAMTDkthcmwg RGVubmluZ2VyMSEwHwYJKoZIhvcNAQkBFhJrYXJsQGRlbm5pbmdlci5uZXQwggIiMA0GCSqG SIb3DQEBAQUAA4ICDwAwggIKAoICAQC5n2KBrBmG22nVntVdvgKCB9UcnapNThrW1L+dq6th d9l4mj+qYMUpJ+8I0rTbY1dn21IXQBoBQmy8t1doKwmTdQ59F0FwZEPt/fGbRgBKVt3Quf6W 6n7kRk9MG6gdD7V9vPpFV41e+5MWYtqGWY3ScDP8SyYLjL/Xgr+5KFKkDfuubK8DeNqdLniV jHo/vqmIgO+6NgzPGPgmbutzFQXlxUqjiNAAKzF2+Tkddi+WKABrcc/EqnBb0X8GdqcIamO5 SyVmuM+7Zdns7D9pcV16zMMQ8LfNFQCDvbCuuQKMDg2F22x5ekYXpwjqTyfjcHBkWC8vFNoY 5aFMdyiN/Kkz0/kduP2ekYOgkRqcShfLEcG9SQ4LQZgqjMpTjSOGzBr3tOvVn5LkSJSHW2Z8 Q0dxSkvFG2/lsOWFbwQeeZSaBi5vRZCYCOf5tRd1+E93FyQfpt4vsrXshIAk7IK7f0qXvxP4 GDli5PKIEubD2Bn+gp3vB/DkfKySh5NBHVB+OPCoXRUWBkQxme65wBO02OZZt0k8Iq0i4Rci WV6z+lQHqDKtaVGgMsHn6PoeYhjf5Al5SP+U3imTjF2aCca1iDB5JOccX04MNljvifXgcbJN nkMgrzmm1ZgJ1PLur/ADWPlnz45quOhHg1TfUCLfI/DzgG7Z6u+oy4siQuFr9QT0MQIDAQAB o4HWMIHTMAkGA1UdEwQCMAAwEQYJYIZIAYb4QgEBBAQDAgWgMAsGA1UdDwQEAwIF4DAsBglg hkgBhvhCAQ0EHxYdT3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFHw4 +LnuALyLA5Cgy7T5ZAX1WzKPMB8GA1UdIwQYMBaAFF3U3hpBZq40HB5VM7B44/gmXiI0MDgG CWCGSAGG+EIBAwQrFilodHRwczovL2N1ZGFzeXN0ZW1zLm5ldDoxMTQ0My9yZXZva2VkLmNy bDANBgkqhkiG9w0BAQUFAAOCAQEAZ0L4tQbBd0hd4wuw/YVqEBDDXJ54q2AoqQAmsOlnoxLO 31ehM/LvrTIP4yK2u1VmXtUumQ4Ao15JFM+xmwqtEGsh70RRrfVBAGd7KOZ3GB39FP2TgN/c L5fJKVxOqvEnW6cL9QtvUlcM3hXg8kDv60OB+LIcSE/P3/s+0tEpWPjxm3LHVE7JmPbZIcJ1 YMoZvHh0NSjY5D0HZlwtbDO7pDz9sZf1QEOgjH828fhtborkaHaUI46pmrMjiBnY6ujXMcWD pxtikki0zY22nrxfTs5xDWGxyrc/cmucjxClJF6+OYVUSaZhiiHfa9Pr+41okLgsRB0AmNwE f6ItY3TI8DGCBQowggUGAgEBMIGjMIGdMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHRmxvcmlk YTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExDMRwwGgYD VQQDExNDdWRhIFN5c3RlbXMgTExDIENBMS8wLQYJKoZIhvcNAQkBFiBjdXN0b21lci1zZXJ2 aWNlQGN1ZGFzeXN0ZW1zLm5ldAIBCDAJBgUrDgMCGgUAoIICOzAYBgkqhkiG9w0BCQMxCwYJ KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDA5MzAwMDI0MDBaMCMGCSqGSIb3DQEJBDEW BBR18phB1+c89/B+HhtpAiO++cKgYDBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjAL BglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFA MAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIG0BgkrBgEEAYI3EAQxgaYwgaMwgZ0xCzAJBgNV BAYTAlVTMRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoT EEN1ZGEgU3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExLzAtBgkq hkiG9w0BCQEWIGN1c3RvbWVyLXNlcnZpY2VAY3VkYXN5c3RlbXMubmV0AgEIMIG2BgsqhkiG 9w0BCRACCzGBpqCBozCBnTELMAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExEjAQBgNV BAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1zIExMQzEcMBoGA1UEAxMTQ3Vk YSBTeXN0ZW1zIExMQyBDQTEvMC0GCSqGSIb3DQEJARYgY3VzdG9tZXItc2VydmljZUBjdWRh c3lzdGVtcy5uZXQCAQgwDQYJKoZIhvcNAQEBBQAEggIAEaeYA8oFyq8UGPB1Fskf4eIrDA9U LP20qB8qq/05wYT36l63DIRHhhXKttOuJz67WPGEoHOyXdJV8kJqyQWh5EmoJByrPwizP8ln X24mFNEbklamnCSBwGtTRPdfpxn+uIev5mshiHBEv2rblq/nqZm76pt8s8c2aI0dz0qNmPBR +6cu+jte7pKRRV2hhs63zgCh5zlCep5F46SOtkfvb+6P1ZbVfZBhOadAlqHKvP+NHocW97bH aLB4E4ngzRdAYSLKJuD/KO5TSZS18QhAHN9ny7i9k8gngCXmx2BBftj5SKemoLEXATsWQzFK EqYwyUxnSCs91b/Bk0mInJI3nCQD5PpcxHXunpyVgjk5MWhx6ot04ezEFa5XYaA9yRLcn1Fp xl3AEFXV80/Wb7osffYOjpmJ0ehWvI26oODwEzSXdMDn+PI4ILAymQOcsS0YUWjGHnqBDELN AIes0yjG7IojbZK0f8zEBikpGL3jcTOLolFi8TRJNIn2jM2oXk7QNYhAXo5S/Ox4p98nsx+B x9u2u3SFmRfjyXd4Tx8oeJ5EIY+8quSwZm/WN6GmJmIw2UR+LHUp+VzbAerGSvfZz2UidguV 3XxCv3IwVFpB9gwBbNGVIvvAT5B1Ls2mGjbMY5AC/5KYUVvgozYfmoXzoxjQmcNXh3P22LcJ s7+l8X0AAAAAAAA= --------------ms040804000906030202030207-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 30 00:41:33 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EEE776DE for ; Tue, 30 Sep 2014 00:41:33 +0000 (UTC) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id B3B0DFC0 for ; Tue, 30 Sep 2014 00:41:33 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id C749120E7088B; Tue, 30 Sep 2014 00:41:31 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.multiplay.co.uk X-Spam-Level: ** X-Spam-Status: No, score=2.2 required=8.0 tests=AWL,BAYES_00,DOS_OE_TO_MX, FSL_HELO_NON_FQDN_1,RDNS_DYNAMIC,STOX_REPLY_TYPE autolearn=no version=3.3.1 Received: from r2d2 (82-69-141-170.dsl.in-addr.zen.co.uk [82.69.141.170]) by smtp1.multiplay.co.uk (Postfix) with ESMTPS id 48C8E20E70885; Tue, 30 Sep 2014 00:41:30 +0000 (UTC) Message-ID: From: "Steven Hartland" To: "Karl Denninger" , References: <5429BB41.8080609@denninger.net> <018BC41041EE4DF589EF5D834AD45BAD@multiplay.co.uk> <5429F820.6040305@denninger.net> Subject: Re: MPS Date: Tue, 30 Sep 2014 01:41:26 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 00:41:34 -0000 ----- Original Message ----- From: "Karl Denninger" > Glabel works fine across the board provided you put it on a slice rather > than a disk, which I do anyway so as to maintain "nice-nice" with AF > (4k) disks along with leaving a small amount of space at the end > unallocated, so if by some chance a different brand replacement drive > isn't quite the same number of sectors it can be dropped into the pool > as a replacement. You can also use gpart add with a -l